"I'm a perfectionist" has been said so many times that interviewers visibly deflate when they hear it. It's not a real weakness, everyone knows it, and it makes you sound either dishonest or unaware. This guide gives you real weakness examples that show self-awareness, honesty, and growth, which is exactly what the question is designed to surface.
What not to say
"I'm a perfectionist." This is the most common non-answer in interviewing. It reads as an attempt to describe a strength as a weakness.
"I work too hard." Same problem. No interviewer is fooled.
"I don't really have weaknesses." This is worse than the perfectionist answer. It shows no self-awareness at all.
A weakness that's a core requirement of the job. Don't say you're bad at written communication for a role that requires producing reports. Don't say numbers aren't your strength for a finance role.
What makes a weakness answer actually good
A good weakness answer has three parts: the actual weakness (real, specific, not trivial), what impact it's had (brief acknowledgment that it matters), and what you're doing about it (concrete, not vague). The third part is where most candidates are too vague: "I'm working on it" is not enough. Describe a specific practice or change you've made.
Real weakness examples with sample answers
Delegating
"I've historically found it hard to delegate work that I know I can do well myself. The downside is that I take on more than I should and it creates a bottleneck when I'm the resource constraint. I've been deliberate about it over the last 18 months: I now have a personal rule that anything that doesn't require my specific judgment should go to someone else, even if I think I could do it faster myself. It's improved my team's development and my own output."
Public speaking or presenting
"Large-group presentations have been an area I've found uncomfortable. I'm confident in one-on-one or small group settings, but presenting to an audience of 50 or more has taken effort. I joined a Toastmasters chapter 18 months ago and have done eight presentations since. I'm noticeably better and I've volunteered for two all-hands presentations at work in the last year that I would have avoided before."
Giving feedback in the moment
"I tend to process before I speak, which means I'm not always quick with feedback in real time. If someone presents something that needs significant rework, my instinct is to say 'let me think about this' rather than give my view on the spot. This can frustrate people who want immediate reactions. I've been working on it by preparing a mental checklist of the dimensions I'll always assess, so I can give structured immediate feedback even when I haven't had processing time."
Getting too deep in the detail
"I sometimes go deeper into the detail of a problem than is necessary for the decision at hand. This is useful in some contexts but it can slow things down or cause me to over-invest in analysis when a faster, good-enough answer would serve better. I've started asking myself 'what's the actual decision this analysis needs to support?' before I go deep. That framing helps me stop at the right level of detail."
How to close the answer
End with a brief signal that this isn't a dealbreaker: "It's something I'm actively working on and I've seen real improvement." Don't over-explain or apologise. State the weakness, the impact, the action, and move on. The longer you stay on a weakness, the more it feels like a bigger deal than it is.