"My biggest weakness is that I'm a perfectionist." Please don't say this. Interviewers have heard it a thousand times, and it comes across as either fake or lacking self-awareness.

But you also can't say "I struggle with showing up on time" or "I have trouble working with others." That's the trap—how do you answer honestly without disqualifying yourself?

Here's the framework that works: pick a real weakness that isn't core to the job, then show genuine progress.

The Formula

1
Name a real weakness — Not a humble brag. Something you've actually struggled with.
2
Give a specific example — When did this weakness show up? What was the impact?
3
Show what you're doing about it — Concrete steps you've taken to improve
4
Share the progress — Evidence that you're getting better

What Makes a Good "Weakness" to Share

Good Weaknesses to Mention

Skills that are learnable and you're actively improving
Things that aren't core to the role you're applying for
Areas where you can show measurable improvement
Weaknesses that demonstrate self-awareness

Weaknesses to Never Mention

Core job requirements (e.g., "I'm bad at coding" for an SWE role)
Character flaws (unreliable, dishonest, can't take feedback)
Disguised strengths ("I work too hard")
Things you have no plan to fix

Example Answers for Software Engineers

Example 1: Public Speaking

"I've historically struggled with presenting to large groups. In my first job, I avoided demo days and would ask teammates to present my work. I realized this was limiting my career—senior engineers need to communicate effectively.

So I started small. I volunteered to lead team standups, then presented at internal tech talks. Last quarter, I presented our new architecture to about 50 people. Was I nervous? Yes. But I got through it and got good feedback.

I'm still working on this, but I'm much better than I was two years ago. I've gone from avoiding presentations to actively seeking them out."

Example 2: Saying No

"I used to have trouble saying no to requests. Someone would ask for help, and I'd drop what I was doing—even if I had my own deadlines. This led to me overcommitting and sometimes missing my own deliverables.

I've been working on this by being more intentional about my time. I now block focus time on my calendar and have learned to say 'I can help with that tomorrow afternoon' instead of immediately switching contexts.

It's still my instinct to say yes, but I've gotten much better at protecting my time while still being helpful to teammates."

Example 3: Asking for Help

"I sometimes spend too long trying to solve problems on my own before asking for help. Early in my career, I'd spend hours stuck on something when a senior engineer could have pointed me in the right direction in 5 minutes.

I've set a personal rule now: if I'm stuck for more than 30 minutes on something, I'll at least rubber duck it with someone or post in our team channel. It was uncomfortable at first—I didn't want to seem incompetent—but I've learned that asking for help is actually seen as a strength.

My manager actually mentioned in my last review that he's seen me improve in this area."

Example 4: Technical Depth in New Areas

"When I encounter new technologies, I sometimes want to learn everything before building anything. This has slowed me down in the past—I'd spend weeks reading documentation when I could have been learning by doing.

I've learned to balance this by setting time limits. I'll give myself a day or two for research, then start building something small. I can always learn more as I go. This has actually made me faster at picking up new technologies.

Just last month I had to learn Kubernetes for a project. Old me would have read for two weeks. Instead, I spent two days on basics then just started deploying things and learning from mistakes."

What NOT to Say

Answers That Will Hurt You

"I'm a perfectionist"

Cliché. Everyone says this. It also sounds like a humble brag.

"I work too hard"

Another obvious fake weakness. Not believable.

"I care too much"

Same problem—trying to disguise a strength as a weakness.

"I don't have any real weaknesses"

Shows lack of self-awareness. Everyone has weaknesses.

"I'm not very good at [core job requirement]"

If you're applying for a backend role, don't say you struggle with databases.

Practice Your Answer Live

LastRound AI helps you practice behavioral questions and get real-time feedback on your answers before the actual interview.

Why Interviewers Ask This Question

Understanding the intent helps you answer better. They're looking for:

Self-awareness: Do you know yourself? Can you honestly assess your areas for growth?
Growth mindset: Do you believe you can improve? Are you actively working on it?
Honesty: Will you give a real answer or try to game the question?
Fit assessment: Is this weakness something that would cause problems in the role?

The Bottom Line

Pick a real weakness—something you've actually struggled with. Show that you're self-aware enough to recognize it and motivated enough to work on it. The key is genuine progress, not perfection.

The best answers make you seem human and coachable. That's more valuable than pretending you have no flaws.

LastRound AI

"What's Your Biggest Weakness?" — The One Answer Strategy That Actually Works