Clear the rounds
Why Should We Hire You? The 3-Part Answer
Thirty-four minutes in. Aarav has explained his project, survived two SQL questions and drawn a schema on the whiteboard. Priya closes the folder, looks up and says: "Last question. Why should we hire you?" Aarav says, "Ma'am, I am a hard worker and a quick learner." Priya writes one word on her sheet and calls the next student.
10 min readFree, no email neededUpdated 11 September 2026
The question that decides it
Thirty-four minutes in. Aarav has explained his project, survived two SQL questions and drawn a schema on the whiteboard. Priya closes the folder, looks up and says: "Last question. Why should we hire you?" Aarav says, "Ma'am, I am a hard worker and a quick learner." Priya writes one word on her sheet and calls the next student.
By this point they know you can code. Three students cleared the same rounds. This is the only question where you choose what they remember when they compare the three of you.
It is not a personality test. It is a one-line business case: here is what you need, here is my proof, here is why it is you I want to do it for.
Thirty to forty-five seconds. Three to five sentences. Then stop talking.
What they need
Do not start with yourself. Start by naming the job, in their words. It tells the interviewer you read the JD, and it sets up everything you say next.
"For this role you need someone who can , and who is comfortable with ."
- Use their words, not yours.If the JD says "own a service end to end", say "own a service end to end". Not "handle full responsibility".
- One need, not five.Pick the requirement listed first or repeated most. Five sounds like you are reading the advertisement back to them.
- No JD? Use the round you just finished."You need someone strong on SQL and query tuning" — because that is what they spent twenty minutes on.
Your proof
Now answer that need with evidence, not adjectives. One project or one result, with a number inside it. The number is the only part of your answer that nobody else in the corridor can copy.
"I have done exactly that. I built , which — using ."
"I am good at backend development and I have done many projects in Node.js."
"I built the attendance API my department uses — 120 students, eight months live, Node and PostgreSQL. It has not gone down since March."
Numbers you already have, even with no internship: users, records, rows, requests per minute, seconds saved, percent improved, problems solved, contest rank, team size, weeks taken, months live. Estimate honestly and say "about".
The fit line
One sentence you could not say to the company interviewing in the next room. Almost nobody prepares this part, which is exactly why Priya remembers it.
"And I want it here because — that is what I want my first two years to look like."
Where to find your one specific thing
- The team line in the JD itself: "payments platform", "10 million users", "0 to 1 team".
- A product of theirs you have actually used, and one honest sentence about it.
- Their engineering blog, a launch, or a news item from the last six months.
- A senior from your college who works there. Message them on LinkedIn the week before.
"It is a reputed company with a good work culture and great learning opportunities."
"Your refund flow is the only UPI one I have used that tells me the exact date. I want to work on that."
Read the JD, take 3 words
Paste the job description into Notepad. Mark every noun or verb that appears more than twice. Ignore the adjectives — "passionate", "dynamic", "excellent" are decoration.
Where each word goes: word 1 into Part 1 — "you need someone who can own a service end to end". Words 2 and 3 into Part 2 — "I built a REST API on PostgreSQL, alone, from schema to deploy". Use each word once. Say it three times and it stops sounding like you and starts sounding like the advertisement.
The 5 weak answers
Priya hears each of these about forty times a season. None of them is wrong. All of them are empty, because the next student says the same words.
Six answers
01Product company · SDE role
"For this role you need someone who can own a backend service end to end, and who is solid on data structures. That is what I have been doing on my own. I built a bill-splitting app that 40 hostel students use every month — it holds about 900 expense entries and works out the fewest payments needed to settle up. Node, PostgreSQL and JWT, live for seven months. I have also solved 400 problems on LeetCode, so today's DSA round was familiar ground rather than a surprise. I want it here because your team ships to real users every two weeks, and I would rather write code people open than code that sits in a report."
02Service company · TCS, Infosys, Wipro style
"You hire people you will train and then put in front of a client, so you need someone who picks up a new stack fast and can explain their work in plain English. I have done that twice. In January I had never written Java; in six weeks I rebuilt my college notice-board portal in Spring Boot, and 300 students use it now. When my project partner left, I wrote the handover document and a junior finished the last module from it. I am comfortable being mapped to whichever technology the project needs, and I am open to relocating. I want it here because every senior from my college says your training programme is the thing that actually taught them to work on a live client codebase."
03Startup · small engineering team
"In a team of five you need someone who takes a problem end to end and does not wait to be told the next step. That is already how I work. I built and shipped a slot-booking tool alone — design, API, Postgres, Razorpay test payments and the deploy — in three weeks, and 60 people used it in the first month. When UPI payments started failing I read the docs and fixed it the same day, because there was nobody to escalate to. I want it here because your product is still at the stage where one engineer's work is visible in the app, and that is the kind of first two years I want."
Six answers
04Student with no internship
"I have not done an internship, so let me show you the work instead. You need someone who can write clean React and take review comments. In the last year I shipped two applications that are live and used: an attendance tracker 120 students in my department open daily, and a bus-timing Telegram bot with 300 users. Both are on GitHub with commits spread over ten months, not one weekend, so you can see how the code changed. My classmates and I review each other's pull requests, so being told my code is wrong is normal for me. I want it here because your team reviews every commit — I have been doing that informally and I want to do it properly."
05Non-CS branch student
"I am from Mechanical, which means I am in this room by choice and not by default. You need someone who can write Python and work with data. I have spent two years doing that: I built a vibration dashboard for my department's lab that reads about 8,000 sensor rows and flags a failing bearing before the machine is opened. Python, Pandas and Streamlit; two professors use it every week. I taught myself SQL from scratch and I have solved 300 problems in Python. My branch gave me one thing a CS student does not have — I have stood next to the machines this software is written for. I want it here because your product sits between hardware and software, and that is the gap I understand."
06Low CGPA, strong projects
"My CGPA is 6.4, and I would rather explain it than let you guess. My second year went badly — I was building things and I let attendance and internals slide, and that was my mistake. I fixed it: my last three semesters are 7.8, 8.1 and 8.3. What never slipped is the work. I built a campus marketplace 200 students use, and a REST API that held 200 requests a minute in load testing. You need someone who can write working code from day one and keep going when it breaks at 1 a.m. That is the part I am genuinely good at, and it is the part this job is made of."
The confident close
The last sentence is the one they carry out of the room. End it on them, end it with a full stop, and then be quiet.
- Never end on a question."…so I hope I am a good fit?" hands the room back and sounds like you are asking permission.
- Never trail off with "so, yeah" or "that's it basically".Practise the last seven words until they come out the same way every single time.
- Stop, and count two seconds in your head.The silence is theirs to fill. Filling it yourself is how a good answer turns into a rambling one.
Want this on your phone?
Everything above, as a PDF built to read on a phone the morning of the interview. It costs nothing — we ask for an email so we can send it, and that is all.