Ask ten candidates what their greatest strength is and at least seven of them will say some version of "I'm a hard worker," "I'm a good communicator," or "I'm detail-oriented." These answers are so common they've stopped meaning anything.
The goal of this question isn't to say something positive about yourself. It's to differentiate yourself, to give the interviewer a reason to remember you when they're comparing notes after a day of back-to-back interviews.
The problem with most strengths answers
Two things go wrong with the average answer to this question. First, candidates pick generic strengths, the ones that sound safe rather than the ones that are actually true or useful for the role. Second, even when the strength is good, they state it as a claim without backing it up.
"I'm a strong communicator" is a claim. "I ran the weekly engineering all-hands for two years and reduced the average meeting length from 75 minutes to 40 without reducing the information shared" is evidence. Evidence is what makes a strength believable.
How to choose the right strength
Two filters. First: is it real? Pick something you are genuinely better at than most people in your field, not something you think sounds good. Interviewers can usually tell. Second: is it relevant to this role? A strength that doesn't connect to what the job requires is a wasted answer.
Read the job description carefully. What skills or behaviors does this role need most? Then think about which of your genuine strengths maps to that. That intersection is your answer.
The framework: Strength, Evidence, Impact
- Name the strength, one specific thing, not three vague ones
- Give evidence, a specific example of when this strength showed up
- State the impact, what happened because of it, ideally with a number
Sample answers
Product manager
"My strongest area is probably translating between technical and commercial teams. I spent the first three years of my career as a developer, which gives me enough technical depth that engineers trust my judgment, and I've since built enough business context that the commercial side takes me seriously. That's let me cut through alignment issues that usually stall product work. In my last role, we had a recurring conflict between engineering and sales over roadmap priorities. I ran a structured prioritisation session that got both teams to a shared framework in two meetings. We reduced roadmap disagreements from a constant issue to something that came up maybe once a quarter."
Sales / account manager
"I'm unusually good at expanding accounts. Most salespeople are better at new business than at growing existing ones, but I've always found the relationship side more interesting. In my last role I grew our top 10 accounts by an average of 40% over 18 months without any additional headcount on the team. The main driver was identifying upsell opportunities through quarterly business reviews that most teams were treating as formalities."