Greatest Weakness Answer: Formula and Examples by Level
By Kieron
Last updated October 4, 2026
When an interviewer asks about your greatest weakness, they want three things: that you know yourself, that you can talk about a flaw without being defensive, and that you do something about it. The strongest answers name a real, work-relevant weakness that is not central to the job, and then show specific steps that are already working. This page gives you a formula and examples at different levels.
The formula: weakness, evidence, fix, progress
- Name a real weakness in one sentence, in plain words.
- Give a brief example of when it showed up, so it is credible.
- Describe what you do about it with specific habits or tools.
- Show progress so the interviewer hears improvement, not a confession.
Keep it to about a minute. The whole answer should end on the fix and the progress, not on the flaw.
How to choose one
Pick something that is true, not central to the role you are interviewing for, and fixable. If you are applying for an accounting job, "I miss details" is a bad choice; "I used to avoid public speaking" is fine. Avoid these:
- Disguised strengths: "I am a perfectionist" and "I work too hard" sound evasive and interviewers have heard them many times.
- Disqualifiers: "I cannot meet deadlines" or "I do not take feedback well".
- Personality labels with no behavior behind them.
Examples by level
Entry level: asking for help
Early on, I tended to struggle on a problem for too long before asking for help, because I did not want to look like I could not figure things out. In my internship, that cost me most of an afternoon on a database error a colleague fixed in five minutes. Since then I give myself a time limit, usually thirty minutes, and then I ask with a short write-up of what I have tried. It has made me faster, and my supervisor has said my questions are easy to answer.
Mid level: delegating
I have a habit of taking on tasks myself rather than handing them off, because I know exactly how I want them done. That worked until I led a project with five people and became the bottleneck. I started writing down what a good result looks like and giving people ownership of whole pieces, then checking in at set points instead of redoing the work. The team now ships faster, and I spend my time on the parts only I can do.
Senior level: saying no
I find it hard to say no to reasonable requests, so my own priorities can slip. A few quarters ago I realized I was in too many meetings to finish a design I had promised. Now I ask what the request is blocking and by when, I decline or defer what is not urgent, and I keep two protected blocks a week for focused work. My commitments are more reliable, and people know what I am working on.
Software engineer: writing documentation
I used to put off documentation until after the code was done, and then it never got written. A new teammate once spent a day on a setup problem that a few lines would have prevented. Now I write the README and the key decision notes as part of the pull request, and I use a short template so it does not take long. Onboarding questions about my services have dropped.
Career changer: confidence in a new field
I am still building depth in the technical side after moving from teaching, so I sometimes hesitate to speak up in technical discussions. I handle that by preparing a question or two before each design review and by pairing with a senior engineer weekly. I am speaking up more, and my last two suggestions made it into designs.
What the interviewer hears
| Answer element | Interviewer hears |
|---|---|
| A specific example | "This is real." |
| A concrete habit or tool | "They act on feedback." |
| A sign of progress | "They improve." |
| A flaw central to the job | "They may not be able to do this." |
| A disguised strength | "They are avoiding the question." |
Related questions to prepare
Interviewers ask weakness questions in several forms: "tell me about a time you failed", "what would your manager say you need to improve?" and "what feedback have you received?" The same structure works: be specific, own it, show change. For the failure version, see tell me about a time you failed. For the opening question, see tell me about yourself.
Practice
Say the answer aloud and time it. If it takes more than a minute, trim the story. Weakness answers are easier to hear than to write: you will notice quickly when one sounds rehearsed or defensive. A mock interview is a low-pressure way to run it a few times.
Frequently asked questions
Is "I am a perfectionist" a good answer?
No. It is the most common disguised strength and interviewers read it as avoiding the question. Name a real, specific weakness instead.
How honest should I be?
Honest about a real weakness, but choose one that is not central to the role. You do not need to confess your worst trait; you need to show self-awareness and action.
What if I cannot think of a weakness?
Ask a former manager or colleague what they would say. Look at feedback in past reviews. Everyone has one, and the exercise is useful beyond the interview.
Should I give more than one weakness?
One is enough unless the interviewer asks for more. A second one, if asked, should follow the same structure.
Put this into practice
Continue with the Aissence workflow this guide supports.