'What are your strengths?' is not an invitation to list nice qualities — it is a claims test. The interviewer is going to pick whichever strength you name and probe it: where did it show up, what did it cost, would your colleagues agree? Candidates fail this question in the follow-up far more often than in the answer, because they chose a strength they could name but not evidence.
The reliable architecture is claim–evidence–calibration: name the strength precisely, prove it with one checkable episode, then calibrate it honestly — where it runs out, or what it costs you. Calibration is the move most candidates skip, and it is exactly what separates a self-aware answer from a rehearsed one.
One scope note before the answers: this page covers the killer question itself. If you are preparing for a strengths-based interview — the format built entirely from questions like this, common in the public sector — our strengths-based interview questions guide covers the format's own rules; the two link but do not overlap.
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: Analytical claims are the most commonly made and the least commonly evidenced — every second CV says 'strong analytical skills'. The interviewer's follow-up is nearly always a request for a worked example, so the strong answer builds the example in before it is asked for.
The strength I'd pick first is finding the question inside the data that nobody asked. The clearest example: our depot managers kept asking for faster stock reports. Instead of just speeding the report up, I spent two days on what they did with it — and found they only ever used it to chase eleven volatile lines. I built them an exceptions view of those eleven, and the weekly report conversation stopped happening because the problem had.
Where I'd calibrate that: it makes me slow on genuinely simple requests. If someone needs a number by three o'clock, my instinct to ask what it's for can be friction they don't need that day — I've learned to ask once, briefly, and deliver either way.
So: strong at turning vague asks into the real question. Costs me some speed on the trivial ones. In a role like this one, where the analysis brief is mostly ambiguous, I think that trade lands on the right side.
Marking guide
Why it's asked: 'Good communicator' is the most devalued phrase in interviews, so a communication strength has to be claimed narrowly and proved quickly. The interviewer wants to know which specific communication problem you solve — writing, translating, de-escalating, aligning — because 'all of them' means none reliably.
Mine is translating between people who think they're speaking the same language. On a store refit last autumn the designer's drawings said one thing, the client's operations team assumed another, and both were sure they'd agreed. I ran a forty-minute walk-through on site with both of them and a roll of masking tape — taped out where the counter would actually stand, watched the ops lead physically fail to get a cage trolley past it, and we resolved in one morning what the email chain had been escalating for two weeks.
The calibration is that I'm better face-to-face than on paper. My written updates used to be too brief — clients read terse where I meant efficient — so I now write them against a fixed template and have my deputy sanity-read anything sensitive.
For a role that's mostly boots-on-site with weekly client contact, that mix works: the strength is where the job is, and the weaker channel has a system around it.
Marking guide
Claim–evidence–calibration reads simply — the probe is the hard part
You've now read two answers built to survive follow-up. The test is making the same structure hold out loud, when a live interviewer picks your claim apart and asks where it failed you. An aurate session does exactly that — probes the claim, then marks the answer on the same four criteria used across this page. Two free sessions. No credit card.
Try it freeWhy it's asked: Organisation claims fail by sounding administrative — tidy lists, colour-coded calendars. Interviewers rate the version that is really about judgement under load: what you choose NOT to do, and how the system holds when the week goes wrong. The strong answer shows the machinery and the exception it survived.
I'd say sequencing under load — knowing what has to be true by when, and working the plan backwards from the immovable date. Producing a 300-exhibitor trade show, my critical path ran to about 70 items, and the discipline that made it work wasn't the spreadsheet — it was the weekly kill-list: the five things that would sink the show if they slipped, reviewed every Monday, everything else explicitly allowed to wobble.
It got tested properly when our keynote venue flooded 19 days out. Because the plan was staged, I knew within an hour which 12 items were affected and which 58 didn't care, and we re-signed a replacement venue in six days without touching the exhibitor build.
The honest cost: people who work loosely find me relentless in show month, and early in my career I let that become friction. Now I publish the kill-list to the whole team — it turns out people forgive the chasing when they can see why their item made the list.
Marking guide
Why it's asked: Candidates without management titles routinely concede this ground — 'I haven't led yet, but…' — when the interviewer is actually testing whether they can see leadership as behaviour rather than hierarchy. Claiming it through evidence, without inflating the title, is a high-skill move panels remember.
The strength I'd claim is steadying a team I don't formally lead. I'm the senior technician on our bench — no management line, but when our band 7 left and the replacement took five months to arrive, the day-to-day fell to me by gravity. What I actually did: set up a fifteen-minute morning huddle so the two trainees stopped saving their questions for whenever panic peaked, rewrote the sample-priority crib sheet everyone claimed existed but nobody could find, and flagged early that we'd miss turnaround on histology unless a locum picked up two sessions — which got approved because I asked in week two, not week ten.
I'd calibrate it honestly: I led the operational layer, not the people layer. I wasn't doing appraisals or managing the sickness case that ran through that period, and I watched how much of the real job that was.
But wanting the title with evidence of the behaviour — that's the case I'd make. The huddle is still running, fourteen months on.
Marking guide
Why it's asked: The singular form is a prioritisation test wearing a small disguise: from everything true about you, which one thing do you lead with for THIS role? Prepare a first-choice strength per application, not per career — the right answer changes with the job description, and interviewers can tell when it hasn't.
Why it's asked: A triangulation probe — it tests whether your self-image survives contact with other people's. The strong shape is reported speech with evidence: what a named-role colleague actually says, and the episode they'd cite. Including the mildly unflattering thing they would also say, unprompted, is advanced play that reads as genuine confidence.
Why it's asked: The commonest strategic error is leading with your proudest strength instead of the role's scarcest one. Read the job description for the problem that appears twice — it is usually the real one — and lead with the strength that solves it. Your second-favourite strength with perfect role fit beats your favourite without it.
Why it's asked: Interviewers increasingly chase strength claims with their failure case — it is the fastest test of whether the claim was real. A genuine strength has a real failure story, because you have used it enough to find its edge. If you cannot name where your strength once misfired, the panel concludes you haven't used it much.
Why it's asked: Panels compare notes: claim rigorous attention to detail as a strength, then offer perfectionism as your weakness, and both answers die of the contradiction. Build the pair together — a strength with an honest cost, a weakness that is not the same fact restated — and each answer makes the other more believable.
One, properly, unless asked for more — claim, evidence, calibration takes 60 to 90 seconds and lands. Three strengths in the same time means none get evidence, and unevidenced strengths are just adjectives. Keep a second and third ready for the follow-up.
The ones the role actually spends — read the job description for the problem mentioned twice and match it. A narrowly claimed, well-evidenced strength of any kind beats a prestigious-sounding one you cannot prove. 'Best' is a fit question, not a menu.
Calibrate, don't confess: name where the strength runs out or what it costs, in one sentence, then stop. That is different from volunteering a separate weakness — calibration makes the claim believable; an unprompted confession just changes the subject against you.
Claim the behaviour, evidence it from wherever it genuinely showed up — a course project, a part-time job, a team you organised. Interviewers accept evidence from any setting if it is concrete; what they discount is a claimed strength with no episode behind it at all.
Arrogance is claiming without evidence or edge; confidence is a checkable claim, calibrated honestly. 'I'm the best analyst you'll meet' is bravado. 'I turn vague requests into the real question — here's the episode, here's the cost' is just an accurate report, delivered plainly.
Two free sessions. No credit card.