How to Answer 'What Are Your Weaknesses' in a Job Interview

A structure for naming a real limitation, showing what you changed, and proving the fix worked, plus scripts for five versions of the question.

By Priya Nandakumar · Oct 06, 2026 · 8 min read

Featured image for "How to Answer 'What Are Your Weaknesses' in a Job Interview"

"What are your weaknesses?" is a test of whether you can describe a real limitation and then show what you did about it. The answer that works names one specific gap, attaches a concrete fix, and ends with a result the interviewer can picture — in the language of the job you're applying for.

This guide gives you five versions of the question with answers you can say aloud, a full script, and a checklist to finish before you walk in.

Why Interviewers Ask This

Two things are being checked, and neither is the flaw itself. The first is self-awareness: Indeed's guidance says hiring managers ask about weaknesses to evaluate whether you can see yourself accurately and whether you are taking steps to improve (Indeed Career Guide (India), undated), and Indeed's UK guide adds honesty and the ability to keep improving (Indeed Career Guide (UK), undated).

The second is risk. An interviewer hiring a staff accountant or a med-surg nurse wants to know the gap you name is not the core of the role.

The red flags are specific: a non-answer such as "I care too much"; a weakness that is actually a listed requirement in the posting; and a weakness named with no fix attached. CareerOneStop's practice question page tells candidates to be honest, choose a weakness that won't significantly impact job performance, and then discuss the steps taken to overcome it (CareerOneStop (U.S. Department of Labor), undated).

Sample Questions & Answers

Each answer below moves through the same order: what the situation was, what you were asked to do, what you changed, and what happened. Swap the roles for your own.

"What is your greatest weakness?"

Assistant store manager, grocery retail
"When I was promoted to assistant store manager, I kept building the weekly schedule myself instead of handing it to my two shift leads. My district manager was clear that my job was to develop those leads, not to do their work. So I wrote a one-page scheduling checklist, trained both leads on it, and changed my role to reviewing their draft on Fridays. They've built the schedule for 14 weeks running, and my admin time dropped from about six hours a week to under two. I still write down what I delegate every Monday so I don't quietly take it back."

"Tell me about a weakness that has actually affected your work."

Staff accountant, regional CPA firm
"In my first year as a staff accountant, I rushed through the month-end variance summary because speaking to a room made me uncomfortable, and the controller twice had to ask me to repeat figures. I had to present that summary every month, so avoiding it wasn't an option. I started writing my opening two sentences word for word, rehearsing the summary three times out loud the night before, and standing up to deliver it. I've presented eight closes since, and the controller stopped asking for my slides in advance because the live version was clear enough."

"What would your last manager say you need to improve?"

QA analyst, software company
"She'd say I sat on problems too long. On a release team of six, I'd dig into a blocking bug for a day or two before telling anyone, because I wanted a complete explanation first. Her ask was simple: flag blockers the same day I find them. I set a rule for myself — thirty minutes of investigation, then a message in the release channel with what I know so far. Across the last three releases, every blocker I found was flagged the same day, and we shipped two of the three on the original date."

"What skill in this job posting would you need to develop?"

Marketing coordinator moving into an analyst role
"Your posting lists SQL reporting as a daily requirement, and I haven't used it in a paid role — that's the honest gap. In my current marketing coordinator job at a B2B software company, I pull campaign numbers out of three dashboards by hand. I finished an eight-week SQL course in the evenings and rebuilt our weekly campaign report as a single query. Build time went from about three hours to twenty minutes. I'd still expect to need review on anything complex for the first month."

"Can you give me two or three weaknesses?"

Registered nurse, med-surg unit
"I'll give you two. The first is charting — I used to leave most of it to the end of a twelve-hour shift, which pushed me into about four hours of overtime a week. My charge nurse asked me to chart at the point of care instead. I made a pocket template and now chart after each round; I stayed late once in the last six weeks. The second is the new infusion module in our EHR. I've signed up for super-user training, and until then I ask the shift lead to check my entries."

Sample Answer Script

Customer support team lead, software company
"I'll give you the honest version. When I stepped up to customer support team lead, I had six agents reporting to me, and two of them were closing tickets without the troubleshooting notes our escalation team needed. I said nothing for about a month. I told myself I was waiting for the quarterly review, but what was really happening is that I avoid direct feedback when I like the person.
My manager made the expectation plain: feedback within a week of the behaviour, in writing, with a specific ticket attached.
So I changed how I run the week. I block fifteen minutes with each agent every Friday, and I write one sentence of specific feedback before the meeting so I can't talk myself out of it. I also use a set opening — 'Here's one thing I'd like you to do differently next week, and here's the ticket I'm looking at.' That makes it an ordinary conversation instead of a confrontation.
The result is measurable. Escalation rework on my team dropped from about fourteen tickets a month to four, and both agents now write full notes without being asked. I still find those conversations uncomfortable, so the Friday block is permanent in my calendar. That's the part I'm still working on."

Before You Walk In

Write your qualifications against each requirement in the job posting and circle the one you'd rate yourself weakest on — CareerOneStop suggests this as a way to identify and plan for skill gaps (CareerOneStop (U.S. Department of Labor), undated).
Cross off every weakness that appears in the posting's top three requirements, and choose your answer from what's left.
Write one sentence naming the weakness and one naming the specific step you took — Indeed's guidance requires both the weakness and the steps being taken to improve (Indeed Career Guide (India), undated).
Put one number into your result sentence: hours saved, tickets, shifts, weeks, or a count of reports.
Write a second and a third weakness, one sentence each, in case you're asked for more than one (Indeed Career Guide (India), undated).
Read the full answer out loud three times with a timer running and cut it to under 90 seconds — CareerOneStop advises practising answers on paper and out loud (CareerOneStop (U.S. Department of Labor), undated).
Book a free mock job interview at a local American Job Center for feedback (CareerOneStop (U.S. Department of Labor), undated).
Set a calendar alert that gets you to the building or the video link 10 to 15 minutes before the start time (CareerOneStop (U.S. Department of Labor), undated).

Frequently asked questions

Can I say I don't have any weaknesses?

No. The question exists to test self-awareness, and a denial reads as either evasion or poor judgement. CareerOneStop's practice question page tells candidates to be honest and pick a weakness that won't significantly impact job performance, then describe the steps taken to overcome it (CareerOneStop (U.S. Department of Labor), undated). Pick a real one and attach the fix.

Is "I'm a perfectionist" a good answer?

It is heavily used and usually lands as a disguised strength, which is the opposite of what the question is checking. If over-checking genuinely costs you time, say so concretely: name the task, the delay it caused, and the rule you set to stop it — for example, a marketing coordinator capping proof rounds at two before a mailer goes out.

Should I admit a weakness that's listed in the job posting?

Avoid naming anything in the posting's top requirements as a weakness, since that invites doubt about the core of the role. A genuine gap in a secondary or preferred skill is different — name it, then describe what you've already done about it, as in the SQL example above, and say what support you'd expect in month one.

How long should my weakness answer be?

Aim for 60 to 90 seconds. Give two or three details of context, one sentence on what was expected of you, the most time on what you changed, and almost as much on the result — Indeed's STAR guidance advises spending only slightly less time on results than on actions and using concrete examples (Indeed Career Guide, undated).

What if I haven't fixed the weakness yet?

Say what you are doing now and what comes next. Indeed's guidance recommends making the answer actionable by sharing how you intend to work toward overcoming the weakness (Indeed Career Guide (India), undated). A nurse awaiting EHR super-user training, or an analyst midway through a course, can name the interim safeguard they use in the meantime.

Sources

CareerOneStop (U.S. Department of Labor) — Practice interview questions
CareerOneStop (U.S. Department of Labor) — Get ready to interview

Written by

Priya Nandakumar

Priya covers the texture of offices, remote teams, and the spaces in between — what makes a workplace bearable or unbearable long after the paycheck stops mattering. She likes stories where nobody is the villain.