What Is Your Greatest Weakness? How to Answer (+ Examples)

"What is your greatest weakness?" is one of the most dreaded interview questions, but it is also one of the most predictable, which means you can prepare a strong answer in advance. This guide explains what the interviewer wants, how to choose a weakness that is honest without hurting your chances, and gives example answers for different types of job.

Why do interviewers ask about your greatest weakness?

Interviewers ask about weaknesses to test your self-awareness, honesty and willingness to improve. They are not looking for a flawless candidate; they want to know whether you can assess yourself accurately and act on what you find. Career coaches at the University of Illinois Chicago describe both the strengths and weaknesses questions as a check on self-awareness.^⁠[1]

A good answer tells the interviewer three things:

• You can name a real limitation without getting defensive.
• You understand how it affects your work and the people around you.
• You do something about problems once you spot them.

That last point is why the improvement part of your answer matters more than the weakness itself.

How do you pick a weakness to talk about?

Choose a weakness that is genuine, relevant to working life, and not a core requirement of the job. A real weakness makes the answer credible; avoiding the core requirements stops it from disqualifying you.

UIC's career coaches suggest two useful kinds of weakness:^⁠[1]

• Experiential weaknesses: a skill you have learned but haven't yet had much chance to use, such as managing a budget or presenting to senior leaders.
• Trait-based weaknesses: a tendency that doesn't come naturally to you but that you recognise and manage, such as being uncomfortable with ambiguity.

Run your candidate weakness through these checks:

A good source of material is past feedback: a comment from a manager, a performance review or a project retrospective. These are real, and they come with a natural improvement story.

What is the best way to structure your answer?

Use three parts: name the weakness, give a brief example of how it affected your work, and explain the specific steps you are taking to improve. End on the progress you have made.

The improvement should be specific. "I'm working on it" is not an answer; "I now block out two hours on Monday to plan the week, and I haven't missed a deadline since" is. Keep the whole thing to about a minute.

Example answers by job type

These answers are illustrative. They show the structure and level of detail to aim for; build yours from your own experience.

Software developer: estimating work

I've tended to underestimate how long tasks will take, especially when they touch parts of the codebase I don't know well. On one project I committed to a feature for the end of a sprint and only realised halfway through that it needed a database migration I hadn't accounted for.

Since then I break work into smaller tickets before I estimate, and I add a short investigation step for unfamiliar areas. I also compare my estimates with actual time at the end of each sprint. My estimates have become much more accurate, and my team lead has noticed.

Marketing: delegating

I've found it hard to delegate, because I like to know a campaign is done exactly the way I pictured it. When I first led a small team, that meant I was editing everyone's copy late at night while they had capacity to spare.

My manager pointed it out, and I changed how I hand over work. Now I write a short brief with the goal, audience and examples of what good looks like, and I review at agreed checkpoints instead of rewriting at the end. The team produces more, and I have time for strategy.

Sales or account management: following up in writing

I'm strong in conversations with clients, but I used to be inconsistent about following up in writing afterwards. Once, a client and I remembered a call differently, and it took a week to sort out.

Now I send a short summary email after every client call, listing what we agreed and the next steps, and I log it in the CRM the same day. It's become a habit, and it has also made handovers to colleagues much smoother.

Nursing or healthcare: speaking up with senior colleagues

Early in my career I was hesitant to question senior colleagues, even when I had a concern about a patient. I once waited longer than I should have to raise a change I'd noticed, assuming someone more experienced would have seen it.

I've worked on this deliberately. I use a structured handover format so my concerns come across clearly and factually, and I asked my preceptor to role-play escalation conversations with me. I now raise concerns promptly, and I see it as part of patient safety rather than a confrontation.

Customer service: saying no

I want customers to leave happy, and in my first year that sometimes led me to promise things I couldn't control, such as delivery dates.

I learned to be honest about what I can commit to and to offer alternatives instead of a vague yes. I also keep a short list of what I can and can't authorise so I don't guess. Customer complaints about broken promises on my tickets dropped, and my satisfaction scores stayed strong.

Finance or accounting: newer software tools

My technical accounting is solid, but I've had less hands-on experience with automation tools than some of my peers, because my last firm did most reconciliations manually in spreadsheets.

I've been closing that gap. I completed an online course in Power Query and rebuilt one of our monthly reconciliations with it, which made it quicker and less error-prone. I'm keen to keep building on that in a team that already uses these tools.

Project manager: patience with detail

I'm comfortable with the big picture, but I can move too quickly past detail. On one project I approved a vendor timeline without checking a dependency, and we lost a week.

I now use a pre-approval checklist for every plan, and for larger projects I ask a colleague who is strong on detail to review the schedule before sign-off. It has caught several issues early.

Student or graduate: public speaking

Presenting to groups has never come naturally to me. In my first year at university I rushed through a seminar presentation and lost marks for clarity.

Since then I've volunteered to present in every group project, and I joined the debating society to get more practice in front of an audience. I still prepare carefully, but I'm much more confident, and my final-year presentation was one of my best-marked pieces of work.

Which weaknesses should you avoid?

Avoid weaknesses that disqualify you, that sound like disguised strengths, or that raise concerns about reliability or integrity. These answers tend to do more harm than good:

The humblebrag ("I care too much") is the most common trap. It avoids the question, and the interviewer knows it.

How do you answer "What is your greatest strength?"

The strengths question is the mirror image: name one strength that matters for this role, back it with a concrete example, and connect it to the job. Prepare both answers together, so they sound like an honest, balanced picture of the same person. UIC's coaches suggest preparing a few strengths most relevant to the position and stating them confidently without bragging.^⁠[1]

My biggest strength is turning messy information into something people can act on. In my current role I took over a backlog of customer feedback spread across email and spreadsheets, grouped it into themes and presented the top issues to the product team. Two of those issues were fixed in the next release. This role involves a lot of stakeholder reporting, so I'd use that skill from day one.

Keep the strength and the weakness consistent. If your strength is attention to detail, a weakness about speed or delegation fits naturally; a weakness about carelessness would contradict it.

How should you prepare and practise?

Prepare at least two weaknesses, so you have a second one ready if the interviewer asks for another.^⁠[1] Write each answer out once, then practise saying it aloud from a few bullet points until it is natural and about a minute long.

Weakness answer checklist

• The weakness is real and you can give an example
• It is not a core requirement of the role
• Most of the answer is about what you are doing to improve
• It ends on progress or a positive result
• It doesn't contradict your strengths answer
• You have a second weakness ready

The interviewer may follow up with "Can you give me another example?" or "How do you know you've improved?", so practise with follow-up questions too. Many weakness stories also work as behavioral answers; our behavioral interview guide shows how to structure them with STAR, and the job interview preparation guide covers the rest of the interview.