What Is Your Greatest Weakness? 10 Honest Answers That Work
Few interview questions cause as much quiet panic as "What is your greatest weakness?" Admit something serious and you worry you will be rejected. Give a fake answer like "I'm a perfectionist" and you can see the interviewer's eyes glaze over. Most candidates end up somewhere uncomfortable in the middle.
There is a better way. This question is not a trap; it is a test of self-awareness and of how you respond to feedback. Handled well, it can actually be one of the strongest moments in your interview. Below you will find a simple structure, ten example answers across different roles, and a list of answers to avoid.
Why interviewers ask about weaknesses
Every employer knows that nobody is perfect. What they want to learn is:
- Do you know yourself? People who can name a real weakness usually take feedback well.
- Are you honest? A polished non-answer suggests you might hide problems at work too.
- Do you improve? The most important part of your answer is what you are doing about the weakness.
- Is the weakness a deal-breaker for this job? This is why choosing the right weakness matters.
A three-step structure
- Name a real, specific weakness that is not central to the role. "I'm not great at public speaking" is fine for a data engineer; it would be risky for a sales trainer.
- Give a short example of how it showed up, ideally one where you noticed it or received feedback.
- Explain what you are doing about it and what has improved. This should be the longest part of your answer.
The whole answer should take under a minute. End on the improvement, not the problem.
Ten example answers
1. Delegation (managers and team leads)
"When I first became a team lead, I held on to too much work myself because I knew I could do it quickly. It meant I became a bottleneck before a release. My manager pointed it out, so I started using a simple rule: if someone on the team can do it at 80% of my standard, it goes to them with clear notes. I now review rather than redo, and two people on my team have grown into areas I used to own."
2. Public speaking (technical roles)
"Presenting to large groups has never come naturally to me. In a quarterly review last year I rushed through my slides and didn't leave time for questions. Since then I've joined an internal presenting group and I practise every talk with a timer. My last demo went well enough that I've been asked to present again next month."
3. Saying yes to too much
"I used to accept every request because I wanted to be helpful, and a couple of times my own deadlines slipped. Now I check my priorities before agreeing and I'm more comfortable saying 'I can do this on Thursday' rather than 'yes, right now'. My manager has noticed that my estimates have become much more reliable."
4. Detail over speed (analysts, accountants)
"I can spend too long polishing an analysis that only needs to be directionally right. I've learned to ask at the start how precise the answer needs to be and what decision it supports. For quick questions I now share a first version early with the caveats stated, and save the deep checking for reports that go to leadership or the board."
5. Asking for help late (junior candidates)
"In my internship I sometimes spent a whole afternoon stuck on a problem before asking anyone, because I didn't want to look inexperienced. My mentor told me that thirty minutes of trying is enough before asking. I now write down what I've tried and then ask, which makes the conversation quicker for everyone."
6. Direct feedback (people-pleasers)
"I've found it hard to give critical feedback to colleagues, and in one project I let a quality issue continue too long. I took a short course on feedback conversations and now use a simple structure — what I saw, its impact, and a suggestion. It feels much less personal and the conversations have been productive."
7. Unfamiliar tool or skill
"My experience with advanced Excel modelling is thinner than I'd like, because my last role used a dedicated planning tool. I've started a financial modelling course and I've rebuilt two of our old forecasts in Excel as practice. I'm confident I'll be comfortable with it within the first couple of months."
This works well when the skill is useful but not essential. If you are thinking of formal training, our guide to free online courses with certificates lists good starting points.
8. Impatience with slow processes
"I can get impatient when decisions take a long time. Early in my career that came across as pushy. I've learned that slow processes usually have a reason, so now I ask what information people need to decide and I try to provide it. It's turned my impatience into something more useful."
9. Over-communicating in remote teams
"When I started working remotely I over-corrected and sent too many status messages, which created noise for my team. I now post one written update a day in our project channel and keep direct messages for things that are genuinely urgent. My teammates say it's much easier to follow."
10. Big-picture thinking (specialists)
"I sometimes focus so much on my own part of a project that I lose sight of how it affects other teams. I now add a quick check to my planning: who else does this touch? It has helped me catch dependencies before they become problems."
Answers to avoid
| Answer | Why it fails |
|---|---|
| "I'm a perfectionist." | Overused and usually a disguised strength. Interviewers hear it constantly. |
| "I work too hard." | Sounds rehearsed and avoids the question. |
| "I don't have any weaknesses." | Signals a lack of self-awareness. |
| A core skill of the job | An accountant who is "bad with numbers" will not get the offer. |
| A personal trait with no fix | "I'm lazy" or "I'm often late" raises red flags with no upside. |
How to find your own weakness
If you are struggling to choose, look at real evidence:
- Feedback from performance reviews or managers.
- Tasks you tend to postpone.
- Skills listed in job ads that you feel less confident about.
- Moments when a project went wrong and you played a part.
Pick one that is genuine, relevant enough to be credible, and that you have actually worked on. If you have not worked on anything yet, start now — even a week of deliberate effort gives you something honest to say.
Related questions you might hear
- "What would your manager say you need to improve?"
- "Tell me about a time you received critical feedback."
- "What skill are you currently working on?"
The same three steps apply. For behavioural questions, you can use the STAR method (Situation, Task, Action, Result) to keep your story tight.
Frequently asked questions
Can I give a weakness that is really a strength?
It is better not to. Interviewers recognise the trick. A modest real weakness with genuine progress is far more convincing.
Should I mention more than one weakness?
No, unless asked. One well-explained weakness is enough.
What if they ask for three weaknesses?
Prepare one main answer and two shorter ones, each with a brief improvement point.
Keep preparing
Pair this answer with a strong opening — see how to answer "tell me about yourself" — and a confident close with "why should we hire you?". Then check the role-specific questions in our interview preparation hub, and find your next role.