OfferDrill.

Interview questions

The hard ones

How to answer "what is your greatest strength" without bragging or sounding generic.

This page shows you how to pick one real strength, prove it with a short story, and connect it to the job in under ninety seconds. You'll get the mistakes that flatten this answer, a four-step build, and sample answers you can adapt to your own facts.

Why they ask it

On the surface it's a softball. Underneath, the interviewer is checking three things at once: do you know what you're actually good at, can you back it up with something that happened, and is that thing useful to them.

They're also watching how you talk about yourself. Not for confidence in the vague sense — for whether you can make a claim and support it without either shrinking or overselling. That's the same skill you'll use in a status update, a client meeting, or a disagreement with your manager. They're getting a free sample.

And there's a quieter test. Most people answer with a word that could describe anybody. When you answer with something specific and slightly unusual, you become a person instead of a candidate. That's most of the battle.

What not to say

"I'm a hard worker" or "I'm a perfectionist" or "I'm a people person."

These are the three most common answers in the world. They don't tell the interviewer anything they can use, and they signal you didn't prepare. Worse, "perfectionist" reads as a dodge — a weakness dressed up as a strength, and they've heard it a thousand times.

Listing four or five strengths.

They asked for one. Giving five means you couldn't choose, and none of them get the airtime needed to stick. The interviewer remembers nothing. Pick one, go deep, stop.

The claim with no evidence — "I'm great at solving problems under pressure," then silence.

An unsupported claim about yourself sounds like bragging no matter how you say it. The same claim followed by thirty seconds of what actually happened sounds like a fact. The story is what protects you from sounding arrogant.

Picking a strength that has nothing to do with the job.

If you're interviewing for a data role and your answer is about being a natural public speaker, you've spent your best minute on something they won't use. Choose a real strength that's also load-bearing for this specific job.

Undercutting yourself mid-answer — "I guess I'm okay at this, at least people have said so."

Hedging is the most common way anxious, qualified people lose this question. It plants doubt that wasn't there. State it plainly once, then let the example do the convincing.

How to build a strong answer

  1. Pick the one thing people actually come to you for.
    Don't start from a list of adjectives. Start from memory. When coworkers walked over to your desk or pinged you, what was it about? Who got handed the messy account, the angry client, the spreadsheet nobody could untangle, the new hire who needed training? That pattern is your real strength, and because it's real you'll be able to answer follow-ups about it. If you're early in your career, use school, the internship, the part-time job. Someone relied on you for something. Find it.
  2. Check it against the job posting.
    Read the posting again and find the two or three things the role actually lives or dies on. If your strength maps onto one of them, you're set. If it doesn't, look for another true strength that does. You're not inventing anything — most people have several genuine strengths and this is just about which one you lead with today.
  3. Attach one specific story with an outcome.
    Name the situation, what you did, and what came of it. Keep it to three or four sentences. Real details do the heavy lifting: the actual timeline, the actual number of accounts, the actual result. If you don't remember a number, don't make one up — say "most of the team" or "about a quarter of our orders" and keep going. Vague but honest beats precise and invented every time.
  4. Close with one line about them, then stop talking.
    One sentence tying it to what they need: "That's most of what I saw in this posting, so it's the part I'm most interested in." Then be quiet. The silence after a good answer feels long to you and normal to them. Filling it is how strong answers get talked back down.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, laid off, hasn't interviewed in years.

The thing people came to me for was untangling accounts that had gone sideways. When a client was upset and three different people had already talked to them, it got routed to me. Last year I took over [the account or project], where we'd missed [what actually went wrong] and the client was close to leaving. I didn't lead with apologies — I got everyone on one call, laid out exactly what broke and what we were changing, and sent a short written recap every Friday until it was stable. They renewed at [the actual terms, if you know them]. I read in your posting that this team handles escalations directly, and that's the work I'm best at.

It opens with evidence of demand — people came to me — which is a fact, not a boast. The story has a real shape and a real ending. It closes on their needs in one line and stops.

Early career, one internship, not much to point to yet.

My strongest thing is that I chase down the answer instead of waiting for someone to hand it to me. During my internship at [company], I was given a report to update every week, and I noticed the numbers never matched what the sales team was quoting. Nobody had asked me to look into it. I traced it back to two systems pulling from different date ranges, wrote up what I found in half a page, and brought it to my manager. They fixed the source. It wasn't a huge project, but it's how I work — I'd rather ask an awkward question early than pass along something that's wrong.

It doesn't pretend the story is bigger than it was. The honest framing — "it wasn't a huge project" — makes the rest more believable, and the behavior it describes is exactly what a manager wants from a junior hire.

Changing fields, worried the strength won't transfer.

I'm good at making complicated things simple enough that people will actually act on them. In [previous field] I spent [number] years explaining [the complicated thing] to people who had no background in it and no patience for jargon — and had to do it in a way that held up when they made a real decision based on it. When I moved toward [new field], that turned out to be most of the job: taking [the technical work] and putting it in front of people who need to decide something. I know I'm newer to [the specific tool or domain], and I'm building that. But the translation part I've been doing for years.

It names the gap out loud in one sentence and doesn't linger there. Naming it yourself is stronger than waiting for them to find it, and it makes the claim about the transferable skill more credible.

What comes next

Answer this one well and the interviewer usually goes here:

  • Can you give me another example of that?
  • What would your last manager say your greatest strength is? (Answer with what they actually said in a review or a conversation — and it's fine if it's different from yours, as long as you can explain why.)
  • And what's your greatest weakness?
  • Where does that strength get you into trouble?
  • How would you use that in this role specifically?
  • What's something you're not good at that this job needs?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You already have the answer — it's the thing people kept walking over to your desk for — and all you're doing tonight is finding the words for it and practicing them out loud twice.