About us

How to answer 'what is your greatest weakness' without flinching

Why interviewers ask about your greatest weakness, the honest-plus-fix structure, six worked answers for different roles, and the answers that backfire.

By CredibleNow Editorial | Job Search |
Read time: 9 mins
How to answer 'what is your greatest weakness' without flinching
Photo: USDAgov (Public domain)

“What is your greatest weakness?” is the interview question people dread most and prepare for least. The usual response is to reach for something that is secretly a strength (“I’m a perfectionist,” “I work too hard”) and hope the interviewer does not notice. They notice. They have heard it four times that week.

The question is answerable, and answering it well is one of the easier ways to stand out, precisely because so many people fumble it. What follows is why interviewers ask, a structure that produces an honest answer without handing them a reason to reject you, six complete worked answers for different kinds of role, the answers that reliably backfire, and how to handle the variations.

Why interviewers still ask

Some interviewers ask because it is on the list. But the good ones ask for three specific reasons, and it helps to know which one you are answering.

Self-awareness. Can you see your own work clearly? People who cannot name a weakness usually cannot take feedback either, and that is expensive to manage.

Coachability. What have you done about it? An honest weakness with no attempt at a fix is a warning sign. A weakness you have visibly worked on is close to a strength.

Honesty under mild pressure. The question is slightly uncomfortable by design. The interviewer wants to see whether you deflect, bluff, or answer straight. Answering straight is worth more than the content of the answer.

There is also a fourth, less flattering reason: some interviewers are checking that your weakness is not the job. A candidate for a bookkeeping role who says “I’m not great with detail” has ended the interview, however they phrase the fix.

The honest-plus-fix structure

A good answer has four parts and takes forty-five seconds to a minute. Longer and you are dwelling on it; shorter and it sounds rehearsed.

  1. Name a real weakness, specifically. Not “communication,” which means nothing, but “I tend to write emails that are too long when the situation is simple.” Specific weaknesses sound true. Vague ones sound like evasion.
  2. Give one short example of how it has shown up. A sentence or two. This is what makes the interviewer believe you.
  3. Say what you do about it. A concrete habit, tool or approach, not “I’m working on it.”
  4. Show it is improving, with a small piece of evidence. The point is not that the weakness is gone. The point is that you noticed, acted, and can see the difference.

Then stop. Do not add a second weakness, do not circle back to reassure them, do not say “but I think that also makes me a strong candidate because.” End on the evidence and let them ask the next question.

Choosing the right weakness

The weakness you pick has to pass five tests.

  • It is real. You will be asked follow-ups, and an invented weakness collapses under one.
  • It is not central to the job. Delegation is a fine weakness for an individual contributor and a bad one for a team lead candidate.
  • It is a working habit, not a character flaw. “I sometimes take on too much” is a habit. “I have a temper” is a flaw, and no fix makes it safe to say.
  • It has a fix you can describe. If you do not know what to do about it, pick something else.
  • You can talk about it calmly. If naming it makes you defensive, the interviewer will see that, and the defensiveness becomes the weakness.

Common weaknesses that pass all five, for most roles: reluctance to delegate; over-preparing before checking in; taking on too much and struggling to say no; impatience with slow processes; discomfort presenting to senior audiences; a tendency to go quiet in large meetings; over-long written communication; being slow to ask for help; a specific technical skill gap that is not a core requirement.

Six worked answers

Each follows the four-part structure. Adapt the details; keep the shape.

Customer service or retail

“I used to take difficult customer interactions personally. Early on, if someone was rude on a call, it would sit with me for the rest of the shift and I’d be slower and flatter with the next few customers. What changed it was a supervisor who suggested I write one line about each hard call in a notebook and then close it, literally shut the book. It sounds small, but it gave the call somewhere to go. Now I can take a rough call and be fully present for the next one, and my customer satisfaction scores in the last year have been steady rather than dipping after bad shifts.”

Software developer

“I have a tendency to go too deep before checking in. I’ll get a ticket, see three ways to solve it, and build the most elegant one, and then find out in review that the team wanted the simple one because the feature might be cut next quarter. It cost me most of a sprint once. What I do now is post a short plan in the ticket before I write code, three or four bullets, and ask for a thumbs up. It takes ten minutes and it has almost eliminated the big rewrites. My lead has commented that my pull requests have got smaller and easier to review since I started.”

Nurse or healthcare worker

“Handing off is something I’ve had to work on. On a busy ward I’d rather do a task myself than ask a colleague, partly because I know it will get done to my standard. The problem is that on a bad shift that means I’m behind on everything and nobody knows what I haven’t got to yet. My charge nurse pointed it out and I started using the handover board properly, flagging tasks I’m not going to reach before the second half of the shift instead of quietly carrying them. It was uncomfortable for a few weeks. Now the shift runs better and I’ve been asked to help newer staff do the same thing.”

Sales

“My weakness is the admin side of selling. I’m good in front of a customer and I’m bad at updating the CRM the same day, which meant my pipeline reports used to be out of date and my manager would get surprised by deals I’d been working for weeks. I fixed it by blocking the last twenty minutes of every day for CRM updates, with the calendar reminder on, and by logging notes on my phone straight after a meeting rather than trusting memory. My pipeline accuracy is now something my manager relies on instead of double-checking, and I’m not losing follow-ups the way I was.”

New or aspiring manager

“I give critical feedback too softly. When someone on my team is underperforming, my instinct is to cushion it so much that they leave the conversation not realizing there is a problem. That happened with one team member last year, and it took two extra months to address something that should have taken two weeks. I’ve since worked with my own manager on a simple structure: say the specific behavior, say the impact, say what needs to change, and stop talking. I still find it uncomfortable, but the last two feedback conversations I had were clear enough that the person could repeat back what I’d asked for, which is my test.”

Recent graduate or entry-level candidate

“I don’t yet have much practice at prioritizing when everything is urgent. At university, deadlines were spaced out and I could work through things in order. In my internship, I had three people asking for things at once and my first instinct was to do whichever was asked most recently. My supervisor showed me how to check which task actually had the nearest deadline or the biggest consequence, and I started writing a ranked list each morning and checking it with her for the first couple of weeks. By the end of the placement I was doing that on my own. I know it’s something I’ll keep building in a first full-time role, and I’d welcome a manager who is direct about what matters most.”

Notice that none of these ends with a flourish. The last sentence is a piece of evidence or a realistic statement about where things stand.

The answers that backfire

The disguised strength. “I’m a perfectionist.” “I work too hard.” “I care too much.” Interviewers hear these as either evasion or a lack of self-awareness, and either way the honest-answer test has been failed.

The weakness that is the job. A data analyst who is “not really a numbers person.” A project manager who is “not great with deadlines.” A care worker who “gets impatient.” The fix does not matter.

The character flaw. Lateness, temper, dishonesty, difficulty with authority. Even framed as historic and fixed, these raise more questions than the answer can settle in a minute.

“I don’t have one.” This is the worst answer available. It says you either lack self-awareness or think the interviewer is a fool.

The overshare. A minute on a weakness is fine. Three minutes, with two examples and a digression about your childhood, has turned the interview into a therapy session.

The weakness with no fix. Naming a problem and shrugging is honest but not reassuring. If you have not started addressing it, the answer is incomplete.

The obviously rehearsed one you do not believe. If you picked “public speaking” from a list and have never once been asked to present, the follow-up question (“tell me about a time that caused a problem”) will expose it.

Handling the variations

The same structure works for the many ways this question gets dressed up.

  • “What would your current manager say you need to work on?” Same answer, framed as feedback you received and acted on. This version is actually easier because the example is built in.
  • “Tell me about a time you failed.” Lead with the example rather than the trait, then the lesson, then what you did differently next time. It is the same four parts in a different order.
  • “What area would you most like to develop?” A gentler version. You can pick a skill gap here rather than a habit, and the fix becomes what you want from the role.
  • “What is a piece of feedback that was hard to hear?” Name the feedback, be honest that it stung, then move fast to what you did about it.
  • “What are your three weaknesses?” Give one full answer and two short ones. Do not give three full answers; it becomes a list of reasons not to hire you.

In UK, Canadian and Australian competency-based interviews, this question often appears inside a structured scoring framework, and the interviewer is looking for evidence of self-awareness and development against a written criterion. The four-part structure maps neatly onto that, because it gives them something to write in each box.

If the interview is on video, the temptation to glance at notes for this question is strong. Resist it; this is one answer that should be rehearsed to the point where you do not need them. Our guide to preparing for a video interview covers how to use notes for everything else.

Rehearse it once, out loud

Pick your weakness against the five tests, write the four parts as bullet points, and then say it out loud to a phone camera. Watch it back once. If it is over a minute, cut the example. If your voice goes up at the end as though you are asking permission, say the last sentence again flatly, as a fact. Then leave it alone and rehearse your opening answer instead; you have this one covered.

  • interviews
  • interview-questions
  • job-search

This article is general information, not legal, financial or medical advice. Rules differ by country, state and employer; check the current position for your situation. See our editorial policy and disclaimer. Spotted an error? Tell us.

More to read