How to Answer 'What Is Your Greatest Weakness?' (With Real Examples)
Most candidates either dodge this question or over-prepare a fake answer that fools no one. Both approaches backfire.
Here's what interviewers are actually looking for, the three-part framework that works, and eight complete example answers you can adapt to your situation.
Why Interviewers Ask This
This question is not a trap. Interviewers aren't hoping you'll reveal a career-ending flaw.
They're checking two things:
- Self-awareness. Can you identify where you fall short? Someone with no weaknesses is either lying or has no insight into their own performance — neither is a good hire.
- Coachability. Are you actively working on it? A person who names a weakness and describes what they're doing to improve signals that they grow. That's what managers want on their teams.
A genuine, specific, improvement-focused answer scores higher than any polished deflection.
What Makes a Bad Answer
Fake strengths disguised as weaknesses. "I'm a perfectionist." "I work too hard." "I care too much about the quality of my work." Interviewers have heard these so many times they're effectively a red flag. They signal that you're not willing to be honest — which raises questions about everything else you've said.
Deflection. "I don't really have any major weaknesses right now." This signals a lack of self-awareness, not confidence.
Confessing a job-critical flaw. Applying for a role that requires public speaking and saying "I'm terrified of public speaking and haven't made any progress" is a different situation. There's a difference between a genuine weakness you're working on and a disqualifying gap.
Vague non-answers. "I sometimes struggle with work-life balance." Without specifics or a description of what you're doing about it, this is noise.
The 3-Part Framework
Every strong answer has three parts:
1. Name the real weakness. Be specific. Not "communication" — say which aspect. Not "time management" — say what specific pattern causes problems.
2. Show what you're doing about it. Name a concrete action: a course, a process change, a habit, a feedback loop. "I'm working on it" doesn't count — describe what you're actually doing.
3. Connect it to your growth. Show that this is an area of active development, not an unexamined problem. A sentence about the progress you've made or what you've learned is enough.
8 Real Example Answers
1. Public Speaking
"I've always been more comfortable in small-group conversations than presenting to large audiences. When I had to lead quarterly business reviews at my last company, I'd often rush through slides and lose the thread. I've been addressing this directly — I joined a Toastmasters chapter eight months ago and have now given over a dozen prepared talks. I'm still working on it, but I'm no longer dreading those presentations the way I used to."
2. Delegating Tasks
"My instinct has always been to handle things myself rather than hand them off — partly because I care about quality, partly because I didn't want to overload colleagues. The problem is it created bottlenecks and prevented the people around me from developing. I've been working on this deliberately: at my current job I assign ownership at the start of every project rather than the end, and I've gotten better at accepting that someone else's approach can be as good as mine, even if it's different."
3. Being Overly Detail-Oriented
"I have a tendency to get into the details of something when the bigger picture needs the attention. Early in my career this meant I'd spend too much time refining work that was already good enough, and miss the forest for the trees. I've gotten better at this by setting explicit 'done' criteria before I start any task — if the work meets the standard, I ship it. It's helped me move faster without sacrificing the quality I actually care about."
4. Saying Yes to Too Much
"I have a hard time saying no when someone needs help, which has led to me taking on too much and delivering some things later than I should have. I've learned to be more honest upfront — when a new request comes in, I now ask myself whether I can genuinely commit to the timeline before agreeing. I've also started being more transparent with my manager about capacity rather than trying to figure it out alone. It's a work in progress, but I rarely over-commit the way I used to."
5. Getting Up to Speed in New Technical Tools
"When I move to a new tool or platform, I take longer than I'd like to get fully comfortable with it. I've noticed I rely on what I already know and avoid the unfamiliar parts until I have to use them. I've started addressing this by spending the first week with any new tool deliberately exploring its features — not just the ones I need immediately. It's made me more confident and means I'm not discovering key functionality months into using something."
6. Difficulty with Ambiguity
"Early in my career, I was uncomfortable when projects didn't have clear requirements or direction. I'd either wait for clarity that wasn't coming or ask too many clarifying questions before making any progress. I've gotten significantly better at this — I now try to define the most reasonable interpretation of an ambiguous brief, move forward on it, and check in at natural checkpoints rather than stalling at the start. Working at a startup for the last two years has pushed me to get comfortable with uncertainty faster than anything else."
7. Impatience
"I tend to move quickly and expect others to move at the same pace — which I've learned isn't always fair or realistic, especially on cross-functional projects where teams have different priorities and constraints. I've worked on this by being more explicit about timelines upfront and asking what's needed from my side to unblock others, rather than treating delays as a personality flaw in whoever's slower. I've also gotten better at recognizing when my impatience is about the work and when it's just me being frustrated."
8. Asking for Help
"My default is to try to figure things out on my own before asking for help — which can be a strength for independent work but a liability when I'm new to something or genuinely stuck. I've spent time on this specifically over the past year: I now set a personal time limit before asking for help rather than letting it stretch indefinitely. The change has made me faster on complex problems and, honestly, has improved my relationships with colleagues who want to help but weren't getting the chance."
What to Avoid: 5 Answers That Will Tank Your Interview
1. "I'm a perfectionist." Overused, sounds fake, signals you're not willing to be honest.
2. "I work too hard / I care too much." Same problem. Interviewers have heard this from thousands of candidates. It signals evasion.
3. A weakness that disqualifies you. "I'm not very good with numbers" for an analyst role. "I hate dealing with people" for a customer-facing job. Know what the role requires and pick something outside that core.
4. A laundry list. One weakness, well-answered, is far stronger than three weaknesses mentioned superficially. Don't volunteer more than asked.
5. A weakness with no follow-through. "I sometimes struggle to speak up in meetings" with no explanation of what you're doing about it reads as unresolved — which is exactly what you don't want.
How to Pick Your Weakness: 3 Criteria
1. It's genuine. You should actually recognize this in yourself. Invented weaknesses sound hollow — experienced interviewers hear dozens of answers a week and can usually tell.
2. It's not job-critical. Picking a weakness that directly undermines your ability to do the job is unnecessary. There's almost always a genuine developmental area that isn't disqualifying.
3. You're actively working on it. The most important part. A weakness you've identified, named specifically, and are doing something concrete about shows exactly the kind of self-aware, growth-oriented person most companies want to hire.
FAQ
Q: Should I pick my biggest weakness or a "safe" one? A: Pick a genuine one that you're actively working on — and that isn't central to the job you're applying for. "Safe" weaknesses that are actually strengths are transparent and annoying. Real ones, handled well, are impressive.
Q: What if the interviewer asks for more than one weakness? A: Give two. Pick a second one that's also genuine and also has a clear improvement narrative. Don't volunteer a third unless explicitly asked.
Q: How long should my answer be? A: 60–90 seconds. Name the weakness, explain the pattern briefly, describe what you're doing about it, and say what's changed. Don't over-explain or apologize.
Q: Can I say I'm working on something that's already mostly fixed? A: Yes — just be accurate about where you are. "This used to be a significant weakness and I've made a lot of progress, but I still catch myself defaulting to old habits occasionally" is both honest and shows growth.
Q: What if I'm asked this question at the end of a panel interview vs. a first-round screen? A: The framework is the same either way. In a late-round panel, your answer may face more follow-up — expect questions like "Can you give me a specific example?" Have a STAR story ready to back up whatever weakness you name.
Walk Into Every Interview Prepared — Not Just for This One Question
The weakness question is one of dozens of questions that separate prepared candidates from unprepared ones. The Career Toolkit has answer frameworks for every interview question you're likely to face — behavioral, situational, and closing — plus salary negotiation scripts and templates. One-time price, $39.
Get every interview question answered with the Career Toolkit → View the Career Toolkit
Also useful:
Ready to level up your job search?
ATS-optimized templates, cover letters, and interview prep — one-time price.