"What Are Your Greatest Weaknesses?" — Best Answers + Examples (2026)

"What is your greatest weakness?" is one of the most disliked interview questions — and one of the most mishandled. Most candidates either give a fake answer the interviewer sees through immediately, or name a real weakness without any structure and end up creating doubt.

This guide covers the three-step formula that works, 15 real example answers across different roles and experience levels, and the mistakes you need to avoid. For structuring answers to other difficult interview questions, the STAR method is the framework most interviewers respond to best.

Why Interviewers Ask This Question

This question is not a trap, and it is not designed to catch you out. Interviewers ask it to assess two things: self-awareness (do you understand your own limitations?) and growth mindset (do you actively work on improving them?).

A candidate who names a genuine weakness and demonstrates they are managing it tells the interviewer something important: this person is honest, knows themselves, and takes their own development seriously. That is a more attractive hire than someone who claims to have no weaknesses.

The question also reveals how you handle pressure. Candidates who panic and give a fake answer, deflect, or ramble signal that they struggle with difficult situations — which is more damaging than the weakness they were trying to avoid mentioning.

The 3-Step Formula for Answering the Weakness Question

A strong answer to this question follows a consistent structure. Use this formula for any weakness you choose:

Step	What to cover	Example
1. Name the weakness	State it directly and briefly — one sentence	"I tend to find public speaking uncomfortable"
2. Give brief context	Explain how it has affected you — one sentence	"Earlier in my career this meant I held back in meetings where I had useful things to contribute"
3. Describe what you are doing about it	Specific steps, not vague intentions	"Over the past year I have joined a Toastmasters group and volunteered to lead the monthly team briefings..."

The critical element is Step 3. Anyone can name a weakness. What separates a good answer is evidence that you are taking active, specific steps to address it — not "I am working on it" but "here is what I have done."

What Makes a Good Weakness to Mention

Not all weaknesses are equally safe to discuss. A good weakness to name in an interview meets three criteria:

It is real. Interviewers have heard "I work too hard" thousands of times. A genuine weakness handled confidently is more impressive than a transparent non-answer. If you struggle to think of one, ask a trusted colleague what they would say your development areas are.

It is not a core requirement of the job. A nurse should not say their weakness is staying calm under pressure. A writer should not say they struggle with attention to detail. Think about what the role fundamentally requires and choose something that sits outside that core.

You are actively working on it. The weakness should be something you have already taken steps to address — not something you have noticed but done nothing about. The improvement story is the most important part of the answer.

Weaknesses to Avoid

"I am a perfectionist." This is the most overused non-answer in interviews. Interviewers hear it as "I have nothing genuine to offer" or, worse, "I think this is a strength in disguise." Avoid it entirely.

"I work too hard." Same problem. It signals that you are not willing to be genuinely self-reflective.

"I do not have any real weaknesses." This tells the interviewer you either lack self-awareness or are being evasive. Either is a red flag.

Weaknesses that are central to the role. If the job requires strong data analysis and you say you struggle with numbers, you have given the interviewer a reason not to hire you. Choose something peripheral.

Personal or character flaws. Weaknesses related to reliability, honesty, or working with other people are high-risk. Stick to skills or working styles rather than character traits.

15 Greatest Weakness Answer Examples

The examples below follow the 3-step formula. Each includes a brief note on which role or situation it suits best.

1. Public Speaking

Suits: roles where public speaking is not a core requirement — analysts, engineers, individual contributors

"I have always found public speaking more challenging than one-to-one conversations. Early in my career this held me back from contributing in larger group settings, even when I had something useful to add. Over the past 18 months I have been attending a Toastmasters group monthly and volunteering to lead our team's weekly stand-ups. I am now comfortable presenting to groups of 15–20 people, and my goal this year is to get to 50."

2. Delegating Work

Suits: team leads, managers, project managers — shows awareness of a common leadership pitfall

"For a long time I found it hard to delegate work I could do well myself. I was worried about quality and found it quicker to do things myself than to brief someone else. What I realised is that this limits what the team can achieve and prevents people from developing. Over the past year I have made a deliberate effort to delegate more, using a brief-back technique where I ask the person to summarise the task in their own words before starting. The team's output has improved, and two people I delegated to have taken on work I would previously have done myself."

3. Saying No / Setting Boundaries

Suits: people-oriented roles — customer success, account management, coordinators

"I have historically found it difficult to push back on requests, even when my plate was full. This meant I occasionally over-committed and delivered some things late rather than managing expectations earlier. I have worked on this by getting clearer on my own priorities at the start of each week, and by practising language for pushing back — something like 'I can take that on, but it would mean delaying X. Is that the right trade-off?' That framing has helped me have honest conversations without feeling like I am letting people down."

4. Impatience With Slow Processes

Suits: analytical or results-driven roles; avoid if the job involves stakeholder management or consensus-building

"I can become impatient when processes feel slower than they need to be. This sometimes shows up as frustration in collaborative settings where decisions require more rounds of sign-off than I think are necessary. I have worked on contextualising this better — understanding why certain processes exist, particularly in regulated environments — and on channelling the impatience productively by drafting proposals to streamline things rather than just being frustrated by them."

5. Difficulty With Ambiguity

Suits: structured or process-driven roles where you are moving toward an environment with more clarity

"I work best when I have a clear brief and defined goals. Earlier in my career, ambiguous projects would slow me down because I would wait for clarity that was not coming. I have got much better at this by defaulting to documenting my own assumptions and sharing them early with stakeholders — that way I move forward and surface misalignments quickly rather than getting stuck."

6. Overexplaining

Suits: technical or analytical roles — engineers, data analysts, finance professionals

"I have a tendency to over-explain my reasoning, especially when presenting analysis. I want people to understand how I reached a conclusion, but I have learned that senior stakeholders often just want the recommendation and can ask for the detail if they need it. I have been working on structuring my communications with the headline first and the supporting detail second, which has made my presentations noticeably more concise."

7. Networking and Self-Promotion

Suits: technical roles, introverts moving into more visible positions

"I have found professional networking uncomfortable — it has always felt somewhat performative to me, and I have tended to let my work speak for itself. What I have come to understand is that visibility matters for career development and for the team. Over the past year I have been more deliberate about this, including contributing to industry conversations on LinkedIn and attending two sector events where I introduced myself to people I would not otherwise have met."

8. Data Presentation Skills

Suits: data, research, or analytical roles where presenting is not the core function

"While my analytical skills are strong, presenting data in a clear, visual way to non-technical audiences is something I have had to work at. I used to produce charts that made sense to me but needed more explanation than they should have. I have since completed a data visualisation course and have rewritten our internal reporting templates, which has improved how the team communicates findings upward."

9. Asking for Help

Suits: junior to mid-level candidates, especially in self-sufficient or autonomous roles

"I tend to try to solve problems independently before asking for help, which is usually fine but occasionally means I spend longer on something than I need to. I am working on recognising earlier when a quick conversation would save significant time, and I have made a habit of checking in on blockers at the end of each day so they do not carry over."

10. Managing Up

Suits: mid-level candidates moving toward more senior roles

"In earlier roles I did not communicate my progress upward as much as I should have. I assumed my manager knew what I was working on and how things were going, when in reality I was creating uncertainty for them. I now make a point of providing proactive status updates — particularly on longer projects — so that there are no surprises and my manager has what they need without having to ask."

11. Writing Under Pressure

Suits: technical roles where writing is secondary — engineers, developers, data professionals

"When I am under time pressure, my written communication can suffer — I produce something accurate but not as clear or well-structured as I would like. I have been working on this by building in a short review step even for quick emails on complex topics, and by using a simple structure (context, ask, next step) for routine written communication."

12. Giving Feedback

Suits: roles with team leadership or peer-review responsibilities

"I have historically been more comfortable receiving feedback than giving it, particularly when it involves telling a colleague something difficult. I tended to soften feedback to the point where the message got lost. I have worked on this through my current role, where I manage two direct reports and have had coaching on delivering feedback using the SBI framework — Situation, Behaviour, Impact — which has made those conversations more useful for both sides."

13. Prioritisation Under High Volume

Suits: roles in fast-paced environments with multiple concurrent workstreams

"When my workload is high I have sometimes spent too long on tasks that feel urgent but are not necessarily the most important. I have addressed this by building a daily prioritisation practice using the Eisenhower matrix — splitting tasks into urgent/important quadrants at the start of the day — which has helped me stay focused on the work that actually moves things forward."

14. Technical Skills in a Specific Area (Example: SQL)

Suits: roles where the gap is in a supplementary tool, not the core job requirement

"SQL is not a weakness exactly, but it is a skill I have been developing because I want to be more self-sufficient when pulling data for analysis. In my current role I rely on the data team for anything complex. I have been working through an online SQL course over the past few months and can now write intermediate queries independently. I am not at the level of a data analyst, but I am less dependent than I was."

15. Tendency to Overthink

Suits: roles where pace and decisiveness are valued but not the single most important quality

"I can spend more time than necessary analysing decisions, particularly when the consequences feel significant. In most cases this leads to good outcomes, but it can create delays when a faster decision would have been fine. I have worked on this by setting a decision deadline for myself — particularly for lower-stakes choices — and by distinguishing more deliberately between decisions that are hard to reverse (which warrant careful analysis) and those that are easy to adjust later."

Tailor Your Application With resum8

Before your interview, make sure your CV gives you the strongest possible foundation. resum8 analyses your CV against the job description, identifies missing keywords, and gives you a Skill Match Score so you know exactly where your gaps are before you walk into the room. The interview preparation tools in resum8's paid tier generate likely interview questions based on your CV and the specific role.

Try resum8 Free

How to Prepare Your Answer

1. Identify 2–3 genuine weaknesses you would be comfortable discussing. Having options means you can choose the one most appropriate for the specific role and interviewer.

2. Map your improvement steps for each one. Be specific: which course, which habit, which person, which framework? Vague intentions ("I am working on it") are unconvincing.

3. Practise out loud. Saying this answer in your head and saying it to a person are very different experiences. Rehearse with a friend or record yourself to check your tone — you want to sound calm and matter-of-fact, not defensive or apologetic.

4. Check the job description. Confirm that the weakness you plan to mention is not listed as a core skill. If it is, choose one of your alternatives.

Frequently Asked Questions

What is the best answer to "What is your greatest weakness?"

The best answers name a real weakness, briefly explain its impact, and then describe specific steps you have taken to address it. Interviewers are not looking for someone with no weaknesses — they are assessing self-awareness and whether you actively work on improvement. A good structure: name the weakness, one sentence on how it used to affect you, then two to three sentences on what you have done (and are doing) about it.

Should I give a fake weakness like "I work too hard"?

No. Experienced interviewers recognise fake weaknesses immediately, and they signal a lack of self-awareness. Answers like "I am a perfectionist" or "I work too hard" are the most common and least convincing responses. A genuine, modest weakness handled confidently leaves a far better impression than a transparent non-answer.

How many weaknesses should I mention?

One is almost always the right number. The question is usually phrased as "greatest weakness" (singular) for a reason. Naming one weakness and handling it well shows more confidence than listing three. If the interviewer asks for another, have one ready — but do not volunteer more than asked.

Which weaknesses should I avoid mentioning?

Avoid weaknesses that are core requirements of the job. If you are applying for a sales role, saying your weakness is phone confidence will raise serious doubts. Similarly, avoid anything that suggests dishonesty, unreliability, or inability to work with others. Choose a real weakness that is peripheral to the job's core demands and that you are actively working on.

Can I say I have no weaknesses?

No. Saying you have no weaknesses signals a lack of self-awareness, which is itself a red flag. Every credible candidate has things they are working on. The willingness to identify and address your weaknesses is a quality employers actively look for.

How long should my answer be?

60 to 90 seconds is ideal. Long enough to cover the weakness, its past impact, and your improvement steps — short enough to stay focused. If you find yourself talking for more than two minutes about a single weakness, you have given it too much weight and may be making it seem larger than it is.