Why they ask both
The pair does something that neither question manages alone. Your strength tells them what you think you are good at. Your weakness tells them whether the first answer was calibrated or advertised.
A candidate who claims a sharp strength and then a genuine weakness reads as somebody with an accurate picture of themselves. A candidate who claims a sharp strength and then a weakness that is secretly a strength reads as somebody managing an impression, which makes the interviewer go back and discount the first answer too.
That is the mechanism worth understanding. The weakness answer is not scored on its own. It is scored as evidence about whether to believe everything else you said, including the answers from twenty minutes earlier.
It also explains why the pair is so resistant to preparation. You can rehearse a strength into something polished, and polishing it makes the weakness that follows look more managed rather than less. The only version that holds together is one where both halves sound like they came from the same person having an ordinary conversation about themselves.
The strengths half
What they are looking for
One strength, not three. Relevant to this job specifically. With evidence attached.
Candidates hedge by offering a range, on the theory that more surface area means more chance of a hit. It has the opposite effect. Three strengths produce three shallow claims with no evidence for any of them, and the interviewer remembers none of the three.
There is a practical reason for this beyond attention. Interviewers write up what you said afterwards, usually against a competency framework, and they need something specific enough to type. One claim with an incident attached gives them a line to write. Three adjectives give them nothing, and what does not get written down does not get argued for in the debrief.
The structure
Name it in a sentence. Give one example with a number. Say what it costs you, briefly.
That last part is unusual and it is what makes the answer land. Every real strength has a shadow. Somebody fast is sometimes careless. Somebody thorough is sometimes slow. Naming yours does two things: it makes the strength believable, and it pre-answers the weakness question with something already framed.
Sample answer: strengths
The thing I am genuinely good at is getting to the actual cause of something rather than the first plausible one. At my last company we had a plateau in our weekly revenue number that everyone had accepted, and I did not believe a number could be that stable, so I went into the query rather than the dashboard. A join was dropping any order with more than one shipment, about nine percent of volume. We had been making roadmap decisions against a broken number for six weeks. What it costs me is that I am slower to agree that something is fine, and I have annoyed people by re-checking things that turned out to be correct.
One claim. One example carrying two numbers. One honest cost. Sixty seconds, and nothing in it that could be said by somebody else about a different job.
Notice that the strength is described as a behaviour rather than a quality. Getting to the actual cause rather than the first plausible one is something a person does, repeatedly, and can be shown doing. Analytical is a label somebody else applies after watching it happen. Claim the behaviour and let the interviewer supply the label.
Strengths that are worth claiming
Anything you can evidence with a specific incident. The unglamorous ones are underused and travel further:
- Finding the real cause rather than the first one
- Writing things down so decisions survive the meeting
- Telling people bad news early
- Cutting scope without drama
- Being the person who reads the whole document
Every one of those is more distinctive than leadership, communication or problem-solving, which are the three most claimed and least evidenced strengths in interviewing.
The weaknesses half
The rule
Pick something true, with a cost that has actually landed on somebody, and describe what you changed. That is the entire answer.
The reason candidates struggle is that they are optimising for the wrong thing. They try to find a weakness that will not count against them, which produces the perfectionism answer, and the perfectionism answer counts against them more than almost any real weakness would.
What does not work
I work too hard. I care too much. I am a perfectionist. These are strengths in costume, and every interviewer has heard them several hundred times. The cost is not that they are unconvincing. It is that they tell the interviewer you will manage an impression rather than give an honest answer, which is a much worse finding.
A weakness irrelevant to the job. I am not a strong public speaker, for a role with no speaking in it. It is honest and it is a dodge, and the follow-up will ask for one that matters.
A weakness you have completely fixed. If it is resolved, it is a story about growth rather than a weakness, and you have again answered a different question.
Something disqualifying. I miss deadlines. I struggle to take direction. Honesty has a floor, and the floor is anything that would make a reasonable manager decide the job cannot be done by you.
A weakness about other people. I get frustrated when colleagues do not pull their weight. This is a complaint wearing the costume of self-awareness, and it tells the interviewer how you will describe your future teammates.
What works
The zone is narrow and easy to describe: real, currently true, costs something to somebody other than you, and you are doing something about it that you can name. Every answer that satisfies those four conditions works, and almost every answer that fails does so by dropping the third one.
Sample answer: weaknesses
I escalate too early. When something starts slipping my instinct is to get it in front of my manager fast, and twice now that has meant I went to her before I had spoken to the person directly, which landed badly both times. The second one was a designer on a campaign launch who found out I had raised it upstairs before I had raised it with him, and that took a while to repair. What I do now is a rule rather than a judgement call: the person owning the work hears it from me first, same day, even when the deadline makes that feel expensive. It has been about eight months and I have not gone over anybody's head since, though I still feel the pull.
Real, specific, somebody was affected, the fix is a mechanism rather than an intention, and the last clause admits it is not fully solved.
That mechanism point deserves emphasis, because it is where most honest answers still fall short. I am working on being more patient is an intention, and intentions are unfalsifiable. The person owning the work hears it from me first, same day, is a rule you either followed or did not. Interviewers trust rules over intentions for the same reason they trust numbers over adjectives: one can be checked.
Picking yours
Most people try to invent an answer to this question. It works far better to find one, because both halves already exist in things that have happened to you.
For the strength, look for the thing colleagues route to you. Set aside what you enjoy and what your job title says. The signal is the category of problem that lands on your desk because people have learned, over time, that you are good at it. That routing is other people's assessment of your strength, accumulated across years and many small decisions about who to ask, and it is considerably more reliable than anything you would arrive at by introspection.
For the weakness, go through the feedback you have actually received in the last two years. Reviews, a difficult conversation with a manager, something a peer said that you have not forgotten. Pick the one that stung, that you did something about, and that has not fully gone away. You will know it immediately, because you will not want to use it. That reluctance is the signal you have the right one.
Then check three things before you commit to it. Can you name the person or the project it affected. Can you describe the mechanism you put in place, rather than an intention. And would you be comfortable if the interviewer repeated it back to your future manager on your first day, because in a well-run process they sometimes do.
If all three hold, the answer is ready. If the third one makes you wince, it is too severe. If the first one has no answer, it is not real.
The version for managers
Senior candidates get the same question with a higher bar, and the common failure is answering it as an individual contributor.
A manager's strength should be about what happens to other people. I find the real cause is an individual contributor's answer. The team stopped shipping broken numbers because I made a check mandatory is a manager's version of the same underlying quality. A manager's weakness should have cost somebody on their team something, not just cost them personally, and the fix should be structural rather than a change in personal habit.
The question that separates the two levels is what happened to your team as a result. If your weakness only ever affected your own output, you have answered as an individual contributor, and a senior interviewer will notice.
Where these answers break
The follow-up on strengths is the mild one: can you give me another example. It catches people who have one rehearsed anecdote and no second instance, which suggests the strength is a story rather than a pattern. Have two of them, drawn from different projects, because two tellings of the same story is really only one instance.
The follow-up on weaknesses is the one that does damage:
Who has this actually affected, and what did they say about it?
A weakness chosen for safety cannot answer that. Perfectionism has no victim. Nobody has ever been harmed by somebody caring too much, so the candidate either invents something or admits nobody was affected, and admitting nobody was affected concedes the weakness is not real.
A true weakness answers it immediately, because the whole reason you know about it is that somebody told you. That is how people find out about their weaknesses. Almost nobody identifies their own through reflection; it arrives as feedback, usually uncomfortably, and usually from someone who had to be affected by it before they said anything.
Which is why the best preparation for this question is not brainstorming. It is going back through the last two years of feedback you actually received and picking the one that stung, that you have done something about, and that has not gone away entirely.
There is a second follow-up worth preparing: is that still true. Candidates describe a weakness in the past tense to soften it, and this question removes the softening. The strongest answer is yes, partly, with a mechanism in place, because that is what being aware of a real limitation sounds like.
The deeper point is that this pair of questions is not testing for a defect. Everybody has defects and the interviewer has several. It is testing whether you can say something slightly costly about yourself under mild pressure, in a room where the incentive runs entirely the other way. That is a reasonable proxy for whether you will tell your manager the truth on a Tuesday when the news is bad and nobody has asked yet. Answer it as though that is the question, because that is the question.
Related
The weakness you name here will usually have arrived as feedback from somebody, which is covered in receiving negative feedback. If it showed up in a project that went wrong, see telling me about a time you failed. The strengths half connects directly to why should we hire you, and the evidence for both comes from the same stories you prepare for behavioral interview questions.