How to prepare for interview questions

The two ways people prep wrong

The first mistake is studying the wrong questions. A list of “top 50 interview questions” is generic by design, so you spend hours on prompts that don't match your role, your level, or this company's loop — and you miss the ones you'll actually face. The second mistake is rehearsing in your head. You read a question, think “yeah, I'd talk about the migration project,” and move on, having never said a single sentence out loud. Then in the room, the words don't come out the way they did in your head, and you ramble or freeze. Fixing both is most of the battle.

Predict the questions you'll actually get

You can't know the exact wording, but you can predict the shape with real accuracy, because interviews follow the loop. Start from the job description — it tells you what they're prioritising right now — and map it onto the typical rounds for your role and level. Our 2026 Tech Interview Report and each role guide lay out that loop shape and the themes each round tests, for 28 roles.

Then prioritise. The questions most worth your time are the ones aimed at the gap between your CV and the posting — if the role wants distributed-systems depth and yours is thin, that's the round they'll drill, so prep it first. Knowing which questions are coming, and which ones are aimed at you, beats grinding a generic list every time — it's the same logic as figuring out whether you're a fit and where your gaps are before you apply.

Build reusable stories, not scripts

Don't memorise answers — memorised answers sound memorised, and they shatter the moment a question is phrased differently than you practised. Build raw material instead: five or six real stories from your career covering impact, conflict, a failure you learned from, leadership, and your strongest technical work. Structure each one — the STAR method is the standard — so you can bend any of them to whatever they actually ask. With a good set of stories, you're never answering cold; you're choosing which one fits and adapting it on the spot.

Practise out loud — knowing isn't saying

Here's the one that costs the most offers, because it feels like the optional step. Knowing an answer and being able to say it under pressure are different skills, and the interview only grades the second one. The fix is uncomfortable and simple: say your answers out loud, ideally recorded, so you actually hear where you wander, trail off, or never quite land the point. Going quiet or rambling is a top reason strong candidates get rejected — and it's entirely a practice problem, not a knowledge one.

Get feedback that's tied to the bar

Practising out loud to yourself helps; getting graded helps more. The catch is that a friend can tell you that you sounded nervous, but usually can't tell you whether your answer clears the bar for a Staff Engineer versus a Senior one — and that calibration is the whole game, as what gets you the offer spells out. You want feedback that knows the level you're being assessed against, not just whether you seemed confident.

The fast way: predicted questions you can practise on

This is the core of what Calibrd does. Paste a real job description and it predicts the questions for that company and level, round by round — each round its own card with the focus, prep tips, and the questions you're likely to get, plus example angles pulled from your own CV for behavioural and motivation prompts. Then you practise each one: type or speak your answer (recording transcribes free via Whisper, in 99+ languages), and one click calibrates the draft — it keeps your wording but sharpens the structure to what the level expects. It's the whole loop in one place: the right questions, your real answer, and feedback tied to the bar.

So what do you actually do

1. Predict the questions from the JD and your role's loop — skip the generic list.
2. Prep the rounds aimed at your gaps first; they're the ones you're most likely to be drilled on.
3. Build five or six structured, reusable stories instead of memorising scripted answers.
4. Say every answer out loud and record it — close the gap between knowing and saying.
5. Get feedback calibrated to the level, not just “you sounded fine.”