Guide

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

Q: Choose the right strength

Pick one or two strengths, not five. A good choice is: Relevant. It matters for this job. Attention to detail matters for an accountant; calm under pressure matters in customer support. Specific. "Breaking a big task into small steps" is more believable than "good at everything I do". Provable. You can give a real example from study, work or an activity.

Q: A simple structure: claim, example, link

Claim. Name the strength in a sentence. Example. One short story that shows it. Two or three sentences is enough; save the full STAR method for when they ask for more. Link. Say how it would help in this role.

Q: Choose the right weakness

This is the half people dread. A good weakness is: Real. Something you've genuinely noticed in yourself, or that someone has told you. Not central to the job. A developer saying they struggle with logic is a problem. A developer saying they used to avoid speaking in large meetings is not. Being worked on. You can describe what you've done about it, and some progress. Common honest choices include: finding it hard to say no to extra work, getting too deep into detail on small tasks, being uncomfortable with public speaking, not asking for help early enough, or being impatient with slow decisions.

Q: A simple structure: weakness, effect, action, progress

Weakness. Name it plainly, in one sentence. Effect. Briefly, how it has affected your work. Action. What you've done about it. Progress. Where you are now. Be honest; "better, but still working on it" is fine.

Interviewers ask about strengths and weaknesses to see how well you know yourself. Here's how to choose a strength worth naming, a weakness worth admitting, and how to talk about both with examples.

Updated 2026-10-16 · by Kalyan Kaushik K N

What the interviewer wants to learn

This question comes in many forms: "What are your strengths and weaknesses?", "What are your greatest strengths?", "What's a weakness you're working on?" or "What would your manager say you could improve?" Whatever the wording, the interviewer is looking for self-awareness.

People who know what they're good at can be placed where they'll do well. People who can name a real weakness, and show they're working on it, are easier to manage and more likely to improve. An answer that's honest and specific says more about you than one that tries to sound perfect.

There's a short version of this advice in our list of common HR interview questions. This guide covers both halves in detail, with full examples.

Answering the strengths part

Choose the right strength

Pick one or two strengths, not five. A good choice is:

Relevant. It matters for this job. Attention to detail matters for an accountant; calm under pressure matters in customer support.
Specific. "Breaking a big task into small steps" is more believable than "good at everything I do".
Provable. You can give a real example from study, work or an activity.

A simple structure: claim, example, link

Claim. Name the strength in a sentence.
Example. One short story that shows it. Two or three sentences is enough; save the full STAR method for when they ask for more.
Link. Say how it would help in this role.

Example strength answer: fresher

One of my strengths is staying organised when several things are due at once. In my final year, I had my project, two internship interviews and my exams in the same month. I made a weekly plan every Sunday, broke the project into small tasks with dates, and checked them off each evening. I finished the project a few days early and didn't fall behind on revision. In a trainee role like this one, where I'll be learning several things at the same time, I think that habit will help me keep up.

Example strength answer: experienced

I'm good at explaining technical problems to people who aren't technical. In my current role, I'm usually the one who joins calls with clients when something has gone wrong, because I can tell them what happened, what we're doing and when it'll be fixed without jargon. Our account managers now bring me into those calls early. This role works closely with customers, so I'd expect to use that a lot.

Answering the weaknesses part

Choose the right weakness

This is the half people dread. A good weakness is:

Real. Something you've genuinely noticed in yourself, or that someone has told you.
Not central to the job. A developer saying they struggle with logic is a problem. A developer saying they used to avoid speaking in large meetings is not.
Being worked on. You can describe what you've done about it, and some progress.

Common honest choices include: finding it hard to say no to extra work, getting too deep into detail on small tasks, being uncomfortable with public speaking, not asking for help early enough, or being impatient with slow decisions.

A simple structure: weakness, effect, action, progress

Weakness. Name it plainly, in one sentence.
Effect. Briefly, how it has affected your work.
Action. What you've done about it.
Progress. Where you are now. Be honest; "better, but still working on it" is fine.

Example weakness answer: fresher

I used to be quite nervous speaking in front of groups. In my second year I avoided presenting in team projects and let others do it, which meant I didn't get credit for work I'd done. So I joined the college debating society and made myself speak at least once at every meeting. I'm still not the most relaxed speaker, but I presented our final-year project to the panel myself and handled the questions well. I'm still practising, because I know it'll matter in a client-facing job.

Example weakness answer: experienced

I've had a habit of taking on too much myself instead of delegating. When I first became a team lead, I kept the hardest tasks because it felt quicker, and a couple of times I became the bottleneck. My manager pointed it out, and since then I've made a point of handing over one meaningful task each sprint and reviewing it rather than doing it. The team has grown in confidence, and I have more time for planning. I still catch myself wanting to do it all, but I notice it sooner now.

Answers to avoid

The disguised strength. "I'm a perfectionist" or "I work too hard" are so common that interviewers hear them as a way of dodging the question.
"I don't have any weaknesses." Nobody believes it, and it suggests you either lack self-awareness or aren't being honest.
A weakness that rules you out. Don't name something the job depends on, such as poor attention to detail for an auditor.
Something too personal. Keep it to work and study. This isn't the place for private matters.
A weakness with no action. Naming a weakness and stopping there sounds like you've given up on it. Always say what you're doing about it.
A strength with no example. "I'm a team player" on its own is a claim, not an answer.
A long list. One strength and one weakness, done well, beats several rushed ones.

How it should sound

Interviewers notice how you say this as much as what you say. Many candidates speed up and look away when they reach the weakness. Keep the same pace and eye contact for both halves, and avoid hedges like "I guess maybe" that make a prepared answer sound unsure. Our guide on reducing filler words can help with this.

Practise it out loud

Prepare two strengths and two weaknesses, so you have a spare for a follow-up question. Write each as four or five bullet points, then practise saying them without notes.

In Kayavak, choose Interview mode and the Common interview questions set, which includes "What are your greatest strengths?" and "What is a weakness you are working on?". Your report highlights filler words and hedges in your transcript and shows your pace, answer length, eye contact and posture. Retake the weaker answer and compare the two. More on the report is on the interview practice page, and you can download Kayavak for free.