“What Is Your Greatest Weakness?” How to Answer, With 12 Examples
How to answer the greatest weakness question honestly: a three-part formula, 12 real weakness examples with sample answers, and the answers to avoid.
Key takeaways
- The question tests self-awareness and growth, not whether you are flawless.
- Use a real, non-critical weakness, show what you do about it, and give evidence of progress.
- Avoid fake weaknesses (“I’m a perfectionist”) and weaknesses in the core skill of the job.
- Keep it to about 60 seconds and end on the improvement, not on the problem.
- Prepare two weaknesses: interviewers often ask for a second one.
Contents
To answer “What is your greatest weakness?”, name a real weakness that is not central to the job, explain the concrete steps you are taking to improve it, and give evidence that it is working. That three-part answer shows what the interviewer is really testing: self-awareness, honesty and the ability to grow.
Below you will find the formula, a quick way to choose the right weakness for your role, 12 examples with sample answers, and the answers that quietly cost candidates the job.
Why interviewers ask about weaknesses
Nobody expects you to be flawless. The weakness question checks three things:
A candidate who says “I don’t really have weaknesses” fails all three at once. A candidate with a real, managed weakness passes all three.
The three-part formula
About 60 seconds in total.
- Name the weakness (10–15 s)Be specific and honest. “I’ve struggled with delegating” beats “Sometimes I take on too much”.
- Show the action (25–30 s)What you are doing about it: a habit, a tool, training, feedback you asked for.
- Give evidence (15–20 s)A concrete sign of progress: a result, a change in feedback, something you now do differently.
Notice that most of the time goes to the action. An answer that spends 50 seconds describing the problem leaves the interviewer remembering the problem.
How to choose the right weakness
The best weakness is real, specific and not essential for the role you are applying for. The same weakness can be safe for one job and fatal for another.
| Weakness | Fine for | Risky for |
|---|---|---|
| Public speaking | Software engineer, analyst, designer | Sales, teacher, consultant |
| Detailed documentation | Sales, early-stage product roles | QA engineer, compliance, technical writer |
| Delegating | Individual contributors, first-time managers | Senior manager, director |
| Saying no to requests | Most roles, if you show prioritization | Project manager, product manager |
| Working with spreadsheets | Engineering, design, creative roles | Financial analyst, operations |
| Patience with slow processes | Startups, fast-moving teams | Government, healthcare, regulated industries |
Never choose these
Avoid weaknesses that are core requirements of the job (a developer who struggles with debugging), character issues (honesty, reliability, punctuality), and anything that suggests you cannot work with people.
12 weakness examples with sample answers
1. Delegating tasks
My biggest weakness has been delegating. When I became a team lead, I kept taking the hardest tasks myself because it felt faster. It wasn’t sustainable, and it meant my team wasn’t growing.
Now, at the start of each sprint, I go through my tasks and ask which ones someone else could do with a bit of guidance, and I pair with them for the first hour. Last quarter I handed over our release process to a junior engineer, and she now runs it independently. My manager’s feedback in my last review specifically mentioned the change.
2. Public speaking
Presenting to large groups doesn’t come naturally to me. I’m comfortable in small meetings, but I used to over-prepare slides and rush through talks.
Last year I volunteered to give a 10-minute update at our monthly all-hands every quarter, and I practice each one with a colleague who gives me honest feedback. I’ve also started using fewer slides and more examples. My last talk ran on time and three teams asked for follow-up sessions, which is a good sign that it landed.
3. Saying yes too often
I tend to say yes to too many requests. I like helping, but a year ago I noticed I was regularly working late on other teams’ tasks while my own priorities slipped.
Now I keep a visible list of my current priorities, and when a new request comes in, I ask which existing task it should replace or offer a later date. It felt awkward at first, but people respond well when the trade-off is clear. I’ve hit all my quarterly goals since I started doing this.
4. Impatience with slow decisions
I can get impatient when decisions take a long time. In the past I sometimes pushed for a decision before everyone had shared their concerns.
I’ve learned that the slow part is often where risks come out. Now I ask people to send concerns in writing before the meeting and I set a clear decision date up front, so the process has a structure and I’m not pushing in the moment. Our last two architecture decisions were made faster than before and without anyone feeling rushed.
5. Too much focus on detail
I sometimes spend too long polishing work that is already good enough. Early in my career I’d rewrite reports several times, which delayed decisions.
Now I agree on the level of detail with my manager before starting, and I set myself a time box for each piece of work. For drafts, I share early versions labeled clearly as drafts. My turnaround time on analysis requests has dropped from about a week to two or three days, and the quality feedback hasn’t changed.
6. Asking for help
I used to wait too long before asking for help. I’d spend a day stuck on a problem a colleague could solve in ten minutes.
Now I use a simple rule: if I’ve been stuck for an hour without progress, I write down what I’ve tried and ask someone. Writing it down often solves the problem by itself. My team lead noticed I’m unblocked much faster, and I’ve started doing the same for newer team members.
7. Giving critical feedback
Giving critical feedback has been hard for me. I tended to soften it so much that the message got lost.
I took a short course on feedback and now use a simple structure: the specific behavior, its impact and a request. I also schedule regular one-on-ones so feedback isn’t saved up for big conversations. One of my team members told me in our last review that my feedback has become much clearer and more useful.
8. Lack of experience with a tool
I don’t have much hands-on experience with Kubernetes yet. In my current role our deployments are managed by a platform team.
Since I saw it’s used heavily here, I’ve been working through a course and I deployed my side project on a small managed cluster to learn the basics properly. I’m comfortable with the concepts now and I expect to get up to speed quickly with real production systems.
9. Difficulty with ambiguity
I’ve found it hard to start work when requirements are unclear. I used to wait for more detail, which slowed things down.
Now, when something is ambiguous, I write a one-page summary of what I think the goal is, list my assumptions and send it to the stakeholder within a day. Even if I’m wrong, it gets a fast correction. On my last project that approach saved about two weeks of back and forth.
10. Overcommitting to deadlines
My estimates used to be too optimistic. I’d plan for the best case and then have to explain delays.
I started tracking my estimates against actual time for every task. It showed I was underestimating by about 30% on average, mostly on testing and reviews. I now add explicit time for those steps, and over the last two quarters almost all of my tasks have finished within the original estimate.
11. Writing concisely
My written updates used to be too long. I’d include every detail, and people missed the key points.
Now I start every update with a three-line summary: what happened, what it means and what I need. Details go below for anyone who wants them. Response rates to my updates went up noticeably, and my manager started forwarding them to leadership as they are.
12. Taking feedback personally
Earlier in my career I took critical feedback on my work personally and would get defensive in code reviews.
I’ve changed how I approach it: I read review comments once, wait before replying and ask clarifying questions instead of defending my choices. I also started asking for reviews earlier, when changes are cheaper. Now I see reviews as the fastest way to learn from more experienced people, and I’m one of the most active reviewers on my team.
Answers to avoid
Strong answers
- A specific, real weakness
- Concrete actions you are taking
- Evidence that it is improving
- Relevant to work but not to the core of the job
- About 60 seconds, ending on progress
Weak answers
- “I’m a perfectionist” or “I work too hard”
- “I don’t have any weaknesses”
- A weakness in the main skill of the role
- A long story about the problem with no action
- A joke instead of an answer
Variations of the question
| Phrasing | How to adapt |
|---|---|
| What are your strengths and weaknesses? | One strength with a quick example, then one weakness with the full formula |
| What would your manager say you need to improve? | Quote real feedback and show what you did with it |
| What is one area you are working on? | Lead with the action you are taking; the weakness is implied |
| Tell me about a time you received critical feedback | Use STAR: the feedback, how you reacted and what changed |
| Why shouldn’t we hire you? | Name a gap relevant to the job and show how you will close it quickly |
The last variation is rare but stressful. Treat it as the weakness question in disguise, not as a trap.
Practice before the interview
Write down two weaknesses using the formula, say each one out loud with a timer and cut until it fits in about a minute. Then ask a friend to follow up with “How do you know it’s improving?” If you can answer that without hesitation, your answer is ready.
For other common questions, see our guides to “Tell me about yourself”, behavioral interview questions and the STAR method. During live interviews, Sottena can show a short outline of your prepared answer as soon as the question is asked; use it in line with the rules of each interview.
Frequently asked questions
What is the best weakness to say in an interview? +
Is it okay to say “I'm a perfectionist”? +
Should I mention a weakness from my personal life? +
What if they ask for three weaknesses? +
How do I answer “What are your strengths and weaknesses?” together? +
Keep your weakness answer structured under pressure
Sottena listens to the interviewer, detects each question and shows short answer points in about a second. 150 free credits, no card required.