When an interviewer asks about your strengths and weaknesses, give one of each, and make both specific to the job. For the strength, name a quality the job posting asks for and prove it with one result. For the weakness, name a real one that is not central to the role, show it with a short example, and explain what you now do about it. That last part is where most answers fail. In a Harvard Business School study, 77% of students answering "what is your weakness?" gave a strength in disguise, and the raters reading their answers were less interested in hiring them than the students who admitted a real flaw. Below are a three-part formula, eleven sample answers written for specific roles, a table that turns a job posting into strength answers, and a list of answers that backfire.
Why interviewers ask both
The two questions test different things. The strength question checks fit: does what you are best at match what the job needs? The weakness question checks judgment. Bentley University's career blog puts it plainly: "What interviewers really want to know is whether or not you're self-aware", and whether you are taking steps to improve.
Both can come up in the recruiter screen, which is the hardest round to pass. Ashby's 2026 Talent Trends report, covering about 54 million applications on its platform, found that about 35% of candidates pass the recruiter screen, against 95% after the onsite and 81% at the offer stage. A vague answer in a screening call costs more than it would in a final round, where the interviewers have already seen your work.
What each question is really asking:
| Question | What the interviewer is checking | What a strong answer contains |
|---|---|---|
| What are your strengths? | Does your best skill match this job? | One quality the posting asks for, one result that proves it |
| What is your greatest weakness? | Can you see your own gaps, and do you fix them? | A real gap, one example of its cost, one concrete fix with evidence |
| What are your strengths and weaknesses? | Both, plus whether you can be brief | One of each, strength first, under a minute and a half |
How to pick a real weakness
A good weakness passes four tests. Run your candidates through them before you write a word.
| Test | Question to ask yourself | Fails the test |
|---|---|---|
| Real | Would a former manager or teammate recognize it? | "I care too much" |
| Not core | Is it absent from the posting's required list? | An accountant who is careless with detail |
| Shown | Can you describe one time it cost something? | "I sometimes could be more organized" |
| Fixed | Can you name a habit, tool or result that shows progress? | "I'm working on it" |
Where to find candidates:
- Old performance reviews and feedback. The "areas for development" box is a ready list, and a reviewer has already confirmed the weakness is real.
- The posting's "nice to have" list. A preferred skill you lack is an honest, safe weakness, because the employer has already said it is not required. Pair it with what you are doing to learn it.
- The work you put off. Whatever you delay, delegate badly or redo is usually where your weakness lives.
One boundary: the question is about work habits and skills. Under EEOC guidance on the Americans with Disabilities Act, "at the pre-offer stage, an employer cannot ask questions that are likely to elicit information about a disability", although it can ask whether you can perform the job's functions. You do not need to offer a health condition as your weakness.
A formula: the weakness, the evidence, the fix
Every answer below follows the same three parts.
- The weakness. Name it in one plain sentence. No hedging, no "some people say".
- The evidence. One short example of when it cost you or your team something. This is what makes the weakness believable.
- The fix. What you changed, and proof that it is working: a habit, a tool, a course, a result.
Here is one answer split into its parts. It is a sample, written for this post.
| Part | Sample text |
|---|---|
| Weakness | "My weakness is that I've been slow to raise problems early. I like to arrive with a solution, so I sit on bad news while I work one out." |
| Evidence | "On a reporting project last year, I spent two days on a data issue before mentioning it, and my manager had already promised the client a date I then missed." |
| Fix | "Now I flag any blocker within half a day, even without an answer, using a two-line note: what's wrong, and what I'm trying next. On my last two projects, nothing slipped without warning." |
Spend the most words on the fix. The weakness and the evidence earn trust; the fix is what the interviewer hires. Four to six sentences is plenty. Stop once the fix is said; if they want more, they will ask.
Weakness examples with sample answers
Each sample below is written fresh for this post and is not a real person's answer. Change the details to your own; an answer that is not true will not survive one follow-up question.
| Weakness | Good fit for | Avoid for | What the interviewer hears |
|---|---|---|---|
| Delegating too little | New team leads, senior individual contributors | Manager roles with large teams | You can do the work and know you have to scale |
| Overpreparing presentations | Analysts, engineers, researchers | Sales, events, live client roles | You are careful and learning to ship faster |
| Slow to raise problems early | Most roles | Incident response, operations on call | You own your mistakes and changed a habit |
| Public speaking | Back-office, technical, research roles | Teaching, sales, client advisory | You know your gap and practice deliberately |
| Saying yes to too many requests | Support, operations, coordinators | Roles built on saying no (procurement, compliance) | You are helpful and now protect priorities |
| A tool from the preferred list | Any role where the tool is optional | Roles where that tool is required | You read the posting and are closing the gap |
| Giving direct feedback | Peers moving into leadership | People management roles with reviews due soon | You are learning a management skill on purpose |
Software engineer: overpreparing
"I tend to polish code longer than the task needs. On one feature I spent a day refactoring a module nobody else would touch for months, and the release went out late. Now I agree on a 'good enough' bar with the reviewer before I start and leave cleanup as a separate ticket. My last four pull requests merged inside the sprint they were planned for."
Data analyst: slow to share early work
"I don't like showing analysis before it's finished, which means people sometimes see the wrong question answered very thoroughly. Early in my current role, I built a full churn model before learning the team only needed a simple cohort table. Now I send a rough version on day one with the question I think I'm answering, and I ask someone to confirm it."
Nurse: saying yes to every request
"I find it hard to turn down a colleague who asks for help, even when my own patients need attention. On one busy shift I fell behind on charting because I kept covering for others. I now check my own list before I agree, and I'll say 'I can in twenty minutes' instead of dropping what I'm doing. My charting has been on time every shift this quarter."
Marketing coordinator: a tool from the nice-to-have list
"Your posting lists SQL as a plus, and it's my weakest area. I can read a simple query, but I've relied on analysts to pull campaign data. I'm halfway through an online course and I now write my own weekly report query, which an analyst checks before I share it."
New team lead: delegating too little
"When I first led a team, I kept the hardest tickets for myself because it felt faster. Two sprints in, I was the bottleneck and a junior engineer told me he felt underused. Now I assign the hard work first and pair on it instead of taking it. Our sprint completion went up and he shipped his first major feature last month."
Notice what these have in common. Each weakness is a real cost, none of them is the core skill of the job, and every fix is something the interviewer could check with a reference.
Strength examples tied to the job posting
The strength question is easier, so people waste it. "I'm a hard worker and a team player" tells the interviewer nothing. Take the strength from the posting itself.
- Read the posting and mark the qualities it repeats or lists first.
- Pick the one you can prove best, not the one you like best.
- Back it with one specific result, ideally with a number. A short story in the STAR format works well here.
- Close by connecting it to something the role needs.
If the posting is vague, the US Bureau of Labor Statistics publishes an "Important Qualities" list for each occupation in its Occupational Outlook Handbook. It is a neutral starting point:
| Occupation | Important qualities listed by BLS |
|---|---|
| Software developers | Analytical, communication, creativity, detail oriented, interpersonal, problem solving |
| Data scientists | Analytical, computer, communication, logical thinking, math, problem solving |
| Registered nurses | Critical thinking, communication, compassion, detail oriented, emotional stability, organizational, physical stamina |
| Accountants and auditors | Analytical and critical thinking, communication, detail oriented, math, organizational |
| Project management specialists | Analytical, communication, critical thinking, interpersonal, organizational, problem solving, time management |
| Customer service representatives | Communication, customer service, interpersonal, listening, patience, problem solving |
Employers hiring new graduates look for the same handful. NACE's Job Outlook 2026 Spring Update, a survey of 185 employers, found 85% look for teamwork on the resume, with problem solving and communication also among the top priorities.
Sample strength answers, written for this post:
Project coordinator: organization
"My strength is keeping a lot of moving parts on schedule. At my current job I took over a vendor rollout that was three weeks behind, rebuilt the plan around the two suppliers who were actually blocking us, and we went live on the original date. Your posting mentions coordinating across five regional teams, and that's the kind of work I'm best at."
Software developer: debugging
"I'm good at finding the cause of problems other people have given up on. Last year our checkout service had an intermittent failure that had been open for two months. I added logging around the payment calls, traced it to a timeout setting, and the error rate went to zero after the fix. I'd expect that to be useful on a platform team like this one."
When the interviewer asks for both at once, give the strength first, then the weakness, and finish on the fix. Ending on the fix leaves them with what you are doing about the gap, not the gap itself.
New grads and career changers
The formula is the same. The evidence comes from different places.
New graduates draw strengths from coursework, projects, internships and part-time jobs, and weaknesses from the gap between school and work.
Sample, new graduate, weakness: "I don't have much experience with deadlines set by someone else. In school I could plan my own time, and in my internship I underestimated how long code review would take, so my first project ran a week over. Now I build review time into every estimate, and I ask my lead to check my plan in the first week."
Sample, new graduate, strength: "I explain technical work clearly. In my capstone project I was the one who presented our results to the sponsor company, and they adopted our recommendation. I've also tutored statistics for two years, so I'm used to explaining the same idea three different ways."
Career changers have a natural weakness: the new field. Say it before the interviewer does, and pair it with the transferable strength that makes you worth the risk. Our guide to tell me about yourself covers how to frame the switch in your opening answer.
Sample, teacher moving into instructional design, weakness: "My weakness is the authoring tools. I've built lessons for ten years, but I'm newer to the software most teams use. I've built three sample modules in the last two months and put them in my portfolio, and I'd expect to need a few weeks to get fully fast."
Answers that backfire
| Answer | Why it hurts | Instead |
|---|---|---|
| "I'm a perfectionist" or "I work too hard" | Raters see through it (research below) | A real habit with a real cost |
| "I don't have any weaknesses" | Fails the only thing the question tests | Any honest, non-core gap |
| A weakness that is the job's core skill | Answers the question "should we hire you?" with no | Check the posting's required list first |
| A list of three or four weaknesses | Sounds unprepared and gives them more to doubt | One, with a fix |
| A fix with no evidence | "I'm working on it" is a promise, not a result | A habit, a tool, a course, a number |
| Blaming a manager or team | Turns a self-awareness question into a complaint | Keep it about your own behavior |
| Personal or health details | Not what the question is about, and you are not required to share | A work habit or skill gap |
| Five adjectives for a strength | Nothing sticks | One strength and one result |
The disguised strength is the most common mistake, and it is the one with evidence behind it. In study 1b of the Harvard Business School working paper by Ovul Sezer, Francesca Gino and Michael Norton (April 2015, later published in the Journal of Personality and Social Psychology), 122 university students wrote how they would answer "what is your weakness?" in a job interview. Coders classed 77% of the answers as humblebrags and 23% as real weaknesses. The most common disguises were being a perfectionist (32.8%), working too hard (24.6%) and being too nice and helpful (14.8%). Asked why they answered that way, 66% of the humblebraggers gave a strategic reason, such as wanting to get hired.
It did not work. A separate pair of raters, who did not know the hypothesis, scored each answer on "To what extent would you want to hire this person?" from 1 to 7. Humblebraggers averaged 3.03 and those who named a real weakness averaged 3.93. The raters were research assistants, not hiring managers, so treat the finding as a strong hint rather than a hiring statistic. It matches what Harvard's Working Knowledge summary reported in 2015: the raters "were much more interested in hiring the honest answerers than the humblebraggers."
If perfectionism really is your weakness, you can still use it. Drop the word and describe the behavior and its cost instead, as in the software engineer sample above. "I polish code longer than the task needs, and a release went out late" is a real weakness. "I'm a perfectionist" is a brag.
Practice and prep
Write both answers out, read them aloud, and prepare for the two natural follow-ups: "Can you give me another example?" and "How would we know it's fixed?" Our guide on how to prepare for an interview builds a full prep sheet from the posting, and these two answers belong on it.
The posting is also where your resume should come from. ApplyEze writes a resume for every posting it applies to, and a cover letter when the form asks for one. The resume mirrors that posting's language and brings its named skills and tools onto your skills line, even when your own record does not list them. There is no step to remove one before a live run, so use a dry run to see what it writes, and be ready to discuss anything on the page, because the strength question is where an interviewer will probe it.