"What's your biggest weakness?" is a trap on both sides. Candidates fear it because they think any honest answer torpedoes the offer. Interviewers half-hate it because they hear the same three fake answers from everyone ("perfectionist", "I work too hard", "I'm too detail- oriented"). The fix is being honest in a specific way.

Three-part structure. The weakness (real, specific, not fatal). What you've done about it. What changed. Done.

The fake answers everyone hears

According to a LinkedIn talent survey of recruiters, the three most-cited red-flag responses to this question are:

"I'm a perfectionist." Reads as either a humblebrag or a lie. Recruiters discount it.
"I work too hard." Same problem.
"I have no weaknesses." Self-awareness signal of zero. Worst of the three.

The panel knows you have weaknesses. They want to see if you know what they are.

The 3-part structure

The weakness, real and specific. One sentence. A skill or habit that genuinely isn't your strongest. Picked from a domain where being weak isn't fatal for the role.
What you've done about it. Two or three sentences. Specific actions, not "I'm working on it".
The evidence it's improving. One sentence. A concrete data point or recent example.

Total length: 45 to 60 seconds. Long enough to be substantive. Short enough that you don't dig a hole.

Real example (backend engineer)

"I'm not naturally good at delegating. For most of my career I shipped the trickiest parts of a project myself rather than handing them to someone else who could learn from doing them."

"Last year my manager flagged it. I started forcing myself to assign one piece of complex work per sprint to an engineer who hadn't done that thing before. I do the design review with them, but I don't take the keyboard. It's slower for the first sprint and faster for the next three."

"Last quarter two of my reports shipped database migrations end-to-end that I would've done myself six months earlier. That's the evidence it's actually working."

That answer works because the weakness is real (a specific senior-engineer failure mode), the action is specific (one piece per sprint), and the evidence is measurable (two engineers shipped migrations they hadn't before).

Real example (early-career / new grad)

"I'm slow at reading other people's code. When I join a new codebase I want to understand everything before I commit a change, and that costs me time my team doesn't have."

"My fix this year was to time-box it. I give myself 90 minutes to skim a module, then I write the smallest change I can, ship it as a draft PR, and let review feedback teach me the rest. Two of my PRs the last month were merged with zero review comments. Six months ago I was getting fifteen."

Weaknesses to pick from (and ones to avoid)

Safer picks for an engineering role:

Delegation / over-ownership
Time-to-context on new codebases (early career)
Public speaking / large-group presentations
Saying no to scope creep
Documentation discipline
Async written communication

Avoid:

Anything in the job description as a core skill
Things that suggest you can't be trusted (lateness, missing deadlines, ghosting)
Soft-skill basics for the role (don't say "I'm bad at working with people" for any role)
Strengths in disguise. The interviewer can tell.

What we hear in mock rounds

The most common LRAI-coached candidate mistake on this question is choosing a weakness that's too vague. "Sometimes I take on too much." OK, but what specifically, when, and what did you do about it? The panel reads vagueness as a stalling tactic. Specificity reads as self-awareness.

The second most common mistake is no third part. Candidates land the weakness and the action, then stop. The evidence sentence is the close. Don't skip it.

Run the weakness answer in a mock

LastRound AI runs behavioural mock rounds with the weakness question as a fixed slot. Get specific feedback on which part of your three-part answer isn't landing.

LastRound AI

"What's Your Biggest Weakness?": How to Actually Answer Without Sabotaging Yourself