INTERVIEW QUESTION
What are your weaknesses? How to give an honest answer that still helps you
Pick a real weakness that won't cost you the job, and focus your answer on what you've changed.
“I'm a perfectionist.” “I work too hard.” Interviewers have heard these so often that they sound like a refusal to answer.
The opposite mistake happens too: a weakness so central to the job that the interviewer stops picturing you in it.
The answer that works sits between those two. It's honest enough to believe, and it shows you notice your own patterns and change them. That habit is what they're trying to see.
Choosing a weakness you can safely share
Picking the weakness is the hardest part. Before you use one, check it against these three things:
- It's real. Someone who works with you would recognize it straight away.
- It isn't the core of the job. An analyst who is careless with numbers, or an engineer who can't debug, is giving a reason not to hire them.
- You're already working on it. You can name a specific change and a recent time you used it.
In a thread about a culture-fit interview with an engineering manager, the advice is the same: be honest, but don't pick a weakness that makes you a poor fit for the role.
The fastest way to find one is to ask a colleague or former manager, “What's one thing I could do differently?” Their answer is usually more believable than anything you'd choose yourself.
How to tell it
Say the weakness in one plain sentence. Then give a short, real moment when it caused a problem, ideally one that shows how it affected other people.
That's the advice in a talk by the author of Cracking the PM Interview: show you understand the effect on the people around you, then describe what you do to manage it. Interviewers want a genuine answer.
Spend most of the answer on what you do now, with a recent example. Be honest that it's still a work in progress.
Make sure it fits the rest of your interview, too. If your weakness contradicts a strength you claimed ten minutes earlier, the interviewer will notice.
Example answers
In each made-up stronger answer, the cost takes a sentence or two and the change takes most of the time. If yours is the other way round, shorten the cost.
Software engineer
Weaker
“Honestly, I'd say I'm a bit of a perfectionist. I just care a lot about getting things right, so sometimes I work longer hours than I need to.”
It's a compliment presented as a weakness, with no example and no change. Many interviewers will hear it as avoiding the question.
Stronger
“I tend to keep digging into a problem on my own for too long before asking for help. Last spring I spent most of two days on a failing integration test that a teammate recognized in ten minutes.
Now I give myself a time limit. If I haven't made progress in about two hours, I write down what I've tried and post it in the team channel. Often, writing it down solves it. When it doesn't, my question is much better.
I still go past the limit sometimes when a problem feels close.”
The cost is concrete and the change is specific. The last sentence makes it believable, because real habits take time to change.
Product manager
Weaker
“My weakness is that I care too much about the product. Sometimes I get so invested that I work late to make sure everything is perfect for our customers.”
Caring too much is a strength presented as a weakness. There's no cost and no change.
Stronger
“I find it hard to say no to requests, especially from sales. Last year I agreed to several small customer requests in one quarter, and our main project slipped by a month.
Now I keep a written list of what we're not doing this quarter and share it with sales at the start. When a new request comes in, we look at the list together and decide what it would replace.
It's made those conversations much easier, though I still find the first no uncomfortable.”
A real weakness for a product manager that isn't fatal, a concrete cost, and a specific change.
Product designer
Weaker
“I'm too much of a perfectionist with my designs. I spend a lot of time on the details because I want everything to be pixel-perfect.”
This is one of the most common ways to avoid the question. It also hints at a real problem without owning it.
Stronger
“I used to polish designs too early, before we knew the idea worked. On one project I spent two weeks on detailed screens for a feature, and the first user test showed people didn't understand the basic idea.
Now I test rough sketches first, sometimes on paper, and only polish once the idea holds up. It's saved a lot of time.
I still feel the pull to make things look finished before I share them.”
It turns the perfectionist cliché into a real habit, with a real cost and a real change.
Data analyst
Weaker
“I'd say my weakness is that I'm very detail-oriented. I double-check everything, which can take a bit longer, but I think it's worth it.”
For an analyst, being careful is part of the job. This doesn't tell the interviewer anything new.
Stronger
“I tend to present too much of my method and not enough of the answer. After one review, my manager told me the leadership team had stopped listening by the fourth slide.
Now I start every presentation with the recommendation and one chart, and keep the method in an appendix for questions. People ask better questions now, because they know what I'm recommending.
I still have to cut slides I'm proud of.”
A real weakness that isn't about accuracy, feedback that prompted the change, and evidence that it's working.
Program manager
Weaker
“My weakness is that I'm too organized. I like having a plan for everything, and sometimes I get frustrated when people don't follow the process.”
This sounds like a strength, and the frustration could worry an interviewer more than it reassures them.
Stronger
“When a task is late, my instinct is to do it myself rather than chase the person who owns it. On one program I ended up writing three teams' status updates for a month, and it hid how far behind they really were.
Now every action has a named owner and a date, and I follow up instead of doing it myself. Problems show up earlier, and the teams own their updates.
I still catch myself drafting things for people when I'm busy.”
A real habit, a cost that mattered to the program, and a change that's still in progress.
Consultant
Weaker
“I sometimes take on too much because I want to help everyone. I also find it hard to delegate because I like things done properly.”
Two weaknesses mentioned in passing, and neither has an example or a change.
Stronger
“I put too much detail into presentations. On one project, the client's finance director stopped me ten minutes into an update and asked for the answer.
Since then I write a one-page summary with the recommendation at the top before I build any slides. If I can't fit it on a page, I'm not ready to present.
It's become a habit, though I still have to resist adding backup slides.”
A believable weakness for a consultant, a moment when it cost something, and a specific change.
Real weaknesses that tend to work, by role
Most people struggle to think of a weakness that is honest without being harmful. This table shows the kind that tend to work in each role: real enough to recognize, but not about the core of the job.
Use it to recognize your own, not to borrow one. Only use a weakness that's true.
| Role | A real but survivable weakness | A change you might describe |
|---|---|---|
| Software engineer | Staying stuck alone too long; pull requests too large to review | A time limit before asking; smaller, staged changes |
| Product manager | Saying yes to too many requests; consulting everyone before deciding | A written list of what you're not doing; a decision date for each choice |
| Product designer | Polishing screens before testing the idea; getting attached to a first concept | Testing rough sketches first; bringing several directions to each critique |
| Data analyst | Presenting too much of the method and not enough of the answer | Leading with the recommendation and keeping the method for questions |
| Consultant | Putting too much detail in presentations | One-page summaries with the recommendation first |
| Program manager | Doing tasks yourself instead of chasing the owner | Naming an owner and date for each action, then following up |
What not to say
Each of these makes the interviewer doubt either your honesty or your fit for the role:
- Disguised strengths: perfectionism, working too hard, caring too much.
- The main thing the role exists to do.
- “I don't have any.” It suggests you don't look closely at your own work.
- Something too personal. Keep it to how you work.
- A weakness with no change. “I'm working on it” with nothing behind it is the weakest version of an honest answer.
Related questions
“What would your manager say you need to work on?” Real feedback is more convincing than anything you'd pick yourself, so use it if you have it.
“What's hard about working with you?” A sharper version of the same question. Choose a real edge and explain how you manage it. It's the same answer, told from your colleagues' side.
“Tell me about feedback that changed how you work.” This is the experience-based version of the same question, and it comes up a lot in engineering interviews. See the software engineer guide.
“What are your strengths and weaknesses?” Pair this with a short version of your strengths answer.
If your answer runs past a minute, shorten the cost, not the change. The change is the part they're listening for.