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?

What the interviewer is looking for

• This question tests end-to-end feature delivery. Breaks features into shippable slices, makes pragmatic decisions at each layer, and owns the result through launch.
• Strong answers: Clear decisions at each layer with reasons, how they sliced the work, testing, rollout and what they learned after launch.
• Likely follow-up: What would you build differently now?

Another way it may be asked: Pick something you shipped that touched every layer. Walk me through how you built it.

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

• You're asked to deliver a large feature in six weeks with a small team. How would you break it down and decide what ships first?
• 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?
• 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?

Browse all questions