How to Answer "What Is Your Greatest Weakness?"
How to choose an honest weakness that is not central to the job, structure your answer, and avoid the replies interviewers have heard too often.
By the Nextrova team · · 6 min read
Interviewers do not ask this question hoping to hear that you are perfect. They want to see whether you know yourself, whether you can talk about a shortcoming without getting defensive, and whether you act on feedback. A plain, honest answer with a clear improvement plan does all three. A disguised strength does none of them.
Why do interviewers ask about your greatest weakness?
The question tests several things at once:
- Self-awareness. Do you know where you struggle?
- Honesty. Will you give a real answer or a rehearsed dodge?
- Growth. When you spot a problem, do you do something about it?
- Fit. Is your weakness something this role cannot work around?
It comes in several versions: "What would your manager say you need to work on?", "Tell me about an area for development" or "What feedback have you had that was hard to hear?" Prepare one answer and adapt it to the wording.
How do you choose the right weakness?
A good weakness for this question passes five tests:
- It is real. You can give an actual example.
- It is not core to the role. Read the posting and rule out anything that hits a must-have.
- It can be improved. Skills and habits work better than fixed personality traits.
- You are already working on it. You have taken at least one concrete step.
- It is appropriate to share. Keep it professional. Health, family and other private matters are not what the question is about.
Good places to look: past performance reviews, feedback from managers or colleagues, and the moments at work you found hardest.
Whether a weakness is safe depends on the job. The same answer can be harmless for one role and disqualifying for another.
| Weakness | Usually manageable for | Risky for |
|---|---|---|
| Presenting to large groups | Analyst, developer and back-office roles | Sales, training and communications roles |
| Delegating work | Individual contributor roles | Senior management roles, unless you show clear progress |
| Saying yes to too many requests | Most roles, if you show how you now prioritize | Roles centered on managing other people's workload |
| Little experience with a tool not in the posting | Roles that do not use it | Roles where the posting lists it as required |
| Impatience with slow processes | Fast-moving teams | Compliance-heavy or regulated work |
How should you structure your answer?
Use three parts:
- Name the weakness plainly. One sentence, no hedging.
- Give a short real example. One or two sentences on how it showed up at work.
- Explain what you are doing about it. The specific steps, and a sign of progress.
Spend most of your time on the third part. That is where the interviewer learns how you handle problems.
What are some good example answers?
These answers are fictional and meant to show the structure. Use your own real weakness and your own words, because a memorized script sounds like one.
FICTIONAL EXAMPLE 1: software developer, presenting
"Presenting to large groups doesn't come naturally to me. In my last role I prepared well for sprint demos but rushed through them, and my manager told me stakeholders were missing key points. Since then I've volunteered to run our team's demo regularly, and I rehearse with a colleague beforehand. I'm not a natural presenter yet, but the feedback on recent demos has been that they're clearer and easier to follow."
FICTIONAL EXAMPLE 2: new team lead, delegating
"My weakness has been delegating. When I first became a team lead, I kept the hardest tickets for myself because it felt faster, and two people told me in one-to-ones that they weren't getting stretch work. Now I plan the week's work with the team on Mondays and hand at least one complex task to someone else, with a check-in midweek. It was slower at first, but one person on the team now handles escalations I used to take."
FICTIONAL EXAMPLE 3: graduate, tool experience
"I don't have much hands-on experience with [tool] yet. My degree projects used [other tool], so I understand the concepts, but not that product specifically. I've started an introductory course and built a small practice project with it, and I plan to keep learning in my first months on the job."
The third example works because, in this fictional case, the posting lists the tool as preferred, not required. If it were a core requirement, choose a different weakness and address the tool gap separately.
Which weakness answers should you avoid?
- "I'm a perfectionist" or "I work too hard." Interviewers recognize these as strengths in disguise, and they suggest you are avoiding the question.
- "I don't really have any weaknesses." This fails the self-awareness test straight away.
- A weakness central to the job. For example, "I struggle with deadlines" for a project coordinator role.
- A weakness with no action attached. Naming the problem without a plan makes it sound permanent.
- Jokes. "Chocolate" might get a smile, but it wastes the question.
- Personal or health details. These are private and not what the interviewer is asking about.
- Blaming others. "My last manager never gave clear instructions" is a complaint, not a weakness.
- Long confessions. Several minutes on a single flaw changes the tone of the whole interview.
How do you handle follow-up questions?
Interviewers sometimes push a little further. Prepare for:
- "Can you give me another one?" Have a second weakness ready, built the same way.
- "How do you know you're improving?" Point to feedback, a result, or a change someone else noticed.
- "What would your current manager say?" Your answer should match what that manager would actually say if contacted for a reference.
Weakness questions also come up indirectly, when an interviewer asks about a requirement your resume does not show. Treat those the same way: acknowledge the gap honestly, mention the closest experience you have, and say how you would close it.
How can Nextrova help you prepare?
Gaps between your resume and the posting are often where interviewers probe. Nextrova's resume checker compares your resume with the job posting and lists which requirements it found, with the line as evidence, and which are missing, so you know which questions to prepare for. The first check is free. Pro also includes interview prep built from your CV; see the pricing page for plan details.
Related questions
Can my weakness be a technical skill?
Yes, if the skill is not a core requirement for the role. Show what you are doing to learn it.
Should I use the same weakness in every interview?
You can, if it suits each role. Check it against every new posting, because a safe weakness for one job can be a red flag for another.
What if they ask for three weaknesses?
Prepare two or three in advance, each with a short example and an improvement step. Keep each answer brief.
Is it ever fine to say "I'm a perfectionist"?
Only if you describe a specific, real problem it causes, such as missing deadlines by over-polishing, and what you now do differently. Even then, a less common example usually works better.
Try it
Tools for this step.
Keep reading
Related guides.
Job search
6 min read
Questions to Ask at the End of an Interview
Good questions to ask an interviewer about the role, the team, how success is measured and next steps, which to save for later, and how many to ask.
Job search
6 min read
How to Spot a Fake Job Posting
Warning signs of fake job postings, how to check that a company and recruiter are real, and how to protect your personal data while you apply.
Job search
7 min read
How to Get a Call Back After Applying for a Job
A practical, honest guide: fewer and better applications, evidence for each requirement, a readable file, and a sensible follow-up.