The short answer
A behavioural interview asks what you have done and scores the evidence. A technical interview asks you to do something now and scores the process as much as the answer. They need different preparation: a story bank for one, deliberate practice and thinking aloud for the other. Most real processes mix both.
What matters most
- Behavioural rounds score evidence of past behaviour; technical rounds score current process.
- Thinking aloud is not optional in a technical interview β a silent correct answer scores worse.
- Take-home tasks should be scoped, timeboxed, and accompanied by a note on your decisions.
- Most loops are mixed, and the behavioural round is often the one that actually decides it.
The two formats, side by side
| Behavioural | Technical or practical | |
|---|---|---|
| The question sounds like | "Tell me about a time youβ¦" | "How would youβ¦", "here is a problem", "walk me through this" |
| What is being assessed | Evidence of how you have behaved before | Whether you can do the work, and how you approach it |
| Preparation that works | A bank of six to eight developed stories | Deliberate practice on realistic problems, out loud |
| The main failure | Vagueness β no specifics, no result, everything in "we" | Silence β solving in your head and presenting only the answer |
| Recovering from a blank | Ask for a moment, or offer a related example and say it is adjacent | Say what you do know, state your assumption, and ask for a hint |
| Who usually runs it | Hiring manager, HR, panel | A practitioner who does the job |
| What a good answer feels like | A short, specific story with a clear ending | A visible chain of reasoning, including the wrong turns |
Almost every real process is a mixture. A typical loop runs a recruiter screen, a technical or practical assessment, and one or two behavioural conversations, in that order. It is worth noticing that the technical round is more often the filter and the behavioural round more often the decision: candidates who clear the technical bar are then separated on the evidential questions.
Preparing for behavioural rounds
The whole method is covered in our STAR method guide, and the short version is: build stories rather than answers, spend your speaking time on what you personally did, and finish on a result. The specific thing worth adding here is how to work out which competencies you will be asked about, because behavioural question sets are rarely improvised.
- Read the posting for behavioural language. "Influences across teams", "works with ambiguity", "manages competing priorities" are competencies, and competencies become questions. Our job description decoder pulls them out of a posting for you.
- Check the company's published values. Some employers interview directly against a public list of principles, and where that is true the mapping from values to questions is almost one-to-one.
- Ask what the round covers. Recruiters will frequently tell you the competencies, and in structured public-sector processes they sometimes send the framework in advance.
- Prepare for the negative pair. Every competency has a failure question attached β a time you influenced someone, and a time you failed to. The second is asked more often than candidates expect.
Preparing for technical and practical rounds
"Technical" covers far more than coding. A financial modelling exercise, a clinical scenario, a teaching demonstration, an in-tray test, a design critique, a mock client call and a live troubleshooting session are all the same category: you are asked to perform the work rather than describe it.
The single highest-return change. Solving silently and narrating are different skills, and the interview scores the second. Rehearse against a friend, a rubber duck or a recording.
Work problems slightly harder than the role requires, then stop. Grinding puzzle problems far above the job's level is a common and poorly targeted use of preparation time.
You will be asked about what is on your resume. Anything you listed and have not touched in two years is a liability β either refresh it or take it off.
A shared editor, a whiteboard, a screen-share with someone watching. All of them are slower than working alone, and the first time should not be the assessed time.
Two or three questions you always ask before starting: what the constraints are, what the input looks like, what "done" means. Assessors mark this.
Decide in advance what you will say when you have nothing. Having a sentence ready is the difference between a recoverable pause and a spiral.
Thinking aloud, specifically
This is the instruction candidates hear most and follow least. The assessor cannot mark what they cannot see, and in most technical rubrics the reasoning carries more weight than the final answer. Narrate the shape of your thinking: what you understand the problem to be, what approach you are considering and why, what you are ruling out, what you would check if you had more time. When you make an assumption, say it out loud β an assumption stated is a decision, and an assumption unstated is a mistake.
When you get stuck, say so and say what you do know. "I am not certain of the right structure here, so I am going to write the brute-force version first and then look at where it repeats work" is a strong sentence. Sitting silently for four minutes is not, and neither is guessing confidently. Assessors are far more forgiving of a wrong turn taken visibly than of a right answer that appeared from nowhere.
Take-home tasks
The most abused format in hiring, and the one where candidates most need a boundary. A reasonable take-home is scoped to a few hours, clearly briefed, and used as the basis for a follow-up discussion. An unreasonable one is an unpaid piece of real work, and you are entitled to ask which you have been sent.
- Ask how long it is expected to take, and whether there is a deadline. Both are fair questions and the answers tell you a lot about the employer.
- Timebox to roughly what they said, then stop. Spending fifteen hours on a four-hour brief sets a precedent and rarely scores proportionally better.
- Answer the brief literally before doing anything clever. Unrequested extras do not compensate for a missing requirement.
- Write a short note with it: your assumptions, what you would have done with more time, what you deliberately left out. Assessors consistently value this, and it converts a shortcut into a stated decision.
- Make it easy to run and easy to read. Whatever the discipline, a reviewer who has to work to open your submission is already annoyed.
- If the task is clearly production work for their business, or is very large with no discussion attached, it is legitimate to ask about scope or to decline. Some employers pay for substantial take-homes, and asking is not rude.
Assessments, tests and your rights
Some processes add standardised elements: aptitude tests, personality inventories, situational judgement tests, work sample tests, assessment centres. These are selection procedures in the legal sense, and in the US they sit under the EEOC's guidance on employment tests and selection procedures, which sets out the requirement that a test be job-related and not operate to exclude protected groups without justification. Other countries regulate this differently, so check the relevant authority where you are applying rather than assuming.
Two practical points follow. If a format is a barrier because of a disability or a health condition, you can ask for an adjustment β extra time, an alternative format, assistive technology β and in many jurisdictions the employer has a duty to consider it; the EEOC's disability discrimination pages set out the US position. And if a technical exercise strays into questions about your health, your family or your age rather than the work, that is a separate problem covered in our guide to interview red flags.
When both happen in one day
A full loop that mixes a technical exercise with two behavioural conversations is genuinely tiring, and fatigue is the main reason strong candidates fade in the last session. Two things help. Prepare the behavioural material first, because it is the part you can rehearse to the point of not needing energy, and leave the technical practice closer to the day. And treat the breaks as part of the process: eat something, get outside for two minutes, and reset rather than reviewing the round that has just finished. A poor round is not recoverable by brooding on it and is frequently recoverable by performing well in the next one.
Between sessions, note which examples you have already used. Interviewers in a loop compare notes, and the person in session three has usually heard what you told session one. Repeating a story is fine if you flag it; presenting it as new is what gets remarked on.
Questions people actually ask
What is the difference between a behavioural and a technical interview?
A behavioural interview asks for evidence of what you have done before and scores the specificity of that evidence. A technical or practical interview asks you to perform the work now and scores your approach as much as your answer.
How do I prepare for a technical interview?
Practise realistic problems out loud rather than silently, rehearse in the actual environment you will be assessed in, refresh anything on your resume you have not used recently, and prepare the clarifying questions you will ask before starting.
What should I do if I get stuck in a technical interview?
Say so, say what you do know, state your assumptions, and describe the approach you would take to find out. Asking for a hint is normal and is usually scored better than a long silence or a confident guess.
How long should I spend on a take-home task?
Roughly the time the employer stated, and no more. Ask if they did not say. Include a short note covering your assumptions and what you would do with more time β assessors value it consistently.
Are behavioural or technical rounds more important?
The technical round is more often the filter and the behavioural round more often the decision. Candidates who clear the technical bar are usually separated on the quality of their evidential answers.
Can I ask what format the interview will be?
Yes, and you should. Ask the recruiter what each stage involves, how long it runs and whether there is an exercise. Employers expect the question and the answer changes how you prepare.
