In this article
Before you start
Why interviewers ask this
The question is a test of self-awareness, and it exposes whether you have a flaw that would stop you doing the job. The career office of the online Master of Business Administration (MBA) programme at the University of North Carolina (UNC) says it tests self-awareness and whether you can answer an uncomfortable question honestly, and that it reveals whether you have a weakness that would disqualify you for the role (UNC Kenan-Flagler, 2016).
In a structured interview, every candidate gets the same questions and is rated on one scale; Google describes them as "using the uniform methods to assess candidates applying for the same job" and says its rubrics illustrate poor, borderline, solid and outstanding answers (Google re:Work, March 2026). A weak answer names a cliché; a strong one gives the interviewer something to score. The behavioral interviews hub places this question among the others in that round.
The greatest weakness question from first principles
- Bounded weakness
- A bounded weakness is a real, specific flaw in how you work that does not sit on the core requirements of the job and that you can describe with one example, so the interviewer can judge both its size and your honesty.
- Disguised strength
- A disguised strength is a so-called weakness such as "I work too hard" that is really a boast, which interviewers recognise and treat as a non-answer.
In plain words
Answering the weakness question is like reporting a bug in your own work. A good bug report says what the bug is and how it showed up. It says what you changed and whether it is fixed. A bad one says "the software is too good". The analogy breaks in one place. A bug report can be about code you did not write, but here the flaw is yours, so the interviewer also judges whether you will own it.
Stated precisely, the answer is one bounded weakness, one mitigation and one result, in about 100 words. The UNC career office says to name a real weakness and describe the concrete steps you have taken, and it warns against disguised positives, weaknesses core to the job and answers that are irrelevant or overly personal (UNC Kenan-Flagler, 2016).
Step 1: Pick a real weakness that does not break the job
The first step is choosing a flaw that is true, small enough to be managed and absent from the job's core requirements. The input is the posting's top skills; the output is one weakness that is not on that list. UNC's example of a poor choice is a call-centre applicant who dislikes phones. A good choice is a work habit, such as keeping too much review work for yourself, an uncertainty about public speaking that you are practising, or a tendency to underestimate how long tasks take.
Avoid the disguised strength and avoid anything deeply personal. Choose one, because one weakness handled well uses the whole minute on evidence. Penn Career Services suggests reframing a weakness as "an area of further growth or development" and warns against one "that would disqualify you" (Penn Career Services, 2021). What you now know: which flaw you are admitting.
Step 2: Show the system you built
The second step is a mitigation: the specific change you made to how you work, with one example of the weakness appearing. The input is your weakness; the output is a concrete action, a rule or a habit, that an interviewer could imagine you doing again on their team. "I am working on it" is not a system. "I listed which reviews needed me, trained two colleagues and set a one-day waiting limit" is one. Add the moment you noticed the weakness, because noticing is evidence of self-awareness, and say it in one sentence. What you now know: the interviewer has a method, not a promise.
Step 3: Report the result and stop
The third step states what changed, admits what remains, and ends. The input is the system; the output is a measured or observable result plus one sentence on the part that persists. This is the rubric line that separates a weak answer from a strong one: a strong answer ends on how the candidate works now, such as a standing check, not on a feeling.
What lifts a strong answer to Staff is scope, covered in the Staff-level section below. Then stop speaking; do not apologise or add a second weakness. In the sample below, review wait time fell from about two days to under one, and the habit still returns under pressure, so a Friday check remains. What you now know: the answer is complete and the next question is the interviewer's.
Step-by-step description
- A real, bounded weakness outside the job's core.
- The specific change you made, with one example.
- What changed, what remains, then stop.
- The first step is choosing a flaw that is true, small enough to be managed and absent from the job's core requirements.
- The third step states what changed, admits what remains, and ends.
Three answers side by side
The difference between a weak, a strong and a Staff answer is evidence, not length. All three examples below are illustrative composites written for this page for an engineering team lead: no real person and no named company; every figure in them is made up. Word counts and speaking time at 164 words per minute, the turn-wise rate in a study of 2,438 telephone conversations (Yuan, Liberman and Cieri, 2006), were computed in assets/data/weakness-timing.py.1
What the numbers show
The weak sample is the shortest and carries no evidence. The strong and Staff samples spend their words on an example, a system and a result.
The lesson is about content, not length. A 57-word answer is not too long for a one-minute slot; it simply says nothing a hiring panel can check. The 95-word and 108-word answers use up to almost twice the words on three things the panel can test later: one real incident, one named change and one measured effect. Because the longest sample still takes about 40 seconds at the study's speaking rate, there is room for the extra 13 words of the Staff sample, which go on scope: a pattern and a change in how the team decides.1
Text description of the diagram
- The weak sample is the shortest and carries no evidence.
- The strong and Staff samples spend their words on an example, a system and a result.
| Fact | Weak sample | Strong sample | Staff sample |
|---|---|---|---|
| Words | 57 | 95 | 108 |
| Seconds at 164 words per minute | 21 | 35 | 40 |
| Real, bounded weakness named | No | Yes | Yes |
| Mitigation shown | No | Yes | Yes |
| Result stated | No | Yes | Yes |
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
A Staff-level answer differs from a strong one in scope, not in having an ending: the weakness is a pattern, and the fix is a system the whole team uses. Both levels end on the result and what you still watch. It is still three moves, but the scope is a team, not one task.
What is your greatest weakness?
My weakness is that I default to doing the work instead of building the system that does it. As a team lead I noticed our releases waited on my review, which capped the whole team at my pace. I mapped which decisions truly needed me, wrote the criteria down, and gave two senior engineers the authority to approve the rest, with a one-day limit on waiting. Median review wait fell from about two days to under one, and I now measure myself by how few decisions need me. The habit comes back under deadline pressure, so I put a standing review of my own queue in my calendar.
What makes it Staff-level: it names a pattern rather than an incident, and it counts a change in how a team decides as the result. That is the one Staff criterion used on this page: a pattern plus a team-level system.
The rubric
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Honesty | Disguised strength | A real, bounded flaw | A pattern, owned plainly |
| Evidence | None | One example and a measured result | A recurring pattern, with a measured team-level effect |
| Mitigation | "I am working on it" | A specific rule or habit | A system the whole team uses |
| Ending | A feeling | The result and what you still watch | The result as a team-level change, plus what you still watch |
| Fit to the role | Core skill or irrelevant | Not on the core list | Not on the core list |
Three variants of this question
"What are your strengths and weaknesses?"
Answer the strength first, with one example, then the weakness in three moves. Keep the weakness to about half the time you give the strength (a rule of thumb, not a sourced figure), and do not let the weakness answer sound like a second strength.
"What would your last manager say you should improve?"
A manager's view is the same question reported by a third party, so name something a manager really would say, with the change you made. It is checkable by a reference call, which is why a disguised strength fails here fastest.
"What is a skill you are still developing?"
Pick a skill that is real but not core, say what you have done to build it, and give the current level in words, such as "comfortable with small groups, practising with larger ones". UNC's own example is a student who was uncomfortable with public speaking, had enrolled in a course, and did not expect to become a keynote speaker (UNC Kenan-Flagler, 2016).
Common mistakes
- Disguising a strength. (wrong) "I am a perfectionist; I work too hard." It scores nothing because the interviewer has heard it many times; Penn calls "perfectionist" "very cliche" and "a bit disingenuous" (Penn Career Services, 2021). (right) Name a real flaw in how you work, such as keeping review work to yourself.
- Naming a core skill. (wrong) A call-centre applicant who dislikes phones. (right) Pick a flaw outside the job's top three requirements.
- Stopping at the flaw. (wrong) "I am bad at delegating." (right) Add the rule you made, the result, and what still needs watching.
- Giving four weaknesses. (wrong) A list of flaws. (right) One, said well, with a second only if the interviewer asks for more.
- Saying "I don't know". (wrong) It signals that you have not reflected. (right) Prepare one answer in advance and rehearse it aloud. The same preparation helps the opener, covered in tell me about yourself, and the wider set of stories you need.
Follow-up questions
What are examples of weaknesses?
Safe categories are work habits and developing skills that are not core to the role: keeping review work to yourself, underestimating how long tasks take, discomfort with public speaking, or difficulty saying no to extra requests. Each needs its own example, mitigation and result; the category alone is not an answer.
Should you give 3 weaknesses in a job interview?
No. Give one, said well, because one weakness with an example, a system and a result uses the whole minute on evidence that can be checked; three would split that time into three claims with none of it. This is this page's reasoning, not a figure from a source. If the interviewer asks for more than one, name a second briefly and keep the same three-move shape.
How do you answer interview questions about weaknesses?
In three moves: name one real, bounded weakness, show the system you built with one example, and report the result and what you still watch, in about 100 words. Penn Career Services suggests using the situation, task, action, result (STAR) method to show the steps you took (Penn Career Services, 2021). The steps above and the sample answers show it in full.
What are good examples of strengths and weaknesses for an interview?
Pair a strength that the posting stresses with a weakness that it does not: for example, strong at diagnosing delivery problems, but inclined to keep review work for yourself. Penn's own example is a student who names discomfort with delegating and can talk about ways of trying to delegate more (Penn Career Services, 2021). Whatever the pair, the weakness still needs its example, mitigation and result.
Is it fine to say you have no weakness?
No, because the interviewer reads it as a lack of self-awareness or as evasion. Choose a bounded weakness and show how you manage it; the rubric rewards the management more than the flaw.
What if the weakness is a skill the job asks for?
Choose a different weakness, or phrase the skill as a stage you are past: say what the gap was, what you did, and what you can do now. UNC warns against weaknesses that are core to the job, so a skill the posting stresses is the wrong one to volunteer. For senior roles, the same structure appears in the leadership interviews guide and the engineering management interviews guide; the interview loop overview shows where the question tends to appear, the questions to ask the interviewer page covers how the round ends, and salary negotiation covers what comes after.
- Name one real weakness that is not on the job's core list.
- Show the system you built, with one example.
- End on the result and what you still watch, then stop.
- Avoid the disguised strength; interviewers recognise it.
- About 100 words, under a minute, rehearsed aloud.
Sources
- A unique and effective way to answer the interview question, "What is your biggest weakness?" — UNC Kenan-Flagler Online MBA (Mary Ryan, career and leadership services), 2 Mar 2016
- How to answer the "tell me about yourself" and "greatest strength/weakness" questions — University of Pennsylvania Career Services, 2 Nov 2021
- A guide to structured interviewing for better hiring practices — Google re:Work, 1 Mar 2026
- Towards an Integrated Understanding of Speaking Rate in Conversation — Interspeech 2006 (Yuan, Liberman, Cieri; University of Pennsylvania), 17 Sep 2006
