What are your weaknesses? How to answer, with examples by role
'How to answer "what are your weaknesses" in an interview: a four-part answer, example answers by role, and a check of 147 real job postings for which weaknesses to avoid.'
"What are your weaknesses?" is the interview question people dread most, and the one they prepare worst. Most candidates either dodge it with "I'm a perfectionist" or confess something that costs them the job.
There is a better way, and it is checkable. A good answer names a real gap, shows how you found it, and shows what you changed. And whether a given weakness is safe depends on one thing you can read before the interview: the requirements list of the job you applied for. We counted those lists in 147 real postings to show how much that varies by role.
What published interview guides do with this question
Most advice on this question explains what "interviewers want" without quoting any interviewer guidance. So we read what three large employers publish for their interviewers and candidates.
The US Office of Personnel Management's Structured Interview Guide never uses the word "weakness". Its questions have to come from the competencies of the job, and question writers are told to use words like "most, last, worst, least" so the candidate describes one real incident. The guide's premise is that past behaviour in similar circumstances is the best predictor of behaviour on the job.
The UK Civil Service's published guidance doesn't mention weaknesses either. Its Success Profiles strengths guidance tells candidates there are "no right or wrong answers" and asks them not to rehearse. Its behaviour framework has a "Developing self and others" behaviour, and at entry grades the published examples include to "identify gaps in your skills and knowledge and make plans of how to develop these" and to "listen to and act on feedback from colleagues". That rubric is the shape of a good answer, which the next section turns into four parts.
Private employers say similar things. Amazon's Earn Trust principle says leaders are "vocally self-critical, even when doing so is awkward or embarrassing".
If you hear the generic "what are your weaknesses?", you are probably in a less structured interview, and a clear, specific answer stands out. In a structured interview, the same ground gets covered by a question like "tell me about the last time you got critical feedback". So prepare the story first. The one-line weakness comes out of it, and you are ready for both versions.
The answer in four parts
Every strong answer to this question has the same four parts, in this order:
- The gap. One specific skill or habit, named in plain words.
- How you know. A moment, a piece of feedback, a result that showed it to you.
- What you changed. The concrete thing you do differently now.
- Where it stands. An honest status. Better, not cured.
Keep it to about a minute. The interviewer wants to see that you can look at your own work the way a manager would, and that you do something about what you see.
A full answer and the job each sentence does
I used to hold on to my work until it felt finished, and share it too late for feedback to change much.
On a pricing page redesign, I showed my manager the final version two days before launch. She spotted a problem with the annual plan that a ten-minute look a week earlier would have caught.
I now share a rough draft at about a third of the way through any task longer than a few days, with two questions I want answered.
It still feels uncomfortable to show unfinished work, but I haven't had a late surprise like that since.
Notice what the answer doesn't do. It doesn't apologise, it doesn't turn the weakness into a hidden strength, and it doesn't claim the problem is gone.
Check your weakness against the job posting
Almost every guide tells you to avoid a weakness that is "core to the job". None of them shows what that looks like in practice. So we checked the weaknesses those guides suggest most often against real requirement lists.
Method. On 1 October 2026 HiredFolio pulled postings from the public Greenhouse job-board API (boards-api.greenhouse.io/v1/boards/<company>/jobs?content=true) of 20 tech employers, mostly US-based (Stripe, Datadog, Dropbox, GitLab, MongoDB, Lyft and others). We kept up to 3 postings per employer and role, 147 in all: 30 each for the four roles below, plus 27 customer success and analyst postings, too few to report on their own. We searched only the requirements section, never "nice to have", for each weakness and its common wording ("presentation skills", "highly organized", "manage multiple priorities").
| Weakness the guides suggest | All 147 | Account exec (30) | Marketing (30) | Project/program mgr (30) | Software eng (30) |
|---|---|---|---|---|---|
| Public speaking / presenting | 17 | 6 | 3 | 3 | 0 |
| Organized or prioritizing | 29 | 4 | 5 | 12 | 0 |
| Attention to detail | 17 | 0 | 4 | 5 | 1 |
| Mentoring or coaching others | 7 | 1 | 1 | 0 | 4 |
| Delegation | 1 | 0 | 0 | 1 | 0 |
| Conflict | 1 | 0 | 0 | 1 | 0 |
| Patience | 0 | 0 | 0 | 0 | 0 |
The pattern runs against the usual advice.
The clichés are safe and useless. Delegation, conflict and patience almost never show up as requirements, which is why guides keep recommending them. They are also the answers interviewers hear most, so they tell the interviewer nothing about you.
The more specific weaknesses guides suggest are the ones that collide with real jobs. "Public speaking" sits in the requirements of 6 of 30 account executive postings and none of the 30 software engineer postings. Being organised, or juggling several priorities, is asked for in 12 of 30 project and program manager postings and in no engineering posting. The same weakness is fine for one job and a red flag for another.
Our sample has limits: tech companies on one applicant tracking system, a word search rather than a reading of intent, one day's snapshot. The check itself takes five minutes on your own posting:
- Copy the requirements list of the job, not the whole posting.
- Search it for your weakness and its synonyms ("presenting", "presentation", "stakeholders").
- If it appears, pick another weakness. If it sits under "preferred", you can keep it, as long as part 3 of your answer is strong.
Example answers by role
These are examples we wrote to show the four parts at work, not scripts. Swap in your own facts, or the follow-up questions will expose you.
Account executive
Avoid presenting, which appears in a fifth of the sales postings we read. Pick a sales habit that isn't a listed requirement.
I held on to deals too long once they had stopped moving.
Reviewing my pipeline with my manager last year, a third of my open opportunities hadn't had a reply in over a month. I was spending follow-up time on them instead of new prospects.
After the second call I now ask the buyer directly about budget and timeline, and I close out any deal with no next step booked after three weeks.
My pipeline is smaller but more honest, and my forecast calls are easier to defend.
Project or program manager
Never "disorganised" or "time management" for this role. Pick a gap next to the job rather than at its centre, like technical depth for someone who came from operations.
I came into program management from operations, so my weak spot was technical depth. I couldn't always tell when an engineering estimate was risky.
A data migration I ran slipped by three weeks because of a dependency the team had mentioned in a design review. I hadn't understood why it mattered.
I now read every design doc before the review and bring one question per risk. I also booked a monthly hour with our staff engineer to go through the architecture.
I still lean on engineers for the details, but I catch the dependency questions early now.
Software engineer
Presenting never appeared in our engineering requirements, so it is a fair pick here. Mentoring did appear (4 of 30), so avoid it for senior roles.
I'm much better in writing than when I present to a large group.
I demoed a caching change at an all-hands. I read from my slides, ran over time, and two teams who would have benefited didn't adopt it until months later.
I volunteered to run our team's fortnightly demo for a quarter, and I rehearse any talk once in front of one colleague.
Short demos are comfortable now. A conference talk would still be a stretch.
First job or career change
Lack of experience is the obvious weakness, and the interviewer already sees it on your resume. Name one tool or skill from the "preferred" list, not the required one, and show you've started.
I haven't used Salesforce in a real job. Your posting lists it as a plus.
In my last role as a teacher, I tracked parent contacts in a spreadsheet, so I know the process but not the tool.
I've worked through a free Trailhead admin trail and rebuilt my spreadsheet as a practice org.
I can log activity and build a simple report. Your team's setup is what I'd learn first.
Whatever you pick, make sure your resume doesn't claim the opposite. If your skills section says "excellent presenter", don't name presenting as your weakness. Our guide to writing an effective resume covers how to keep the two consistent.
Clichés, rewritten
The usual answers fail because they hide the gap. Here are two rewrites.
Example the perfectionist answer
Cliché
I'm a perfectionist. I just care too much about quality.
Specific
I spent too long polishing internal reports nobody read closely. I now ask who the report is for and set a time limit before I start.
Example the hard-worker answer
Cliché
I work too hard and forget to take breaks.
Specific
I used to say yes to every request and tell my manager I was overloaded only when a deadline was already at risk. Now I flag it at the Monday check-in, with what I'd drop.
The second rewrite is close to "can't say no", which appears in several guides. It works because it names the exact behaviour and what replaced it.
Follow-up questions to expect
A prepared answer often gets a follow-up. The most common ones:
- "Can you give me another one?" Have a second weakness ready, built the same way.
- "How did your manager react?" This tests whether the story is real. Know who said what.
- "Is it still a problem?" Your "where it stands" line answers this. Don't claim it's solved.
If the interviewer says the question is about the role itself ("what part of this job would be hardest for you?"), answer with a part of the actual job, using the same four steps. For the rest of the interview, from your introduction to the questions you ask at the end, see our guide to succeeding in a job interview.
Using HiredFolio before the interview
The check above needs the posting, and postings are often taken down once applications close. HiredFolio keeps the job description with each application in your tracker, next to your notes and follow-up date, so the requirements list is still there the evening before.
After the interview, write down which weakness you used and how it landed. If a second round follows, use the same one. Interviewers compare notes.
Key takeaways before your next interview
Search the posting's requirements list for your weakness and its synonyms, and pick another if it appears.
Write the answer in four parts (the gap, how you know, what you changed, where it stands) and say it out loud in under a minute.
Prepare the story of the last time you got critical feedback, so you can answer the structured version of the question too.
If the recruiter goes quiet afterwards, here is what their replies usually mean.
Read next
- Why do you want to work here? How to answer with what the job posting doesn't say
'How to answer "why do you want to work here": find company details others miss, see a worked example from an annual report, and read five sample answers.'
- Why should we hire you? How to answer, with 5 example answers
'How to answer "why should we hire you": three proofs from the job posting, a 150-word budget, and example answers based on real job postings.'
- What are your salary expectations? How to answer on the form and the call
'How to answer "what are your salary expectations" on an application form and a recruiter screen, with scripts, the state laws that apply, and a count of 243 real application forms.'