A user reports that saving their profile sometimes fails with no error message. How would you figure out whether it's a frontend or backend problem?

What the interviewer is looking for

• This question tests testing & debugging across the stack. Narrows problems layer by layer using network tools, logs and tests, and writes tests at the right level.
• Strong answers: Checking browser network requests and console, server logs and error tracking, reproducing with the user's data, narrowing layer by layer, and fixing the missing error message too.
• Likely follow-up: What test would you add once you find the cause?

Another way it may be asked: Some users click save and nothing happens. How do you work out where the problem actually is?

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 how you would build a page that shows a list of items from a server, including what the user sees while it loads.
• What happens, step by step, when a user submits a sign-up form on a website, from the browser all the way to the database?
• If you were storing users, their posts and comments on those posts, how would you set up the tables and relationships?
• Tell me about a feature you built from the database all the way to the user interface. What decisions did you make along the way?
• How do your changes usually get from your machine to production, and what checks happen along the way?

Browse all questions