"Tell Me About a Project": How to Survive the Follow-Up Questions

"Walk me through a project you are proud of" sounds like the easiest question in an interview. It is often the hardest, because the interviewer is not really asking about the project. They are testing whether you understood it, made decisions in it and can explain those decisions under pressure.

What the interviewer is listening for

• Ownership: which parts you personally designed, built or decided.
• Judgement: the alternatives you considered and why you rejected them.
• Depth: whether you can go one or two levels deeper on any part.
• Outcome: how you know it worked.

The follow-up questions you should expect

After your first two minutes, most interviewers dig in with questions like these:

• "What was the hardest technical or analytical decision, and what were the options?"
• "What would break first if usage grew ten times?"
• "How did you test it? How did you know the numbers were right?"
• "What did you get wrong, and how did you find out?"
• "If you started again today, what would you change?"
• "Who disagreed with you, and how did you resolve it?"

If you cannot answer the follow-ups, the interviewer will usually assume your role was smaller than your resume suggests, even if it was not.

A structure for the first two minutes

1. The problem in one sentence: who had it and why it mattered.
2. Your role: "I owned the data pipeline and the alerting; two other engineers built the UI."
3. One key decision: the option you chose, the alternative and the reason.
4. The result: a number if possible, and one thing you would do differently.

Then stop and let the interviewer choose where to go deeper. A short, structured answer invites good follow-ups. A ten-minute monologue invites interruptions.

How to practise

Write down your project in the structure above, then ask someone to question you for ten minutes without letting you change the subject. Note every question where you said "I'm not sure" or "the team handled that". Those are the parts to prepare.

This is the exact situation MockInterview was built for. The AI interviewer reads your resume and the job description, chooses a real project and keeps asking follow-up questions on vague answers. The report then quotes your own words, so you can see which answers held up. You can try three free questions first.

For role-specific examples, see the deep-dive scenarios for software engineers, frontend engineers, backend engineers, data analysts and product managers. Engineers can also read software engineer interview questions.