Weaknesses for a job interview

Why interviewers ask about your weaknesses

There are three reasons, and watching you squirm is not one of them.

The first is self-awareness. Someone who can describe a real limitation accurately is usually someone who can be coached, told about a problem and trusted with feedback. Someone who cannot tends to be expensive to manage, and interviewers learn that the hard way.

The second is honesty under mild pressure. The question has an obvious dodge and an obvious wrong answer, so whatever you choose is informative. The National Careers Service, the UK government’s careers site, puts the expectation plainly in its guidance on common interview questions: be honest about a weakness, and say what you are doing to improve it.

The third is risk. If the weakness you name is the main thing the job requires, that is a genuine problem and the interviewer needs to hear it now rather than in month three. This is why choosing the weakness is most of the work, and why the answer should be prepared rather than improvised.

How to choose a weakness you can actually say

A usable weakness passes five tests.

It is real. Interviewers hear invented weaknesses constantly, and they recognise them by the absence of detail. If you cannot produce an example, pick something else.

It is specific. “Bad at communication” is too broad to answer well and sounds worse than whatever you meant by it. “I used to send long written updates when a two-minute call would have been faster” is a weakness with edges, and edges are what make it answerable.

It is not the core of the job. A weakness in public speaking is fine for a back-end developer and disqualifying for a trainer. Read the job description and rule out anything in the first three requirements.

It is improvable, and you have already started. The strongest version of this answer is a before and after, not a confession. You need something concrete that changed: a habit, a tool, a checklist, a conversation you now have earlier than you used to.

You can say it calmly. If a weakness makes you defensive or embarrassed, that will be the thing the interviewer remembers. Choose one you can discuss the way you would discuss somebody else’s.

If nothing comes to mind, three places usually hold the honest answer: your last performance review, feedback you have received more than once, and the type of task you quietly postpone.

A three-part shape: name it, show it, show the fix

Name it in one sentence, with no wind-up. Hedging (“this is a tricky one, I suppose if I had to pick something…”) spends your credibility before you have said anything.

Show it with one short, specific instance. Not a dramatic failure, just enough evidence that you are describing something you have lived with. One or two sentences is plenty.

Then give the rest of the answer to what you do about it now and what changed as a result. This is the part interviewers actually remember, because it is the only part that tells them how you will behave on their team. If the improvement is partial, say so. “It is better, and I still catch myself” is more convincing than a tidy cure.

The whole thing should take forty-five to sixty seconds. A weakness answer that runs two minutes starts to sound like a problem rather than a story about one.

Example weaknesses with sample answers

Five worked answers, each built on name it, show it, show the fix. Treat them as patterns and put your own facts in, because borrowed detail is easy to hear.

Presenting to a large group

My weakness is presenting to big rooms. I am fine in a meeting or a workshop, but the first few times I presented to fifty people I spoke too fast and lost my own thread.

After one quarterly review that went badly, I started rehearsing out loud against a timer and writing the first and last thirty seconds word for word, because that was where I was losing people. I also joined an internal lunch and learn series so I would get practice every month instead of twice a year.

I would still rather run a workshop than a keynote, but I presented our roadmap to the whole department in March and got through it at the right pace.

Delegating instead of doing it myself

When I first became a team lead I kept doing work I should have handed over. It felt faster, and honestly some of it was work I enjoyed.

The cost showed up in my one-to-ones: two people on my team said they were not getting anything that stretched them. So I started each sprint by writing down what only I could do, and gave away everything else, with a check-in halfway through rather than a review at the end.

It took a few months to stop reaching for tasks. The useful side effect is that two of those people now run projects I used to run myself.

Waiting too long to ask for help

I used to stay stuck far too long before asking anyone. I treated asking as admitting I could not do the job.

On one integration I lost most of a week on a problem a colleague had already solved. After that I gave myself a rule: forty-five minutes of genuine effort, then write the question down and ask it, including what I have already tried.

It made me slower to panic and faster overall. I give new joiners the same rule now, partly so that I keep following it.

Saying yes to too much

I have a habit of agreeing to things I do not have room for. That used to mean a lot of late evenings, and once or twice a commitment I delivered later than I promised.

What changed it was being honest about capacity in writing. I keep a visible list of what I am committed to this week, and when someone asks for something I answer with what it would displace rather than just saying yes.

I still have to think before I answer, but I have not missed a promised date since I started doing it, and people get a straight answer sooner.

Underestimating how long work takes

My estimates used to be optimistic, especially on anything involving another team. I planned for the work and not for the waiting.

I started recording my estimate against the actual time for every task over a day long. The pattern was obvious within a month: anything with a review or a handoff in it took about twice as long as I thought.

Now I estimate the work and the dependencies separately, and I flag a date as provisional until the other team confirms. My last two projects landed within a day of plan.

Weaknesses to avoid naming

“I am a perfectionist.” The most common answer there is, and interviewers read it as a strength wearing a disguise. The same goes for “I work too hard”, “I care too much” and “I am too much of a team player”.

“I do not really have any.” This reads as either no self-awareness or no willingness to be honest, and it shuts down a conversation the interviewer opened deliberately.

Anything that disqualifies you outright. Timekeeping for a shift role, attention to detail for an accounting role, writing for a communications role. Honesty does not require self-sabotage, so pick a different true weakness.

Personal and medical matters. You are not obliged to discuss your health, and an interview is not the place to start.

Weaknesses that are really complaints. “I get frustrated with people who are not as committed as I am” tells the interviewer how you talk about colleagues, which is not what they asked.

A weakness with no action attached. Naming a flaw and stopping leaves the interviewer to imagine the consequences, and imagination is rarely generous. The fix half is not optional.

And avoid the engineered non-weakness, like “I am too organised”. If it could appear word for word in your own reference, it is not a weakness.

If you are asked for two or three weaknesses

Some interviewers ask for three, usually to get past the single rehearsed answer. Prepare by having three candidates from different areas rather than three shades of the same thing: one about a skill, one about a working habit, one about how you work with other people.

When you give several, keep each to two or three sentences. The full name it, show it, show the fix treatment belongs to the first; the rest need the weakness and the action and nothing more. Three complete stories is five minutes, and five minutes on your flaws is not a good trade.

The same preparation covers the variants: your biggest weakness, what you most need to develop, or what your last manager would say you should work on. That last phrasing shifts the evidence, so use real feedback you have had and say where it came from. It is the version where an invented answer is easiest to spot, because the natural follow-up is what you did after that review.