How to answer “Why should we hire you?”
This question tends to arrive in the middle or near the end of an interview, after the interviewer has already heard your background. It asks you to sell yourself in a minute, out loud, to a stranger. Most people either undersell (“I’m a hard worker”) or recite their CV a second time. The thread below has dozens of replies, which tells you how unsure people are about it:
“How do you answer “Why should we hire you?””
Reddit, r/interviews
What is the interviewer really checking?
Every role has a short list of things the new person must be able to do. The interviewer knows that list better than anyone. When they ask why they should hire you, they want to see whether you can find that list on your own and put yourself next to it, without them leading you there.
So the first thing they learn is whether you understood the job. An answer built on “I’m passionate and a quick learner” could be given for any job in any company, and that is exactly how it sounds. An answer that names the hardest part of this particular role tells them you read the description and listened during the interview.
The second thing is what you think your strongest point is. If you pick something that barely matters for the role, that says something about your judgement. The third is how you carry yourself on a slightly uncomfortable question. Confident and specific reads well. Boastful reads badly, and so does a voice that trails off as if you do not believe your own answer.
There is also a practical side. After the interview, most interviewers write feedback or argue for candidates in a debrief. A clear sentence from you (“she has already run the exact migration we are planning”) is something they can repeat for you. A vague one leaves them nothing to work with.
How is it different from “Tell me about yourself” and “Why do you want to work here?”
The three questions overlap, which is why people end up giving the same paragraph to all of them. They should not.
“Tell me about yourself” is your story in time order: who you are now, what got you here, where you are heading. “Why should we hire you?” is an argument, and it starts from their needs, not your timeline. If you have already told your story, do not tell it again. Pick the two pieces of it that best fit the job and say why they matter here.
“Why do you want to work here?” turns the direction round. It is about the company and what draws you to it. Plenty of people find that one pointless:
“Why is ‘why do you want to work here?’ a common question in interviews? The answer is obviously ‘to get paid’.”
Quora
Everyone in the room knows you want to be paid. What the interviewer is really asking is whether you would pick them over a similar offer and stay once you join. A reason specific to them (their product, their customers, the kind of work this team does) answers that. In short, one question is about what you bring, the other is about why them, and a strong “why hire you” answer can end with one sentence of the second to tie the two together.
What is a simple structure for the answer?
Use four moves. I call them need, proof, edge and close.
- Need. Name what the role needs most, in their words. “From the description and what you said about the team, the hardest part of this job looks like keeping releases on schedule while the product grows.”
- Proof. One specific example of you doing that, or something close to it, with a number or a visible result. One good example beats three thin ones.
- Edge. One thing most other applicants probably do not bring: a language their customers speak, experience with the tool they use, a background in their industry, having used their product for years.
- Close. One sentence on what you would do with it here. Not “so please hire me”; something like “and that’s the first thing I’d want to look at in your setup.”
To prepare, print the job description and underline the three or four requirements that are listed first or repeated. Next to each, write one example from your own CV. The row where your example is strongest becomes your need and proof. The odd thing on your CV that nobody else will have becomes your edge. This takes about fifteen minutes and it works better than memorising someone else’s sample answer.
One more thing. If the interviewer mentioned a problem earlier (“we’ve had a lot of churn on the team”, “our reporting is a mess”), use it as your need. A need they told you about themselves will always beat one you guessed from the job post.
A weak answer, rewritten
Here is the kind of answer interviewers hear all day:
“I’m hardworking, I learn quickly and I’m a team player. I’m really passionate about this field and I’ll give a hundred percent.”
Nothing in it is wrong. It just proves nothing, it fits every job, and it never mentions theirs. Here is the same person, applying to lead a customer support team:
“You mentioned the team is doubling this year and reply times are already slipping, so I think the job is mostly about keeping quality up while you grow. At my current company I took over a team of six when our average first reply was about nine hours. We got it under two within a quarter by splitting the queue by issue type and writing templates for the twenty most common tickets. I also speak Tamil and Telugu, which should help with the South India customers you’re adding. The first thing I’d do here is look at your queue the same way: which tickets come up most, and who on the team is best at each kind.”
Same person, same experience. The second version simply does the matching for the interviewer instead of leaving it to them.
How should a fresher answer “Why should we hire you?”
“Why should we hire you, a fresher?”
Quora
Without a full time job behind you, the proof has to come from somewhere else: a final year project, an internship, a college fest you organised, a part time job, something you taught yourself and can show. Nobody expects years of experience for an entry level role. What helps is evidence that you learn fast and finish things.
Do not open with “I don’t have experience, but”; it puts the gap first. And do not build the whole answer around what the job gives you (“this will be a great learning opportunity for me”). The question is what you give them.
Example: engineering graduate, software trainee role
“Your trainee role works in Java and SQL, and those are the two things I’ve used most outside the syllabus. For my final year project, three of us built a library management system for our college and I wrote the backend and the database. The librarians still use it to track about two thousand books. Last summer I did a two month internship where I fixed bugs in an invoicing tool, so I’ve already worked with code someone else wrote and had my changes reviewed. When I didn’t know Spring Boot for that internship, I learned enough in the first week to ship my first fix. Your programme puts trainees on client work early, and that is how I learn fastest.”
Every claim in it points to something the interviewer can ask about, which is what keeps it honest. For more on the whole fresher interview, see how to crack an interview as a fresher.
What if you’re up against candidates with more experience?
This version feels impossible to win:
“How should you even answer “why should we hire you instead of an experienced person?” As an inexperienced person?”
Reddit, r/recruitinghell
Start from this fact: they invited you. They read your CV, saw your level, and still decided you were worth their time. So the question is not really “why are you better than someone with ten years”. It is “why are you the right hire at the level this role is pitched at”.
Do not argue against the other candidates. You do not know who they are, and running them down makes you look small. Do not pitch yourself as the cheaper option either. Cost is the employer’s sum to do, and offering it up front undersells you.
What works is to acknowledge the gap in a few words, then move to what you offer that experience does not guarantee. That could be tools you use every day right now, or a track record of getting up to speed quickly, told with dates. If the role is a junior one, it is also fair to say this is the level you want.
Example: junior data analyst
“I’m sure some of the people you’re seeing have more years than me. What I can show you is how fast I get useful. In my first job I went from not knowing our data warehouse to owning the weekly sales report in six weeks, and that report is still built the way I set it up. I also work in the same tools your team uses, Python and Power BI, every day, so I already know the tools in your job post.”
Example answers for experienced hires, career changers and internal moves
The details below are invented. Copy the shape and swap in your own.
Experienced professional
“You’re moving your billing to a new platform next year, and I’ve done that exact project twice. At my current company I led the move from our old system for about forty thousand customers, and we did it with no double charges and fewer than fifty support tickets in the first month. Most of that came from running both systems side by side for a full cycle before switching. I’ve also managed the finance and support teams through a change like this. In the first week I’d want to check that your timeline leaves room for a full side by side cycle.”
With experience, the risk is the opposite of the fresher’s: too much to say. Choose the one project closest to their problem and save the rest for follow up questions.
Career changer
A career changer has to answer an unspoken worry: will this person really stick with the new field, and how long until they are useful? Answer it before they ask, in a sentence or two.
“I spent six years as a nurse, and for the last year I’ve been working towards a customer success role in health tech. For this job I think the hardest part is getting hospital staff to actually use the software after it’s installed. I trained thirty nurses on a new records system on my ward and I know which objections come up on a night shift. I’ve also done a course in customer success and spent the last three months helping a small clinic software company with their onboarding calls, so this isn’t a guess about whether I’ll like the work.”
Internal move
An internal panel already knows your work, so they are not asking whether you are good. They are asking whether you will be good at this new job, and whether you are moving towards something or away from your current team. Read your company’s internal hiring policy, and tell your current manager before they hear it from someone else.
“You know my work on the support side, so I’ll focus on why I fit this product role. For two years I’ve been the person who collects customer complaints and turns them into tickets for your team, and three of the features you shipped last year started as my write ups. I know our customers and our codebase’s weak spots from the inside, which an outside hire would still have to learn. My manager knows I’m applying, and we’ve already agreed a handover plan for my current work.”
Does the answer change for HR, the hiring manager and the final round?
The core of your answer should stay the same in every round. If three people ask the same question and later compare notes, consistency helps you. What changes is how much detail you give, because each person is scoring something different.
HR or the recruiter is mostly checking that you match the brief at a basic level: the right skills on paper, clear communication, salary and notice period in range, a believable reason for applying. Keep the answer shorter and broader. They usually cannot judge a technical example in depth, so keep it to a sentence.
The hiring manager is asking a narrower question: will this person solve my problem? Go deeper on proof here. Use their team’s language, mention the tools or the customers they work with, and expect them to push back with “give me another example” or “what would you have done differently?”
The final round is often with a senior leader or a panel, and they care about the longer term: will this person grow, and will the others agree with the hire? At Amazon, for example, loops include a Bar Raiser, and Amazon says part of that role is to help make sure “every new hire has growth potential”. In a round like that, add a sentence about where you would grow in the role. The Amazon interview questions page has more on how those loops work.
How is it asked in Indian campus placements and HR rounds?
In campus placements the wording shifts a little. You may hear “Why should we select you?” or “Why should we take you over the other students from your college?”, and it often sits next to its company cousin, “Why TCS?” or “Why Infosys?”. Some students meet it for the first time in a placement interview:
“What is the best answer for the question ‘Why shold I hire you’ when asked to a fresher who didn’t attend interview even once?”
Quora
A few things are specific to these rounds.
- Do not compare yourself with classmates. “I am better than the others” cannot be proved. “Here is something I built beyond the syllabus” can.
- Expect practical questions alongside it. HR rounds at large IT services companies commonly pair “why should we hire you” with questions on relocation, rotational or night shifts, a service agreement and your joining date. If you cannot relocate or work nights, say so now rather than after the offer.
- Have one real reason for “Why us?”.“It is a big company with a good name” tells them nothing about why you chose them. Their training programme or a client domain you care about does.
- Write it as carefully as you say it. Internshala asks “Why should you be hired for this internship?” on every application, and its own blog warns against pasting the same generic text each time. Write it fresh for each listing.
If English is not your first language, it helps to practise this answer out loud more than any other, because it is the answer where you most need to sound sure. See interviewing in your second language for help on the call itself.
What mistakes make this answer fall flat?
- Making it about you. “This role would really help my growth” answers a question nobody asked. Growth can come in at the end, after you have shown what they get.
- Listing every skill. Ten skills with no example blur together. One skill with a story sticks.
- Over-apologising. “I’m not sure, but maybe because…” signals that you do not believe your own case. Say it plainly, even if your voice shakes a bit.
- Sounding desperate. “I really need this job” may be true, but it makes the interviewer worry rather than want you.
- Reciting it. A paragraph learned by heart sounds like one. Know your four moves and your example, and put them into words on the day.
What do interviewers ask after it?
Expect at least one follow up. These come up often.
“What makes you different from other candidates?”
Give your edge here, not your proof again. If you already used it, have a second one ready, or go deeper on the first: how you got it and where it has paid off.
“Why shouldn’t we hire you?”
Name a real gap that is not central to the job, and what you are doing about it. “I haven’t managed a budget on my own yet; my manager has started giving me our team’s training budget to run this quarter.” Saying you have no weaknesses ends the conversation badly.
“Can you give me another example?”
It can mean the first one did not quite convince them, or that they want to see whether it was a one off. Keep a second piece of proof for the same need, ideally from a different job or project.
“What would you do in your first ninety days?”
Talk about listening first, then one small early win, then one larger thing you would want to understand. Do not promise to change their process before you have seen it.
“Are you interviewing anywhere else?”
Be honest and brief. “Yes, a couple of places, but this is the role I’m most interested in because…” and give your one specific reason, if it is true.
How can PiriPiri AI help with this question?
The hard part of “Why should we hire you?” is the matching: connecting your own experience to their needs, live, while someone watches you think. That matching is what PiriPiri AI helps with.
It is a desktop app for macOS and Windows that listens to both sides of the call: your microphone and the interviewer’s audio from your computer. When it hears the question, it drafts a short reply on a small overlay, built from the CV and job description you added before the interview and the role you picked. So the reply already pairs a requirement from their job post with an example from your own CV. If they ask for more, the deep dive hotkey (Cmd+Shift+6 on Mac, Ctrl+Shift+6 on Windows) asks for a longer version. The previous answer hotkey (Cmd+Shift+comma) brings back an earlier draft if a follow up returns to the same point.
No meeting bot joins the call, and it works with Zoom, Google Meet, Microsoft Teams, Webex and others. The overlay is excluded from screen capture by the operating system, so it does not appear when you share your screen or record. Afterwards the transcript and notes are saved to your account, so you can check how you answered and what they asked next.
It has limits. It cannot give you experience you do not have; the draft can only use what is in your CV. Reading it word for word sounds rehearsed, and interviewers notice. Treat it as a prompt you glance at when you go blank, then say it your own way. Some employers and places also have rules about recording or AI help in interviews, so check them first. If you are wondering what an interviewer can pick up on, read can interviewers tell if you use AI. The setup guide shows how to add your CV and job description.
Questions people ask
How long should my answer to “Why should we hire you?” be?
Aim for about a minute, which is roughly 120 to 180 spoken words. That is enough for one need, one example and one extra point. If the interviewer wants more, they will ask for another example, and you will look better giving it on request than squeezing it in up front.
Should I say I am the best candidate?
No. You have not met the other candidates, and the interviewer knows that. Say what you are sure of instead: that you have done the core of this job before, or that you meet the two requirements they care about most. A claim you can back up lands better than a claim nobody could check.
What if I do not meet every requirement in the job description?
Few people do. Job descriptions mix essentials with nice to haves, so work out which is which. Build your answer on the requirements you do meet strongly. If a gap is obvious, name it in one sentence along with what you are doing about it, then return to your strengths.
How do I answer if I am overqualified for the role?
The worry behind the question is that you will be bored or leave soon. Give a concrete reason this role fits where you are now, such as wanting to be hands on again or moving into a new industry, and show you have thought about the level. Avoid saying you will take anything.
Should I mention salary or that I can join quickly?
Leave salary out; it has its own conversation. A short notice period or immediate availability is fine to mention at the end if the recruiter has said they need someone soon, because then it answers a real need of theirs.
What if they ask it right at the start of the interview?
Then you have not heard their problems yet, so lean on the job description. Pick the requirement listed first or repeated most, give your proof for it, and keep it shorter than usual. You can come back to it later: “Earlier you asked why you should hire me, and what you just said about the team makes me think of another example.”
Is “Why should we hire you?” a trick question?
No. It is one of the plainest questions in an interview: make your case. It feels awkward because most people are not used to praising themselves out loud. Treat it as a short, factual summary of the evidence, the way you might recommend a friend, and the awkwardness drops away.
Where to go next
For practice telling the stories behind your proof, use the behavioural question guide. If you freeze mid answer, see what to do when your mind goes blank, and if the interview is tomorrow, start with this short plan. When they ask if you have questions, here are good ones to ask.
PiriPiri AI costs about $2.50 an interview, paid per interview with packs that never expire and no subscription required. Every new account gets 3 free sessions, so you can try it on a practice call first. See pricing for pack sizes, or the India page for prices in rupees.