What Is Your Greatest Weakness? Examples

A strong answer to "What is your greatest weakness?" names a real, role-relevant limitation, shows a specific cost, explains what you changed and acknowledges what still needs work. Choose something you can discuss honestly without hiding a requirement essential to the job. The examples below are fictional practice patterns, not claims to repeat as your own experience.

Everyone knows this question is coming and most people still fumble it, because the standard advice (pick a strength and disguise it) stopped working years ago.

"I'm a perfectionist." "I care too much." "I work too hard." Interviewers hear these constantly. The answer is not just unconvincing; it actively answers the real question badly, because the real question is not what are you bad at.

What they are actually asking

Three things, in order:

1. Do you know yourself? Someone who cannot name a weakness either has not reflected or is not being straight. Both are a problem.
2. Do you do anything about it? A weakness you are working on is an ordinary professional trait. A weakness you have never addressed is a risk.
3. Is it disqualifying for this job? They are not hoping you have no weaknesses. They are checking that yours is not the thing the role is made of.

Point three is the only real constraint. Everything else is fair game.

A structure that works

Name it plainly. One sentence, no hedging, no disguise.

Say what it actually costs. A specific instance where it caused a real problem. This is the part that makes it credible: an abstract weakness is indistinguishable from a made-up one.

Say what you changed. Not "I'm working on it". A mechanism: a habit, a check, something you now do differently.

Say where it stands. Honest, not triumphant. "Better, not solved" is a perfectly good ending and more believable than a cure.

Worked example:

"I under-communicate when I'm deep in a problem. On a migration last year I went quiet for most of a week, and my manager found out we'd slipped from someone else. Since then I post a short status at the end of each day, whether or not there's progress. It felt like overhead for about a fortnight and now I don't think about it. I still have to make myself do it when things are going badly, which is exactly when it matters most."

That last clause does more than the rest of the answer. It shows you are still watching it.

Eight greatest-weakness answer examples

The right example depends on the job. Use these as patterns, not scripts: name the weakness, show its cost, explain the mechanism you changed, and be honest about where it still needs attention.

Delegating too late

"I used to hold onto work longer than I should because explaining it felt slower than doing it myself. On one launch that made me the bottleneck for two approvals. I now assign owners when the work is planned and write the handoff before I start my own part. I still notice the urge to take work back when a deadline gets tight, so I check that explicitly in our daily update."

Asking for help too late

"I can spend too long trying to solve a problem alone. Last year I lost most of a day on an integration issue that a teammate recognised in ten minutes. I now set a 45-minute limit: if I have no new evidence by then, I write down what I tried and ask someone to challenge it. I am faster at escalating, but I still have to watch it when the problem is interesting."

Over-polishing before sharing

"My first instinct is to make a draft presentable before anyone sees it. That delayed feedback on a proposal and I ended up polishing a direction the team did not want. I now share an outline at 20 percent and label what is still rough. The work is better, although showing an unfinished idea still feels less comfortable than it should."

Saying yes too quickly

"I have been too quick to accept extra work before checking what it displaces. In one sprint I agreed to three small requests and put the main deliverable at risk. Now I answer with the trade-off: I can take this on, but this other item moves. I am better at making the choice visible instead of silently absorbing it."

Presenting to large groups

"I am comfortable in a working session but less natural in a formal presentation. I rushed through a quarterly review and left too little time for questions. I now rehearse the opening out loud, cut the slide count, and ask a colleague to interrupt me once in practice. I still get nervous, but it no longer controls the pace."

Focusing on detail before direction

"I can go deep before confirming that the direction is right. On a reporting project I spent two days improving a calculation before learning the team needed a different decision entirely. I now write the decision and audience at the top of the brief before analysing anything. I still enjoy the detail; the check keeps it attached to the outcome."

Giving feedback too indirectly

"I used to soften difficult feedback so much that the other person could miss the point. That happened with a repeated review problem and it took a second conversation to resolve. I now state the observed behaviour, its impact, and the change I am asking for before adding context. I can be direct without making the conversation harsh."

Learning an unfamiliar tool

"I have less hands-on experience with [tool] than this role ideally asks for. The closest work I have done is [related example], where I learned a similar system while delivering [result]. I have completed [specific preparation] and can explain what transfers, but I would still expect a learning curve in the first few weeks."

The last example works only when the missing tool is not the core qualification for the role. Do not use a weakness answer to negotiate away a requirement the interviewer has already said is essential.

Choosing one

Two constraints.

Not the core of the job. Do not tell an interviewer for a customer-facing role that you find people draining. Not because it is dishonest to say so, but because it answers a different question (should you have this job?) and the answer becomes no.

Real, but not alarming. "I miss deadlines" and "I clash with managers" are answers to a question nobody asked. Good territory: delegation, saying no, over-polishing before sharing, asking for help too late, communicating under pressure. Common, genuine, fixable, and not disqualifying.

If you are asked for more than one

Some interviewers ask for two or three. Prepare a second; it need not be as developed. The failure here is visible scrambling after the first one, which suggests the first was the only one you had.

What not to do

• Don't say you have none. It reads as either no self-knowledge or no honesty.
• Don't confess something that ends the conversation. Honesty is not the same as volunteering a reason not to hire you.
• Don't over-rehearse it. Word-for-word delivery on this question in particular sounds exactly like what it is.

---

The test of this answer is whether it survives "can you give me another example?", which is how interviewers check whether the first one was real. Use the STAR structure to make the example concrete, then rehearse it and find out.

How to practise your weakness answer

Record a short answer, then check four things: did you name the weakness, explain a consequence, describe a repeatable change and say what you still watch? Ask a friend to challenge one detail rather than simply tell you it sounds good. Keep the answer specific enough that you could explain the incident if the interviewer asks.

For story-based questions, practise the complete STAR examples. If the interview is close, use the seven-day preparation checklist to decide what to practise first.