Interview questions
How to answer “What is your greatest weakness?”
Most people dread this one and answer it with a strength in disguise. Interviewers have heard "I'm a perfectionist" hundreds of times. A real, specific weakness with a real fix is what lands.
What the interviewer is really asking
Everyone has weaknesses, and the interviewer knows it. The question tests whether you can see your own and talk about them honestly.
They also want to know whether you do anything about it. The weakness itself matters less than what you've done since you noticed it.
And they're quietly checking for a dealbreaker: a weakness that is the core of the job, or one that sounds like a character problem.
The structure: name it, show it, fix it
- Name it. A real weakness, in one sentence. Pick something true that isn't the center of this job.
- Show it. One short example of a time it cost you something. This is what makes it believable.
- Fix it. What you do about it now, specifically, and how it's going. Spend most of the answer here.
Aim for 45 to 60 seconds out loud, roughly 100 to 150 words. Get through the weakness quickly and spend the time on the fix.
An example answer
An analyst whose weakness is speaking up in big meetings. Everything in brackets is a fact only you know, so fill it in with something true.
Honestly, speaking up in large meetings hasn't come naturally to me.
In a small group I'm fine, but in a big room I used to hold my ideas until afterwards.
That cost me on [a project where it mattered],
when a problem I'd spotted didn't come up until [how late it came up].
So I changed how I prepare. Before any big meeting I write down the one point I want to make,
and I make it early, before the discussion moves on.
I've also [a real step you've taken, like a class or volunteering to present].
It's still not my favorite thing, but I don't leave meetings with things unsaid anymore.
Why it works
- The weakness is real and specific, not a compliment dressed up as a flaw.
- It matters for the job but isn't the job. An analyst is hired to find problems, not to run meetings.
- The example shows a real cost, which is what makes the rest believable.
- Most of the answer is the fix, and it ends on progress, not on a claim that it's solved.
Write your own answer
Paste in your role and a few real facts, and the free answer generator builds this answer around them. It won't invent your numbers: anything only you know comes back in brackets.
Write my answer, freeAdjusting it to where you are
Recent graduate. Pick something from school or an internship, like asking for help too late or underestimating how long a project takes. Then show the habit you built to fix it.
Moving into management. Delegating is the honest classic here: you're used to doing the work yourself. Show the moment you saw it slowing the team down and what you do differently now.
Technical role. A non-technical skill is usually safer than a gap in the core stack: explaining work to non-engineers, estimating, or pushing back on scope. If it is a technical gap, name what you're doing to close it.
Common mistakes
- The disguised strength. "I work too hard" and "I'm a perfectionist" read as dodging the question, which is the opposite of what it tests.
- A weakness that is the job. Don't tell an accounting team you're careless with details. Pick something real that sits at the edge of the role.
- Stopping after the weakness. If you never get to the fix, all they remember is the flaw.
- Something that sounds like character. A temper, being unreliable or not getting along with people raises doubts no fix can settle. Keep it a work skill.
- Saying it's completely fixed. It sounds false, and then why mention it? "Better, and still working on it" is more believable.
- Inventing the story. The follow-up questions will find the holes. Use something that really happened.
The question you didn't practice
Practicing the common questions helps. The hard part is the one you didn't see coming, asked live while someone waits for you to think. InterviewWhisperer is a Mac app that hears the interviewer and puts an answer like the one above on your screen while you talk, built from your resume and the job description. Your first 30 minutes of live answers are free, no card.
Questions people ask
Can I say I don't have any weaknesses? No. It tells the interviewer you either can't see your own weaknesses or won't admit them, and those are exactly the two things the question tests.
Is "I'm a perfectionist" a bad answer? Usually, because it's the most common dodge. If perfectionism really costs you something, like slow reviews or missed deadlines, name that cost and talk about how you handle it.
What weaknesses are safe to mention? Real work skills that aren't central to the role and that you can improve, such as delegating, public speaking, saying no, giving direct feedback, or a tool you're still learning.
How long should my answer be? About 45 to 60 seconds. Name the weakness quickly, give one short example, and spend most of the time on what you're doing about it.
What if they ask for more than one weakness? Have a second one ready with the same structure, shorter. It's a common follow-up when the first answer sounded rehearsed.