Last updated · Guides
"What are your strengths and weaknesses?" is one of the most predictable interview questions, and yet it catches many candidates off guard. Strengths feel like boasting, and weaknesses feel like a trap. So people fall back on safe, rehearsed lines such as "I am a perfectionist" or "I get too involved in my work". Interviewers have heard those many times, and they rarely help. The question is really about self-awareness. The interviewer wants to know whether you understand what you do well, whether you can be honest about what you do not, and whether you take steps to improve. This guide shows you how to choose your strengths, how to pick a weakness that is real but not damaging, and how to structure both answers with examples.
From the employer's side, the question is practical. A manager wants to know where you will add value quickly and where you may need support. Your answer also shows:
Sometimes the question comes as one ("What are your strengths and weaknesses?") and sometimes as two separate questions, often with "greatest" attached. The approach is the same either way.
List the skills and qualities the role mentions or clearly needs. A customer support role needs patience, clear writing and the ability to stay calm with upset customers. An accounts role needs accuracy and a comfort with deadlines. A developer role needs problem-solving and the ability to learn new tools. Your strengths should come from this list, not from a generic list of positive words.
For each strength, find one specific example from work, internships, college or projects. The example turns a claim into evidence. A simple pattern is: strength, situation, what you did, result.
You do not need to sound modest or grand. State the strength, give the example and stop.
Organisation (operations or admin role): "One of my strengths is organising work so nothing falls through the cracks. In my current role I coordinate travel and logistics for field staff across three states. I set up a shared tracker with a daily status column, and since then we have had far fewer last-minute booking problems."
Explaining technical things simply (developer or analyst role): "I am good at explaining technical issues to people who are not technical. When our team had a recurring data mismatch, I wrote a one-page note with screenshots for the operations team showing exactly where the numbers came from. They started catching the issue themselves before it reached us."
Attention to detail (accounts role): "I am careful with numbers. During my internship I did monthly bank reconciliations, and I found a duplicate vendor payment that had been missed in an earlier month. I now use a simple checklist for every reconciliation."
Learning quickly (fresher, any role): "I pick up new tools quickly. In my final-year project we had to use a framework none of us had worked with. I spent the first week building small test apps and then wrote a short setup guide for my teammates, which saved the group a lot of time."
This is the harder half. A good weakness answer has three parts:
| Weakness | Suits candidates for | How to show improvement |
|---|---|---|
| Public speaking | Technical, analytical and back-office roles | Volunteering to present in team meetings, a speaking course, practising with smaller groups first |
| Difficulty delegating | Individual contributors moving towards team lead roles | Handing off defined tasks with clear checklists, weekly check-ins instead of redoing work |
| Saying yes to too many requests | Most roles | Using a task list to show priorities, agreeing timelines before accepting new work |
| Limited experience with a specific tool | Freshers and career switchers | A course in progress, a small project using the tool |
| Over-preparing and spending too long on first drafts | Writing, design, analysis roles | Time-boxing drafts, sharing early versions for feedback |
| Not asking for help early enough | Freshers and new joiners | A personal rule to raise a blocker after a fixed amount of time stuck |
Fresher, public speaking: "My weakness is speaking in front of large groups. In my second year I froze during a seminar presentation even though I knew the topic well. Since then I have taken every chance to present in smaller settings, like lab reviews and our coding club, and I joined a public speaking group on campus. I am much more comfortable now, though I still prepare more than most people for big presentations."
Experienced, delegating: "I have found it hard to delegate. When I became the senior person on my team, I kept taking the complex tickets myself because it felt faster. That left the juniors without growth and left me overloaded. Over the last few months I have started pairing with them on one complex ticket a week and then handing over the next similar one. It takes more time up front, but the team is now handling work that used to wait for me."
Any level, taking on too much: "I tend to say yes to every request, and earlier in my career that meant a few deadlines slipped. Now I keep a visible task list, and when someone asks for something new I share what is already on my plate and ask which one should move. My manager and I agreed on this approach, and it has made my commitments more reliable."
Freshers often worry that they have no work examples. You do not need them. College projects, internships, competitions, society roles, part-time jobs, tuition you gave, and even group assignments give you plenty of material. For weaknesses, a lack of experience with a particular tool or with professional presentations is honest and expected, as long as you show you are addressing it. What interviewers want from a fresher is evidence that you can reflect on yourself and learn.
Your strengths should echo what you said in your introduction. If you mentioned a project when answering tell me about yourself, you can reuse it as proof for a strength. That consistency makes your story easier to remember. For more role-specific samples, see our strengths and weaknesses examples, which cover different professions and experience levels.
It also helps to have a place where interviewers can see the proof behind your strengths: projects, certificates and work samples. You can create an online resume with those details and share the link before or after the interview.
Two or three is enough. It is better to explain two strengths with a clear example each than to list six without any proof.
Yes, especially for freshers and career switchers, as long as it is specific, such as limited experience with a particular tool, and you explain what you are doing to close the gap.
Yes. Choose a professional weakness that affects how you work, not a personal or health matter. Keep the tone calm and factual.
Prepare two in advance. Use the same structure for the second one: a real example, why it matters, and the steps you are taking to improve.