How to Answer "What Are Your Weaknesses?" in an Interview

What this question is actually testing

It's not really about the weakness itself — everyone has gaps, and no interviewer expects a flawless candidate. What they're actually evaluating is whether you have enough self-awareness to notice a real limitation in yourself, and enough initiative to have already done something about it without being told to. A disguised strength ("I care too much about quality") answers neither of those things, which is exactly why it reads as evasive rather than honest.

A structure that sounds credible

Four parts, in this order:

Name a real weakness: Something genuine, ideally not directly core to the job you're interviewing for. If you're applying for a backend role, "I'm still building confidence presenting to large groups" is safer than "I struggle with system design."

Give one concrete example of its impact: A specific moment it actually showed up, briefly — not a confession, just enough detail to prove it's real rather than invented for the interview.

Explain the specific action you took: A course, a habit, a deliberate practice, feedback you asked for — anything that shows you noticed the gap on your own and did something about it before this interview forced the question.

Show the current state: Not "fully fixed" — that reads as untrue for most real weaknesses — but measurably better, with the honest acknowledgment that it's still something you keep working at.

Which weaknesses are safe to mention

Safe territory: things that are real but peripheral to the role's core responsibilities — public speaking, delegating instead of doing everything yourself, impatience with slow processes, or a skill you're actively building but don't yet use daily. Risky territory: anything that's actually a requirement listed in the job description, anything about reliability or integrity (showing up late, missing deadlines), and anything so vague it could describe anyone.

Two example answers

For an engineering role: "I used to write code and only ask for review right before merging, which meant I'd sometimes go too far down a wrong path before anyone caught it. On my last project I started sharing a rough design doc before writing any code, which cut my rework way down and got the team more involved earlier. I still have to deliberately remind myself to do it on smaller tasks where it feels like overkill."

For a non-technical role: "I tend to want to double-check everything myself before handing it off, which doesn't scale once you're managing more than one or two things at once. I've been working on defining clear checkpoints upfront instead of reviewing everything at the end, which has made me faster to trust people with bigger pieces of work. It's still something I have to consciously practice."

Common mistakes that undercut this answer

• A disguised strength ("I'm too much of a perfectionist") — interviewers have heard this hundreds of times and it signals you didn't prepare a real answer.
• Naming something that's actually a hard requirement of the role you're interviewing for.
• Claiming it's "fully fixed now" — growth is more believable than a finished transformation, and it invites a harder follow-up question you may not be ready for.
• Being so self-critical it raises doubt instead of showing growth — this isn't a confession booth, it's one data point in a longer conversation.
• Answering with no example at all, leaving the interviewer to take your word for it with nothing concrete behind it.

How to prepare it in advance

Pick your weakness before the interview, not during it — this is one of the few questions you know is coming, so there's no reason to improvise it live. Re-read the job description first and rule out anything that overlaps with its core requirements. While you're at it, browsing a few open roles in your field is a quick way to notice which skills keep coming up as non-negotiable, so you know exactly what to steer clear of.

The takeaway

A real weakness, a concrete example of its impact, a specific action you took, and honest evidence of improvement — that combination sounds like self-awareness. A disguised strength sounds like avoidance. Interviewers can tell the difference immediately, so prepare the honest version ahead of time.