INTERVIEW ROUNDS
Interview rounds, and what each one is really deciding
Nobody is preparing "for an interview" in the abstract. You are preparing for a phone screen tomorrow afternoon, a technical round on Thursday, or a final panel next week. Each has a different person, a different length and a different decision — and the same stories have to be told differently in each.
| Round | Who runs it | Typical length | What decides it | What to bring |
|---|---|---|---|---|
| Phone screen | Recruiter or hiring manager | 15–30 min | Relevance and fit | 90-second story, 3 questions |
| Technical round | Engineer or tech lead | 45–60 min | Can you do the work | One project with numbers, one design |
| Hiring manager | Your future manager | 30–45 min | Judgement and ownership | A tradeoff, a disagreement, a setback |
| Final round | Skip-level or panel | 45–60 min | Consistency and seniority | The same stories, tighter |
Lengths are the common ranges. MockInterview simulates the lower end so you practise under more pressure than the real call.
Phone screen
Run by: A recruiter or hiring manager · Length: 15 minutes simulated · Interviewer style: Hiring manager
They are deciding: Whether you are worth a technical slot.
What gets asked
- Walk me through your background in two minutes.
- Why this role, and why now?
- What is your notice period, location and salary expectation?
- One question that checks you read the job description.
The mistake that costs this round
Reciting the whole resume. The screen is 15 minutes and the interviewer is filtering, not evaluating depth — a 90-second story with a clear target role beats a chronological tour.
How to rehearse it
Practise a short introduction and two role fundamentals questions. Keep the closing questions about the team and the process.
Technical round
Run by: The engineer you would work with · Length: 30 minutes simulated · Interviewer style: Technical lead
They are deciding: Whether you can do the work without help.
What gets asked
- What exactly did you own in that project, and what did you not own?
- Why that design and not the obvious alternative?
- What broke in production, and how did you find out?
- Design this component, or write the query/function for this task.
The mistake that costs this round
Describing the team outcome instead of your own mechanism. Engineers will keep asking "but what did you build" until they hear a concrete decision, a tradeoff and a measurement.
How to rehearse it
Pick one project, prepare the mechanism, the rejected alternative and the number that changed. Include one design task and one code/pseudocode task.
Hiring manager
Run by: The person you would report to · Length: 30 minutes simulated · Interviewer style: Hiring manager
They are deciding: Whether they want you on their team for the next year.
What gets asked
- Tell me about a decision you made with incomplete information.
- Who disagreed with you, and what did you do?
- What would you do in your first 90 days here?
- How do you use AI in this role, and where do you not trust it?
The mistake that costs this round
Answering with technology when the question is about judgement. This round is about scope, ownership and how you behave when the answer is not obvious.
How to rehearse it
Prepare one story about a tradeoff you argued for and one about a setback. Practise explaining both to someone who is not an engineer.
Final round
Run by: A skip-level, a panel, or both · Length: 30 minutes simulated · Interviewer style: Pressure interview
They are deciding: Whether they are confident enough to defend the offer.
What gets asked
- The same stories again, shorter, with harder follow-ups.
- A counter-example to your last answer.
- A sudden change in requirements.
- Why should we choose you over someone with more experience?
The mistake that costs this round
New stories. By the final round the panel is checking consistency; a fresh anecdote that contradicts an earlier one costs more than a familiar story told tighter.
How to rehearse it
Run the full interview under a pressure interviewer, then repeat the same material until each story is under two minutes.
How to use the four rounds together
Prepare the material once, then cut it to length. The project story that fills eight minutes on a technical round has to become ninety seconds for a phone screen, and the tradeoff you explained to an engineer has to become a business consequence for a hiring manager. Candidates who fail late rounds usually have plenty of material and no shorter version of it.
If you only have one evening before a phone screen, rehearse the introduction and the two role questions, not the project deep dive. If you have one evening before a technical round, rehearse the mechanism and the number, not the introduction.