Answering Strengths and Weaknesses in an Interview
The strength half is easy to answer and easy to waste. The weakness half is where interviews are actually lost — usually by candidates who deploy a disguised strength and signal that they are managing the interviewer rather than answering.
STAR: the structure for any behavioural question
| Letter | Means | Say |
|---|---|---|
| Situation | The context | One or two sentences. Where and when. |
| Task | Your responsibility | One sentence. What you specifically owned. |
| Action | What you did | The bulk of the answer. Concrete steps, in first person. |
| Result | The outcome | One or two sentences, with a number where one exists. |
Saying 'we' throughout
The interviewer is evaluating you, not your team. Describe the team's situation, then switch to "I" the moment you reach the Action — that is the part being graded.
The strength
Pick one strength that the job description actually needs, and prove it with a short STAR story. An unproven adjective is worth nothing — "I am a fast learner" and "I am hardworking" are what every other candidate is also saying at that moment.
Worked example
"I am good at debugging problems that are not reproducible on demand.
During my internship, our order service failed roughly once every two thousand requests, and nobody could reproduce it locally. I added correlation-ID logging across the three services involved and left it running for a day. The failures all shared one pattern — a retry firing while the first request was still in flight, creating a duplicate row. I added an idempotency key on the request, and the errors stopped.
It took me about three days, and most of that was building the visibility rather than fixing the bug."
Specific, verifiable, and it demonstrates the strength rather than asserting it. The final line is doing quiet work too: it shows an understanding that measurement usually precedes the fix.
The weakness
The question tests self-awareness and whether you act on feedback. It does not test whether you have flaws — everyone does, and the interviewer knows it.
- Name a real weakness that will not stop you doing this job.
- Show the cost — a specific moment it caused a problem.
- Show the correction — what you changed, and how you know it is working.
Worked example
"I used to keep working on a problem alone for far too long before asking anyone.
In my third-semester project I spent two days on a deployment failure that my teammate had already solved in a different module — I just had not asked.
Since then I keep a hard rule: forty-five minutes stuck, then I write up what I have tried and ask. It has changed how the work goes — I still try things myself first, but the write-up itself often surfaces the answer, and when it does not, someone else has usually seen it before."
The disguised strength
"I am a perfectionist." "I work too hard." "I care too much." Every interviewer has heard these hundreds of times, and all they signal is that you would rather manage the question than answer it.
The other extreme
Do not name a weakness that is the job. "I find it hard to focus for long stretches" in a software role, or "I avoid presenting" in a client-facing one, is honest and disqualifying. Choose something real and survivable.
Build a story bank, not answers
Most behavioural questions are the same handful of stories asked from different angles. Prepare four or five STAR stories and you can answer almost anything: a project you led, a conflict you resolved, a failure you owned, a deadline you were under, something you learned quickly.
| Question | Angle to lead with |
|---|---|
| Tell me about a challenge you faced | The obstacle and how you got past it |
| Tell me about a failure | What went wrong and what you changed after |
| Tell me about working under pressure | The deadline and how you prioritised |
| Tell me about a disagreement | How you reached a decision without stalling |
Key takeaways
- Answer behavioural questions with STAR, and spend most of it on Action.
- Say 'I' in the Action — that is the part being evaluated.
- A real weakness plus a specific correction beats any disguised strength.
- Prepare four or five stories, not one answer per question.
Practice
| Problem | Pattern | Level |
|---|---|---|
| Write your 90-second 'tell me about yourself' | Present, proof, purpose | Easy |
| Write one STAR story about a failure you owned | STAR | Easy |
| Write one STAR story about a disagreement | STAR | Medium |
| Record yourself answering, then cut it by a third | Delivery | Medium |
Frequently asked questions
What is the STAR method?
A structure for behavioural answers: Situation, Task, Action, Result. It keeps the answer concrete and stops it drifting into generalities, with most of the time spent on the actions you personally took.
What is a good weakness to mention in an interview?
A real one that does not prevent you doing the job, told with a specific example of the trouble it caused and the concrete change you made afterwards. Avoid disguised strengths such as perfectionism.
How many stories should I prepare for an HR round?
Four or five well-chosen STAR stories cover almost every behavioural question, because most questions are asking for the same experiences viewed from different angles.
Test yourself on HR Interview
Reading is not recall. Take a timed quiz on this topic solo, or share a room code and battle friends on it.
⚡ Start the HR Interview quiz