The structure that works
- Name a real weakness, specifically.
- Give one concrete example of it causing a problem.
- Say what you changed as a result.
- Be honest about where you are now — improved, not cured.
The fourth part is what makes it credible. Weaknesses that were completely solved read as fiction.
An answer that lands
"I hold on to work too long before showing it. On a migration project last year I spent nine days building something in isolation, and when I finally shared it, two of my assumptions about the data model were wrong. Most of that week was wasted.
Since then I have made myself share at the point where it is still embarrassing — usually a rough version within two days. It still feels bad, and I still have to make myself do it. But I have not repeated that particular nine-day mistake."
Choosing which weakness to give
Pick something real that is not the core competency of the job. A weakness in public speaking is fine for a backend engineer and a serious problem for a sales lead.
- Safe and true for most roles: delegating, saying no to scope, over-preparing, impatience with ambiguity, holding work too long.
- Avoid: anything about reliability, honesty, or getting along with people. These read as character issues, not skill gaps.
- Avoid: the exact skill the job posting lists first.
Why honesty outperforms
Interviewers hear the rehearsed non-answers all day. A real one is memorable, and it makes everything else you said more believable — a candidate who will admit a genuine failure is a candidate whose claimed successes are probably also true. The risk of naming a real flaw is much smaller than the cost of sounding evasive.