How to Answer 'What Is Your Greatest Weakness?'

"What's your greatest weakness?" is a trap only if you treat it like one. Interviewers aren't hoping you'll disqualify yourself. They're checking for self-awareness and whether you actively work on your gaps.

What not to say

• The humblebrag: "I'm a perfectionist / I work too hard." Interviewers have heard it a thousand times and it reads as evasion.
• A real dealbreaker for the role: "I'm bad at writing code" in a software interview.
• "I don't have any weaknesses." Instant credibility loss.

The framework: real weakness + active correction

Name a genuine weakness that isn't central to the job, then spend most of your answer on what you're doing about it. The correction is the part they're actually grading.

Example

"Early on I struggled to delegate — I'd take on too much because I trusted my own execution. It bit me when I burned out mid-project and became the bottleneck. Since then I've made myself hand off at least one meaningful task per sprint and write clearer specs so others can own work end-to-end. My last project shipped faster specifically because I wasn't the single point of failure anymore."

That answer works because it's specific, shows a real consequence, and demonstrates a system for improvement.

Pick the right weakness

Good candidates: public speaking, delegation, saying no to scope creep, over-indexing on detail early in a project, impatience with slow processes. Choose something true, something you've made real progress on, and something that won't sink your candidacy for this role.

Rehearse the correction, not just the confession

The mistake most people make is nailing the weakness and mumbling the fix. Flip the ratio. If you want to pressure-test your answer, Understudy can run it back to you in a mock interview and flag whether it reads as self-aware or defensive.