Most people answer this question badly in one of two ways: a fake weakness that is secretly a strength, or an honest confession that raises real doubts. Interviewers have heard “I’m a perfectionist” thousands of times, and they stop listening.
The question is simpler than it looks.
What the interviewer is really asking
Three things:
- Do you know yourself? Can you name something real without being defensive?
- Do you act on it? Did you do anything about it, or just notice it?
- Is it a problem for this job? A fear of public speaking matters for a sales role and much less for a lab role.
Answer those three and you have answered the question.
The three-part structure
Name it plainly. One real weakness, in ordinary language.
Show the impact you noticed. A short, specific example. This is what makes the answer credible.
Explain what you changed, and how it is going. Include the mechanism, not just the intention.
Keep the whole thing to about 45 seconds, and end on the improvement.
Examples you can adapt
Delegation:
I used to take on too much myself rather than hand work over, because it felt faster. On a project last year it meant I became the bottleneck for two weeks. Since then I write down who owns each piece at the start, and I’ve made myself hand over at least one task I’d normally keep. The last project ran without waiting on me.
Detail versus speed:
I over-polish first drafts. I once spent a day on a deck that was only needed internally. Now I agree the standard before I start, and I set a time limit for internal work. It has been a noticeable change in how much I get through.
Speaking up in large meetings:
I think slowly in big meetings and often have the useful thought afterwards. I started sending a short follow-up note with my point, and recently I’ve begun preparing one question in advance so I contribute live. I’m better than I was, and still working on it.
Unfamiliar technical area:
My statistics were weaker than my SQL, which limited the analysis I could do alone. I finished a statistics course this spring and applied it to our churn analysis, where I had to be honest about what the sample could and could not support.
What to avoid
- Disguised strengths: “I work too hard”, “I care too much”.
- A weakness that is the core of the job: “I’m disorganized” for a project manager.
- Anything about honesty, reliability or getting along with people.
- A list. One weakness, well told.
- Over-sharing personal or health matters you are not asked about.
Choosing yours
Pick something true, fixable and not central to the role. The most convincing answers tend to come from real feedback you have received, which is also why asking for feedback regularly is useful preparation. Our guide on giving and receiving feedback covers how to collect it.
Prepare it alongside your other stories, as described in our interview preparation checklist, and watch for the related traps in our list of interview mistakes.
Frequently asked questions
Can I say I am still learning something technical?
Yes, if you show the learning is active and specific. “I’m newer to Python and I’m halfway through a course, using it on a reporting project” is a solid answer.
What if my weakness really is central to the role?
Then it is worth asking whether the role fits you. If it is a smaller part of the job, be honest about the limitation and show how you manage it with process or with colleagues.
Should I rehearse word for word?
Rehearse the three parts and the example, not a script. Memorized answers sound memorized, and interviewers notice.
