Why interviewers ask both at once, the matched pair method, how many to prepare, strengths by job and safe weaknesses, five sample answers, and the other ways the question is asked.
Name one or two strengths the job needs, each with a short proof. Then name one real weakness that is not central to the job, say what you are doing about it, and give a recent sign it is working. End on that evidence, or on a line that links back to the job. The whole answer should run about a minute and a half.
This post is about answering both halves together, which is how the question is usually asked. For a deep look at the weakness half alone, read what is your weakness. To draft the strengths half from your resume, use the free strengths answer generator.
Key takeaways
Asked alone, "what is your strength?" invites a sales pitch and "what is your weakness?" invites a dodge. Asked together, the question checks something else: whether you see yourself clearly. An interviewer listens for three things:
A good combined answer sounds like someone who has thought about their own work. That is why it often comes early, right after "tell me about yourself".
The easiest way to make the two halves sound honest is to take one trait and show both sides of it. Most strengths have a shadow:
| Strength | Its shadow (the weakness) | The fix you can describe |
|---|---|---|
| Careful with details | Slow to call a task finished | A "done" checklist agreed with the manager |
| Direct, clear communicator | Can sound blunt in writing | Rereading messages before sending, opening with context |
| Takes ownership | Slow to hand work to others | Delegating one task a week and checking in at set times |
| Fast worker | Underestimates how long tasks take | Adding a buffer to every estimate and tracking real times |
| Calm with customers | Avoids difficult conversations with coworkers | Raising issues in the weekly one-to-one instead of waiting |
Why it works: the interviewer can see that the weakness is real (it follows from how you work) and that you manage it. It also keeps the answer short, because the two halves share one story.
You do not have to use a matched pair. If your real weakness has nothing to do with your strength, that is fine. Just keep the same order: strength with proof, weakness with fix, evidence.
The career team at the University of Illinois Chicago's business school advises preparing three strengths, "especially those most relevant to the role", and to "be ready with at least 2 weaknesses". It also says "I don't know" or "I can't think of any" are not acceptable answers, and that you should explain how you are working to improve.
In the interview itself, say fewer than you prepared: usually one or two strengths and one weakness. Keep the rest for the follow-up "Can you give me another one?".
For proof, use the same idea as a behavioral answer. MIT's career office suggests "I" statements and results you can measure. "I closed the month-end two days early for three months" is proof. "I am very efficient" is not.
| Job | Strengths worth naming |
|---|---|
| Customer service | Patience, clear explanations, staying calm with upset customers |
| Accounting and finance | Accuracy, meeting deadlines, spotting errors |
| Software and IT | Debugging, learning new tools quickly, writing clear documentation |
| Sales | Building trust, following up, handling rejection |
| Healthcare | Care for patients, following procedures, calm under pressure |
| Team lead or manager | Coaching, setting priorities, giving feedback |
Pick from the job post, not from this table. The table just shows the kind of thing to look for.
A safe weakness is real but not central to the job: public speaking for a back-office analyst, a spreadsheet skill for a designer, delegating for someone who does not manage yet. A risky weakness is a core skill of the job: accuracy for an accountant, punctuality for a shift worker. The weakness guide has five full templates and the fake answers to avoid. The greatest weakness answer generator drafts one from your situation.
These are examples written for this post. Use the shape and change every detail to your own.
"My main strength is writing for different audiences. For my internship I wrote the weekly newsletter for a nonprofit and the open rate went up over the summer. My weakness is that I find it hard to speak up in big meetings. I've started preparing one point before each meeting and saying it in the first ten minutes. Last month that is how my idea for a student campaign got picked up."
A fresh graduate can use internships, school projects and volunteering for proof.
"My strength is accuracy. In two years of month-end closing I've had no reports sent back for errors. The other side of that is I used to check things too many times and finish late. Now I agree a review checklist with my manager, and once it's done, I submit. My last three closings went in a day early."
One trait, two sides, and a result at the end.
"I'm strong at debugging. I like taking the bug nobody wants and finding the cause, and last quarter I fixed a memory leak that had crashed our app for months. A weakness is estimating. I used to say two days and take four. Now I break tasks into small steps and add a buffer, and my estimates in the last sprint were close to the real time."
Technical proof plus a weakness that every developer will recognize.
"My strength is staying calm with upset customers. I handle escalated calls on my team and most end with the customer satisfied. A weakness is that I avoid hard conversations with coworkers. When a teammate kept leaving tickets half done, I waited too long to say anything. Since then I raise issues at our weekly check-in, and that problem was fixed in a week."
The weakness is real but not about customers, the core of the job.
"My strength is coaching. Two of the people I trained have been promoted. My weakness is delegating: I used to keep the hard tasks for myself. Now I hand one important task a week to someone on the team and check in at set times. Our team finished the last project on time without me working late."
For a manager role, delegation is a common and honest weakness, as long as the fix is real.
Write your strength with proof, your weakness with fix and evidence, then say it aloud with a timer. If it runs past two minutes, cut the strength story, not the fix. Then try the free AI mock interview: it reads questions for your job aloud, asks follow-ups and reports on pace, filler words and structure. It reads its questions in English, so it is good practice for an interview in English.
In a live video interview on Zoom, Teams or Google Meet, ClapAssist listens on your own computer and shows a suggested answer from your resume and the job post, so your proof is in front of you when the question comes. It understands many languages, and the "Answer in" setting chooses the language of the answer. Some employers do not allow AI help in interviews or tests, so read the rules first.
Next questions to prepare: tell me about yourself, why should we hire you and how to answer interview questions.
Outside pages that back the advice above, opened and checked on the date shown.
One or two strengths the job needs, each with a short proof, then one real weakness that is not central to the job, what you are doing about it, and a recent sign it is working.
Strengths first, then the weakness with its fix. End on the evidence that the fix is working, not on the problem.
Prepare about three strengths and at least two weaknesses, then use one or two strengths and one weakness in the answer. Keep the rest for follow-ups.
Usually not. It sounds like a strength in disguise. Name a specific habit instead, such as slow to call a task finished, and the method you use to fix it.
About a minute and a half, with both halves close in length.
ClapAssist shows answers from your resume on Zoom, Teams and Meet. 10 free minutes, no card.