How to answer “why should we hire you?”

This question usually arrives in a first-round screen, from someone with ten minutes and four more calls that day. They are not exploring. They are filtering, and they have been told to come back with two names.

That context is the answer key. Anything that sounds like it could have come from another candidate is a wasted turn, because the whole purpose of the call is to separate you from the other candidates.

The words that no longer register

'I'm a fast learner.' 'I'm passionate about the product.' 'I'm a real team player.' 'I'm detail-oriented but I also see the big picture.' A hiring manager has heard each of these several hundred times, and they no longer produce any reaction at all — not scepticism, just nothing.

The problem is not that they are untrue. It is that they are unfalsifiable, and unfalsifiable claims carry no information. Every rejected candidate said the same sentence.

Trade the adjective for the outcome

Every generic claim has a specific version hiding behind it. The specific version is the answer.

1. 1Instead of 'I'm a fast learner': 'I joined a Rust codebase having never written Rust and shipped my first production change in three weeks.'
2. 2Instead of 'I work well under pressure': 'I ran the incident response the night our payments provider went down, and wrote the postmortem that changed our on-call rota.'
3. 3Instead of 'I'm good with stakeholders': 'I got finance and engineering to agree on a shared definition of active user, which had been disputed for two years.'

Each of these invites a follow-up question, which is what you want. A ten-minute screen where the interviewer asks you three follow-ups is a screen you have passed.

Expect the ownership question

When you claim an outcome, a good interviewer will ask what your specific part in it was. This is not suspicion — it is the most efficient way to tell a contributor from a narrator. Have the answer ready, and make it honest about scope. 'I didn't build the pipeline, I owned the migration plan and ran the cutover' is a stronger answer than an implied claim to the whole thing.

End with a question that only you would ask

In a ten-minute call, the sharpest signal you can send is a question that shows you have thought about their actual situation. Not 'what's the culture like' — something like 'you've been rebuilding the onboarding flow for two quarters; is the constraint the design or the data model underneath it?'

A question like that does more than any adjective could. It demonstrates the thinking rather than describing it.

They are not choosing the best candidate. They are choosing the two they can most easily defend to someone else.

Practise thisWhy Should We Hire You?Amina Brooks has ten minutes between back-to-back calls, will not fill your silences, and asks the original question again if the answer was generic.