Strengths & Weaknesses · UK 2026
How to answer "What's your greatest weakness?"
Interviewers also phrase it as:
- "What are you working on improving?"
- "What's an area of growth for you?"
- "What would your manager say you need to develop?"
Why interviewers ask
Tests self-awareness, honesty, and growth orientation simultaneously. Strong answers name a real weakness (not a humblebrag), describe a specific incident where it caused a problem, and show what you've been doing about it. Weak answers fall into two camps: humblebrags ('I'm a perfectionist') or unforced honesty ('I don't manage my time well') without a development arc. Both fail.
Model answer
My genuine development area is [a real, specific weakness — not a disguised strength]. I noticed it sharply when [specific situation where it cost something — a deadline, a relationship, an opportunity]. I've been working on it deliberately for the last [X months] by [specific action — feedback cadence, deliberate practice, coaching, a structured method]. I'm meaningfully better than I was, but I'd be lying if I said it was solved. For this role specifically, [light note on whether the weakness affects core requirements — usually a 'no' or 'partial' with a mitigation].
What to avoid (common bad answer)
My greatest weakness is that I'm a perfectionist — I work too hard and care too much about quality. (Humblebrag — interviewers detect this within 5 seconds and mark you down for it.) Or: My weakness is time management; I struggle with deadlines. (Unforced honesty without a development arc — sounds like you're admitting you can't do the job.) Both fail.
Structure of a good answer
- 1 A real weakness — not a humblebrag, not a strength in disguise
- 2 Specific incident where it caused a real problem
- 3 Concrete development action you have been taking for several months
- 4 Honest progress note — better but not solved
- 5 Brief mitigation for the role-specific implications
Common mistakes
- ✗ 'I'm a perfectionist' / 'I work too hard' — every interviewer rejects this within seconds
- ✗ Picking a weakness that's a core requirement of the role (e.g., 'I struggle with managing teams' for a manager role)
- ✗ Naming a weakness without showing development action — sounds like resignation
- ✗ Naming three weaknesses — too much; pick one and go deep
- ✗ Theoretical weakness without a real-life example — flags you haven't thought about it
Recruiter pro tip
The candidates who land this question well pick a weakness that's real but doesn't undercut the role's core requirements. Example: a senior PM saying 'I default to data when emotional intelligence work matters more — I've been deliberately running 1:1s with stakeholders to build the muscle.' That's a real weakness, evidenced development, and a non-fatal-for-the-role framing. Three components, every time.
FAQ
Can I say my weakness is something irrelevant to the role? ▼
Yes, this is the safe play — pick a real weakness that doesn't directly intersect with the role's core requirements. But it should still feel real and have a development arc.
How honest should I be? ▼
Honest enough to be credible, calibrated enough to not raise red flags. 'I struggle with cold outreach' for a quiet IC role is honest and fine. The same answer for a sales role would be a problem.
Should I mention how I've improved? ▼
Yes — the development arc is the most important part of the answer. Without it, you're just admitting a flaw with no resolution.