Last weekend, I went through Reddit posts from people who were actively looking for work. One pattern kept appearing: candidates could handle the parts of the interview process they had prepared for, then struggle when the conversation moved to a different kind of question.
One candidate had reached the final round with the CTO of a startup after spending days on preparation. They researched the company, collected past interview questions, and practised LeetCode.
The earlier rounds went well. The questions were technical and connected to work they had done before.
Then the CTO asked how one of their changes had contributed to the company's success.
The candidate got stuck and started rambling.
I wanted to understand why. This wasn't someone who hadn't prepared. They'd passed three rounds of actual technical scrutiny. So why did one question about a past project undo all of it?
Different Interview Rounds Assess Different Things
A common interview process for a technical role has several parts.
The first is often a 30-minute screening call with HR, recruiting, or talent acquisition. The company is usually checking practical fit: location, salary expectations, availability, interest in the role, and whether the resume broadly matches what they need.
The next stage is often a 30- to 60-minute conversation with the hiring manager. For an engineering role, that may be an engineering manager, director, head of engineering, or CTO at a smaller company. This conversation goes deeper into previous work, team fit, and the problems the person would handle after joining.
Then comes an in-depth stage that tests expertise.
For engineering roles, this may be a live coding challenge, system-design interview, debugging exercise, or take-home task. For product, design, sales, and other roles, it may be a case study or presentation prepared in advance.
A final stage often changes again. Candidates may speak with potential teammates, adjacent functions, senior leaders, or people with veto power over the hire.
The process varies by company and role. Some companies combine stages into one day. Some add more interviews. The pattern still matters because a candidate is not being asked the same question in every round.
A technical exercise asks whether someone can do the work.
A hiring-manager conversation asks whether their experience fits this team.
A final-stage interviewer may ask whether the person understands the business around their work, can explain decisions to people outside their function, and can show judgment when the question does not have an obvious answer.
The CTO's question belonged in that final category.
“How did this change contribute to the company's success?” asks more than whether the candidate built the change. It asks whether they understand what changed for the company, which result mattered, and what part of the outcome they can credibly claim.
That is why someone can perform well in earlier technical rounds and still struggle in a final interview.
Why A Question List Only Gets You So Far
Most interview preparation starts with the same material.
Candidates search the company, search the role, and find articles with titles such as “Top 50 behavioural interview questions.” They prepare a few stories that can be reused across different interviews.
This is useful. A candidate should know their resume, their strongest projects, and the results they are proud of.
But a prepared story is only one view of an experience.
A product designer may be able to explain why a redesign was easier for users to navigate. A final-stage interviewer may ask whether the redesign changed conversion, activation, retention, support tickets, or another business measure.
An engineer may be able to explain how a system was built. A senior leader may ask why that approach was chosen, which tradeoff the team accepted, who disagreed, and what happened after the launch.
The candidate needs to find the relevant example, explain the context, identify their own contribution, answer the follow-up, and give a result.
A prepared paragraph does not make those decisions for them.
It only gives them one route through one version of the story.
What Candidates Actually Need To Practise
Interview practice should include more than a list of expected questions.
It should include questions that approach the same experience from different angles. It should include follow-ups about numbers, tradeoffs, disagreement, failure, and business impact. It should include the moment where the exact metric is unavailable and the candidate has to explain how the result was measured instead.
That kind of practice teaches a more useful habit. The candidate stops trying to remember a perfect script and starts learning how to talk through their own work.
What withLyra Is Built To Practise
withLyra starts with the role being targeted.
The user chooses the interview type and interviewer. Questions can come from different angles instead of repeating one familiar list. The interviewer's voice and pace are designed to feel like a conversation, including pauses while the user speaks.
The session then ends with a review of where the user was clear and where the thread was lost.
Find out which questions make you blank.
Don't wait for a real interview. Practise until explaining your own work feels normal under pressure.
