It's the question that breaks people. 'Tell me about your strengths' sits there at the top of the interview, the appraisal, or the application form, and most people have one of two reactions. They go blank, scrambling for something that won't sound arrogant. Or they reach for the nearest acceptable adjective, say 'I'm a hard worker', and feel like they've just made it up.
There's a better way to handle the question, and it doesn't require inventing anything. It just requires translating things you already know about yourself into language that lands.
Why the question feels like it's asking you to lie
A lot of people experience this question as an invitation to brag, and bragging feels uncomfortable. So they hedge, and they say things they don't quite mean ('I'm a perfectionist' has been deployed by people who are not, in fact, perfectionists, more times than anyone can count). The hedge feels safer than the brag, but it sounds like it's invented because it is.
The problem isn't that the question is asking too much. It's that we've been trained to think of strengths as character traits ('I'm hardworking', 'I'm a team player') rather than as capabilities backed by specific things you've actually done. Character-trait answers feel like claims you can't prove. Capability-with-evidence answers feel like reporting facts.
What a good answer is actually doing
A good answer to 'tell me about your strengths' has three layers, and you can build it for any strength you have. The capability, named precisely. The evidence, drawn from something you've actually done. And the impact, briefly, on something that mattered.
Here's the same person answering the question two ways.
The vague version: 'I'm a really good communicator. I work well with all kinds of people and I'm always trying to improve.'
The same answer with structure: 'I'm good at translating between technical teams and clients. Last year I sat in on the engineering stand-up and then ran the client check-ins, and when I started, the engineers and the client were sending each other emails that ended up in a meeting to clarify the meeting. By the end of the project, the client could read the engineering updates without needing me to explain them, and the volume of clarifying meetings dropped to about a quarter.'
Same person, same skill. The second version isn't longer because it's padded; it's longer because it tells the listener what the strength actually is, gives them evidence that you have it, and tells them what difference it made.
What to avoid
A few patterns that tend not to land. The adjective list ('I'm hardworking, organised, and a fast learner') doesn't tell the listener anything they can verify. Anyone could claim it, and it leaves the interviewer with nothing to follow up on, which makes the conversation harder for both of you.
The false-modesty version ('I guess I'm okay at organising things, I don't know if it counts as a strength') tells the listener two things: that you're uncomfortable with the question, and that you don't quite trust your own evidence. Neither of those helps you.
The borrowed-language version (using the exact phrasing from the job ad) signals that you're answering the question they asked rather than the question about you. Sometimes that lands; usually it makes the answer feel rehearsed.
The 'I work too hard' inversion ('my biggest strength is that I'm a perfectionist and don't know when to stop') is famous enough that most interviewers groan when they hear it. It also doesn't actually describe a strength.
How to build your version
Start with the inventory you already have. If you've done the work of figuring out what you're actually good at (covered in How do I know what I'm good at?), you've got candidates to work from. Pick two or three that are most relevant to the situation you're in, and for each one, write down the specific story that shows you doing it.
The story doesn't need to be dramatic. A small, real moment is more useful than a big, vague claim. The tutoring you did for one struggling classmate last year is better evidence than 'I'm passionate about helping others'. The shift you reorganised because the rota wasn't working is better evidence than 'I'm a natural leader'. Specificity is what makes the answer believable, and the more specific, the more it sounds like reporting rather than claiming.
When you're stuck for evidence, look for the moment something changed. Strengths tend to leave behind a before-and-after. Before you got involved, the situation was X. After you'd been working on it for a while, the situation was Y. You don't need to claim sole credit; you just need to be honest about what you contributed.
A simple structure to practise
If you're rehearsing for an interview, drill three answers using the same shape:
- Capability. Name the thing you're good at, in one short sentence. Use language that's specific rather than generic.
- Evidence. Tell a real story about a time you did it. Keep it short, and don't get lost in context. Two sentences of setup, two of action.
- Impact. Name what changed. One sentence is plenty.
Three answers like this, drilled until they feel natural, will cover almost any interview question about strengths, and most behavioural questions besides. You're not making anything up. You're just telling the truth about yourself in a way the listener can use.