How to answer "What are your strengths and weaknesses?"

"What are your strengths and weaknesses?" is one of the most predictable interview questions, which is exactly why weak answers stand out. Interviewers have heard "I'm a perfectionist" thousands of times. What they are really testing is self-awareness: do you know what you are good at, can you see where you need to improve, and are you doing something about it?

Choosing your strengths

Good strengths have three qualities:

• They matter for this role. Read the job description and pick strengths that match what the job needs most.
• They are specific. "Hardworking" is vague. "I'm good at debugging problems in code I didn't write" is specific and memorable.
• You can prove them. Every strength you mention should come with a short example.

Some examples by role:

• Developer: picking up unfamiliar codebases quickly, writing readable code, methodical debugging.
• Data analyst: attention to detail with data, turning numbers into a clear story for non-technical people.
• Technical support: staying calm with frustrated customers, explaining technical issues simply.
• Tester: thinking about edge cases others miss, writing clear bug reports.
• Team lead: unblocking people, giving honest feedback, planning realistic timelines.

How to answer the strengths half

Name the strength, prove it with a short story, and connect it to the job. For example:

"One of my strengths is learning new tools quickly. In my internship, the team used Django, which I'd never worked with. I spent the first week going through the official tutorial in the evenings and reading the team's existing code, and by the second week I'd shipped my first feature to production. I know your team uses a stack I haven't fully worked with yet, and I'm confident I'd get productive fast."

Choosing a weakness

This is the half that worries most candidates. A good weakness is:

• Real. Interviewers see through fake weaknesses like "I work too hard" or "I care too much". They make you sound either unaware or evasive.
• Not central to the job. For a client-facing role, "I find it hard to talk to people" is a deal-breaker. For a backend developer, "I'm still building confidence presenting to large groups" is not.
• Something you are working on. The improvement plan is the most important part of the answer.

Weaknesses that work, with what you are doing about them

• Public speaking: volunteering to present in team meetings, joining a speaking club.
• Saying yes to too many things: now checking current workload and agreeing priorities with your manager before accepting new tasks.
• Over-researching before starting: setting a time limit for research, then building a first version and improving it.
• Limited experience with a specific tool the job uses: taking a course and building a small project with it.
• Delegating (for experienced candidates): handing over smaller tasks with clear instructions and reviewing rather than redoing.
• Giving direct feedback (for leads): using regular one-to-ones and focusing on specific behaviour rather than general comments.

Sample answers

Fresher

"My strength is persistence with difficult problems. In my final year project, our face-recognition model performed poorly in low light. I spent two weeks testing different preprocessing approaches until accuracy improved from 71% to 88% on our test set. My weakness is that I've tended to take on too much. During college, I joined three clubs and a hackathon team in the same semester, and my coursework suffered. Now I keep a simple weekly plan and check it before agreeing to anything new. It's helped me say no when I need to."

Experienced professional

"I'd say my main strength is breaking large, vague problems into clear steps. When our team had to migrate a legacy reporting system, I wrote the migration plan that let us move one report at a time without downtime. As for a weakness, I've found delegation hard. I used to take on difficult tasks myself because it felt faster. Last year, my manager pointed out that this was slowing the team's growth, so I started pairing juniors on those tasks and reviewing their work instead. It took longer at first, but two of them now handle that work on their own."

When they ask for three of each

Some interviewers ask for three strengths and three weaknesses. Prepare a short list in advance, and keep each one brief: a sentence of description and a sentence of evidence or action. You do not need a full story for all six.

Mistakes to avoid

• Clichés. "Perfectionist", "workaholic" and "too honest" make interviewers stop listening.
• A weakness with no plan. Naming a weakness and stopping there sounds like a confession, not self-awareness.
• Contradicting your resume. If your resume highlights team leadership, do not name "working in teams" as a weakness.
• Oversharing. Keep it professional. Personal struggles, health matters and family issues are not what the question is about.

This question often sits alongside "Why should we hire you?" in the HR round. Prepare them together using our guide to answering "Why should we hire you?", and review the other common HR interview questions.