Skip to content
Job interviews

How to Answer "What Is Your Greatest Weakness?"

Interviewers ask about your weakness to test self-awareness and honesty, not to catch you out. A good answer names a real, non-fatal weakness, shows what you are doing about it, and stops. Below: how to choose one, a three-part structure, six example answers for different roles, and how to handle the follow-up questions.

By NORDON Team

7 min read

Also in Srpski, Hrvatski, Deutsch, Français, Español, Português

What the question is really testing

Nobody is rejected for having a weakness. Candidates are rejected for three things this question reveals: they cannot see their own gaps, they are not honest about them, or the gap is central to the job. Your answer needs to pass all three.

  • Self-awareness: you can name something specific, not a slogan.
  • Honesty: it sounds like a real weakness, not a disguised strength.
  • Growth: you have already done something about it, and you can show it.

How to choose your weakness

Make a list of three to five candidates, then run each through these filters:

  1. Is it true? Think of feedback you have actually received in reviews, from a manager or a colleague. True weaknesses are easier to talk about calmly and survive follow-up questions.
  2. Is it outside the core of this job? A weakness in spreadsheets is fine for a sales role and fatal for a financial analyst. Read the job ad and cross out anything in its top requirements.
  3. Is it a skill or habit, not a character flaw? "I find it hard to delegate" can be worked on. "I get angry easily" sounds like a risk.
  4. Can you show progress? You need a concrete step you took and some evidence it is working.
Weaknesses that usually work, and why
WeaknessWorks well forWhy it is safe
Public speaking to large groupsEngineering, analysis, designRarely core; easy to show practice
DelegatingNew managers, senior individual contributorsCommon, fixable, shows you care about quality
Saying yes to too many requestsSupport, operations, project rolesShows willingness; fix is about prioritizing
Going too deep on details earlyProduct, research, data rolesFix is visible: timeboxes, drafts
Giving direct feedbackFirst-time leadsReal growth area, many concrete steps
A specific tool or domain gapAny role where it is not the main skillFactual and easy to close

The structure: name it, show it, fix it

  1. Name it in one plain sentence. No hedging, no "some people say".
  2. Show it with a short, real example of when it caused a problem. One or two sentences is enough; this is not a full STAR story.
  3. Fix it: what you did about it, and what is different now. This should be the longest part.

Keep the whole answer to 45 to 75 seconds. Then stop. Do not add "but I think that's also a strength", which undoes the honesty you just showed.

Six example answers

These are fictional examples. Pick the pattern, not the words, and make sure your version is true.

Example: Software engineer: speaking up in large meetings

"I'm much more comfortable in a code review or a small design discussion than in a big meeting. In larger architecture reviews I used to stay quiet even when I had a concern, and once a design went ahead with a caching issue I had spotted but not raised. It cost us a week later.

Since then I write my concerns down before the meeting and post them in the review doc, so they're on the table even if I don't speak first. I also volunteered to present our team's quarterly tech update, which I've now done twice. It's still not my favorite thing, but I don't let concerns go unsaid anymore."

Example: New team lead: delegating

"When I first became a lead, I kept the hardest tasks for myself because it felt faster. The result was that I became the bottleneck and two people on my team told me in a retro that they weren't getting interesting work.

Now, at the start of every sprint, I pick at least one task I would normally do and hand it to someone with a short walkthrough, then I review instead of redo. It was slower the first month. Now those two people own areas I used to cover, and I have time for planning."

Example: Customer support agent: saying yes too fast

"I tend to promise customers things before I've confirmed them, because I want to solve the problem on the spot. A few times I told someone a refund would arrive in two days when finance needed five.

What I do now is check the policy or ask before I commit, and I use a line like 'Let me confirm that so I give you the right date.' My follow-up complaints dropped, and customers don't seem to mind the extra minute."

Example: Data analyst: going too deep before sharing

"I like to have every number checked before I show anything, and early on that meant stakeholders waited a week for an answer they needed in a day.

I now send a short first cut within a day, clearly marked as preliminary, with what I'm still checking. That way people can react early, and twice it turned out they needed a different question answered altogether."

Example: Product manager: giving direct feedback

"I used to soften feedback so much that the message got lost. A designer on my team didn't realize a flow was off track until late, because my comments sounded optional.

I started using a simple format: what I saw, why it matters, and what I'd like to see changed, with a date. I also ask people to tell me if my feedback is unclear. It feels more direct than I'm used to, but people tell me they prefer knowing where they stand."

Example: Marketing coordinator: a tool gap

"My weak spot right now is analytics. I can read a standard dashboard, but I haven't built my own reports, and in my last role I relied on a colleague for anything custom.

Over the past two months I've taken an online course on analytics for marketers and rebuilt our monthly campaign report myself as practice. I'm not an expert yet, but I can set up the basic reports a role like this needs."

Weaknesses to avoid

  • The humble brag: "I'm a perfectionist" or "I work too hard." Interviewers have heard it many times and it reads as a dodge.
  • A core skill of the role: a project manager who misses deadlines, an accountant who dislikes detail.
  • Character or integrity issues: lying, temper, unreliability, trouble with authority.
  • "I don't have one." It fails the self-awareness test immediately.
  • Something fixed and personal: your age, your accent, being introverted as an identity. Talk about a specific behavior instead.
  • A weakness with no progress: naming it without any action sounds like you are not going to change.

Follow-up questions to prepare

A good interviewer will push once or twice. Have short answers ready:

Typical follow-ups
Interviewer
Can you give me another example of that?
You
Have a second short example ready, ideally a more recent one that shows the fix working.
Interviewer
How would your current manager describe it?
You
Quote real feedback if you have it: "In my last review she said I'd improved at..."
Interviewer
How would this show up in this role?
You
Be honest and specific: when it might come up, and what you would do in that moment.
Interviewer
What's another weakness?
You
Keep a second, smaller one prepared, using the same structure.

Practice the answer out loud

This answer sounds very different spoken than written: under pressure, most people either over-explain or start defending themselves. Say it out loud three times, then have someone ask the follow-ups. If you prepare from a job ad, NORDON's prepared answers feature generates the most likely questions, which often include this one, and marks any personal fact it does not know as a [placeholder] for you to fill in, so you start from your real experience instead of a generic line. Role-specific questions are in the question library, and the answer pairs well with a short opening from our guide to "Tell me about yourself".

Try it in NORDON

Start from a draft built on your own background

Paste a job ad and NORDON prepares the 8 questions you are most likely to hear, with answers built from your documents. You read and edit them before the interview, and anything it does not know about you is left as a placeholder.

Questions

Can I say "I'm a perfectionist"?

It is better not to. It sounds rehearsed, and most interviewers take it as avoiding the question. If attention to detail really slows you down, describe the concrete behavior, such as rechecking work instead of sharing a draft, and what you do about it.

Should I talk about a weakness I have already fixed?

A weakness you have mostly fixed is ideal, as long as you are honest that you still watch for it. A weakness that is completely gone sounds like a past problem, not a current one.

How long should my answer be?

About 45 to 75 seconds. One sentence to name it, one or two for the example, the rest on what you did and what changed.

What if they ask for three weaknesses?

Prepare one main answer and two shorter ones. Use the same structure, but keep the second and third to two or three sentences each.