All interview questions
Self-awareness questionFor job seekers40-60 seconds (roughly 100-140 spoken words)

How to Answer "What Is Your Greatest Weakness?"

The short answer

Name one real weakness that is not central to the job, describe the concrete cost it has had, then spend most of your answer on the specific system you built to manage it and the evidence it is working. Around 45 seconds. Avoid disguised strengths like perfectionism.

Everyone knows "I am a perfectionist" is a non-answer, including you. Here is how to give a real one without damaging your candidacy.

Or skip ahead and have your answer scored — free, no account needed.

Why interviewers ask “What is your greatest weakness?”

Interviewers are not hoping you will disqualify yourself. They are testing self-awareness — whether you can see yourself accurately — and coachability, which is whether feedback actually changes what you do. A candidate who cannot name a real weakness is either not paying attention or not being honest, and both are harder to manage than someone with an ordinary, well-handled flaw.

What they are actually listening for

  • Is this a real weakness, or a strength in a thin disguise?
  • Do you know the cost of it? Naming a flaw without its consequence sounds theoretical.
  • What did you actually do about it? This is the part they care about most.
  • Is it improving, and can you show it rather than assert it?
  • Is it something that would break this particular job? That is the only genuinely dangerous case.

The structure to use: Weakness - Cost - System - Evidence

The weakness itself should take about a fifth of your answer. The rest is what you did about it. That ratio is the whole trick: it turns a question about your flaws into a demonstration that you notice problems and fix them.

  1. Name it plainly, without softening

    ~8 seconds

    State one real weakness in a single sentence, with no hedging and no "some people might say".

    Pick something true, something specific, and something that is not the core competence of the job. A backend engineer can safely say they are a weak public speaker. A sales lead cannot. Avoid anything that touches reliability, honesty, or working with others — those read as risks rather than flaws.

  2. Say what it has actually cost

    ~12 seconds

    Give one concrete example of a time it caused a real problem.

    This is what makes the answer credible. Without a cost, the weakness sounds hypothetical and the interviewer assumes you picked it because it was safe. Keep the example short and do not dramatise it — one sentence of consequence is enough.

  3. Describe the system you built

    ~20 seconds

    Explain the specific, repeatable thing you now do to manage it — not an intention, a mechanism.

    "I am working on it" is not an answer. "I now write the one-page summary before I open the editor, and I have a standing Friday slot to clear it" is. Systems are convincing because they survive motivation. This should be the longest part of your answer.

  4. Show it is working

    ~10 seconds

    End with brief evidence of improvement — feedback you have had, a measurable change, or a situation that used to go badly and now does not.

    Evidence turns a story about a flaw into a story about growth. It also lets you finish on a positive note without any of the forced optimism that makes these answers sound rehearsed.

Example answers to “What is your greatest weakness?”

These are written to be spoken, not read. Do not memorise them — take the shape and put your own experience through it.

Example 1

Software engineer

Weakness: written communication and documentation

My weakness is written communication, specifically design docs. I think through problems by building, so I have historically started coding before I could explain the approach in writing.

It cost me properly about a year ago: I spent three weeks on a caching layer, and at review a staff engineer pointed out a constraint that would have taken ten minutes to catch if I had written the design down first. Most of that work was thrown away.

Since then I write a one-page design doc before any piece of work over about three days, and I get one person to read it before I start. I also joined our internal writing group, which is uncomfortable and useful in roughly equal measure.

It is genuinely better — my last two designs went through review with only minor comments, and my manager called the docs out in my last review as the biggest change of the year.

Why it works

  • The weakness is real, common, and not the core skill of a backend engineering job.
  • The cost is specific and quantified (three weeks of thrown-away work), which makes it credible.
  • The fix is a mechanism with a trigger, not a good intention.
  • The evidence is external — review outcomes and a manager's feedback, not self-assessment.

Example 2

Product manager

Weakness: taking on too much and saying yes to stakeholders

I say yes too easily. When a stakeholder asks for something reasonable, my instinct is to find a way to fit it in rather than to ask what it displaces.

Last year that meant a quarter where my team shipped six half-finished things instead of three finished ones, and the roadmap I had agreed with my director was barely recognisable by December.

What I do now is boring but it works: nothing enters the sprint without something leaving it, and I say that out loud in the meeting rather than absorbing it quietly afterwards. I also keep a visible parked list, so saying no feels like sequencing rather than refusal.

The last two quarters we have hit what we committed to, and my director's feedback was that the roadmap has stopped drifting.

Why it works

  • The weakness is a genuine PM failure mode rather than a disguised strength.
  • The cost is described in outcomes the interviewer recognises.
  • The system is concrete and social — it changes behaviour in the room, not just intent.
  • The improvement is stated in terms someone else observed.

Common mistakes (and the fix)

Giving a disguised strength

"I am a perfectionist", "I work too hard", "I care too much" are the three most common answers to this question and every interviewer has heard them hundreds of times. They read as evasion, which is worse than an ordinary weakness.

Fix: Pick something you would actually mention to a mentor. If it is not slightly uncomfortable to say, it is not a real answer.

Naming something that breaks the job

Honesty has limits. "I struggle to meet deadlines" in a delivery role or "I find it hard to take feedback" anywhere is a hiring risk, not a moment of self-awareness.

Fix: Choose a weakness that is peripheral to the role's core competence, and never one that touches reliability, honesty, or collaboration.

Stopping at the weakness

Naming a flaw and stopping leaves the interviewer holding a negative with nothing to balance it. The improvement is the actual content of the answer.

Fix: Spend two-thirds of your time on the system you built and the evidence it works.

Offering an intention instead of a mechanism

"I am working on it" and "I have been trying to be better about that" are unfalsifiable, and interviewers treat them as no answer at all.

Fix: Describe something with a trigger and a frequency: what you do, when it fires, and who else sees it.

Claiming you have already fixed it

A weakness that is entirely solved is not a current weakness, so the answer dodges the question. It also strains credibility.

Fix: Say it is better and still managed. Ongoing beats cured.

Free · no account needed

Say your answer out loud. Get it scored.

Reading about the structure is not the same as saying it. Answer “What is your greatest weakness?” the way you would in the room, and get a score plus three specific fixes. Aim for 40-60 seconds (roughly 100-140 spoken words).

This browser cannot record audio. .

Practise the other nineteen questions too

“What is your greatest weakness?” is one question. Paste the actual job posting and your CV and prepare.fyi generates the twenty questions that company is most likely to ask, then lets you answer them out loud — with a live AI interviewer and a scored breakdown of every answer.

One free project every month. Credits are one-off and never expire — no subscription.

“What is your greatest weakness?”: frequently asked questions

Can I say "perfectionism"?
It is the single most common answer and interviewers read it as a dodge. If perfectionism genuinely is your problem, you can rescue it by being specific about the failure mode and its cost — "I over-polish work that is already good enough, which made me two weeks late on a launch last year" — but you are starting from behind. Something else is usually a better choice.
How honest should I actually be?
Honest about a real weakness, deliberate about which one. You are choosing from a set of true things, and it is entirely fair to pick the one that is least central to this job. What you should not do is invent a flaw, because follow-up questions expose it quickly.
What if they ask for three weaknesses?
Some interviewers do this to get past the prepared answer. Have a second and third ready, from different areas — one technical, one about process, one about communication. Give the same structure for each but keep the second and third shorter.
Is this the same as "tell me about a time you failed"?
No, and mixing them up costs you. A weakness is an ongoing tendency you manage. A failure is a single event with a specific outcome, and it wants a STAR-shaped story. Prepare both separately.
What if I genuinely cannot think of one?
You have one; you just have not been told about it recently. Look at your last performance review, the feedback you found annoying at the time, the part of your job you postpone, and the kind of work you quietly hope someone else picks up. One of those is your answer.

Practise the next question

Behavioral

“Tell me about a time you failed”

The trap is choosing a failure so small it proves nothing. Here is how to pick one that is real, tell it in ninety seconds, and come out of it looking better.

Opening

“Tell me about yourself”

It is the first question in almost every interview, and the one most candidates waste. Here is the structure, three full example answers, and a way to practise yours out loud right now.

Motivation

“Why do you want to work here?”

This is the question that separates candidates who researched the company from candidates who applied to forty of them. Here is how to answer it without flattery.

Go deeper