Sign in"What Is Your Greatest Weakness?" Best Answers and Examples
How to answer 'What is your greatest weakness?' with a three-part formula, examples by role, weaknesses to avoid, rewrites, and the strengths question too.
Key takeaways
- Pick a real weakness that matters at work but isn't a core requirement of the job you're interviewing for.
- Spend about half your answer on the specific system you use to manage the weakness, not on the weakness itself.
- End with evidence that the fix works, and admit it's managed rather than solved.
- Avoid disguised strengths like perfectionism, and avoid character flaws like a short temper or dishonesty.
- Prepare a second weakness and a matching strength answer, since interviewers often ask for both.
"What is your greatest weakness?" is the interview question people dread most, and the one they most often answer badly. Some candidates dodge it with a fake flaw. Others confess something that quietly disqualifies them. Both lose points on a question that's actually easy to win.
The interviewer isn't hunting for your flaws. They're testing whether you see yourself clearly, whether you take feedback, and whether you fix problems instead of excusing them. A good answer proves all three in about a minute.
This guide gives you a three-part formula, a way to choose the right weakness for a specific job, examples for different roles and career stages, rewrites of common bad answers, and a plan for follow-up questions. Because the strengths question often comes right before or after, you'll find a section on that too.
Why interviewers ask "What is your greatest weakness?"#
Most interviewers aren't trying to trip you up. In structured interviews, each question is tied to a competency and scored against benchmarks. The U.S. Office of Personnel Management describes how structured interviews use set questions and rating standards to make scoring consistent. The weakness question usually maps to self-awareness, coachability, and honesty.
Here's what the interviewer is checking, and how a strong answer shows it.
| What they're testing | What a weak answer shows | What a strong answer shows |
|---|---|---|
| Self-awareness | A vague or fake weakness | A specific, real pattern you've noticed |
| Coachability | Defensiveness or excuses | Feedback you received and acted on |
| Problem-solving | Hope that it gets better | A concrete system you put in place |
| Honesty | A disguised strength | A real limitation, stated calmly |
| Job fit | A flaw at the core of the role | A weakness that's secondary to the job |
Notice that the weakness itself is only one part of the scoring. Most of the credit comes from what you did about it. That's why two candidates can name the same weakness and get very different scores.
How a structured interviewer might score your answer#
Many interview teams use a simple rating scale for each question. The rubric below is an illustrative example of how a weakness answer could be scored on a five-point scale. Real rubrics vary by employer, but most reward the same things.
| Score | What the answer included | Typical example |
|---|---|---|
| 1 (weak) | No real weakness, or a deflection | "I don't really have any." |
| 2 | A weakness with no example or fix | "I'm not great at public speaking." |
| 3 (acceptable) | A real weakness and a general fix | "I'm working on presenting by practicing more." |
| 4 | A specific weakness, a concrete system, some evidence | A named routine plus feedback from a manager |
| 5 (strong) | Specific weakness, clear system, measurable proof, honest status | The structure in the formula below |
Moving from a 3 to a 5 rarely requires a different weakness. It requires a more specific fix and a real result.
The three-part formula for answering the weakness question#
Use Honest, Fix, Proof. It keeps your answer balanced, short, and focused on growth.
- Honest: Name a real weakness in one or two sentences, with a brief example of when it showed up.
- Fix: Explain the specific system, habit, or training you use to manage it. Be concrete: tools, routines, or schedules.
- Proof: Share evidence that it's working, such as a result, feedback, or a before-and-after comparison. Admit it's still a work in progress.
The fix is where you earn the most credit, so give it the most time.
Illustrative: how to split a one-minute weakness answer
Suggested share of speaking time for each part of the formula
- Honest: name it and give an example25%
- Fix: your system for managing it50%
- Proof: evidence it's working25%
Illustrative example, not survey data.
View dataHide data
| Label | Value |
|---|---|
| Honest: name it and give an example | 25% |
| Fix: your system for managing it | 50% |
| Proof: evidence it's working | 25% |
What the formula sounds like#
Here's the formula applied to a common weakness, so you can hear how each part fits together before you write your own.
Honest: I've tended to say yes to every request from other teams. Last spring that meant I had six small projects running at once, and one campaign brief went out two days late.
Fix: Now I keep a visible request board. When something new comes in, I add it, ask the requester for the real deadline, and check it against my current priorities with my manager each Monday. If something has to slip, I say so the same day instead of trying to absorb it.
Proof: Over the last two quarters, I've delivered every campaign brief on time, and two of the teams I support have started using the board to plan their requests in advance. I still have to resist the urge to say yes on the spot, but the system catches it.
Finish with "I'm still working on it" or a similar line. Claiming you've completely fixed a weakness sounds less believable than showing steady progress.
How to choose the right weakness for the job#
The right weakness depends on the role. The same answer can be perfect for one job and a red flag for another. Use this process to pick.
- List three to five real weaknesses. Look at old performance reviews, feedback from managers, and moments when work went sideways.
- Highlight the job's core requirements. Take the top five skills from the posting. Any weakness that overlaps with them is off the table.
- Check the occupation's profile. O*NET lists the skills and work styles that matter most in each occupation. For accountants and auditors, attention to detail, integrity, and dependability are among the top work styles, so a weakness in any of those would hurt.
- Keep weaknesses you've actually worked on. You need a real fix and evidence. A weakness you haven't addressed yet makes a thin answer.
- Choose the one with the best proof. The strongest answer is usually the weakness where you can show the clearest improvement.
Where to find your real weaknesses#
If nothing comes to mind, you're probably looking too broadly. Weaknesses show up in specific moments at work. Check these sources:
- Performance reviews: Look at the "areas for development" section from the last two or three reviews.
- Recurring feedback: Anything a manager or colleague has mentioned more than once is a pattern worth naming.
- Projects that slipped: Think about the last project that ran late or needed rework. What was your part in it?
- Tasks you avoid: The work you put off often points to a skill you're less confident in.
- Questions you'd ask a trusted colleague: "What's one thing I could do that would make me easier to work with?" Their answer is often the most useful.
Write down everything you find, then filter with the steps above. You want a weakness that's real enough to be credible and specific enough to have a clear fix.
Use employer priorities as a guide#
Employer surveys show which attributes matter most and which matter less. The National Association of Colleges and Employers asks employers what they look for in new-grad candidates, and the ranking is a useful map for choosing a weakness.
Attributes employers seek in new-grad candidates
Share of employers seeking each attribute on a candidate's resume
Source: NACE Job Outlook 2026 Spring Update, via Iowa State University
View dataHide data
| Label | Value |
|---|---|
| Teamwork | 85% |
| Problem-solving | 82% |
| Verbal communication | 78% |
| Technical skills | 73% |
| Detail-oriented | 65% |
| Flexibility/adaptability | 58% |
| Organizational ability | 48% |
| Strategic planning | 38% |
| Tactfulness | 25% |
| Creativity | 22% |
Attributes near the top of the NACE ranking are risky choices for entry-level candidates, because most employers screen for them. Attributes further down, like strategic planning or creativity, are often safer, unless the specific job lists them as a core requirement. NACE's write-up of its earlier survey found the same pattern, with problem-solving and teamwork near the top.
A quick risk check#
Before you settle on a weakness, run it through this table.
| Weakness category | Example | Risk level | When it works |
|---|---|---|---|
| Secondary skill gap | Advanced Excel modeling for a recruiter | Low | When the skill is useful but not required |
| Work habit | Over-preparing for routine meetings | Low to medium | When you can show a clear fix |
| Communication pattern | Too much detail in executive updates | Medium | When the role isn't communication-led |
| Core skill gap | Weak SQL for a data analyst role | High | Rarely; only with strong proof of progress |
| Character trait | Losing your temper under pressure | Very high | Avoid |
Weaknesses to avoid, and what to say instead#
Some answers fail no matter how well you deliver them. Here are the most common, with safer alternatives.
| Avoid saying | Why it backfires | Try instead |
|---|---|---|
| "I'm a perfectionist." | Sounds like a dodge or a disguised strength | "I rewrite drafts too many times before sharing them." |
| "I work too hard." | Not credible, and it avoids the question | "I'm slow to ask for help when I'm stuck." |
| "I don't have any." | Shows no self-awareness | Any real, secondary weakness with a fix |
| "I get impatient with slow coworkers." | Suggests friction with teammates | "I get impatient with slow processes, so I document fixes." |
| "I'm not good with details." (for an analyst) | Hits a core requirement | A secondary skill like presenting to large groups |
| "I procrastinate." | Vague and unsettling with no context | A specific pattern, like starting large reports late |
Red flags interviewers listen for#
Beyond specific weaknesses, certain patterns in your answer can worry an interviewer even if the weakness itself is fine:
- Blaming others: "My last manager never gave clear instructions."
- No fix: naming the weakness and stopping there.
- Humor as deflection: "Chocolate," or "I'm too good at my job."
- Over-sharing: long personal stories or health details you don't need to share.
- A weakness that contradicts your resume: claiming you struggle with deadlines after listing on-time delivery as a key strength.
Never name a weakness that suggests dishonesty, unreliability, or trouble with authority. Even with a great fix, those raise questions that a single interview answer can't resolve.
Greatest weakness examples by role#
The examples below show how the formula changes by job. Use them to see the structure, then build your own from your real experience. Copying a sample answer word for word tends to sound rehearsed, and interviewers may probe with follow-up questions you can't answer.
Software engineer: underestimating task time#
Estimating is useful for engineers but usually not the core skill being hired for. The fix can be concrete and measurable.
I've tended to underestimate how long tasks will take, especially when they touch code I haven't worked in before. On one feature last year, my two-day estimate turned into five, and our sprint plan had to shift.
Since then, I break any task over a day into smaller pieces before estimating, and I add a buffer for unfamiliar code. I also log my estimate next to the actual time in our tracker. Reviewing that each sprint has shown me exactly where I'm optimistic.
My estimates over the last three months have been within about 20% of actual time, and my lead has started using them for release planning. I still check myself on unfamiliar areas.
Customer service representative: dwelling on difficult calls#
This is honest, common, and shows emotional self-management without suggesting you can't handle customers.
After a tough call, I used to replay it in my head, and it affected my tone on the next one or two calls. My team lead noticed it in our quality reviews.
Now I use a short reset routine: I write one line about what I'd do differently, take a 30-second pause, and read the next customer's history before I pick up. If a call was especially rough, I flag it for my lead so we can talk it through later instead of me carrying it all shift.
My quality scores on calls that follow escalations have improved since I started, and I feel much steadier across a full shift.
Teacher: spending too long on written feedback#
Detailed feedback sounds positive, but the real weakness is time management, and the fix shows structure.
I used to write long comments on every assignment, which meant students sometimes waited over a week to get work back. By then, the feedback was less useful.
Last year I built a rubric with a bank of specific comments for the most common issues, and I focus my written notes on one strength and one next step per student. For major projects, I hold short conferences instead of writing everything out.
I now return most assignments within three school days, and students are acting on the feedback more because it arrives while the unit is still fresh. I'm still refining the comment bank each term.
Project manager: too much detail in status updates#
Communication is important for project managers, so frame this as audience adjustment rather than poor communication.
My status updates used to be too detailed for senior stakeholders. I'd include every task and risk, and a director once told me she had to read three paragraphs to find out whether we were on track.
Now every update starts with a one-line status, green, yellow, or red, followed by the top three items leadership needs to know. The detailed task list sits in a linked document for anyone who wants it.
Executives respond to my updates faster now, and the director who gave me that feedback asked me to share the template with two other project leads. I still write the detailed version first; I just don't lead with it.
Accountant: explaining numbers to non-finance colleagues#
For accountants, accuracy and integrity are core, so steer clear of them. Explaining results to non-finance audiences is useful but usually secondary, which makes it a strong choice.
I've found it hard to explain financial results to managers outside finance. Early on, I'd walk department heads through every variance, and I could tell I was losing them halfway through the meeting.
Now I prepare a one-page summary for each monthly review: the three numbers that changed most, why they changed, and what it means for their budget. I keep the full detail in a backup tab if they want it. I also ask one question at the end to check what they'll do with the information.
Two department heads now ask for the summary before our meetings, and our variance reviews have gone from an hour to about 30 minutes. I'm still working on making the summaries visual.
Other roles at a glance#
Not every role needs a full script. Here are starting points you can adapt using the same formula.
- Sales representative: Keeping CRM notes current after calls. Fix: a 10-minute block at the end of each day. Proof: forecast accuracy improved.
- Registered nurse: Learning advanced reporting in a new electronic health record system. Fix: super-user training and practice reports. Proof: now helps colleagues pull unit data.
- Data analyst: Exploring data too long before confirming the question. Fix: a 15-minute scoping call with the requester first. Proof: fewer rework requests.
- Manager: Waiting too long to give corrective feedback. Fix: addressing issues within 48 hours in a scheduled one-on-one. Proof: smaller issues stay small.
- Administrative assistant: Hesitating to push back on conflicting calendar requests. Fix: clear priority rules agreed with the executive. Proof: fewer double bookings.
Weakness examples by type, with fixes#
If you want more options, this table covers common weaknesses that work in many roles, along with a concrete fix you could describe. Treat it as a menu of patterns, not a script. Your answer needs your own example and your own result.
| Weakness | How to frame it | A concrete fix | Avoid if the role is |
|---|---|---|---|
| Saying yes too often | Taking on requests before checking priorities | Weekly priority check with your manager | Highly self-directed with no manager |
| Asking for help late | Trying to solve everything alone first | A 30-minute rule before asking | Solo or fully independent |
| Over-detailed updates | Giving more detail than the audience needs | One-line summary first, detail linked | Communications or executive support |
| Speaking up in large meetings | Sharing ideas later in writing instead of live | Prepare one point before each meeting | Sales, teaching, or client-facing |
| Delaying hard conversations | Waiting too long to raise concerns | Raise issues within 48 hours | People management |
| Underestimating timelines | Optimistic estimates on new work | Break tasks down, track estimate vs actual | Project management |
| A secondary tool gap | Limited experience with a specific tool | A course plus a real project using it | Roles where that tool is required |
| Impatience with slow processes | Frustration with manual workflows | Document and propose one fix at a time | Heavily regulated, process-bound work |
| Overcommitting to side projects | Volunteering for too much outside your role | Limit to one extra project per quarter | Roles that reward broad involvement |
| Discomfort with ambiguity | Wanting clear specs before starting | Draft a short plan and confirm it early | Startups or research roles |
Notice the last column. The same weakness can be safe in one role and risky in another, which is why you should check the job posting before you choose.
Weakness answers for new grads and career changers#
Your experience level changes which weaknesses are safe and where your examples come from.
If you're a student or recent graduate#
Interviewers expect less experience, so a skill gap is often your most honest and safest answer. Draw your examples from school projects, internships, part-time jobs, or volunteering. A good structure is: "In my group capstone project, I noticed I..." Our guide to the STAR method shows how to turn those experiences into tight stories.
Good options for new grads include speaking up in large meetings, asking for help early enough, estimating how long assignments take, or a software tool you haven't used professionally yet.
If you're changing careers#
Industry knowledge is a natural weakness to name, because the interviewer already knows you're new to the field. Name the gap directly, then show how fast you're closing it: courses, certifications, informational interviews, side projects. This turns an obvious concern into proof of initiative. Our guide on how to change careers covers how to present the transition consistently across your resume and interviews.
My biggest gap is experience with corporate learning tools. I've designed curriculum for eight years, but mostly for classrooms, not for e-learning platforms.
Over the past six months, I've completed a course in a common authoring tool and built three short modules for a nonprofit, including one on volunteer onboarding that they now use for new sign-ups. I'm also learning how corporate teams measure training results, which is different from how schools measure learning.
I'm not as fast in the tools as someone with five years in the field yet, but my instructional design foundation is strong, and the tool skills are coming quickly.
Before-and-after rewrites of weak answers#
Most weak answers have the right weakness and the wrong structure. Here's how small changes transform them.
BeforeI'm a perfectionist. I just want everything to be right.
AfterI've tended to keep polishing work after it's good enough. On a client report last year, I spent an extra day on formatting while the client was waiting. Now I set a done checklist at the start of each project and share a draft once it meets the checklist. My last four client reports went out on or before the deadline.
BeforePublic speaking makes me nervous. I've always been more of a behind-the-scenes person.
AfterI used to avoid presenting in team meetings. Last year I joined a speaking club at work and volunteered to present our monthly metrics. The first few were rough, but I've now presented six times, and last month my manager asked me to present our results to the regional director.
BeforeSometimes I'm not as organized as I could be.
AfterI used to track tasks across email, sticky notes, and a notebook, and a vendor invoice slipped through once. I moved everything into one task app with due dates and a 10-minute review every morning. I haven't missed a payment deadline since, and my manager now forwards me the team's vendor follow-ups.
How to handle follow-up questions#
Interviewers often dig deeper after your first answer. Prepare for these, because a strong main answer can unravel on a weak follow-up.
| Follow-up | What it tests | How to respond |
|---|---|---|
| "Can you give me another weakness?" | Whether you prepared only one | A second weakness from a different category, shorter |
| "How would that show up in this role?" | Realism about the job | A specific scenario and how your fix would handle it |
| "What would your manager say your weakness is?" | Consistency with external views | The same or a related weakness, framed as their feedback |
| "Why haven't you fixed it yet?" | Persistence and honesty | Explain progress and why it's an ongoing habit, not a one-time fix |
| "What did you learn from that?" | Reflection | The broader principle you now apply elsewhere |
The best way to prepare is to have two weaknesses ready, each with a different fix and proof point. If you're asked for a third, a brief answer about a skill you're actively learning works well.
If you blank on the question#
Nerves can wipe out even a well-prepared answer. If it happens, don't apologize at length. Say, "Let me think about the most honest example," take a breath, and start with the weakness itself. Once you name it, the fix and proof usually come back, because you practiced them together. A short pause sounds thoughtful; a rushed, invented answer doesn't.
Variations of the weakness question#
The question doesn't always use the word "weakness." Recognize these versions so you can use the same prepared answer:
- What's an area you'd like to improve?
- What would your manager say you need to work on?
- What feedback have you received that surprised you?
- What's a skill you're developing right now?
- Tell me about a time you failed.
The last one is a behavioral question, so it needs a full story with a result. Our list of behavioral interview questions covers that format, and the free STAR method answer generator can help you structure the story.
How to answer "What is your greatest strength?"#
Interviewers often ask about strengths first, or ask for "strengths and weaknesses" together. The strength answer should be the mirror image of the weakness answer: central to the job, specific, and proven.
Use Claim, Proof, Link:
- Claim: Name one strength that matches a top requirement in the job posting.
- Proof: Give a specific example with a result.
- Link: Connect it to what the employer needs.
My greatest strength is finding the root cause of recurring problems instead of patching symptoms.
At my current company, our warehouse had repeated shipping errors on one product line. Rather than adding another inspection step, I traced the errors back to a labeling mismatch between two systems. Fixing that one mapping cut errors on that line to almost zero within a month.
Your posting mentions reducing fulfillment errors as a key goal for this role, and that kind of investigation is exactly the work I enjoy most.
Strength examples by role#
Your strength should match what the job needs most. Some starting points:
- Software engineer: Breaking large problems into small, testable pieces. Proof: a complex feature shipped with few defects.
- Customer service: Staying calm and solution-focused with upset customers. Proof: high satisfaction scores on escalated cases.
- Teacher: Adapting lessons for students at different levels. Proof: improved results for a specific group.
- Project manager: Spotting risks early and getting decisions made. Proof: a project that stayed on schedule despite a major change.
- Sales representative: Building trust quickly with new prospects. Proof: conversion rate from first call to second meeting.
- Accountant: Building checks that catch errors before close. Proof: fewer adjustments after month-end.
Pick the one that matches the posting, then make the proof as specific as you can. A number, a named project, or a direct piece of feedback all work.
Answering strengths and weaknesses together#
When both come in one question, lead with the strength, keep it slightly shorter, then move to the weakness and finish on your progress. Make sure the two don't contradict each other. Claiming strong organization as a strength and disorganization as a weakness will confuse the interviewer. For more on presenting your strengths, see our guides to answering "why should we hire you" and soft skills for your resume.
How to practice your answer#
A weakness answer only works if it sounds natural. That takes a few rounds of practice out loud.
- Write it out once, using Honest, Fix, Proof, then cut it to under 170 words.
- Reduce it to keywords: the weakness, the moment, the fix, and the result. Practice from those, not the full text.
- Say it out loud three times, timing each. Aim for 45 to 75 seconds.
- Record one version and listen for defensive or apologetic phrasing. Replace "unfortunately" and "I'm really bad at" with neutral language.
- Ask a friend to follow up with "Can you give me another one?" so you practice your second weakness too.
The free mock interview practice tool can ask the weakness question and its common follow-ups, and score your answer for structure. For a broader set of practice prompts, see our guide to AI mock interviews. To see which other questions you're likely to face for a specific role, paste the posting into the free interview question generator.
Adjust delivery for phone and video interviews#
On a phone screen, the interviewer can't see your expression, so a calm, steady tone matters more. Keep your answer toward the short end, around 45 seconds. On video, look at the camera when you describe your fix and your result; those are the parts you want to land with confidence.
Your next steps#
Pick two real weaknesses that aren't core to your target role. Write each using Honest, Fix, Proof, and make sure each has a result you can state in one sentence. Then prepare a strength answer that matches the job's top requirement.
Practice all three out loud before your next interview, and add them to your broader prep for common interview questions. If your weakness came from formal feedback, our guide to self-evaluation examples can help you describe your growth in performance reviews too.
Frequently asked questions
Sources
- Structured Interviews, U.S. Office of Personnel Management
- What Employers Want (NACE Job Outlook 2026 Spring Update table), Iowa State University LAS Career Services
- What Are Employers Looking for When Reviewing College Students' Resumes?, National Association of Colleges and Employers (NACE)
- Summary Report for 13-2011.00 Accountants and Auditors, O*NET OnLine, U.S. Department of Labor
Free tool
STAR Method Answer Generator
Turn a work story into a structured STAR interview answer.
Try it freePut this into practice
Draft your resume with an AI assistant that edits inline, then export a clean one-page PDF.
Build my resumeKeep reading
More in InterviewsInterviews19 min read
The STAR Method: How to Answer Behavioral Interview Questions
Use the STAR method to answer behavioral interview questions: time splits for each part, 8 example answers, a story bank template, and variations like CAR.
Interviews19 min read
Behavioral Interview Questions and Sample Answers
60+ behavioral interview questions grouped by competency, with sample STAR answers, a story prep grid, and help decoding the trickiest questions.
Interviews21 min read
50 Common Interview Questions and How to Answer Them
Prepare for 50 common interview questions grouped by type, with five answer frameworks, short examples, and a story bank that covers most of them.