Full-Stack Engineer
How do you keep product managers and designers informed when a feature is taking longer than expected?
What the interviewer is looking for
- This question tests communication. Keeps product and design partners informed early, explains trade-offs plainly and flags risks before they become surprises.
- What to bring out: Flagging early, explaining why in plain terms, offering options like reduced scope, and agreeing a new plan.
- Expect a follow-up like: How do you avoid the same surprise next time?
Another way it may be asked: You're a week into a two-week task and realise it'll take four. What do you do, and when?
A structure to follow: STAR, with the weight on Action and Result
- Step 1
Situation
One or two sentences: where, when and what was at stake. Pick a real example you were close to.
- Step 2
Task
What you personally were responsible for. Say "I", not only "we", so the communication you showed is visible.
- Step 3
Action
The two or three things you did and why you chose them over the alternatives. This should be about half your answer.
- Step 4
Result
What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.
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
- Describing what the team did without saying what you did.
- Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
- Ending on the action and skipping the result and what you learned.
How to practise it
Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.
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?
- 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?