What Are Your Weaknesses: 15 Answers + Free Scored Drill

"What's your greatest weakness?" is the question everyone says is outdated and every interviewer still asks. Why? Because it's the fastest way to separate the self-aware candidates from the rehearsed ones. A strong answer takes 90 seconds. A weak one takes five and says nothing.

This page gives you a framework, 15 real answers, and a live drill so you can rehearse yours right now.

How do you answer "what are your weaknesses"?

Name one real weakness plainly in one sentence. Give one concrete example of when it showed up in your work. Describe the specific correction you're running — what you're doing about it. Skip the stock dodges ("I'm a perfectionist," "I work too hard"). The interviewer is scanning for self-awareness, growth orientation, and honesty under soft pressure; all three get graded in 45 to 60 seconds.

Why interviewers ask it (and what they're scoring)

The literal answer doesn't matter as much as what the answer reveals. Interviewers are scanning for three signals:

1. Self-awareness. Do you know how you work and where you struggle?
2. Growth orientation. Are you doing something about it, or just aware of it?
3. Honesty under soft pressure. Can you say something true about yourself without either deflecting or spiraling?

A bad answer ("I'm a perfectionist" / "I work too hard") fails all three. It signals that you either can't be honest with a stranger or haven't done the work to know yourself.

The framework: weakness + example + correction

Every strong answer has the same three beats. Memorize the shape, improvise the content.

Beat 1: Name the weakness, plainly. One sentence. No hedging. "I'm not great at delegating when I think I can do the task faster myself."

Beat 2: Give one concrete example. One specific time this weakness showed up in your work. The example proves the weakness is real and not rehearsed. "Last quarter I took on writing our Q3 OKR doc myself instead of handing it to my senior PM. I missed my Friday deadline and she had context I didn't."

Beat 3: Describe the correction. What are you actively doing? "Now I do a standing Monday 1:1 with her where we divide the week's docs. My calendar is lighter and her context shapes the output."

The correction is the most important part. Without it, the answer is just confession. With it, the answer is a story about someone who notices their gaps and closes them.

15 real answers that follow the framework

Use these as reference shapes. Don't memorize them verbatim — interviewers can tell.

1. Delegation. "I under-delegate when deadlines are tight. I rewrote two specs my team could have owned last quarter. Now I run a delegation audit every Monday with my lead."

2. Saying no. "I over-commit in scoping meetings because I don't want to seem like I'm slowing things down. I've started using the phrase 'let me get back to you by end of day' instead of nodding in the room."

3. Technical depth. "My SQL fluency is above average for a PM but not at the level of an analyst. I've been taking Jessica Anderson's advanced window-functions course and can now ship my own retention queries."

4. Public speaking. "I get tight in large group presentations — over 20 people. I joined a Toastmasters group in January and have delivered six talks since."

5. Receiving critical feedback. "My first instinct is to defend the work, which eats the first minute of any feedback conversation. I've started explicitly saying 'tell me everything, I'll respond after' and it's made reviews much more productive."

6. Long-horizon planning. "I'm great at 30-day execution, weaker at 12-month roadmapping. I've started shadowing our VP's quarterly planning meetings and drafted my first year-view last month."

7. Writing. "I edit for too long on the first draft. I've set a 25-minute pomodoro for first drafts and forced myself to publish at the bell."

8. Cross-functional empathy. "I default to engineering-first framing and have to work to see the marketing angle. I now include one marketing stakeholder in every scoping doc and it's changed my launch playbooks."

9. Asking for help. "I stay stuck too long before pinging a senior. I've added a rule: if I haven't moved in 45 minutes, I write a question in #help-me-debug."

10. Context switching. "Four-project days wreck me. I've dropped to two deep-work blocks per day and handle quick questions only between them."

11. Negotiation. "My first instinct in salary conversations is to accept the first offer. I worked with a coach, and my last two offers moved 15% each from the initial number."

12. Imposter feelings. "I downplay my own work when presenting to VPs. I now write a two-line 'what I want them to remember' note at the top of every exec doc. It forces me to state the strongest version."

13. Data rigor. "I've trusted directional metrics when I should be significance-testing. I've partnered with our data scientist to establish a minimum-sample threshold for any A/B call."

14. Meeting discipline. "I let meetings run long because I want every voice heard. I've started pre-writing the decision criteria before the meeting so I know when we're done."

15. Perfectionism — but real. "I rewrite emails more than I should. I give myself a two-pass limit — one for content, one for tone — and send."

What to avoid

• "I work too hard." Nobody believes this. It reads as deflection.
• "I'm a perfectionist." Same.
• "I can't think of one." This is the single worst answer. Read it as "I'm either not self-aware or not honest."
• A weakness that disqualifies you. Don't say "I struggle with deadlines" when applying to an engineering lead role. Pick something orthogonal to the core job.
• Listing five weaknesses. Pick one. Depth beats breadth.
• A "humble-brag" weakness. "I'm too detail-oriented" is a strength in a trench coat; interviewers hear it instantly.

What a scored answer actually looks like

Illustrative example — not a real user. The scorecard shape below is the same one the drill widget produces on your own answer.

Answer (first take, 42 seconds spoken):

"Um, I guess my greatest weakness is that I'm a perfectionist. I care a lot about my work and I want every deliverable to be really polished, which sometimes means I spend longer than I should on things. But I've been working on that, and I think it's actually helped me produce higher-quality work overall."

Overall score: 41 / 100

• Clarity 45 · Confidence 38 · Structure 42
• Conciseness 55 · Delivery 40 · Audience awareness 25

What the scorer flagged:

• Named weakness is the stock "perfectionist" dodge — interviewers grade it as a non-answer
• No concrete example — claim without evidence
• "Correction" is vague ("I've been working on that")
• Ends on a humble-brag ("helped me produce higher-quality work") which undoes the self-awareness signal the question tests for
• Hedges: "um," "I guess," "I think"

The credibility rewrite (same length, scores ~85):

"I under-delegate when deadlines are tight — I reach for the doc myself instead of handing it off. Last quarter I took on a 12-page quarterly-review write-up that my senior PM could have owned. I missed my Friday deadline because I was solo on it, and her context would have shaped the narrative better. Since then I've run a Monday delegation check-in with her — we split the week's docs and my calendar is lighter for the strategic work that actually needs me."

The rewrite moves: (a) a weakness specific enough to be credible, (b) a concrete example with a cost, (c) an active correction with mechanism + evidence it's working. The voice tightens because specificity crowds out hedges — "I guess" disappears when you actually know what you're saying.

Rehearse this answer out loud, now

Reading this guide isn't enough. You need to hear yourself say your answer three or four times before it sounds natural. Most candidates think they have an answer — then freeze when the question lands in a real interview.

Rehearse yours now. The drill above runs a 45-second timer and scores you on clarity, confidence, structure, conciseness, delivery, and audience awareness in under 60 seconds.