Mock Interview Guide — Practise Every Round
Knowing the answer and saying it well under time pressure are different skills. This guide explains the common interview rounds and gives you a practice routine for each one.
The usual interview loop
Processes vary by company, but most technical hiring uses some mix of these rounds:
- Recruiter screen — background, motivation, notice period, and expectations.
- Online assessment or take-home — timed coding or SQL problems, or a small project.
- Technical rounds — coding, SQL, or domain questions with an engineer.
- System or solution design — design a service, pipeline, or ML system out loud.
- Project deep dive — walk through something you built and defend your choices.
- Behavioral / hiring manager — how you work with people, handle failure, and make decisions.
Coding and SQL rounds
- Learn the patterns, not individual problems: DSA interview patterns and the top 50 SQL questions.
- Think out loud. State your approach and its complexity before you write code.
- Start with a simple correct solution, then optimise. Test with an edge case before saying “done”.
- Practise with a timer: 25–35 minutes per medium problem.
Design rounds
Use the same skeleton every time so you never freeze:
- Clarify requirements and scale (users, data volume, latency).
- Sketch the high-level components and the data flow.
- Go deep on one or two parts: storage, scaling, failure handling.
- Discuss trade-offs, monitoring, and what you would change at 10× scale.
Practise with the system design interview framework.
Project deep dive
Prepare a three-minute story for your flagship project:
- Problem — who had it and why it mattered.
- Architecture — the components and why you chose them.
- Hardest part — a real bug or design problem and how you solved it.
- Results — numbers you can explain.
- Next — what you would improve with more time.
Behavioral answers with STAR
Structure every story as Situation, Task, Action, Result, and spend most of the time on Action — what you did. Prepare five to six stories you can adapt:
- A time something you built failed, and what you changed.
- A disagreement with a teammate or manager and how it was resolved.
- A time you learned a new tool or topic quickly.
- A time you improved something nobody asked you to.
- A tight deadline and how you prioritised.
- Why this role and this company — specific, not generic.
How to run a mock interview
- Find a partner — a classmate, colleague, or study group. Take turns as interviewer and candidate.
- Simulate the real thing — camera on, timer running, no notes.
- Record yourself — watching the playback shows filler words and unclear explanations fast.
- Score each round — problem solving, communication, correctness, and how you handled hints.
- Practise solo — answer a question out loud from any interview prep lesson, then compare with the written answer.
On the day
- Test your camera, microphone, and coding environment the day before.
- Ask clarifying questions before solving — it is expected, not a weakness.
- If you are stuck, say what you are thinking. Interviewers can only help if they can follow you.
- Prepare two or three thoughtful questions for the end of each round.
Next steps
Pick your role on the career prep hub to find its interview lessons, then read the job search and offers guide.
Discussion
0Have a better approach? Found something outdated? Share it — your knowledge helps everyone learning here.
