What Are Your Strengths and Weaknesses? How to Answer Both Halves, With 10 Sample Answers

When an interviewer asks "What are your strengths and weaknesses?", give one or two strengths that match the job description and back each with a short, specific example. Then name a real weakness that is not central to the role, and describe the concrete steps you are already taking to improve it. Aim for about 90 seconds in total.

That is the answer in one paragraph. The rest of this guide explains why that structure works and how to build your own version from the job posting. It also includes ten sample answers for different roles and career stages, plus the weakness answers that sound safe but tend to cost candidates the most.

What the interviewer is actually assessing

This question looks like small talk, but it's an evaluation with three separate things being scored. Career guides from Indeed, Glassdoor and graduate recruiters describe the same core: self-awareness, fit to the role, and evidence that you improve over time. Knowing which one you're being judged on in each half changes what you say.

1. 1Self-awareness. Can you describe yourself the way a fair colleague would? Candidates who can't name a real weakness, or who list strengths that don't match their record, come across as either unprepared or lacking insight.
2. 2Fit to the role. The strengths half is really asking which of your abilities matter for this job. A strength the role never uses may be true, but it doesn't help your case.
3. 3Evidence of growth. The weakness half is less about the weakness itself than what you do about it. Interviewers want to hear about a specific action with a result, not an intention.
4. 4Composure and honesty. This is a secondary signal. How calmly you discuss a flaw hints at how you'll handle feedback in a performance review.

There's also something the interviewer isn't doing: looking for a reason to disqualify you over a minor flaw. Most interviewers expect you to have weaknesses. Evasion or a scripted cliché will hurt you. A real, well-managed limitation usually won't.

Part one: choosing and proving your strengths

A strong answer about strengths is chosen for the job, not taken from a generic list. Start with the job posting, find what the role will need from you most often, and match two of your real strengths to those needs. Then prove each one with a single concrete example rather than piling on adjectives.

Map your strengths to the job description

1. 1Print or copy the job posting and underline every verb in the responsibilities section, such as manage, analyze, present, resolve or build.
2. 2Group those verbs into three or four themes. A customer success posting might group into relationship management, problem-solving under time pressure, and reporting.
3. 3For each theme, write down one moment from your work, school or volunteering where you clearly did it well. Include a number, a named outcome, or feedback someone gave you.
4. 4Keep the two themes where your evidence is strongest and most recent. Those are your strengths for this interview. They may be different for the next one.

Prove each strength in two or three sentences

The proof shouldn't turn into a full story. The strengths question is a quick overview, so aim for one sentence naming the strength, one describing what you did, and one giving the result. If the interviewer wants more detail they'll ask, and then you can expand into a full situation-task-action-result story. Our guide to the STAR method covers how to build a bank of those longer stories so you're not improvising.

• Weak: "I'm a great communicator, very organized and a real team player." That's three claims with no evidence, and every other candidate says the same.
• Strong: "I'm good at turning messy data into a decision someone can act on. Last quarter I rebuilt our churn report so the account team could see at-risk customers a month earlier, and they saved four of the six accounts we flagged."

Also be careful with strengths that sound like personality traits ("I'm passionate," "I'm a people person"). They're hard to prove and easy to doubt. Turn each one into a behavior that can be seen: instead of "passionate," say "I read every support ticket about the feature I own, every week."

Part two: choosing a weakness that is real but not disqualifying

The weakness half is where most candidates lose ground, usually by being too safe rather than too honest. What you want is a genuine limitation that someone who has worked with you would recognize, that isn't central to the job you want, and that you're already improving in a way you can describe precisely.

Run every candidate weakness through three filters

1. 1Is it real? If a former manager would read your answer and be surprised, choose something else. Made-up weaknesses sound made up.
2. 2Is it survivable in this role? Read the job posting again. If the weakness is one of the top three things the job requires, it's disqualifying no matter how well you frame it. Being uncomfortable with public speaking is fine for a backend engineer and fatal for a sales trainer.
3. 3Can you show movement? You need at least one concrete step already taken, such as a course, a tool, a changed habit or feedback you asked for, and ideally a sign that it's working.

The four-beat structure

Once you've chosen the weakness, deliver it in four short beats. Name it plainly without minimizing it. Give a brief example of how it showed up so it's clear you're not being abstract. Describe the specific steps you took. Finish with where things stand now. Keep the whole answer to three or four sentences, and resist apologizing or explaining too much.

• Name it: "I've tended to hold on to work too long before asking for input."
• Show it: "On a launch last year that meant I found a scoping problem two days before the deadline instead of two weeks."
• Fix it: "Since then I share a rough draft at about the 30% point on anything longer than a week, and I put that checkpoint on my calendar when the project starts."
• Status: "My last two projects both had their scope issues caught in the first review."

Notice the tone: calm, specific, in the past tense for the problem and the present tense for the fix. You're describing a system you already run, not promising to become a better person.

Ten sample answers across roles and levels

Use these as models of structure, not scripts. Each one follows the same logic: strengths chosen for the role with brief proof, and a weakness that passes the three filters. The short note after each explains why it works, so you can apply the same reasoning to your own experience and the posting in front of you.

Entry-level and new graduate

1. Entry-level marketing coordinator. "My strongest skill is writing fast without losing accuracy. I ran the student newspaper's social accounts and published daily for two years with only one correction. I'm also reliable with deadlines, and I never missed a print cutoff. My weakness is that I haven't worked with paid advertising budgets yet. I've finished Google's free Skillshop courses on Search ads and built a practice campaign structure so the terms aren't new to me, but I know real spend is different, and it's something I'd want to learn from the team."

Why it works: the weakness is an honest experience gap that's normal at entry level, and the steps already taken show initiative without pretending to expertise.

2. New graduate analyst. "I'm strongest at structured problem-solving. For my capstone I cut a 40-variable dataset down to the five that explained most of the variation and presented it to faculty in ten minutes. My weakness has been speaking up in large groups. I'd have the analysis ready but wait for someone else to raise it. This year I set myself a rule to make at least one point in the first fifteen minutes of every seminar, and I volunteered to present our group's findings twice."

Why it works: the weakness is common and fixable, and the fix is a measurable habit rather than a vague intention.

Career changer

3. Teacher moving into instructional design. "Designing learning is what I've done for eight years. I rewrote our district's ninth-grade algebra unit, and the share of students passing the end-of-unit assessment went up the next year. I'm also good at explaining complex material to people who don't want to learn it. My gap is authoring tools. I'd been building everything in slides, so I've spent the last three months learning Articulate Storyline and have two sample modules in my portfolio."

Why it works: it turns the career change into the strength, and names the obvious tool gap before the interviewer can, along with portfolio evidence that the gap is closing.

4. Military veteran moving into operations management. "I'm strong at logistics under uncertainty. I coordinated equipment movement for a unit of around 150 people across three sites. I also train people well, because I had to bring new arrivals up to speed in weeks. My weakness is that I'm used to a very direct communication style, which doesn't always land in civilian teams. I've asked two colleagues in my current role to tell me when I come across as abrupt, and I now start requests with the reason behind them, not just the instruction."

Why it works: the weakness is real and relevant to the transition, and asking colleagues for feedback shows coachability.

Manager and senior leader

5. First-time people manager. "My strength is developing people. Two of the three analysts I mentored informally were promoted within 18 months. I'm also good at setting priorities when there's too much work. My weakness has been delegating the interesting work. I kept the complex analyses for myself because they were faster for me to do. I now keep a list of stretch assignments and hand each one to someone on the team, then review their work rather than redoing it."

Why it works: holding on to hard work is a real and well-known mistake for new managers, and the answer shows the candidate understands the shift from doing the work to building the team.

6. Director-level hire. "I'm strongest at turning strategy into an operating plan people can follow. I took our regional expansion from a board slide to a quarter-by-quarter hiring and budget plan that we delivered within 5% of forecast. My weakness is patience with slow consensus. I've learned that moving before key stakeholders are bought in costs more time later, so for any cross-functional decision I now map who needs to agree and meet them one on one before the group meeting."

Why it works: at senior levels interviewers expect an answer about judgment and style rather than a missing skill, and this one describes a clear process that's already in place.

Technical roles

7. Software engineer. "I'm strongest at debugging production issues. I led the fix on our worst outage last year and wrote the postmortem our team now uses as a template. I also write clear documentation. My weakness is estimating. I used to give optimistic numbers and then work late to meet them. Now I break every task into pieces under a day and add a buffer for integration work, and I compare my estimates with actual time in a spreadsheet. My estimates have gotten noticeably closer since I started."

Why it works: estimation is a real but non-disqualifying weakness for engineers, and tracking estimates against actual time is concrete evidence.

8. Data scientist. "My strength is building models that people actually use, not just accurate ones. I cut a forecasting model from 30 features to eight so the finance team could understand it and trust it. My weakness is data visualization design. My charts used to be correct but cluttered. I worked through a data visualization book, and now I have a designer on the team review any chart going to executives before it's sent."

Why it works: it's a supporting skill rather than the core one, and the fix combines personal learning with a review step.

Client-facing roles

9. Account manager. "I'm good at keeping difficult clients. I took over our lowest-rated account and brought it to renewal by setting up a call every two weeks and a shared issue tracker. I also negotiate calmly. My weakness is that I've said yes to too many small client requests, which added up to scope creep. I now log every request against the contract and give the client a weekly summary, which makes trade-off conversations a lot easier."

Why it works: it's a weakness that comes from caring about clients, which is believable in this role, and it has an operational fix instead of a promise to "push back more."

10. Sales development representative. "My strength is persistence with structure. I built a six-touch sequence that booked more meetings than any other rep on my team for two consecutive quarters. My weakness was handing off meetings with too little context, and a couple of account executives told me so directly. I built a four-field handoff note and now I send it with every booked meeting."

Why it works: the feedback came from colleagues, so it's clearly real, and the fix is a small, repeatable system.

Weakness answers that backfire

Some weakness answers feel safe to candidates but sound evasive to interviewers who have heard them hundreds of times. Others are honest but aimed at the wrong target. The patterns below come up again and again in hiring advice. Each one fails for a specific reason, and each has a straightforward fix.

• "I'm a perfectionist." This is the classic cliché. It reads as a disguised strength, so the interviewer learns nothing except that you prepared a dodge. If perfectionism is genuinely your issue, describe its actual cost, such as missed deadlines or over-editing, and what you changed.
• "I work too hard" or "I care too much." Same problem, with an added hint that you'll burn out or struggle with boundaries.
• A weakness central to the role. An accountant who is "not detail-oriented" or a recruiter who "doesn't enjoy talking to strangers" has handed over the reason to reject them. Check your weakness against the posting before the interview.
• "I don't really have one." This fails the self-awareness test immediately.
• A personal or protected-characteristic disclosure. You're not obliged to discuss health, family plans or similar topics, and doing so moves the conversation away from job performance.
• A weakness with no action attached. "I'm disorganized" with nothing after it isn't honest, it's unfinished.
• A long confession. Two minutes on one flaw makes it look bigger than it is. Keep it to four sentences.

Handling follow-ups: "Give me another weakness"

Experienced interviewers often push past a polished first answer to see what you say when you haven't rehearsed. The fix is simple: prepare two weaknesses, not one, and a strength you can prove at more length. Follow-ups test consistency and composure more than content, so a calm, specific second answer matters more than a clever one.

1. 1"Give me another weakness." Use your second prepared weakness, ideally from a different category. If your first was a skill gap, make the second a work-style habit, or the reverse. Don't downgrade to a cliché just because you've run out.
2. 2"How would your last manager describe your weakness?" This checks whether your answer matches outside feedback. Quote the actual feedback if you can: "In my last review, my manager said I…" Then explain your fix.
3. 3"Tell me about a time that weakness caused a problem." Now you need a short STAR-style story. Own the outcome, keep blame out of it, and finish on what you changed.
4. 4"What are you doing about it right now?" If your fix is a course you finished two years ago, update it. Interviewers want to hear about a current habit.
5. 5"What would your colleagues say is your greatest strength?" Give a strength that matches the one you already offered, with a different piece of evidence. Consistency across answers builds credibility.

If the follow-up comes up in a later round, treat it as a sign the panel is testing depth rather than repeating itself. Our guide to second interview questions covers how questions change in round two and how to avoid giving the same answers the first interviewer already wrote down.

Where this question fits in the interview

Strengths and weaknesses rarely comes up on its own. It usually appears early, right after the opening, alongside a few other questions that together shape the interviewer's first impression. Preparing them as a set, with consistent themes, is more efficient than preparing each answer separately, and it stops you contradicting yourself.

• Before it: the opener. The strengths you choose should echo the story you told in your introduction. Our guide on how to introduce yourself in an interview scripts those first 90 seconds, so the two answers reinforce each other.
• Beside it: motivation questions. Your strengths should also explain why the company should want you, while your answer to "Why do you want to work here?" explains why you want them.
• After it: trajectory questions. The weakness you're working on is a natural bridge to "Where do you see yourself in 5 years?" A skill you're building now can reasonably be part of that plan.
• At the end: your chance to turn it around. One of the most useful questions to ask at the end of an interview is what separates people who do well in this role from people who struggle. The answer tells you whether your stated weakness matters here.

A 30-minute prep worksheet

You don't need to memorize anything word for word, and memorized answers usually sound it. Aim for a set of bullet points you know well enough to say naturally in different ways. The process below takes about half an hour per job and gives you material for this question and several of its follow-ups.

1. 1Pull the three or four main themes from the job posting (10 minutes).
2. 2Write one piece of proof for each theme, with a number, an outcome or quoted feedback, and keep the best two (8 minutes).
3. 3List four genuine weaknesses, cross out any that are central to the role, and keep two (5 minutes).
4. 4For each weakness you keep, write down the most recent concrete action and its current result (5 minutes).
5. 5Say the full answer out loud once, timed. If it runs over two minutes, cut the strengths evidence first (2 minutes).

Do this again for each application. The weakness may stay the same across interviews, but the strengths should change with the job. That tailoring is what separates a prepared answer from a generic one, and interviewers notice the difference quickly.