A customer says the product is slow but gives you no other details. What would you ask them first?

What the interviewer is looking for

• This question tests troubleshooting & root cause. Gathers facts methodically, reproduces issues, narrows down possibilities step by step, and finds the real cause rather than a workaround.
• Strong answers: Asks what exactly is slow, since when, for whom, on which device or network, any recent changes, and whether it can be reproduced.
• Likely follow-up: How would you tell whether the problem is on their side or ours?

Another way it may be asked: Someone emails support saying everything is slow today. What questions do you ask to start figuring it out?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• Walk me through a tricky technical issue you solved recently, step by step.
• In simple terms, what happens when you type a web address into a browser and the page loads?
• A frustrated customer tells you this is the third time they have contacted support about the same problem. How do you start the conversation?
• How do you use logs or monitoring tools to narrow down a problem? Give me a real example.
• Tell me about a time you wrote a script or small tool to make your support work faster.

Browse all questions