How to answer “Why should we hire you?” in English

What is the interviewer really checking with “Why should we hire you?”

This question often comes near the end. By then the interviewer has heard your story. Now they want you to do the summary for them, the same summary they will have to write when they recommend you.

• Understanding: do you know what this role actually needs, beyond the job title?
• Evidence: can you point to results, not just qualities?
• Confidence: can you make a case for yourself without sounding arrogant or apologetic?
• Differentiation: what do you bring that other good candidates might not?

Think of it as a short closing argument. If the interviewer could copy your answer straight into their notes, you did it well.

What structure should you use?

Use need, proof, plan. It works because it starts with them, not with you.

1. Need: name what the role requires, in their words. “From what you’ve described, you need someone who can stabilise the data pipeline and also explain trade-offs to the business.”
2. Proof: one result for each need. “At my current company I rebuilt our reporting pipeline and cut failed overnight jobs from several a week to almost none. I also run the monthly review with the finance team, so I’m used to explaining technical risk in business terms.”
3. Plan: what you would do first. “In the first month I’d map where the pipeline breaks today and agree with your team which two fixes matter most.”

Two or three needs is enough. Five sounds like a list, and the interviewer will remember none of them. Pick the needs from the job description and from what the interviewer has said earlier in the conversation, then reuse their exact words. That shows you were listening.

What does a weak answer sound like compared with a strong one?

What are good model answers for different profiles?

These answers are around 60 seconds when spoken. Each one names the need, gives proof, and ends with a plan.

Software engineer: “From our conversation, it sounds like you need someone who can own the mobile release process and help the team ship more often without breaking things. That’s what I’ve done for the last two years. At my current company we went from one release a month to one a week, and I set up the automated tests and the rollout checks that made that safe. I’ve also mentored two junior developers through their first releases. If I joined, the first thing I’d do is sit with the team, look at what’s slowing your releases today, and propose one change we could ship in the first month.”

Product or project manager: “You mentioned two problems: projects slipping because of unclear priorities, and stakeholders who hear about delays too late. I’ve dealt with both. At a healthcare software company I introduced a single priority list that sales, support, and engineering agreed on every two weeks, and the number of mid-sprint changes dropped by more than half. I also send a short weekly risk note, so leaders hear about problems while there’s still time to act. I’d bring the same habits here, starting with the roadmap for the next quarter.”

Sales: “You need someone who can open a new region without a big team behind them. I’ve done that twice. At my current company I was the first salesperson in a new market, and in eighteen months I built the pipeline from nothing to the point where we hired two more people. I’m comfortable doing my own prospecting, running demos, and negotiating contracts. And because I’ve worked with customers in several countries, I’m used to adapting the pitch to how each market buys. In the first ninety days I’d focus on the twenty accounts with the best fit and get first meetings with them.”

How do you sound confident without sounding arrogant?

Confidence in English comes from facts, not from adjectives. “I’m the best person for this job” is a claim the interviewer cannot check. “I’ve done this exact thing twice” is a fact they can.

• Use “I” for what you did, and “we” for team results, but make your part clear: “We cut costs by 15%, and I ran the supplier renegotiation.”
• Avoid comparing yourself with other candidates. You do not know them.
• Replace “I think I could” with “I can” or “I have”. One softener per answer is plenty.
• End with a plan, not a plea. “I’d start by…” sounds more confident than “I hope you give me the opportunity.”

What mistakes do non-native speakers make with this question?

• Over-hedging. Stacking “I think”, “maybe”, and “a little bit” turns a strong case into a weak one. State the result. Let the facts be modest for you.
• Over-apologising or thanking too much. One “Thank you for asking” is polite. Three sounds nervous.
• Translating fixed expressions from your first language, like phrases about giving your best effort or putting all your heart into the work. In English they sound vague. Name what you did instead.
• Sounding memorised. If the answer does not mention anything the interviewer said earlier, it sounds prepared for every company. Adapt the need part in the moment.
• Speaking too fast at the end of the interview. Tiredness and relief speed people up. Slow down for the numbers so they register.
• Filler words before every number: “around like maybe 20%”. Choose one approximation word, “about” or “roughly”, and use it once.

How do you rehearse it out loud?

1. Read the job description and underline the two or three needs that appear most.
2. Write one result for each need, with a number if you have one.
3. Say the full answer out loud with a timer. Aim for 60 seconds, and never more than 90.
4. Record it and check: does it start with their need, or with you? Does it end with a plan?
5. Apply the one-breath test to each proof sentence. If you cannot say it in one breath, cut a clause.
6. Practise a version that adapts the first line to something an interviewer might say, such as “you mentioned the team is growing”.

Eloquent can play the interviewer in a custom roleplay where you describe the role and the company. You answer out loud, and the debrief shows the exact sentences you used next to a stronger version, which is useful for spotting soft claims that should have been results.

Frequently asked questions