Behavioral Interview Questions

Two formats get called "the interview" and they're not the same exercise.

A structured competency interview — scored against a defined framework, often with a panel and a scoring sheet — is now standard across the NHS, most large employers, the public sector, and essentially all of graduate recruitment. Questions come in a fixed order and everyone gets the same ones. The panel is filling in a grid.

An unstructured conversation with a hiring manager wanders, follows what interests them, and rewards different things.

This page is aimed at the first, because it's the one you can prepare for and the one that's spreading. The good news is that preparing for it makes you better at the second anyway.

The premise is simple: the best available predictor of what you'll do is what you've done. That's why a good interviewer won't ask "how do you handle pressure?" — that asks for your opinion of yourself — but "tell me about a week where you were badly overloaded."

Notice the difference, because it's where most answers go wrong. A hypothetical question ("what would you do if…") tests your reasoning. A behavioral question ("tell me about a time…") tests your record. If you answer a behavioral question hypothetically — "generally what I do is…" — you haven't answered it. That is the single most common failure in this entire category, and interviewers are trained to push back on it.

The phrase that fixes it: "There was a situation last March…" Start there and the specifics come out on their own.

STAR — Situation, Task, Action, Result. It's a real tool and it works. It's also taught so uniformly that answers have converged, and experienced interviewers now recognise a STAR-shaped answer from a distance and start probing for whether anything underneath it is real.

So use it, and know where it fails.

One: the situation eats the answer. Forty seconds explaining the company's structure, its reporting lines and its three sites, and then you're out of time before you get to what you did. Two sentences for the situation. They don't need to understand your employer. They need to understand your decision.

Two: the action is narrated in "we". "We decided", "we agreed", "we escalated." This is the most common way strong candidates make themselves invisible, and it's usually good manners doing the damage — sharing credit is a decent instinct. But they're hiring you, not the team you left. Say I in the action, then return to "we" in the result if you like.

Three: the result has no measure. "And things improved" is not a result. If you don't have a number, give a before-and-after: time saved, a step removed, an error that stopped recurring, a complaint that didn't come back.

And add a fifth element the acronym omits: what changed afterwards — a process, a check, something that outlived you in that job. This is the part that separates someone who lived through an event from someone who learned from it, and on mistake questions it's the entire assessment.

The most useful idea on this page, and the one most people do exactly backwards.

The instinct is to prepare an answer per question. There are dozens of behavioral questions, so you memorise twenty answers, then get asked a phrasing you didn't rehearse and freeze — because you prepared answers rather than material.

Do it the other way. Prepare six incidents, not twenty answers. One rich incident answers six different questions depending on the angle you take, because the interviewer is asking about the angle, not the event.

One incident, six uses. A logistics coordinator noticed a carrier had been billing for a fuel surcharge that had been removed from the contract nine months earlier, proved it by pulling the rate card against the invoices, took it to her manager, and ended up recovering the money and adding a quarterly rate-card check:

The hardest group and the most revealing. The interviewer isn't measuring competence here — they're measuring your instinct at the moment something goes wrong. Do you tell someone, or do you quietly fix it and hope? Employers who press hard on these questions have usually been burned by the second kind.

One trap runs through this whole group: spending the answer proving you were right. The interviewer isn't adjudicating your old dispute. They're picturing how you'll describe their team in two years.

A short group that decides more interviews than its length suggests, and it's sometimes asked bluntly enough to be uncomfortable. Candidates at Stryker reported being asked "have you ever told a lie?" and "do you try to make people like you?" — questions designed to watch your reaction more than to collect your answer.

Reported by candidates at Southern New Hampshire Health in the blunt form name a mistake you made while caring for a patient — the same instinct in clinical dress: they want to see whether you have one ready.

Rarely covered on pages like this, and useful — knowing a question is out of bounds makes you calmer in the moment, and being calm is worth more than the answer.

Pay history, across the EU. The EU Pay Transparency Directive gives applicants the right to pay information for the role before the interview, and provides that employers shall not ask applicants about their pay history. Member states were required to transpose it by 7 June 2026. Note the scope precisely, because it's easy to overstate: it bars asking what you currently earn, not the forward-looking "what are you looking for?" Several US states have their own salary-history bans; the UK has no equivalent statutory ban.

Health and disability, in the UK. The Equality Act 2010, section 60, says an employer must not ask about an applicant's health before offering work — or, where they aren't yet in a position to offer, before putting the applicant into the pool they'll select from. That second limb matters, because it closes the obvious workaround of screening people out earlier in the process.

There are defined exceptions, and they're narrower than employers often assume: establishing whether you can take part in an assessment, working out what reasonable adjustments you'd need, whether you can perform functions intrinsic to the job, diversity monitoring, and positive action. "Intrinsic" is doing real work there — it means the job genuinely cannot be done without it, not that it would be convenient to know.

Protected characteristics generally. Questions about marital status, children or plans for them, age, religion or national origin are unlawful or close to it in most of these jurisdictions when used to make a hiring decision.

What to actually do, since knowing your rights and wanting the job are both real. Don't confront. Redirect to your ability to do the work: "I can commit to the full schedule the role needs" answers a question about children without engaging with it. And you're entitled to decline. If the questioning is persistent and clearly discriminatory, that is information about the employer — you're interviewing them too.