How to Answer: What Is Your Greatest Weakness? (with Scored Examples)
Where does a question designed to expose weakness actually start? With the answer candidates rehearse most and use worst. The humble-brag and the unmitigated real flaw are both disqualifiers — and experienced interviewers can spot both in the first sentence.
Practice this out loud. Get scored in 30 seconds.
Voice mock interview with AI scoring — built because ChatGPT can chat, but can't pressure-test you or grade you.
Try the demo →Why this matters
Interviewers ask this question to assess self-awareness, honesty, and the maturity to manage your own development. It is not a trap — it is a signal check. Candidates who give a polished non-answer ('I care too much about quality') tell the interviewer that they are not self-aware or that they are not willing to be honest, either of which is a red flag on a team that needs to give and receive direct feedback. Candidates who name a real weakness but have no mitigation plan signal that they are aware of the gap but have done nothing about it. The strongest candidates name a genuine cognitive or skill weakness, describe a specific system or process they built to manage it, and provide measurable evidence that the mitigation is working. This answer demonstrates exactly the kind of proactive, growth-oriented mindset that high-performing teams want to hire.
What to think about
- I tend to over-index on data before making decisions, which slows me down in fast-moving situations. I have been working on this by setting hard time limits for analysis phases — I give myself a fixed window, note what data is still missing, and make the call with the information I have. My last three sprint planning cycles ran on time as a result.
- I struggle with delegating work I know I could do faster myself. I have put a deliberate system in place: before starting any task, I ask whether this is something a teammate could handle with one hour of context from me, and if so I hand it off. My team's output doubled in the last quarter partly because of this.
- Public speaking used to make me freeze. I joined a Toastmasters group 18 months ago and now present at our monthly all-hands. I am still not the most comfortable speaker in the room, but I no longer avoid opportunities that require it.
- I sometimes lose track of the big picture when I am deep in execution mode. I now do a weekly 30-minute review where I check what I am working on against the top three priorities for the quarter. That single habit has stopped two projects from going in the wrong direction.
- I have historically been slow to raise concerns when I disagree with a decision. I have been working on this deliberately over the past year by practicing direct, specific objections in one-on-ones before escalating to group settings. My manager has specifically noted the improvement in my last two performance reviews.
The framework
Structure your answer in three parts. First, name the real weakness: a genuine cognitive or skill limitation, not a character trait you are secretly proud of. Second, describe the specific mitigation system you built to manage it — this should be concrete enough that the interviewer can picture what you actually do differently. Third, share measurable progress or an observable outcome that shows the mitigation is working. The whole answer should take 60 to 75 seconds. The weakness should be real enough to be credible but not so fundamental that it would disqualify you from doing the core job. For example, if you are applying for a public-facing communications role, do not say your weakness is public speaking.
Common mistakes
- The humble-brag: 'I am a perfectionist' or 'I work too hard and take on too much.' Interviewers have heard these thousands of times. They immediately signal low self-awareness and a lack of willingness to be honest, which is far more damaging than naming an actual weakness.
- Naming a weakness with no mitigation. Saying 'I sometimes struggle with time management' and stopping there suggests you are aware of the problem but have done nothing about it. Every weakness answer needs a system.
- Naming a disqualifying weakness. If the role requires strong written communication and you say your writing is weak, you have just argued yourself out of the job. Pick a weakness that is real but not central to the core competencies listed in the job description.
- Being so vague that the answer is meaningless. 'I sometimes have trouble prioritizing' needs specifics: which situations, what you do now, and what changed. Vague answers suggest you have not actually thought carefully about your own development.
- Pivoting too quickly to a strength. Some candidates answer the weakness question and then immediately add 'but on the other hand, my biggest strength is...' This pivot undermines the whole answer and makes it sound like you could not handle sitting with the vulnerability for even 30 seconds.
Bad answer vs strong answer (scored)
Weak answer
I think my biggest weakness is that I am a perfectionist. I always want to make sure everything is done to the highest standard and sometimes that means I spend more time on things than I probably need to. But I am working on being more efficient and learning when good enough is okay.
What's wrong
- Perfectionism is the single most overused fake weakness in interviews. It signals to the interviewer that the candidate is either not self-aware or unwilling to be honest, both of which are more concerning than any real weakness.
- The mitigation is completely vague. 'Learning when good enough is okay' is not a system — it is an intention. A real mitigation would describe a specific behavioral change with a measurable outcome.
- No evidence of progress is provided. Without a concrete outcome, the interviewer has no reason to believe the 'improvement' is real.
Stronger answer
My genuine weakness is that I have historically been slow to escalate risks. When I can see a project heading toward a problem, my instinct has been to try to solve it quietly myself rather than flag it early to stakeholders. That has occasionally meant surprises that could have been caught sooner. About a year ago I put a concrete rule in place: any risk that would affect the timeline or scope by more than ten percent gets flagged in my weekly status update the same week I identify it, not after I have had time to fix it. My project manager told me in my last review that my risk communication has been one of my most improved areas over the past year. The weakness is still there — I have to work against the instinct — but the system means it no longer creates the downstream problems it used to.
Related practice
Quick answers
Should I mention a weakness that is relevant to the job?
You should mention a real weakness, but not one that is directly central to the core requirements of the role. If the job description lists data analysis as the primary skill required, do not name data analysis as your weakness. Instead, choose something real from the periphery of the role — a process habit, a communication tendency, or a skill adjacent to but not central to the core job function. Real but not disqualifying is the target zone.
What if I have been working on my weakness for a long time and still have not fixed it?
That is completely acceptable and actually more credible. Interviewers do not expect you to have fully solved your weaknesses. They want to see that you are self-aware about the gap, that you have a real system in place to manage it, and that you are making measurable progress even if the weakness is not gone. A weakness you have been managing actively for two years with visible improvement is a stronger answer than one you resolved completely six months ago.
Is it ever okay to name more than one weakness?
Generally no. Naming multiple weaknesses in a single answer can make you appear scattered or overly self-critical, and it gives the interviewer more surface area to probe. Pick your single best answer — the one where you have the most specific mitigation system and the clearest evidence of progress — and develop it fully. Depth beats breadth here.
How do I know if my mitigation system actually sounds convincing out loud?
You probably do not, until you hear yourself say it. Odin scores your weakness answer on specificity, structure, relevance, and delivery, and gives you feedback the way a real interviewer would. Most candidates find their answer sounds far more vague out loud than it did in their head. The scoring shows you exactly where your mitigation system is underspecified and where your evidence of progress is missing — so you can fix it before the interview that matters.