Updated
“What Is Your Greatest Weakness?” — How to Actually Answer It
This question isn't designed to trap you into confessing a flaw — it's testing whether you can be honest about yourself and show you actively work on your gaps. Here's a formula that works, 15 real weaknesses with sample answers, and the clichés every interviewer sees through instantly.
The 4-Part Formula for Answering
Pick a real weakness — genuinely true
Interviewers ask this question dozens of times a week; a rehearsed non-answer is instantly recognizable. Choose something actually true about how you work, ideally minor enough not to disqualify you but real enough to sound honest.
Keep it unrelated to the job's core requirement
A weakness in public speaking is a bigger problem for a sales role than for a backend engineering role. Pick something that doesn't undercut the specific skill this job depends on most.
Show the concrete steps you've taken
This is the part that actually matters — not the weakness itself, but the evidence of self-awareness and initiative. Name a specific action: a course, a tool, a habit change, a process you built for yourself.
End on where you are now, not where you started
Close with the current state, not the struggle: 'I still have to be deliberate about it, but it's no longer something that slows my work down.' The interviewer should walk away thinking about your growth, not your flaw.
8 Good Weaknesses to Say in an Interview
Real weaknesses, applied through the formula above — adapt the wording to something genuinely true for you rather than reciting one of these verbatim:
"Presenting to large groups used to make me genuinely anxious — I'd over-prepare and still stumble. I started volunteering to lead our team's weekly standups specifically to get more reps, and I joined a local Toastmasters group for six months. I still prepare more than most people for presentations, but it's no longer something I avoid."
"I default to doing things myself rather than handing them off, because I trust my own execution more. It became a real bottleneck when I started managing a small team. I now block 15 minutes at the start of each week specifically to identify what should go to someone else, and I've gotten much more deliberate about it — though it's still a habit I have to actively maintain."
"I have a hard time turning down requests, which used to leave me overcommitted and working late to cover it. I started using a simple rule: before agreeing to anything new, I check it against my current workload out loud with whoever's asking. It's made my 'yes' actually mean something, and it's cut down significantly on last-minute scrambling."
"I can go deeper into the details of a problem than a deadline sometimes allows — I want everything to be exactly right. I've built in explicit checkpoints for myself: at certain milestones I force a step back and ask whether the level of polish still matches what's actually needed. It's helped me ship faster without losing the quality I care about."
"I get frustrated with unnecessarily slow processes, and early in my career that frustration sometimes showed. I've learned to separate pushing for efficiency from how I communicate about it — I now bring data and a proposed fix instead of just voicing frustration, which gets a much better response and actually changes things."
"I do my best work with clear direction, and I used to stall when a project was genuinely open-ended. I've started treating ambiguous situations as a first step of their own — I now spend the first hour making my own assumptions explicit and confirming them with a quick check-in, rather than waiting for someone to hand me clarity."
"Receiving critical feedback live, in a group setting, used to put me on the defensive before I'd even processed what was said. I've worked on pausing and asking a clarifying question first instead of responding immediately, and I now actively ask for feedback more often in lower-stakes settings so it doesn't feel as loaded when it happens."
"Quantitative analysis isn't my natural strength — I lean more toward qualitative thinking. Because data literacy matters everywhere now, I took a self-paced course on spreadsheet analysis and make a point of asking data-oriented colleagues to walk me through their reasoning, which has closed the gap a lot faster than I expected."
Answers That Instantly Signal You're Dodging
Interviewers ask this question constantly — these answers are recognized within the first sentence:
The most recognized dodge in interviewing — it's a disguised brag, and every interviewer has heard it a hundred times. It signals you didn't take the question seriously.
Same problem as perfectionism: it's a strength wearing a weakness costume. Interviewers ask this question specifically to test self-awareness, and this answer demonstrates the opposite.
Vague, unfalsifiable, and impossible to follow with a concrete improvement story — which is the actual point of the question.
Naming something true but stopping there is almost worse than a cliché — it answers only half the question and leaves the interviewer with just the negative, no context for how you handle it.
Naming poor attention to detail for a bookkeeping role, or discomfort with public speaking for a sales role, actively works against you rather than just being a neutral answer.
The tell isn't the weakness itself — it's whether the answer includes a real, specific improvement story. That's what separates a strong answer from a rehearsed one.
Weaknesses Question FAQ
What is the best weakness to say in a job interview?
One that's genuinely true, not central to the job's core requirement, and paired with a specific, concrete step you've taken to improve it. There's no single universal best answer — the right one depends on your actual work habits and the role, but common strong choices include delegating, public speaking, impatience with slow processes, and working with ambiguity.
How do I answer 'what is your greatest weakness' without sounding fake?
Avoid disguised-strength clichés like 'I'm a perfectionist' or 'I work too hard' — interviewers hear them constantly and they signal you're dodging the question. Instead, name something real, briefly explain how it's shown up in your work, then spend most of your answer on the specific action you took to address it.
Should I ever say I have no weaknesses?
No. Claiming no weaknesses reads as either dishonest or lacking self-awareness, both of which are worse outcomes than naming a real, minor weakness with a genuine improvement story.
How long should my answer be?
About 45-60 seconds when spoken: 10-15 seconds naming the weakness and a brief example of how it's shown up, then the majority of the time on what you've actively done to improve it and where things stand now.
Can I use the same weakness answer for every interview?
The core weakness and improvement story can stay consistent, but adjust which weakness you lead with based on the role — a weakness that's a bigger risk for one job (e.g., public speaking for a sales role) is often a safe, minor choice for a different one (e.g., a backend engineering role).
Get the full interview playbook
50 tips covering research, behavioral questions, salary negotiation, and follow-up.