'Why should we hire you?' is the interview's closing argument slot, and most candidates treat it as a talent show: three adjectives, a smile, and hope. Interviewers are asking something narrower and easier to answer well — make the case, using evidence we can check, that hiring you is the low-risk, high-return version of this decision. It is a summing-up, not an audition.
The answers that land share one architecture: two or three claims, each welded to a piece of evidence from your career, closed with an honest line about what you would still need to learn. The honest line is not modesty theatre — it is what makes the rest believable.
Below are four fully worked answers — a step-up candidate, a sector switcher, a contractor going permanent, and a deliberate sideways move — each marked against the four criteria aurate uses live, plus the variants panels actually ask ('what makes you different from the other candidates?') and how they differ.
Practise these questions out loud with a live AI interviewer — free. Start with Try Me
How the marking guidance works
Each model answer below is marked against the four criteria a live aurate session scores:
See how a full session is scored
aurate is a practice tool. Marking guidance describes what strong practice answers show — it isn't an employability assessment.
Why it's asked: For a candidate applying one level above their current role, the question really means: why should we take the promotion risk an internal market would price more cautiously? The strong answer names the risk and shows it has already been paid down.
Three reasons, and I'll give you the risk with them. First: the core of this role is commercial control on live sites, and that's the part of my record I'd put money on — I run the cost plans on two schemes now, 46 and 62 units, and both came through final account inside the contingency I set.
Second, the part of senior QS work that isn't in the job title: subcontractor relationships that survive a dispute. I settled a groundworks variation row last year without it reaching adjudication, and that subcontractor priced our next tender keener, not sharper.
The risk you're weighing is that I haven't held the title before. That's true. What I'd say is: I've done the work at its full width on two schemes — what I haven't done is carry it across five, and that's the stretch I'm applying for. I'd rather make that step here, where I know the build system, than somewhere I'd be learning both at once.
Marking guide
Why it's asked: Asked to a switcher, the question carries a silent second clause: '…over someone who already knows our world?' Answers that ignore the clause sound naive; answers that meet it head-on — here is what transfers, here is what doesn't, here is why the trade is worth it — sound like the decision has already been thought through for them.
Because the job you've described is the job I've been doing — in a harder version of it. Front-of-house for your client buildings means thousands of visitors, security that can't feel like security, and staff rotas that survive sickness on the worst possible day. I ran exactly that at a national museum site: 4,000 visitors on peak days, 30 casual staff, and a protest incident that ended with a de-escalation and no coverage anywhere.
What I don't have is corporate-client experience — your world runs on service-level agreements and mine ran on visitor promises. I've read enough to know the vocabulary changes more than the discipline does, but I'll be honest that month one is me learning how your clients measure us.
So the case is: you can teach the contract language in weeks. The calm at the front desk on a bad day took me nine years, and it's what I'd bring on day one.
Marking guide
Your version of this answer needs your evidence in it
Two marked answers in, the architecture is clear: claims, welded evidence, one honest edge. Building yours from your own record — and holding it when the panel asks what they'd be taking a chance on — is what a live session is for. aurate pushes back on the claims and marks the answer on the same four criteria. Two free sessions. No credit card.
Try it freeWhy it's asked: Panels hearing a contractor ask themselves two things: will this person stay, and can they work at permanent-hire depth rather than contract-scope width? The strong answer treats both as fair questions and answers them with decisions, not reassurances.
The honest version is: you should hire me because I've already chosen this. I've contracted across four trusts in six years — I've seen four ways of running informatics, and I know which problems follow you everywhere and which are local. That comparative view is something your permanent team can use, and it doesn't expire when my knowledge of any one system does.
The question behind your question is whether a contractor will stay. Two things I'd offer. I turned down a renewal at a higher day rate to apply for this — that's a decision, not a claim. And the reason is specific: the data-quality programme you're starting is an eighteen-month build, and contract scopes kept handing me the first three months of problems like it and moving me on before the interesting part.
What I'm asking you to weigh is six years of breadth against the depth I'm deliberately here to build. I think that's a strong trade for a team about to start something long.
Marking guide
Why it's asked: A sideways mover triggers a specific suspicion: is this retreat, drift, or design? The question is the panel's invitation to show the design. Strong answers make the lateral step the argument — what this role has that seniority elsewhere does not — without a word against the current employer.
It's a fair question to ask someone applying level-for-level, so let me answer the real one: this isn't a step back or a soft landing — it's a trade I've thought hard about. As head of production I run a department of 14, and the honest audit of my week is that I've become a manager of the work rather than a doer of it. The part I'm best at — and the part your role is made of — is the title-level problem-solving: the 300-page illustrated schedule that's three weeks late with a fixed publication date.
What I bring from the head-of-department years is what they cost: I know what makes production schedules fail upstream, because I spent five years on the receiving end of the failures, and I can head them off from inside a project in a way I never quite could from above it.
What you should check is whether I'll miss the status. I'd point at the last two years: I kept the hands-on titles when I could have delegated them all. The evidence says the work was the point.
Marking guide
Why it's asked: A sharper cousin — it asks for comparison against people you have never met. Don't take the bait of imagining them: name the unusual combination in your own record ('most people with my costing background haven't run a site team; I've done both') and let the panel do the comparing. Claim the intersection, never the superlative.
Why it's asked: 'Why should we hire you?' asks for their business case; 'why do you want this?' asks for yours. Candidates who give the motivation answer to the hire-you question sound self-absorbed; the reverse sounds mercenary. Prepare both, keep them separate, and let each borrow one sentence from the other at most.
Why it's asked: Occasionally asked openly, more often the silent backdrop. Never argue against the internal person — argue for the outside view: the patterns you have seen elsewhere, the absence of local habits, the licence an outsider has to ask naive questions. Respect plus differentiation is the only winning register.
Why it's asked: Panels increasingly ask this straight after, precisely because rehearsed answers collapse on it. If your original answer already named the gap, this follow-up becomes a gift: expand calmly on the same gap and how you would close it, and you have just demonstrated consistency under probing — the rarest signal in the room.
Why it's asked: Usually late — it is a summing-up question, and treating it that way is the trick. Sixty to ninety seconds, two or three claims, evidence attached, honest edge named, stop. Going past two minutes converts a closing argument back into an audition, and auditions are exactly what the strong version of this answer refuses to be.
Sixty to ninety seconds spoken. Two or three claims with evidence, one honest line about what you would still be learning, then stop. Panels remember answers that end deliberately; answers that trail outward past two minutes read as hoping rather than arguing.
Answering with qualities instead of evidence — 'hard-working, passionate, a people person'. Adjectives ask the panel to take your word; evidence lets them check it. One verifiable fact ('both schemes closed inside contingency') outweighs any three adjectives you could pick.
Name one boundary, briefly — the thing month one would teach you. It is strategic, not confessional: an answer with a named edge reads as an honest audit, and it takes the panel's sharpest follow-up off the table by answering it first.
Same case, different discipline. Written versions can build slowly; the spoken answer gets ninety seconds and no second draft. Prepare it as an argument — claims you can say in one breath each — rather than prose to recite, because recited prose collapses at the first interruption.
Treat it as a research symptom, not a character flaw. List what the role needs, list your evidence against each need, and the overlap is your answer. If the overlap is genuinely thin, better to discover that before the interview — it usually means the application was aimed at the title rather than the job.
Two free sessions. No credit card.