"What are your weaknesses?" is the interview question candidates dread most, and the one they most often answer with a disguise: "I'm a perfectionist." Interviewers hear it every week, and it tells them nothing except that you prepared a dodge.
This guide shows you how to answer the weakness question honestly without hurting your chances: what the interviewer is really scoring, a three-step formula (name, proof, fix), how to pick a weakness that fits the role, ten complete example answers, and how to handle the strengths half of the question.
What Is the Interviewer Really Assessing?
The question is not a trap to make you confess something disqualifying. As the University of Alabama Career Center puts it, "interviewers want to know if you're honest and self-aware." Your weakness itself matters less than how you talk about it.
Behind the question, the interviewer is scoring three things:
- Self-awareness — can you see your own pattern, or only other people's?
- Honesty under pressure — will you give a real answer to an uncomfortable question, or a rehearsed escape?
- Correction — once you noticed the problem, did you do anything about it?
There is also a silent fourth check: whether the weakness is a deal-breaker for this specific job. Mary Ryan, an associate director of career services at UNC Kenan-Flagler's online MBA, told Training Industry that answers reveal whether candidates can "give a genuine answer to an uncomfortable question" or have a weakness that is a "deal-breaker for the job at hand."
How to Answer "What Are Your Weaknesses?" in Three Steps
A strong answer has three parts, in this order, and fits in 45 to 60 seconds. Each part does a specific job, so dropping one weakens the whole answer.
- Name it — one specific, work-related weakness, in plain words. Not a personality label ("I'm disorganised") but a behaviour ("I lose track of follow-ups when I juggle several projects").
- Prove it — one short, real moment when it cost something. This is what makes the answer credible; a weakness with no consequence sounds invented.
- Fix it — what you changed, and the evidence it works. End here, on the action, not on the problem.
How the formula looks in a real answer:
I tend to take on too much myself instead of delegating.1 Last spring I kept the quarterly report to myself and finished it two days late, while two colleagues had spare capacity.2 Now I split every project into tasks on day one and assign at least half before I start.3 The last two reports went out on time, and one teammate now owns the data section.4
- 1Name it: a behaviour, not a personality label.
- 2Prove it: one real moment with a cost.
- 3Fix it: a concrete change you can describe.
- 4Evidence: the fix is working, and you end on it.
Notice what the answer does not contain: no apology, no "but it's also a strength", no reassurance that the weakness is fully gone. A weakness you are still managing is more believable than one you claim to have cured.
The structure will feel familiar if you have prepared behavioural answers. It is a compressed cousin of STAR, and our guide to interview answer structure explains how to adapt it when a question asks about mistakes or failure.
How Do You Choose the Right Weakness for the Job?
The same weakness can be harmless in one role and disqualifying in another. Before you pick one, read the job advert and remove anything that touches its core requirements. What is left is your shortlist.
| Weakness | Usually safe for | Red flag for |
|---|---|---|
| Public speaking | Developer, analyst, back-office roles | Sales, teaching, client-facing roles |
| Delegating | Individual contributors, first-time leads | Senior managers with large teams |
| Attention to detail | Creative, strategic, early-stage roles | Accounting, compliance, QA, healthcare |
| Saying no to requests | Most roles, if you show a system | Project management, roles that own priorities |
| A specific tool or skill gap | Any role where the tool is a nice-to-have | Roles where the advert lists it as essential |
| Impatience with slow processes | Startups, operations improvement | Highly regulated or process-driven teams |
Two more filters help. The weakness should be real and current, because the interviewer may ask how it showed up last month. And it should be work-related: personal traits, health or family matters have no place in this answer.
10 Example Answers to "What Are Your Weaknesses?"
Each example follows the name–prove–fix formula. Use them to see the shape, then rebuild the answer from your own experience: an interviewer can usually tell when a story is borrowed.
1. Delegating (team lead or senior specialist)
I find it hard to hand over work I know I can do quickly myself. On a product launch last year that meant I was the bottleneck for every sign-off, and two people on my team were waiting on me for days. Now I decide on day one which decisions I keep and which I hand over, and I check in on outcomes rather than steps.
2. Public speaking (analyst or developer)
Presenting to large groups does not come naturally to me. In my last role I let a colleague present an analysis I had built, and the client's follow-up questions came to me anyway, a week later. Since then I volunteer for the short internal demo every month, and I now present my own work to clients, with notes.
3. Saying yes to too much (support or operations)
I used to accept every request that came in, because saying no felt unhelpful. Last year that meant two important tickets slipped while I handled quick favours. Now I keep a visible priority list and, when a new request arrives, I ask which current task it should replace. Most people are happy to wait once they see the list.
4. A specific skill gap (marketing or junior data role)
My SQL is basic. In my current job I depend on the data team for any query beyond a simple filter, which slows my campaign reports by a day or two. I started an evening course three months ago and I now write my own weekly reporting queries; joins across several tables are the next step.
5. Giving direct feedback (new manager)
I tend to soften feedback so much that the message gets lost. A team member once repeated the same mistake for weeks because my comments sounded optional. Now I prepare feedback in two lines — what happened and what I need next time — and I say those two lines first, before any context.
6. Too much detail in written work (consultant or analyst)
I over-explain in writing. My first board summary was nine pages when the directors wanted two, and the key recommendation was on page six. I now write the recommendation first, in three sentences, and move everything else to an appendix. My last two summaries came back with no requests for clarification.
7. Asking for help too late (graduate or junior)
When I am stuck, I keep trying alone for too long. During my internship I spent two days on a problem that my supervisor solved in ten minutes once I asked. Now I give myself a fixed limit — an hour of real effort — and then I ask, with a note of what I have already tried.
8. Impatience with slow decisions (moving from a startup)
I get impatient when decisions take longer than I think they should. Coming from a small company, I pushed a change through without waiting for the security review, and we had to roll it back. I have learned to ask early who needs to approve what, and to plan that time into the schedule instead of fighting it.
9. Industry knowledge gap (career changer)
I am new to this industry, so I do not yet know its regulations as well as someone who has worked in it for years. When I moved into my current role I misjudged a compliance deadline in my first month. I now keep a regulatory calendar, I read the sector newsletter every week, and I am halfway through an introductory certificate.
10. Not making your work visible (experienced specialist)
I am not good at showing my own results. A colleague was credited with a cost saving I had largely designed, simply because he presented it. Now I send a short monthly summary of what I delivered to my manager. It felt uncomfortable at first, but it has made my reviews far more accurate.
How to Answer "What Are Your Strengths?"
The strengths question looks easier and is answered just as badly. "I'm hard-working and a team player" could describe anyone. The fix mirrors the weakness answer: one strength, taken from the job advert, proven by one story.
- Pick from the advert. Read the requirements and choose the one you can prove best, not the one that sounds most impressive.
- Prove it with a result. One concrete example, ideally with a number or a visible outcome.
- Connect it to the role. End with one sentence on how that strength would help in this job.
One of my strengths is turning messy information into something people can act on. In my last role the sales team had four spreadsheets that disagreed with each other; I merged them into one weekly dashboard, and the Monday meeting went from an hour to twenty minutes. Your advert mentions reporting to regional managers, which is exactly that kind of work.
When the interviewer asks for strengths and weaknesses together, give the strength first and keep it short, then the weakness with its fix. That order means you finish on the action you took, not on the problem. If they ask for three of each, prepare three, but give one full example and keep the others to a sentence each.
Which Weaknesses Should You Never Mention?
Most weak answers fail in predictable ways. Check your draft against this list before you rehearse it:
Do
- Name one real, current, work-related weakness
- Give one moment when it cost something
- Describe what you changed and how you know it works
- Choose something outside the job’s core requirements
- Keep it under a minute
Avoid
- “I’m a perfectionist” or “I work too hard”
- “I don’t really have any weaknesses”
- A weakness in a core skill listed in the advert
- Health, family or personality labels
- Saying the weakness is completely solved
- Apologising or over-explaining
The humblebrag deserves a special mention. Answers like "I care too much" are meant to sound safe, but they fail the honesty check the question exists for, and they suggest you will hide real problems on the job as well.
How to Practise Your Answer
Write your answer out once using the three steps, then reduce it to three bullet points: the weakness, the moment, the fix. Memorise the points, not the sentences, so the answer survives a follow-up question.
Expect at least one follow-up: "Can you give me another example?" or "How would your manager describe it?" Having a second, shorter example ready makes the first one far more believable.
The weakness question rarely comes alone. If you are preparing for your first job, our interview questions for candidates with no experience cover it alongside the other seven classics, with answers built from studies and volunteering. And since most interviews open with a different classic, it is worth preparing how to answer "tell me about yourself" at the same time.
The short version: one real weakness, one moment it cost you, one change that works, all in under a minute. To hear how it sounds before it counts, rehearse it with the AI job interview simulator, which builds a practice interview from your CV and the job description and gives you feedback on each answer.
Frequently Asked Questions
How many weaknesses should I mention in an interview?
One, unless the interviewer asks for more. A single weakness with a real example and a clear fix is stronger than three named in passing. If they ask for three, prepare three but develop only one in full.
Can I say "I have no weaknesses"?
No. It fails the exact thing the question tests — self-awareness — and signals either overconfidence or evasion. Every interviewer knows that every candidate has something to work on.
Is "I'm a perfectionist" a bad answer?
Usually, yes, because it is the most common disguised strength and interviewers recognise it instantly. If perfectionism is genuinely your issue, describe the behaviour instead, such as missing deadlines because you keep revising, and show what you changed.
Should I mention a weakness that is relevant to the job?
Choose one that is related to work but not to the core requirements of this role. A developer can mention public speaking; a salesperson should not. Read the job advert and rule out anything listed as essential.
What is a good weakness if I have no work experience?
Draw on studies, group projects or part-time jobs: asking for help too late, underestimating how long tasks take, or a gap in a specific tool. The formula is the same: name it, give one real moment, and show what you do differently now.