How to Answer "What Is Your Greatest Weakness?" (+ 10 Example Answers)

This is one of the most predictable questions you'll face — The Interview Guys, citing their own research, say over 67% of interviews include a question about weaknesses. Interviewers are checking three competencies.

Self-awareness. Can you describe your own performance accurately, without defensiveness or false modesty? People who can't see their gaps can't be managed.

Coachability and growth mindset. They want evidence that feedback lands and changes your behaviour. The improvement story matters more than the weakness itself.

Authenticity under mild pressure. The question is slightly uncomfortable by design. How you handle that discomfort predicts how you'll handle a hard conversation with a manager or a client. The Interview Guys name these same four things — self-awareness, growth mindset, authenticity, and how you handle vulnerability — as the reasons the question exists.

There is also a screening element: they're listening for anything that rules you out of the core duties.

The question often arrives dressed as something friendlier. Treat all of these as the same question:

• "What's an area you're working on developing?"
• "What would your last manager say you need to improve?"
• "Tell me about a piece of critical feedback you've received and what you did with it."
• "What part of this job do you think you'd find hardest?"
• "Where do you need the most support from a manager?"
• "What's something you're not naturally good at?"

The feedback-based versions want a named source and an outcome. The "hardest part of this job" version is the riskiest, because a careless answer names a core requirement — pick something adjacent to the role, not central to it.

Use The Interview Guys' four-step Strategic Weakness Framework (The Interview Guys, undated). It gives you a shape you can fill in with your own material in about twenty minutes.

1. Choose a genuine but strategic weakness. The same source says a good choice is authentic, peripheral rather than central to the core job duties, improvable, and relatable. Read the job advert, list the three things the role lives or dies on, and rule those out. Then pick something real from your own feedback history — a habit, not a personality trait. The same source lists what never to raise: ethical issues, anything named as a core requirement in the posting, character flaws such as laziness or unreliability, an inability to handle stress, and poor communication.
2. Frame it professionally. Say it in one plain sentence, in behavioural terms, with a short example of the cost. "I hold onto work too long before showing it to anyone" is usable. "I'm a bit of a nightmare with deadlines" is not. Name the situation where it showed up, so it sounds like something you've observed rather than something you invented.
3. Show your improvement plan. This is where most answers thin out. The Interview Guys suggest making the improvement narrative believable by being specific about the actions you took, giving a timeline, describing obstacles you had to get past, quantifying the improvement where you can, and mentioning feedback you've had from other people. Two or three concrete habits beat a vague promise to "keep working on it."
4. Connect it to the role. Close by linking your progress to what this job needs — or by saying honestly where the weakness is least likely to bite here, and what support would help. The same source warns against ending by asking the interviewer whether your weakness is a problem for the role; it reads as insecurity rather than growth.

Write it out, then cut it until it reads in about ninety seconds. Keep one extra detail in your back pocket for the follow-up question.

Five worked answers. Notice that each one is built differently — one starts with an incident, one with a manager's feedback, one with a self-diagnosis, one with evidence from volunteer work, one with a routine built since returning. Borrow the structure, not the content.

New graduate: junior analyst at a housing charity

Priya, geography graduate interviewing for a junior data analyst post

I sit on questions for too long instead of asking them. On a six-week placement last summer I was cleaning a survey of around four hundred tenant responses and hit a merge error that kept duplicating records. I spent a day and a half trying to solve it alone because I thought asking would look like I couldn't cope. My supervisor fixed it in ten minutes and told me, kindly, that I'd wasted a day of her budget. Since then I've used a twenty-minute rule: if I'm stuck for twenty minutes, I write down what I've tried and take it to someone. I also keep a running list of smaller questions for a weekly check-in so I'm not interrupting constantly. By the end of the placement I finished the dataset two days early. In a small analytics team I'd rather be the person who flags a blocker on day one than day five.

Step up in the same field: warehouse team leader to shift manager

Marcus, team leader applying for a shift manager role

In my last review my manager told me I was still doing the work instead of running the shift. She was right. During peak I was doing the stock counts myself for a team of nine, staying late three nights a week, and nobody else knew the process. My instinct is that it's faster to do it than explain it. Over the last three quarters I've worked on that deliberately: I built a count rota so it rotates, trained two pickers as checkers, and keep a one-page list of who can cover what, which I review monthly. The hard part was the first few weeks, when counts took longer and I had to let that happen. The test came in August when I took a week off and the shift ran without a single escalation to me. Stepping up to shift manager means I have to keep resisting that instinct, because the job is coverage and planning, not picking.

Industry switch: hospitality finance to construction finance

Yusuf, accounts assistant moving into a construction finance team

My weakness is that I'm slow to commit to a figure when the vocabulary is new to me. I over-verify. In restaurant group accounts I knew the numbers well enough to draft a reconciliation in an hour; when I first looked at valuations and retentions I was checking every definition twice and my first drafts took a day and a half. I don't think the caution is wrong, but the speed was a problem for a month-end. So I built a glossary of the terms I kept second-guessing, with an example transaction under each one, and I asked a quantity surveyor I know for three fifteen-minute calls to walk me through how a valuation actually gets agreed on site. My drafting time on subcontractor reconciliations is now a couple of hours, not a day. I'd expect to be slower than your existing team for my first month or two, and I'd want my first few reconciliations reviewed.

Career change: teaching to customer success

Hannah, former secondary school teacher moving into customer success

I over-explain in writing. Fifteen years of teaching trained me to anticipate every misunderstanding, so my default is to answer the question and then answer four questions nobody asked. I found out how bad it was when I started volunteering on the help centre for a community sports organisation: my first three articles were roughly double the length of everyone else's, and the coordinator sent them back with about half of each one struck through. Since then I give myself a word ceiling before I start — usually a hundred and fifty for an article, eighty for an email — and I read the draft back asking what a busy person needs in the first two lines. I also ask a colleague to cut anything redundant before I publish. The rewritten articles fit on one screen and generated fewer follow-up messages. For customer success, short and clear is the job, so this is the habit I've worked hardest on.

Returning after a gap: project coordination after two years caring

Dan, project coordinator returning after two years as a full-time carer

After two years out of an office, I came back over-preparing and slow to answer in the room. I'd know the schedule inside out on paper and then take too long to give a straight verbal answer when a delivery manager asked a direct question in a stand-up. Confidence, mostly, plus being out of the rhythm of fast meetings. I've dealt with it by practising the format rather than waiting to feel ready. In three months of temporary coordination work I asked for agendas in advance, wrote exactly three bullets before every meeting, and made myself give a sixty-second verbal update rather than reading a document out. The first fortnight I was still reading off my notes and it sounded stilted. I now chair the Monday scheduling call for a team of twelve without notes. I'd still rather have an agenda than not, but I no longer need one to speak.

Before the interview, check your answer has all five:

1. One named weakness, stated plainly in a sentence, that is true of you and not central to the core duties of this job.
2. A specific situation where it cost something — a delay, a rework, a piece of feedback you were given and by whom.
3. Two or three concrete actions you took, with a rough timeline, not a promise to work on it.
4. Evidence it moved — a result, a later piece of feedback, or something you now do that you couldn't do before.
5. A closing line that faces the role, saying where you are now and what support you'd want, without asking them to reassure you.