How to answer “What is your greatest weakness?” in English

What is the interviewer really checking when they ask about your weakness?

Nobody expects you to confess something that disqualifies you. The question is a test of self-awareness and honesty, and of how you handle an uncomfortable question in real time.

• Self-awareness: do you know where you are weaker, or do you think you have no gaps?
• Honesty: is the answer real, or a strength in disguise?
• Action: when you find a problem in yourself, do you do something about it?
• Composure: can you talk about a negative without getting defensive or over-explaining?

The last point matters more in a second language. A candidate who stays calm, names the weakness in one sentence, and moves to the fix sounds senior. A candidate who circles for a minute before saying anything sounds evasive, even when the content is fine.

What structure should you use for your answer?

Use three steps: name it, show it, fix it. Spend about 20% of your time on the weakness and 80% on what you do about it.

1. Name it in one plain sentence. “One thing I’ve had to work on is delegating.”
2. Show it with a short, real example. “In my first year as a team lead, I kept the hardest tasks for myself, and two people on my team told me in a review that they felt underused.”
3. Fix it with specific steps and a result. “Now I assign the hard ticket first and offer to pair on it instead of doing it myself. In the last two quarters, three people on my team have led features end to end.”

Choose a weakness that is real but not a core requirement of the role. If the job is mostly public speaking, do not say public speaking. If it is a data role, do not say attention to detail.

What does a weak answer sound like compared with a strong one?

Notice the verbs in the strong column: used to, now, set, prepare, plan. They show change over time, which is what the interviewer wants to hear.

What are good example answers for different roles?

Each answer is about 45 to 60 seconds when spoken at a calm pace. Use them as a pattern, not a script.

Software engineer: “One thing I’ve had to work on is asking for help early. I used to spend a whole day stuck on a problem before I’d message anyone, because I wanted to solve it myself. On one project that delayed a release by two days, and the fix took a colleague about twenty minutes. Since then I use a simple rule: if I’m stuck for more than an hour, I write a short message explaining what I tried and ask for a second pair of eyes. It’s made me faster, and honestly it’s made the team better at sharing knowledge too.”

Project manager: “I tend to take on too much myself when a project is under pressure. A couple of years ago, during a big migration, I was writing status reports, running meetings, and fixing the plan at the same time, and some risks didn’t get escalated early enough. Now I assign a clear owner for each workstream at the start, and I keep my own role to unblocking and communication. On my last project, that meant I spotted a supplier delay three weeks before it would have hit the timeline.”

Sales or finance: “I’ve had to work on presenting to senior people. I’m very comfortable with the numbers, but I used to explain the whole analysis before giving the conclusion, and executives would lose interest. A director told me that directly after a quarterly review. Since then I start every presentation with the recommendation and one number, then give detail only if they ask. My last two reviews were shorter, and both recommendations were approved.”

Which weaknesses should you avoid?

• Fake weaknesses: perfectionism, working too hard, caring too much. Interviewers hear these every day and read them as avoidance.
• Core skills for the role: a sales candidate who struggles with rejection, an accountant who is careless with numbers.
• Personality labels with no fix: “I’m impatient”, “I’m lazy”. A label sounds permanent. A behaviour can change.
• Your English level as the weakness. It invites the interviewer to judge the rest of the interview as a language test, and it is not a work behaviour.
• Personal problems: health, family, or anything private. Keep it professional.

What mistakes do non-native speakers make with this question?

• Over-hedging. “Maybe sometimes I can be a little bit…” stacks four softeners. Use one at most. “I’ve had to work on…” is already soft enough.
• Over-apologising. You do not need to say sorry for having a weakness. Everyone has one. Apologising makes it sound bigger.
• Translating idioms or proverbs about self-improvement. They rarely land in English. Plain verbs work better: learned, changed, now I.
• Sounding memorised. This is the question interviewers most expect to be rehearsed, so a word-perfect recital is easy to spot. Keep your example specific and tell it like a short story.
• Speaking too fast to get it over with. Slow down on the fix. That is the part you want them to remember.
• Mixing tenses. Use the past for the problem (“I used to”, “I missed”) and the present for the fix (“Now I”, “I always”). The contrast does the work for you.

How do you practise the answer out loud?

1. Write the weakness, the example, and the fix as three short lines.
2. Say the answer out loud with a timer. Target 45 to 60 seconds.
3. Record it. Listen for how long it takes you to name the weakness. If it is more than ten seconds, cut the warm-up.
4. Do the one-breath test on the first sentence. You should be able to name the weakness in a single breath, without pausing to soften it.
5. Prepare a second weakness. Some interviewers ask, “What else?” and a pause there looks worse than the first answer.

To rehearse with a counterpart, you can describe the role and the interviewer in a custom roleplay in Eloquent and answer out loud. The debrief quotes what you actually said, so you can see how many hedges you used and get a cleaner line to try next time.

Frequently asked questions