How to Answer "What Are Your Weaknesses?" Honestly

"What are your weaknesses?" puts a lot of candidates in a bind. Too honest, and you worry it will count against you. Say "I don't have any weaknesses," and you clearly aren't being truthful. Say "I'm a perfectionist," and the interviewer has heard it hundreds of times.

The question is actually less tricky than it seems. The interviewer isn't hunting for a reason to reject you. They want to know two things: do you understand yourself, and do you know how to grow?

What the interviewer is evaluating

Everyone has weaknesses, and interviewers know it. What they're judging in your answer:

• Self-awareness. Can you see your own gaps honestly?
• Maturity. Can you talk about them calmly, without getting defensive?
• Action. Are you doing something about it?
• Fit. Is this weakness a real risk for this role?

The last point matters most when you choose your weakness. A developer who says "I'm not good at writing code" has a problem. A developer who says "I'm not confident presenting to large groups" is in normal territory, especially if they're working on it.

The three-part formula: weakness, example, fix

A good answer is three to five short sentences in this order:

1. The weakness. Name it clearly in one sentence.
2. A short example. When it shows up, or what effect it has.
3. The fix. Concrete steps you've taken and are taking, plus any result.

The sentence patterns:

One thing I'm working on is [weakness].

For example, [short situation].

So now I [what you do about it]. It's helped me [result].

The third part should be the strongest. An answer that ends on the problem leaves a negative impression. An answer that ends on the fix leaves a positive one.

Sample answers for different weaknesses

Here are a few examples. Pick one that's actually true for you and adjust the details. Don't borrow a weakness that isn't yours just because the example sounds good.

Spending too long on small details

I sometimes spend too long on small details. Once, I spent a full day polishing a button style. The deadline was close, and it wasn't important. Now I set a time limit for each task. I also ask my lead which parts matter most.

Finding it hard to say no

I used to say yes to every request. That made me miss some of my own deadlines. Now I check my task list before I agree. If I'm too busy, I say when I can do it instead.

Not comfortable presenting to large groups

I'm not very comfortable presenting to big groups. In small meetings, I'm fine. To improve, I volunteer to give short demos in team meetings. It's getting easier each time.

Spoken English that's still developing

For many non-native speakers, this is the most honest weakness there is. The interviewer can already hear it in how you speak, so naming it shows self-awareness rather than revealing anything new.

My spoken English is still slower than my written English. I sometimes need a moment to find the right words. So I practice speaking every day for twenty minutes. I also write down key points before meetings. My written communication is clear, and I'm improving my speaking.

If the role depends heavily on speaking, add evidence that you already work well despite it, such as working with overseas clients mainly in writing.

Not having used a specific technology yet

Sometimes the most relevant weakness is a gap in experience. Don't cover it with a false claim.

I haven't used Kubernetes in a real project yet. I've used Docker for two years, so the basics are familiar. I'm taking a course now, and I've set up a small test cluster.

Weaknesses to avoid

Some answers almost always hurt you:

Answer	Why it backfires
"I don't have any weaknesses."	Sounds dishonest or lacking self-awareness.
"I'm a perfectionist." (no example)	A cliché; sounds like you're dodging.
"I work too hard."	Same cliché, and it doesn't answer the question.
A weakness at the core of the job	E.g., an accountant saying "I'm careless with numbers."
Attitude problems	"I get angry easily" or "I don't like rules."
Personal problems	Health, family, or money issues don't belong here.

"Perfectionist" can work if you give a real example and a real fix, like the "small details" answer above. What makes it bad is using it as a trick.

Common mistakes when answering

1. Too long and too confessional. You don't need to list every flaw. Pick one, explain it briefly, and stop.

2. Stopping at the problem. "I'm bad at deadlines." Then silence. That makes the interviewer nervous. Always continue to the fix.

3. A vague fix. "I'm trying to improve" isn't enough. Name the steps: which course, which habit, which tool.

4. Inventing a "safe" weakness. The interviewer may follow up with "Can you give me an example?" If the weakness isn't yours, you won't have one.

5. A defensive or overly apologetic tone. Talk about it calmly, the way you'd talk about anything ordinary. Because it is ordinary.

Follow-up questions to prepare for

After you answer, the interviewer may dig deeper. Have short answers ready for:

"Can you give me an example?"

"How has that affected your work?"

"What feedback have you received about it?"

For questions that ask for an example, the STAR structure helps a lot. See the STAR method for English interviews.

You'll also hear the same question in other forms, like "What would your manager say you need to improve?" or "What's an area you're developing?" The same answer works.

Fill-in template

Weakness:   One thing I'm working on is ________.
Example:    For example, ________.
Fix:        So now I ________.
Result:     It's helped me ________.  (optional, only if there's a real result)

Fill it in with a weakness that's true, then say it out loud. Aim to finish in 30 to 45 seconds.

Summary

The weakness question tests self-awareness and willingness to grow, not perfection. Choose one real weakness that isn't central to the job, give a short example, and finish with concrete steps. Avoid clichés and don't invent anything. For the other questions that usually come up in the same interview, see the most common English interview questions.

Repartee builds answer scripts only from the profile you fill in yourself, including the weaknesses and lessons you write down. If something isn't in your profile, the script won't make it up.