Česky
Slovensky
English"I'm communicative, reliable, and I work well in a team." The recruiter nods, writes nothing down, and moves to the next question. This scene repeats in interview after interview, not because those traits are bad, but because nothing stands behind them.
The strengths question is one of the three most common in any interview. Most people answer it with three adjectives the interviewer has already heard fifty times that week. The difference between the candidate who gets the offer and the one who doesn't is often not which strengths they have, but how they talk about them.
Talking about your strengths convincingly is a skill, not a talent, and you can rehearse it in an afternoon. You need three things: to know what you are actually good at, to name it precisely, and to back it up with an example. We'll leave the discovering to one side. The job here is getting your strengths out of your head and into the head of the person across the table.
Why "communicative" doesn't register
An adjective without evidence is noise to an interviewer. Say you're detail-oriented and you've said nothing verifiable. Anyone can claim anything, and an experienced recruiter knows it, so they mentally filter the adjectives out and wait to see whether something concrete follows.
Look at it from the other side. How many people in an interview say they're unreliable and bad with people? Nobody. So when you claim the opposite, you don't stand out, you blend into the crowd saying the exact same words. A quality that everyone lists cannot, by definition, set you apart.
Worse, the generic answer sounds rehearsed. "I'm a driven team player with an eye for detail" is not a sentence anyone says spontaneously. It reads like it was lifted from an online advice column, which it usually was, and the interviewer clocks that in about a second.
A strength is a claim plus evidence
One simple principle does the heavy lifting: every strength you mention needs proof. The claim says what you can do. The evidence shows it in a concrete situation with an outcome. Drop the second half and the first is just a declaration.
The most reliable way to deliver the proof is the STAR method. You describe the situation (where and when), the task (what you were responsible for), the action (what you specifically did), and the result (how it turned out, ideally in numbers). Nothing fancy, but it forces you to speak in specifics instead of generalities.
| Generic answer | Claim + evidence |
|---|---|
| "I'm communicative." | "I can explain technical things to people outside the field. In my last job I translated developer requirements for customers, and complaints caused by misunderstood specs dropped by roughly a third." |
| "I'm reliable." | "In two years I never missed a single monthly close, even through the stretch when a colleague left and I ran it alone for six months." |
| "I work well under pressure." | "The day before our online store launched, the payment system went down. I took over the vendor calls and we were back online by evening." |
Take a real situation. Two candidates interview for a project coordinator role. The first says: "My strength is organization, I'm very systematic." The second says: "I like holding together things that fall apart easily. On our last project we had five external vendors and no shared calendar. I set up a simple deadline overview everyone could see, and for the first time in a year we launched on time." Which one do you remember?
The second answer works because the interviewer can replay it like a film. They see the problem, they see what the candidate did, they see the result. The first answer is just a label they have to fill in for themselves, and people don't want to fill things in.
One trap lurks even here: the story that runs too long. A three-minute tale that gets lost in detail tires the listener as much as an empty adjective does. Keep it to roughly thirty to sixty seconds. Name the strength, give the situation, action and result, then stop. If the interviewer wants more, they'll ask.
Pick two or three strengths the role actually cares about
A common mistake is dumping everything. The candidate tries to impress and rattles off six qualities at once. The effect is the reverse, none of them sticks. Human attention carries away two or three things from an answer at most, so it's better to choose the ones that fit the role and back them up properly.
Where do you find those strengths? In the job ad. Companies usually describe who they want fairly precisely, they just bury it in phrasing like "we're looking for a self-starter who can juggle several projects at once." Translate that. Independence, tolerance for fragmentation, the ability to set priorities. Those are worth talking about.
Go through the ad line by line and match each requirement to one situation from your own experience that proves it. If it asks for "team spirit," don't show up with a phrase about team spirit. Show up with the moment you helped a colleague finish something that wasn't even your job. The role doesn't care about a list of your virtues. It cares whether you can do what it needs.
Choose strengths you genuinely have, not the ones that sound good, and there's a practical reason that reaches beyond the interview. Dubreuil, Forest and Courcy (2014), writing in The Journal of Positive Psychology, found that people who regularly use their strengths at work perform better and are more engaged, driven by higher vitality and concentration. Gallup has long added that employees who use their strengths every day are roughly six times more likely to be engaged. A strength you invent for the interview will teach you nothing on the job. A real one will pull you forward.
Verifiability beats bragging
Plenty of people worry that talking about their strengths will make them look arrogant. The fix isn't to say less, it's to let the facts do the talking. The line between confidence and boasting runs right through verifiability.
Boasting leans on superlatives: "I'm a brilliant salesperson, the best on the team." A verifiable answer leans on fact: "Last year I closed the most contracts of a five-person sales team." The second sentence says essentially the same thing, yet nobody can accuse you of arrogance, because you only described what happened. The number does the bragging for you.
It also helps to admit context and the part others played. "It worked mainly because I proposed a new process" sounds more credible than "I saved it single-handedly." Crediting the team takes nothing away from you. It shows you as someone people can work with, which the interviewer is weighing just as much as your abilities.
When you don't have hard numbers
Maybe you're objecting: "But I don't have any numbers." New graduates, career changers, and people from roles where performance isn't measured in percentages tend to panic here. Yet proof doesn't have to be a number. It only has to be concrete and verifiable.
Proof can be a change you caused ("before, it was done one way, after my suggestion, differently"). It can be how other people reacted ("my manager started sending me to meetings with the toughest clients"). Or a recurring pattern where people came to you for help with the same thing. All of these tell the interviewer more than any adjective.
Take a fresh graduate with no work history. Instead of "I'm responsible," she can say: "In my third year I ran a student club. When our keynote speaker cancelled days before the event, I found a replacement within two days and it went ahead as planned." No percentage, and still proof. You can draw experience from school, a side job, volunteering, even a hobby, as long as you pull a concrete situation out of it.
Name the strength precisely
"Communicative" can mean ten different things. Can you speak in front of a room? Negotiate a deal? Explain something complicated in plain words? Write an email that finally gets people to do what they're supposed to? Each of those is a different skill, worth a different amount to a different role. The more precisely you name the strength, the better the interviewer can place you.
A good source of precise terms is the classification of character strengths built by Christopher Peterson and Martin Seligman (2004). It describes 24 strengths, from curiosity through perseverance and social intelligence to fairness and perspective. It's not a list to memorize, more a dictionary that gives you language for things you sense about yourself but can't quite name.
When you're stuck on which words describe your strengths, a character strengths test can help. It ranks those 24 strengths by how well they fit you and adds a description of your top five that you can draw on in an interview. Instead of "I'm communicative," you might say "my strength is social intelligence, I can read what the other side needs to hear," and it lands differently at once.
A few examples of swapping a vague label for a precise one:
- "Communicative" → "I can run a meeting so it ends in a decision, not just a debate"
- "Creative" → "I find a way through where other people see a dead end"
- "Hard-working" → "the boring tasks that sink a lot of people, I actually finish"
- "Empathetic" → "I sense when a client is upset before they say so out loud"
Four mistakes that cost you the offer
- False modesty. "I don't know, I guess I'm fairly careful." If you can't name what you're good at, the interviewer assumes it's nothing. Modesty isn't the same as being unable to sell your own work.
- A weakness dressed up as a strength. "I'm a perfectionist" and "I push myself too hard" are so worn out they read as evasion. Save the honest talk about weaknesses for when they actually ask, and don't pretend they're assets.
- A strength with no link to the role. Talking up how well you improvise in an interview for an accounting job misses the mark. A quality the role won't use doesn't interest the interviewer.
- The rehearsed litany. An answer recited without any feeling gives away the template. Talk about situations you genuinely lived through, and you'll sound natural, because you remember them and don't have to act.
Before your next interview, try one thing. Take the job ad, pick three requirements, and for each one say out loud a single concrete situation from your experience that proves it. If nothing comes to mind for one of them, that's useful information in itself. Either you don't have that strength, or you've forgotten it, and both are better to find out at home than across the table from a recruiter.