Everyone knows the rules of this question by now — real weakness, not a strength in costume; evidence of work on it; don't torpedo the role's core requirement. Knowing the rules hasn't helped: candidates still deliver perfectionism-with-a-bow, interviewers still discount it on arrival, and the question keeps earning its place by catching people between honesty and self-sabotage. What's missing isn't theory. It's worked examples for YOUR situation — because a graduate's credible weakness, a manager's, and a career changer's are different animals.
That's this page's job: an answer bank by situation, each specimen marked against the four criteria a real assessment uses. The situational logic matters because the question's risk profile changes with seniority — a graduate admitting overcommitment is endearing; a senior manager admitting it is alarming. The weakness has to be true, worked-on, and priced correctly for the level you're interviewing at.
Scope note: if you want the ground-up method — how to choose your weakness, the psychology of why interviewers ask — our editorial guide to answering the biggest-weakness question walks that path. This page assumes you know the method and need the specimens: answers by situation, with marking guidance showing exactly why each one holds.
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 graduates the question doubles as a maturity test: assessors expect less polish and more honesty, and they're alert to coached answers. The credible graduate weakness is developmental — a skill still forming — with evidence you noticed it yourself rather than waiting for feedback to find it.
I say yes to too much — and I want to describe the actual mechanism, because 'I'm a yes person' sounds like a humble-brag and the reality wasn't.
In my final year I was course rep, on the hockey social committee, doing a dissertation, and tutoring two GCSE students. Each commitment was individually sensible; the stack wasn't. The cost landed in February: I missed a course-rep deadline for collecting exam feedback — the one job that actually affected other people — because the tutoring had expanded into exam season. Nobody shouted at me. The staff-student meeting just went ahead without our year's input, which was worse.
What I worked out afterwards is that my yes reflex isn't generosity, it's discomfort: saying no to a reasonable request feels like letting someone down, so I'd let future-me absorb the cost instead. Naming that made it manageable.
The system I run now is small but real: before accepting anything with a recurring time cost, I write down what it displaces — not whether I have time, but what specifically loses. When I applied that to this year, I dropped the social committee and kept the tutoring, because one had a successor available and the other didn't. First time I'd made that kind of trade deliberately.
I'd expect the first year of this job to test the reflex again — new place, wanting to prove useful. The difference is I now know what my yes costs, and I check before spending it.
Marking guide
Why it's asked: At manager level the question sharpens: your weakness has a team-sized blast radius, and the interviewer is checking you know your own weather system. Credible manager weaknesses come with impact-on-others acknowledged and a mechanism your team can see — ideally one they helped build.
My directness runs ahead of my calibration — with some people, at some moments, what I intend as clarity lands as bluntness. I know this because my team told me, which is both the embarrassing part and the useful part.
The concrete version: in my first year managing the team, our upward feedback included two comments about my review style in one-to-ones. The phrase that stuck was 'you correct the work before you've acknowledged the effort'. My instinct was to defend it — the corrections were right! — and that instinct lasting a full weekend is itself part of the honest answer. By Monday I'd accepted the actual point: right corrections, delivered at the wrong moment in the conversation, cost me information. People had started bringing me their work later and more finished, which sounds good and isn't — it meant problems reached me a fortnight older than they needed to be.
What I changed, mechanically: I open work conversations with one genuine question about where the person thinks it stands, before any view of mine. Not a technique from a book — a repair negotiated with my own team. And I told them what I was doing, which mattered: naming the change made it accountable.
The honest current state: it's managed, not cured. Under deadline pressure the old pattern resurfaces — my deputy has literally said 'acknowledge first' to me in a corridor, and I've thanked her for it. That she can say it is, I'd argue, the system working.
For this role: you'd get a manager whose directness you'll never have to decode — and who has learned, expensively, to spend it at the right moment.
Marking guide
The weakness answer is a composure test wearing a content mask
Every specimen above holds because of delivery you can't rehearse silently: steady voice inside vulnerability, no rush to redemption, a follow-up absorbed without flinching. aurate's Weakness Trap scenario drills exactly this question live — an AI interviewer that probes your answer and marks it on the same four criteria used across this page. Two free sessions. No credit card.
Try it freeWhy it's asked: The career changer's version has a trap inside: the honest answer is often a technical gap, but naming only the obvious gap ('I'm new to the sector') wastes the question — the interviewer already knows. The strong move is a REAL behavioural weakness plus the gap handled as context, showing you can self-assess beyond the obvious.
There's the obvious answer — I'm eighteen months into this field, so my technical depth is younger than my colleagues' — but that's a fact you already have. The weakness worth your time is what being new did to my behaviour.
For about my first year after switching, I compensated for feeling junior by over-claiming certainty. In my old field I'd been the expert people came to; suddenly being the person who asks basic questions was genuinely uncomfortable, and my coping mechanism was to sound more sure than I was. The costly version: in a planning meeting last spring, I nodded through a scoping discussion I'd only partly followed, rather than asking the clarifying question that would have marked me as the new one. The part I let slide contained an assumption that cost us four days of rework — and the worst part is that my basic question would have caught it, because the assumption was only obvious to people too experienced to re-examine it.
My manager and I unpicked it in the retro, and she offered the reframe I now work from: the recently-switched person's naive questions are a feature — we're the only ones who still see the water everyone else swims in.
The practice since: I ask the basic question deliberately, badged honestly — 'new-person question:' — which turns the discomfort into a role. In the last two quarters, two of those questions have caught real issues.
So my weakness isn't the gap. It's that the gap made me perform confidence instead of practising honesty — and that behaviour, unlike the gap, was mine to fix immediately.
Marking guide
Why it's asked: Senior panels ask knowing the stakes have inverted: at this level, unawareness of your own operating flaws is the disqualifier, not the flaws themselves. The credible senior weakness is structural — a bias in how you lead — with organisational-level costs acknowledged and compensating mechanisms built into how you run things.
I have an optimism bias in planning — I systematically believe things will take less time than they do, and at my level that bias doesn't stay personal, it propagates. A director's cheerful timeline becomes a department's missed one.
I can date my acceptance of this precisely, because it cost real money: a systems migration I sponsored three years ago, where I signed off a nine-month plan that my own delivery lead had privately sized at thirteen. She'd told me, carefully. I'd heard the caution as prudence-padding rather than information — because I wanted nine to be true. It took fourteen months. The overrun's direct cost was around £120,000; the trust cost with the board was worse, and entirely mine to own, which I did in those words.
What I've built since — because a senior weakness needs infrastructure, not intentions: first, reference-class planning as standard on anything I sponsor — we check what comparable projects actually took, ours and published ones, before my enthusiasm sets a number. Second, a standing rule my leadership team knows: when someone gives me a range, I repeat back the pessimistic end first, out loud, to prove I heard it. Third — the one I'd highlight — my delivery lead now presents timelines to the board directly, not through me. Removing myself from the transmission path was the honest fix; my summary voice was where the optimism leaked in.
The bias hasn't gone. Last year I still caught myself calling a seven-month estimate 'probably six with a fair wind' — in an email, which my team gleefully quoted back. But the machinery caught it: we planned to seven, and it took seven and a half.
At senior level I'd distrust anyone who claims a cured weakness. What I offer is a known one, with compensators designed by the people it used to cost.
Marking guide
Why it's asked: The reserve-tank probe, increasingly common precisely because first answers ARE prepared. It tests depth of self-knowledge: candidates with real self-awareness have more than one flaw catalogued; candidates with a rehearsed specimen go visibly blank. Always arrive with two, the second slightly rougher than the first.
Why it's asked: Triangulation with a reference check implied: your answer may be compared with an actual referee conversation. The strong shape is a weakness your manager has genuinely raised (appraisals leave records), your honest position on it — agreement, or respectful partial disagreement with reasoning — and what you've done since it was raised.
Why it's asked: The weakness question's behavioural twin: instead of your self-assessment, it probes your feedback metabolism — the moment of receiving, the defensive flinch if there was one, and the distance between hearing and changing. Interviewers rate the honesty of the flinch description as highly as the eventual growth.
Why it's asked: The applied version, and the sharpest: it forces your named weakness into contact with the actual job spec. Strong answers identify the genuine collision point (not a flattering one), size the risk honestly, and bring a specific first-quarter mitigation — proving the self-awareness extends to consequences, not just narrative.
Why it's asked: A maturity filter most candidates never see coming: it asks for a failed self-improvement project, which only genuinely self-aware people can supply. The credible answer distinguishes fixing from managing — a trait that persists, ringed with compensating structure — and demonstrates the adult skill of designing around your own permanent features.
Why it's asked: A meta-question senior interviewers deploy to watch you think. There's no trap: thoughtful candidates note what the question actually measures (calibration, honesty under mild threat, self-knowledge depth) and answer with a view rather than a complaint. Dismissing it as outdated while sitting inside it rarely lands well.
One that's true, specific, and not load-bearing for the role — overcommitment, directness that needs calibrating, optimism in planning, discomfort with ambiguity — paired with its real cost and the mechanism you've built against it. The situational examples on this page show the same rules priced for graduate, manager, changer, and senior contexts.
Anything that torpedoes the role's core requirement (attention to detail for an auditor, deadlines for a delivery role), anything suggesting integrity or reliability problems, and the costume-strengths — 'perfectionism', 'I work too hard', 'I care too much' — which interviewers discount instantly and hold against your honesty calibration for the rest of the hour.
Honest enough that the weakness has a real cost you can name, bounded enough that it doesn't dominate your candidacy: the working range is a genuine flaw with visible management, delivered without over-apology. If saying it aloud feels slightly uncomfortable, you're probably in the credible zone; if it feels flattering, you're not.
Yes — two minimum. The follow-up ('give me another') is now common precisely because first answers are rehearsed, and the second specimen is where genuine self-knowledge shows. Keep the second slightly rougher and less resolved than the first; a matching pair of polished answers defeats the purpose of asking twice.
The stakes invert with seniority: graduates are forgiven forming-skills weaknesses but marked on honesty; managers must show team-visible mechanisms because their flaws have blast radius; seniors are disqualified by unawareness rather than by flaws, so structural weaknesses with organisational compensators are the credible register. Same question, different pricing.
Two free sessions. No credit card.