You memorised the answer. What happens when they ask why?
Your answer has a strong opening. A neat STAR structure. An ending you've practised enough to say without thinking.
Then the interviewer asks: “Why that approach?”
And you start the story again.
That is the follow-up gap: the distance between delivering a prepared explanation and answering a new question about it. You can know the work well and still struggle to retrieve the relevant detail when the conversation changes direction.
The fix is not necessarily a longer script. Practise answering a follow-up as a small, separate task: identify what is being asked, answer that point directly, support it with a fact and stop when the question is answered.
Your story ended. Their question didn't.
An initial interview question can give you considerable freedom to choose an example. A follow-up narrows that freedom.
“What did you do?” asks for your action. “Why that option?” asks for your reasoning. “How do you know?” asks for evidence. Those are not invitations to repeat the same paragraph with more enthusiasm.
This is also why a follow-up is not automatically a bad sign. It can explore something interesting, resolve an ambiguity or ask for information you could not reasonably include in a short opening. Treat the question as a request, not a verdict.
One project. Three different directions.
Consider this fictional example:
“I proposed testing a new support-routing process with one team before rolling it out more widely. We found an escalation problem during the pilot and fixed it before expansion.”
Now take three possible follow-ups.
“Why didn't you roll it out to everyone?”
The missing information is the choice. A direct response might be:
“The broader rollout would have moved faster, but we hadn't tested how urgent cases crossed team boundaries. I recommended the smaller pilot so we could check that handoff before exposing every team to it.”
“What made you think the escalation process was the problem?”
Now the missing information is evidence:
“We reviewed the delayed cases. The common point was a transfer between teams with no named owner. That gave us a specific handoff to investigate; it didn't explain every delay.”
“What would you do differently?”
This asks for learning, not a defence of the original decision:
“I'd include an urgent cross-team case in the pilot checklist from the start. Our original checklist covered ordinary routing but missed that exception.”
The project has not changed. The information the listener needs has. Practising that switch is the work.
Build a small follow-up set, not another speech
Choose one example you genuinely know. On five separate cards or notes, write:
- What did you personally decide or recommend?
- Why did you choose that option over the alternative?
- What downside did you accept?
- What evidence supports the outcome?
- What would you change next time?
Give your opening answer aloud, then pick a question without choosing your favourite. Answer it without restarting the introduction. Two or three sentences are a useful starting constraint for this drill, not a rule for every real interview.
Listen for the first sentence that actually answers the question. If it comes after a long recap, try moving it to the front. Add only the context required to understand it.
Now change the question. Does the response change with it, or do you keep returning to the sentence you rehearsed?
When you get stuck, choose the right repair
Not every pause means the same thing. Before trying to sound more confident, identify what is missing.
You understood the question but need a moment. Pause. “Let me think about the trade-off” is a perfectly usable bridge into an answer. There is no need to fill every second with background.
You are unsure what the interviewer means. Ask a focused clarification: “Do you mean why we chose the pilot, or why I recommended that team?” A clarification is more useful than a polished answer to the wrong question.
You cannot remember an exact fact. State the limit. “I don't remember the exact volume; what I can explain is how we checked the handoff.” Do not invent a number to make the ending sound complete.
You did not own that decision. Say who did and explain your contribution. “My manager approved the rollout; I recommended the pilot scope and checked the delayed cases.” Precision is not an admission of failure.
These repairs keep the conversation moving without pretending that every detail is available on demand.
Test flexibility, not just fluency
On your next attempt, use the same project but change the order of the follow-ups. Then try the drill with a second project.
Keep a simple note: What was asked? Did my first sentence address it? Which fact supported the answer? What do I still need to check?
The goal is not to eliminate follow-ups. It is to make them part of your preparation rather than an interruption to it.
This is where Loopiva fits: an AI interviewer can follow up on your answers, and the completed-session evaluation and coaching give you a way to work on gaps before another attempt. It is practice for a changing conversation, not a prediction of what your next employer will ask.
Your opening answer does not have to contain everything. Your preparation should give you somewhere to go when the next question arrives.