How to answer “What is your greatest weakness?” (with sample answers)

By FindAJobAI teamPublished

Few interview questions cause as much worry as this one, and few are as predictable. You’ll almost certainly be asked it, or a version of it, so it’s worth preparing properly. The good news is that interviewers aren’t hunting for a flawless candidate. They want to know whether you can see your own weak spots, whether you’ll be honest about them, and whether you do something about them.

This guide covers how to choose a weakness that’s true and safe to share, a three-part structure, sample answers for eight common weaknesses, the answers that hurt you, and the strengths question that often comes with it. The sample answers are illustrations; yours has to describe something real.

What the interviewer is really testing

  • Self-awareness. Can you see your own patterns, or do you need someone else to point them out?
  • Honesty. Will you tell them something true, or a rehearsed non-answer?
  • Coachability. When you find a weakness, do you work on it?
  • Fit. Is this particular weakness a problem in this particular job?

In a structured interview, where answers are scored against set criteria, a strong answer names something real, shows its effect and gives concrete evidence of improvement. A non-answer scores low because there’s nothing to assess, however confidently it’s delivered.

How to choose your weakness

A good weakness is real, not central to the role, improvable, and something you’re already improving. Whether a weakness is safe depends on the job:

WeaknessUsually fine forRisky for
Presenting to large groupsEngineers, analysts, designersSales, teaching, communications
DelegatingPeople moving into their first lead roleSenior managers, where it’s the job
Detailed spreadsheet workDesigners, salespeople, writersAccountants, analysts
Taking on too muchMost rolesProject managers, if it shows up as missed deadlines
Giving difficult feedbackJunior and mid-level rolesPeople managers, HR
A tool you haven’t used yetRoles where it’s a nice-to-haveRoles where the ad lists it as required

Check the job ad before you decide: anything in the requirements is off-limits. Avoid character problems such as dishonesty, temper or unreliability, too. Those aren’t weaknesses an employer can coach; they’re reasons not to hire.

Weakness ideas by career stage

If you’re stuck, these are honest starting points. Keep only one that’s genuinely true for you.

  • Students and graduates: limited experience with a specific tool, nerves when presenting, juggling several deadlines at once, or waiting too long to ask questions.
  • Individual contributors: saying yes to too much, impatience with process, getting absorbed in detail, or preferring to work alone when a quick conversation would be faster.
  • New managers: delegating, giving difficult feedback promptly, or stepping back from the hands-on work you used to do.
  • Senior leaders: staying too close to the detail, patience with slow organisational change, or protecting time for long-term work.

The best choice is usually the one a former manager would recognise, because references are sometimes asked the same question.

A three-part structure

  1. Name it plainly. One sentence, without hedging or apology.
  2. Show it. A brief, real example of how it affected your work. This is what makes the answer believable.
  3. Fix it. What you’ve done about it, with evidence of progress: a habit, a course, feedback, a result.

As a fill-in template for your notes:

"One thing I've had to work on is [the weakness, in plain words].
For example, [a short, real situation and the effect it had].
Since then I've [two specific things you did], and [evidence it's improving].
It's [an honest note on where it stands now]."

Most of the time should go on the third part. The interviewer remembers the last thing you say, so finish on the improvement rather than the flaw.

Sample answers for eight common weaknesses

Each answer runs under a minute. The details are invented; replace them with your own.

1. Presenting to large groups

“Presenting to big groups hasn’t come naturally to me. In my first year as an analyst I presented our quarterly results to about 60 people and rushed through it, and the questions afterwards showed that people had missed the main point. Since then I’ve volunteered to present at our monthly team meeting, I rehearse with a colleague, and I build every presentation around three messages. Last quarter I presented to the regional leadership team and was asked to run the same session for another region.”

2. Delegating

“When I first led a small team, I held on to too much of the work because I knew I could do it quickly. Two of my team told me in a review that they weren’t being stretched, and I was working late most nights. Now I plan each week by asking what only I can do, and I hand over the rest with a clear outcome rather than step-by-step instructions. The team has taken over our monthly reporting completely.”

3. Taking on too much

“I’ve tended to say yes to every request, especially from other teams. Last year that meant I missed a deadline on my own project because I’d promised help on two others. Now I keep all my commitments on one board, and when someone asks for help I tell them what I’d need to move to say yes. I still help other teams, and I’ve met every project deadline this year.”

4. Impatience with slow processes

“I can get impatient when a process seems slower than it needs to be. Early on, I skipped a review step to send a report faster, and it went out with an error. I’ve learned to ask why a step exists before I judge it, and if I still think it’s unnecessary, I propose a change instead of working around it. Two of my suggestions to simplify our approval process have since been adopted.”

5. A tool you’re still learning

“I haven’t used Tableau in production; my dashboards have all been in Power BI. I know your team uses Tableau, so I’ve taken a course and rebuilt two of my existing dashboards in it, which are in my portfolio. The concepts carry over, and I’d expect to be productive in it within my first few weeks.”

Use this one only when the tool is a nice-to-have in the ad, not a requirement.

6. Giving difficult feedback

“I used to put off difficult conversations. As a new team lead, I let a performance issue run two months longer than I should have, which wasn’t fair to the person or the team. I took a short course on feedback, and I now raise issues within a week, with a specific example and its effect. It’s still not my favourite part of the job, but my team’s last survey rated feedback as one of our strengths.”

7. Getting lost in detail

“I can spend too long perfecting details that don’t change the outcome. On one project I spent a day polishing a chart nobody needed at that level, and it delayed the feedback I actually needed. Now I agree on what ‘done’ looks like before I start, and I share drafts earlier. I still check my work carefully, but I get feedback days sooner.”

This is the honest version of the perfectionism answer: a real cost and a real fix, rather than a compliment in disguise.

8. Asking for help too late

“I’ve sometimes tried to solve problems alone for too long. In my first month at my current job, I lost two days on a setup issue a colleague fixed in ten minutes. Now I give myself about an hour before I ask, and I write down what I’ve already tried so the question is quick to answer. I solve problems faster, and my questions have become more useful to the team.”

Answers that hurt you

  • “I’m a perfectionist” or “I work too hard” with nothing behind it. Interviewers hear these constantly and treat them as dodges.
  • “I don’t really have any weaknesses.” It reads as low self-awareness or evasion, which is worse than any real weakness.
  • A weakness at the heart of the job, such as “I’m not great with numbers” for a finance role.
  • Character problems like “I’m often late” or “I lose my temper”.
  • Oversharing. Health or personal matters don’t belong in this answer; keep it about work.
  • A joke. “Chocolate” might get a smile, but it wastes your chance to show self-awareness.
  • The flaw without the fix. Stopping after the weakness leaves the interviewer with only the negative.

The other half: “What are your strengths?”

Strengths come up just as often, sometimes in the same breath. Pick two or three that match the job ad, and back each one with a short example. A list of adjectives proves nothing; one result does.

“My main strength is turning messy data into something people act on. At my current job I rebuilt our weekly sales report so managers see problems by store instead of by region, and two regional managers now run their Monday meetings from it. I’m also dependable under deadlines: in four years I haven’t missed a month-end close.”

When asked “What are your strengths and weaknesses?” as one question, give one strength with evidence, then one weakness in the three-part structure, and stop. About 90 seconds in total is plenty.

Other ways the question is asked

  • “What would your manager say you need to improve?” Same structure. Make sure it matches what a reference might actually say.
  • “Tell me about a time you received critical feedback.” This wants a story: use the structure in our STAR method guide, ending with what you changed.
  • “What are you working on developing right now?” A friendlier version; the same three parts work.
  • “If we called your last manager, what would they say about you?” One or two strengths and one development area, honestly.
  • On an application form: two or three sentences covering the weakness, the action and the progress.

Prepare and practise your answer

  1. Write down three real weaknesses, and ask a colleague or former manager which one rings true.
  2. Cross out any that the job ad lists as a requirement.
  3. Draft the three-part answer for the best remaining one, with one concrete sign of progress.
  4. Say it out loud and aim for 45 to 75 seconds. Cut any hedging such as “I guess” or “maybe”.
  5. Prepare a second weakness in case the interviewer asks for another.

The weakness question rarely comes first. It usually follows “tell me about yourself” and a few questions about your experience, which our interview questions by job pages cover role by role, for example for a data analyst or an account executive.

Keep your examples consistent with your CV, since interviewers often pick bullets from it to ask about; the free CV score checker shows how your CV reads against the job. Afterwards, a short note from the thank-you email generator is a good way to close.

Frequently asked questions

What is a good answer to 'What is your greatest weakness?'

A real weakness that isn't central to the job, explained in three parts: name it plainly, give a short example of how it affected your work, and describe what you've done about it, with evidence that it's improving. For example, nervousness presenting that you've tackled by volunteering to present at team meetings.

Is it OK to say perfectionism is my weakness?

Only if you describe a real cost and a real fix, such as missing early feedback because you polished details too long, and now agreeing on what 'done' means before you start. Said on its own, 'I'm a perfectionist' sounds like a disguised strength, and most interviewers have heard it many times.

Should I mention a weakness related to the job?

Not one that's central to it. If the job ad lists a skill as a requirement, don't offer it as your weakness. A gap in a nice-to-have skill, or a soft skill that doesn't define the role, is a safer and more honest choice.

How long should my answer to the weakness question be?

About 45 to 75 seconds. Spend one sentence naming the weakness, two or three on a short example, and the rest on what you're doing about it and the progress you've made.

How do I answer 'What are your strengths and weaknesses?'

Give one or two strengths that match the job, each with a short example as evidence, then one weakness using the three-part structure: name it, show its effect, show how you're improving. Keep the whole answer to about a minute and a half.

Related guides

Free tools