Why do interviewers ask what your greatest weakness is?
They are checking whether the rest of your answers can be believed. Someone who names a real limit, with a cost and a fix, sounds like a person who will report bad news early. Amazon writes this into its hiring principles: leaders are "vocally self-critical, even when doing so is awkward or embarrassing" (Amazon).
The answer also gets written down and scored. The US Office of Personnel Management says highly structured interviews are scored against benchmarks, often by a panel whose members rate each answer on their own first (OPM). Google says it asks every candidate the same questions and grades answers on an identical scale (Google re:Work). A vague weakness gives the interviewer nothing to write in that box.
If you're asked for strengths and weaknesses together, start with the strengths and weaknesses guide. This page goes deeper on the weakness half only: the four parts of an answer that holds up, six example answers you can adapt, and the follow-up questions that come next.
What makes a good answer to the weakness question?
A good answer has four parts. The weakness is true now, it has cost someone something at work, you follow a specific rule to manage it, and you admit it isn't fully solved. Said out loud, that takes about 60 seconds. Most weak answers drop the second part, because naming a cost feels risky.
| Part | What to say | Example line |
|---|---|---|
| 1. The weakness | One work habit, named in plain words | "I take on too much before I check my capacity." |
| 2. The cost | Who or what it affected, once, with a detail | "Two reports went out a day late last spring." |
| 3. The rule | A specific thing you now do every time | "I don't say yes the same day. I check my week first." |
| 4. The status | Where it stands today | "It's better. I still feel the pull to say yes." |
The rule is where most answers go soft. "I'm working on being more organized" is an intention, and nobody can check it. "I block 30 minutes every Friday to plan the next week" is a rule you either kept or didn't. Interviewers trust rules for the same reason they trust numbers.
Which weaknesses should you avoid?
Avoid four kinds of answer. A strength in disguise, like perfectionism, tells the interviewer you'll manage impressions. A weakness that disqualifies you for this job ends the conversation. A weakness you fixed years ago answers a different question, and a weakness about other people is a complaint that sounds like self-awareness.
- A strength in disguise: "I work too hard" or "I care too much." Interviewers have heard these many times.
- A disqualifying weakness: "I miss deadlines" for a project manager, or "I find numbers hard" for an analyst.
- A solved weakness: if it's fully fixed, it belongs in a story about growth instead.
- A weakness about others: "I get frustrated when people don't pull their weight."
- A weakness with no link to work: "I'm bad at cooking" reads as a dodge, and the follow-up will ask for a real one.
Pick from the middle ground instead: a habit that matters in the job, has caused a small and recoverable problem, and that you now manage with a rule. The best source is feedback you've actually received. The guide to answering questions about negative feedback covers how to find it.
Should you mention a health condition as a weakness?
You don't have to, and in most cases you shouldn't use one as your example. In the US, the EEOC says employers generally may not ask disability-related questions before making a conditional job offer, including "What impairments do you have?" (EEOC). Choose a work habit instead.
The same EEOC guidance says employers may ask whether you can perform the job's functions. So if a question is about the job itself, answer it directly. This is general information, not legal advice, and the rules differ outside the US.
What are good example answers to what is your greatest weakness?
Below are six example answers, each labelled with the kind of job it fits. The facts in them are made up, so swap in your own project, the person affected, the number and the rule you follow. If you can't name who your weakness affected, pick another one, because the follow-up will ask.
Example 1: saying yes too fast (coordinator or generalist roles)
My weakness is that I say yes to requests before I've checked what's already on my plate. Last spring that meant two weekly reports went to the sales team a day late, because I'd agreed to help with an event the same week. Now I don't commit on the same day. I tell people I'll confirm by end of day, and I look at my calendar first. It's much better, though I still feel the urge to say yes on the spot.
Example 2: writing too much (analyst or engineer roles)
I write long updates. I used to send status emails that walked through everything I'd checked, and my manager told me the decision she needed was buried in the last paragraph. One time a teammate missed a deadline change because it was in line nine. Now the first line of every update is the decision or the ask, and I keep the rest to five lines with a link to the detail. I still draft long, but I cut before I send.
Example 3: delegating late (first-time manager roles)
My weakness is holding on to work I should hand off. In my first six months leading a team of four, I kept the client reports myself because I knew them best. One person on my team told me in a one-on-one that she felt I didn't trust her with client work, and she was right. Now I list my tasks every Monday and hand off anything someone else could do at 80% of my standard. I still catch myself keeping things, so I ask my team to call it out.
Example 4: avoiding hard calls (sales or customer success roles)
When a client is unhappy, my habit is to write an email when I should pick up the phone. Writing feels safer. Last year a renewal got tense because I sent three careful emails over a week when a 10-minute call would have settled it. My rule now is that if a client's message has a complaint in it, I call within one business day and follow up in writing after. It still isn't my favourite part of the job, but I don't put it off.
Example 5: getting lost in detail with senior people (any role that presents upward)
When I present to senior leaders, I tend to start with how I did the work instead of what I found. In a quarterly review, our director stopped me four minutes in and asked for the answer. Since then I write one sentence with the finding and the ask, and I open with it. I keep the method in an appendix in case someone asks. I'm better at it, and I still rehearse the first 30 seconds before every review.
Example 6: not asking for help early (entry-level or new graduate roles)
I wait too long to ask for help. In my internship I spent most of two days stuck on a data import that my mentor fixed in 20 minutes once I finally asked. That delayed a handoff to another analyst. My rule now is that if I'm stuck for more than an hour, I write down what I've tried and send it to someone. Writing it down often solves it, and when it doesn't, the question is short.
Look at what the six have in common. Each one names a real habit, a cost that landed on someone else, a rule you could check, and an admission that it still takes effort. None of them is a disaster, and none of them is a disguised strength. Example 3 started with feedback from a colleague, which is often the easiest place to find a real weakness.
What follow-up questions come after the weakness answer?
Expect one of three follow-ups: who did it affect, is it still true, and what would your last manager say about it. A weakness picked for safety can't answer the first one. A real weakness answers all three quickly, because you learned about it from someone who was affected.
Example reply to "Who did it affect?": The sales team got their reports late twice, and their lead mentioned it to my manager. That's how I found out it was a pattern.
Example reply to "Is that still true?": Partly. I haven't missed a report since I started confirming by end of day, but I still notice the urge to say yes straight away.
Example reply to "What would your manager say?": She'd say I used to overcommit and that I'm now careful about it. She'd probably also say I sometimes take a few hours to confirm things she'd like answered faster.
The last reply shows a useful move: when the fix has a side effect, name it. That shows you understand the trade-off. The same habit of owning the cost works in answers about a mistake you made and answers about a time you failed.
How long should your weakness answer be?
Aim for 45 to 75 seconds, which is usually 100 to 150 words spoken. That's long enough for the four parts and short enough that the interviewer can ask a follow-up. If your answer runs past 90 seconds, the cost part is usually too long, and you're defending yourself instead of describing the habit.
Practise it out loud with a timer. Write the four parts as four short lines, then say them in your own words without reading. If you trip over the rule, it isn't specific enough yet. The guide to answer length covers timing for other common questions.
What should you do after the interview?
Write down how the interviewer reacted and which follow-up they asked, the same day. If they pushed on whether the weakness was still true, your status line needs work. The free debrief template gives you one page to note each answer and the moment it went flat.
If you'd like to rehearse before the next round, the Prept Mock room asks you questions out loud on a clock and scores each answer out of 10 against your resume. It's included in the free plan. Then go back to why do you want to work here, which is often asked in the same interview.