How to Answer "What Is Your Greatest Weakness?" (With Examples for Engineers)

"What's your greatest weakness?" is one of the most dreaded interview questions, mostly because it feels like a trap. Say too much and you've talked yourself out of the job. Say too little ("I'm a perfectionist") and you sound rehearsed or evasive.

The good news is that interviewers aren't looking for a flaw that disqualifies you. They're checking for self-awareness and growth. Here's how to show both.

What the interviewer is really asking

Behind the question are three smaller ones:

• Do you know yourself? Engineers who can spot their own gaps are easier to coach and safer to give feedback to.
• Are you honest? A believable, specific answer builds trust for the rest of the interview.
• Do you improve? The heart of a good answer is what you're doing about the weakness.

If your answer shows all three, the weakness itself matters much less than you think.

The three-part formula

1. Name a real weakness, specifically

Pick something true that doesn't go to the heart of the role. "I'm not great at communicating" is too broad and too risky. "I used to stay quiet in design reviews when I disagreed with a senior engineer" is specific, believable and fixable.

2. Show its impact with a short example

One or two sentences about a time it caused a problem. This proves the weakness is real and that you've thought about it.

3. Explain what you're doing about it, and what's changed

This should be the longest part. Describe concrete steps and, if you can, a result. The interviewer should finish your answer thinking "that person is getting better at this," not "that person has a problem."

The whole answer should take about a minute.

Example answers for engineers

Taking on too much alone

"I've had a habit of trying to solve hard problems on my own before asking for help. On one project I spent two days debugging a race condition that a teammate had seen before and could have pointed me to in ten minutes. Since then I've set myself a rule: if I'm stuck for more than an hour, I write up what I've tried and ask in the team channel. It's made me faster, and it's helped the team too, because the write-ups often become documentation."

Public speaking

"Presenting to large groups doesn't come naturally to me. Early on, I'd over-prepare slides and still rush through demos. Last year I volunteered to run our team's monthly tech talk specifically to practice, and I joined a speaking group at work. I'm not a natural yet, but I presented our migration plan at an all-hands in the spring, and the feedback was that it was the clearest update of the quarter."

Saying yes to everything

"I tend to say yes to every request, which made it hard to protect time for my main project. At one point I was helping three other teams and slipped a deadline on my own work. Now I keep my priorities written down for the quarter and check new requests against them with my manager. I still help out, but I'm more deliberate about it, and I haven't missed a commitment since."

Unfamiliar part of the stack

"My background is mostly backend, so frontend work is where I'm least confident. When our team needed help on the dashboard last year, I realized how slow I was with modern React. I've been taking on a small frontend ticket each sprint and pairing with one of our frontend engineers. I'm now comfortable shipping UI changes on my own, though I still lean on them for performance work."

Notice that every example ends with something that has already improved. That's what makes the answer land.

Weaknesses to avoid

Some answers backfire almost every time:

• Fake weaknesses. "I'm a perfectionist" and "I work too hard" are humblebrags, and interviewers have heard them hundreds of times.
• Core skills for the role. A backend candidate shouldn't say they struggle with databases. A team lead shouldn't say they avoid giving feedback.
• Character flaws. Being unreliable, dishonest or careless isn't something an interviewer can coach away.
• Weaknesses without a fix. "I'm disorganized" followed by silence leaves the interviewer to imagine the worst.
• Refusing to answer. "I can't think of any" sounds like a lack of self-awareness, which is the very thing they're checking.

Variations you might hear

The same formula works for related questions:

• "What feedback have you received that was hard to hear?"
• "What would your last manager say you need to work on?"
• "Tell me about a skill you've had to improve."
• "If we called your references, what would they say you could do better?"

For the reference version especially, make sure your answer matches what your references would actually say. Consistency matters.

How to find your weakness

If you're stuck, look at:

• Past performance reviews. The "areas to develop" section is a ready-made list.
• Feedback from code reviews and retros. Patterns there are specific and work-related.
• What drains you. Tasks you put off are often the ones you're least confident in.

Pick one weakness, write the three parts out, and say it out loud a few times. Like any behavioral answer, it should sound natural, not memorized. Our STAR method guide covers how to keep short stories like these tight and specific.