What is your biggest weakness?
answer
- one real weakness, stated plainly
- the cost it actually caused
- the correction you run now
- evidence the correction holds
- no strength in disguise
basics
~20 sTests honest self-assessment, not confession. Name one real weakness that would not disqualify you for this job, state the concrete cost it caused, then describe the correction you run now and the evidence it works.
how to answer
5 beats- the weakness, said plainly in one sentenceLead with it, unhedged, in ordinary language. No preamble about how hard the question is and no softening adverbs. Pick something real but off the critical path for the role you are interviewing for.
- the concrete cost it causedGive one specific occasion and what it cost, ideally to other people rather than only to your own comfort. Fifteen to twenty seconds is enough. Resist the urge to explain why it was understandable.
- the correction you put in placeThe bulk of the answer. Describe the mechanical thing you now do, chosen by you rather than imposed on you, and keep it small enough to be believable. Vague resolve to do better is the commonest failure at this beat.
- the evidence it is workingName what changed that someone else could observe: a count, a review comment, a situation you handled differently the second time. This is what converts an admission into a demonstration of growth.
- the honest residue and your guardrailOne sentence on the part that still slips under pressure and what catches it now. This is persuasive precisely because it refuses to claim the weakness is cured, and it costs you nothing with a good interviewer.
your answer
5 story prompts- Write down the last piece of critical feedback you received and what you actually changed afterwards.
- Pick a weakness that cost someone else time, not just your own comfort.
- Name the specific habit or check you run now, plus one occasion where it held.
- Cross out any candidate weakness that is central to the job description you are answering.
- Check that your weakness is not the mirror image of the strength you plan to claim — an interviewer who hears both in one hour will probe the seam.
draft and rehearse your own answer in a learn session
go deeper
This probes self-awareness and coachability, and how you behave when the honest answer is uncomfortable. Interviewers watch whether you can name a real limitation, describe the damage it did without excuses, and show a correction you actually run. That combination is evidence you absorb feedback rather than deflect it.
My biggest weakness is that I treat a verbal yeah, that will be ready from another team as a firm commitment, and then I wait quietly instead of checking back. It cost me on the notifications work at the mobile startup I joined out of school. The push infrastructure belonged to a two-person platform group, and I had been told the token-refresh piece would land early the following week. I never asked which day and I never asked again midweek, so I found out on Friday it had been deprioritised. Five of the nine tickets I owned that cycle rolled into the next one, and my lead had to explain that in planning rather than me. What I do now is small and mechanical. When a dependency comes up in conversation I repeat it back with a date and put it in the shared thread, and if a check-in slips twice I raise it in standup instead of waiting for a third. In the following cycle one ticket carried over rather than five, and that one was a scope change, not a surprise. I still find the escalating part uncomfortable and have to make myself send the second message, but I have stopped confusing being polite with being quiet.
The weakness is real and junior-shaped, and the cost is stated as harm to someone else's planning rather than to feelings. The mechanical fix plus the carried-over count is what makes it credible, and admitting escalation still feels awkward keeps it from sounding conveniently cured.
I default to solving a cross-team problem myself instead of routing it to whoever owns it, and for a while that turned me into the bottleneck I was complaining about. On the mobile side of a consumer product I had become the informal contact for anything touching the payments service, the analytics vendor's SDK, and our own release tooling. It felt efficient, because I could get an answer in an hour that would take somebody else a day. Then I took nine days off and three workstreams stalled. One of them stalled on a question I had answered twice already and never written down anywhere. That was uncomfortable to look at. So I listed every open thread with another team that I sat on. There were fourteen, and I was the only person from my team on eleven of them. I paired each with an owner from my side, joined their first conversation, then got out of the way, and I wrote the four recurring answers into a page anyone could find. About two months later I was on four of those threads instead of eleven, and two teammates now hold relationships I used to hoard. The residue is that under time pressure I still grab things back, so I ask my lead to call it when they see me doing it.
The middle bar shows in owning a cost to the team rather than to a task, and in a fix built from a mechanism, named owners plus written answers, rather than a resolution. Keeping the residual failure mode and the standing request to be called out keeps it honest instead of tidy.
A genuinely junior weakness is welcome: estimating badly, staying stuck too long before asking, over-asking, avoiding a hard conversation. Show the habit you built to correct it and one occasion where the habit held.
Pick something that touches collaboration or scope rather than pure craft, and make the fix something you chose rather than something a manager imposed. Name the cost to other people, not only the cost to you.
Own a weakness with real consequences, such as a bottleneck you created or work you held too long instead of handing over. Describe a systemic correction rather than a resolution, because hedging at this level reads as low self-awareness.
The credible weakness here is usually about influence and pace: over-indexing on one part of the org, driving a standard before consensus existed, under-communicating a decision widely. Show how you calibrate now and who tells you when you are off.
saying these in an interview costs you the question
- Offering a strength in disguise, such as caring too much or working too hard
- Naming a weakness that is the core skill of the job you applied for
- Confessing something and stopping before any correction
- Blaming a former team, manager or process for the weakness
- Claiming the weakness is entirely solved with no trace of effort left
- Naming a trait but no situation where it cost anything
- How do you know you have actually improved on that?Answer with observable evidence rather than feeling: a count that moved, a review comment that changed, a situation you handled differently the second time. If your evidence is that someone else noticed, say who by role and what they said. Vague improvement language here undoes everything the honest admission earned you.
- When did that last cause a problem?Do not say it has not happened recently unless that is true. Give a small recent instance and how you caught it, which shows the correction is live rather than historical. A weakness that last appeared years ago sounds either dishonest or irrelevant, and both readings hurt you.
- This role is heavy on exactly that. How would you handle it?Take the challenge seriously instead of retracting the weakness. Describe the conditions under which you perform well on that axis, the support or structure you would put in place, and what you would want feedback on early. If the fit is genuinely poor, saying so calmly is better than talking your way into a job you will struggle in.
### What the question is actually measuring The weakness question survives, decade after decade, because it is one of the few prompts where the socially easy answer and the strong answer point in opposite directions. Everything in the candidate wants to protect the impression built so far. The interviewer is watching precisely that tension: can you hold a limitation in view, describe the damage it did without excuses, and show that feedback changes your behaviour rather than your defences. The literal weakness matters far less than the shape of the answer around it. ### The three ways it goes wrong **The humblebrag.** Caring too much, working too hard, being a perfectionist. Every interviewer has heard these hundreds of times, and they read as either evasion or a lack of self-knowledge. Both are worse than any real weakness you could have named. **The disqualifier.** Volunteering that you struggle with the core skill of the job, for example admitting you avoid ambiguity when the posting is about a greenfield product, or that you dislike code review when the team's culture is built on it. Honesty is not the same as strategic self-harm; there are many true things about you, and you get to choose which one to discuss. **The unfixed confession.** A real weakness stated bravely and then abandoned. Without a correction and evidence, you have handed the interviewer a risk with no mitigation attached, and they must price it. ### Choosing the weakness: three filters Run your candidates through all three. First, is it real, meaning you can point at a specific occasion where it cost something. Second, is it off the critical path for this specific role, so that hiring you is not a bet against the thing you just named. Third, does it come with a correction you actually run, not one you intend to start. A candidate that fails any filter is the wrong candidate for this answer, however honest it feels. ### Evidence types, in ascending order of strength A stated intention is the weakest. A named habit or check is better. A habit plus an instance where it held is better still. Strongest is a measurable change plus third-party confirmation, for example a count of work that used to roll over, and a manager or peer who noticed the difference. Notice that all of these are about the correction, not about the weakness, which is where most candidates spend all their airtime. ### Delivery and airtime Aim for sixty to ninety seconds. One sentence names the weakness. Fifteen to twenty seconds describes the cost, concretely and without hedging language such as I suppose or a little bit. The bulk goes to the correction and its evidence. Finish with the honest residue, the part that still slips, and the guardrail you use. That residue line is counter-intuitively the most persuasive sentence in the answer, because a weakness described as fully cured is not a weakness and interviewers know it. ### Variants and how they shift the answer The prompt also arrives as what is your biggest area for growth, what would you most want to improve in the next year, or where do you need the most support from a manager. Growth framings invite a slightly more forward-looking answer, with the plan carrying more weight than the past cost. A manager-voiced framing changes the evidence requirement rather than the content: your answer must now be attributable to real feedback someone gave you, quoted close to their actual words, because a reference check could in principle contradict it. ### How the bar moves with seniority Junior weaknesses are expected to be about the mechanics of working: estimation, knowing when to ask, finishing. Middle weaknesses should touch other people, because by then your mistakes cost the team time rather than only your own. Senior and above, the interviewer expects a weakness with organisational consequences and a correction that changed a system rather than a habit. At every level the same rule holds: the weakness is the setup, and the correction is the answer.