Not every interview round is testing the same thing, and preparing the same generic answers for all of them is a common way to underperform in at least one. An HR screener isn't judging your technical depth. A technical interviewer isn't scoring your culture fit. Knowing what each round actually assesses changes how you should prepare for it.

Here's a breakdown of the four round types you're most likely to hit in a modern interview process, sample questions for each, and what the interviewer is really listening for underneath the question.

HR Screening

The first filter. Usually 20-30 minutes, usually not with the hiring manager. The goal is basic fit: are you qualified enough to be worth the hiring manager's time, are your expectations aligned with the role, and are you actually interested or just applying broadly.

Sample Questions

"Walk me through your background." · "Why are you looking to leave your current role?" · "Why this company specifically?" · "What are your salary expectations?" · "What's your notice period?"

What's actually being assessed: motivation clarity and role fit. A candidate who can't give a specific, credible reason for wanting this particular role at this particular company reads as someone applying everywhere, which is a real red flag at this stage regardless of how strong their CV is.

Behavioural

Built around the idea that past behaviour predicts future behaviour. Instead of asking what you would do, these questions ask what you actually did, in a specific real situation.

Sample Questions

"Tell me about a time you disagreed with a decision your manager made." · "Describe a project that failed. What happened?" · "Tell me about a time you had to influence someone without formal authority." · "Give an example of when you had to manage conflicting priorities."

What's actually being assessed: STAR completeness, whether your answer has a real Situation, Task, Action, and Result, not a vague generality. "I'm good at handling conflict" isn't an answer. A specific disagreement, what you actually did about it, and what happened afterward is.

Practise these out loud, not silently
An AI mock interview asks these questions in your voice, drills into vague answers the way a real interviewer would, and scores your answers by round type.
Try a Mock Interview Free

Technical

Role-specific, and the format varies a lot: live coding, system design, case studies, whiteboard problems, or straightforward knowledge questions depending on the role and seniority.

Sample Questions

"How would you design [a system relevant to the role]?" · "Walk me through how you'd debug [a specific type of issue]." · "What trade-offs would you consider between [two approaches]?" · "Explain [a core concept] to me as if I weren't technical."

What's actually being assessed: technical knowledge and problem-solving approach, not just the final answer. Most interviewers are watching how you think, whether you clarify the problem before diving in, whether you consider edge cases, whether you can explain your reasoning as you go. Silently arriving at the right answer often scores worse than talking through a good approach that gets close.

Cultural Fit

Often the last round, sometimes with a future teammate or a senior leader outside your direct reporting line. Less about your skills, more about how you work and whether your values line up with how the team actually operates day to day.

Sample Questions

"How would your last team describe working with you?" · "What kind of work environment do you do your best work in?" · "Tell me about a time you had to adapt to a very different way of working." · "What matters most to you in a team?"

What's actually being assessed: values alignment. There's rarely a single "right" answer here, the interviewer is checking whether your working style and priorities are a realistic match for how the team actually functions, not testing you against a fixed rubric.

How to practise for each one

Reading these sample questions helps you know what's coming. It doesn't tell you whether your actual answer, spoken out loud under a bit of time pressure, actually lands. That gap is why rehearsing out loud matters more than most people give it credit for, and why a tool that questions you, listens, and pushes back on vague answers gets you further than a static list ever will.

The most useful version of this practice mirrors the real thing as closely as possible: pick the round type you're actually about to face, answer out loud instead of typing, and get pushed on anything that sounds thin, the same way a real interviewer would push before moving on.

Match questions to the round you're actually facing
Choose HR Screening, Behavioural, Technical, or Cultural Fit and get questions grounded in your real CV and the job description, with a scored report at the end.
Try a Mock Interview Free
Check your CV against the job description first
Free AI-powered CV Match Check scores your CV against any job description: missing keywords, weak impact metrics, and ATS parsing risk, before you even apply.
Check My CV Free

Frequently asked questions

What's the difference between an HR Screening round and a Behavioural round?
HR Screening checks basic fit and motivation: why this role, why this company, salary expectations, notice period. Behavioural rounds go deeper into how you actually operate, using past-situation questions to judge how you handle conflict, pressure, leadership, and failure.
How many rounds should I expect for one job?
It varies by company and seniority, but a common pattern is an HR Screening call, one or two Technical or Behavioural rounds, and a final Cultural Fit or hiring-manager round. Smaller companies sometimes compress this into one or two conversations.
Can I practise questions for a specific round type before the real interview?
Yes. An AI mock interview tool lets you select the round type you're about to face, HR Screening, Behavioural, Technical, or Cultural Fit, and generates questions and a scored report specific to that round, rather than a generic mixed set.
Do Technical round questions test only technical knowledge?
No. Most technical interviewers are watching your problem-solving approach as much as the final answer: how you break the problem down, what questions you ask, whether you think out loud. A correct answer reached silently often scores worse than a well-reasoned approach that gets close.