CCareerClutch
← All posts
·13 min read·Nishant Pandey

How to Ask for a Job Referral in India (And Actually Get One)

careerjob-searchcampus-placementsfreshersoff-campus

One message separates a resume that gets read from a resume that never makes it past the ATS. That message is not a cover letter. It is a referral request — sent to the right person, at the right time, with enough substance that they actually respond.

Most students understand referrals matter. They do not understand what makes the ask work. This post covers the full mechanics: what a referral actually does, who to reach out to, what to say, and what to do after they reply — with fully worked messages you can adapt today.

What a referral actually does — and what it does not

Most large Indian tech companies and global MNCs with India offices (Google, Microsoft, Amazon, Flipkart, Swiggy, Razorpay, Meesho, CRED, Infosys BPM, Accenture) have formal employee referral programs. When an employee submits a referral through the internal portal, the application bypasses the standard ATS queue and lands with a recruiter or hiring manager who is specifically responsible for following up on referrals. The referring employee usually gets a bonus — ranging from ₹15,000 at mid-size companies to ₹3 lakh-plus at senior MAANG levels — so they have a real incentive to refer people they think will pass.

What this means in practice: your resume gets read by a human, almost certainly, within a week. For a cold application, that cannot be assumed. At companies that receive tens of thousands of applications per cycle, the ATS filtering rate is brutal. Referrals are not filtered the same way.

What it does not mean: you are hired. You still pass exactly the same rounds as every other candidate. A referral is a door, not a verdict. It gets you into the room; you have to earn everything after that.

That framing matters because it tells you exactly what to promise a potential referrer: I am prepared, my profile is relevant to this role, and you will not be embarrassed by putting my name in.

Why most students get this completely wrong

The default referral message sent by Indian students looks like this:

"Hi sir, I am [Name], final year B.Tech from [College]. I am very interested in joining Google. Can you please help me with a referral? It will mean a lot to me. Please help sir. Thank you."

This message gets ignored — not because the recipient is unkind, but because it asks for a large favour from a stranger with nothing for them to evaluate. The referrer is taking a real risk. If they submit your name and you bomb the first screening, that reflects on their judgment. If they refer ten students who all perform poorly, they lose credibility and sometimes their referral privileges.

The student's message contains:

  • No specific role or team mentioned
  • No evidence of preparation or qualification
  • No context about why they are reaching out to this person specifically
  • Nothing the referrer can use to decide whether this is a sensible ask

Worse, it frames the ask as your benefit ("it will mean a lot to me") rather than framing yourself as someone worth betting on. That is exactly backwards. The referral is for your benefit, yes — but the message has to give the referrer a reason to believe their bet will pay off.

Finding the right person to contact

Before writing a word, you need to find the right person. There is an order of warmth — from easiest to hardest to convert into a reply:

1. College alumni at the company. This is your strongest source. Alumni from your college — especially from your department, one to four years ahead — specifically expect juniors to reach out. Many of them actively want to refer strong juniors. Use LinkedIn's alumni filter: go to your college's LinkedIn page, click "Alumni," then filter by company and graduation year. For a target company, you should be able to find five to fifteen names this way.

2. Someone in your network who can intro you. A mutual connection who can send a quick "hey, a junior from my college wants to reach out to you about a referral" is worth ten cold messages. Check if any of your existing LinkedIn connections work at the company, or know someone who does.

3. Cold outreach to a team member. If you have no alumni and no mutual connections, cold outreach works — but conversion rates are lower. In this case, targeting someone in the specific function you're applying for (backend engineering, data team, product team) rather than someone random is critical. HR or finance people at a company you're applying to for a SWE role cannot give you a meaningful referral.

Before reaching out to anyone, check three things: they are still at the company (look at their current role in the Experience section), they work in a team adjacent to what you're applying for, and you can find one specific, genuine thing to mention — a post they wrote, a talk they gave, the team they're on.

Before/after: what the message should actually look like

Both versions are LinkedIn DMs to a college senior now working at a top product company.

Before:

"Hi sir, I am Priya, final year from NIT Raipur. I want to work at Google. Can you please provide me a referral? It will mean a lot to me. Please help sir. Thank you."

After:

"Hi [Name] — I'm Priya, final year CSE from NIT Raipur. I noticed you're on the backend infra team at Google — I'm targeting SWE roles in a similar space and would love to hear what your first year there looked like, if you have ten minutes.

I've done two internships (one at a Bangalore-based fintech), and I've been seriously prepping DSA and system design for about five months. If you're open to it and my profile seems to fit, I'd really appreciate a referral — but happy to just connect and get your read on my prep first.

My resume and GitHub: [link]"

What changed, and why each change matters:

  • She used their name. "Hi sir" tells the person nothing about whether she looked them up or mass-blasted this to fifty strangers. Using the name costs two seconds and signals she did the work.
  • The first ask is small. "Ten minutes" is easy to say yes to. "Please refer me" is a large favour from a stranger. Lead with the smaller ask; the referral follows naturally once they've talked to her.
  • She named her evidence. Two internships, five months of serious prep. The referrer now has something to evaluate. "I want to work at Google" tells them nothing.
  • She gave the referrer a graceful exit. "If my profile seems to fit" and "happy to just connect" means she is not demanding — she is offering to demonstrate fit first.
  • She included the link in the first message. Making them ask for the resume is friction. Remove friction.

The goal of the first message is not the referral. It is the reply.

Worked examples by role

SDE / backend engineering (targeting a product startup)

Message to an NIT Trichy senior now on Flipkart's backend platform team:

"Hi [Name] — Arjun from NIT Trichy here, graduating this May. I saw you're on the backend platform team at Flipkart, which is exactly the kind of infrastructure work I want to get into.

I interned at a Series-B payments startup last year building the reconciliation backend, and I've been working through system design and distributed systems concepts for the past few months. I'm targeting backend SWE roles and wanted to ask — would you have fifteen minutes to tell me how the interview process there is structured?

If you feel my profile fits and you're open to it, I'd really value a referral. Here's my resume: [link] and GitHub: [link]"

Product / APM roles

"Hi [Name] — I'm Rhea, final year from IIM Indore's IPM program, targeting APM roles at product-first companies. I've been following your posts on product thinking — your breakdown of Zomato's reorder flow was genuinely useful when I was working on my fintech side project.

I've built two products with real users (one is live with ~400 users) and have been practicing PM interview frameworks seriously. Would you have twenty minutes to share what your company's APM hiring process looks for? If you think I'd be a reasonable fit, a referral would mean a lot.

My portfolio brief: [link]"

Data analytics / data engineering

"Hi [Name] — I'm Karan from VIT Vellore, final year CS. I noticed you're on the data team at Swiggy, which is a team I've been researching closely.

I've done two analytics internships and built a customer churn model on real clickstream data as a side project (Python, SQL, GBM — the model found that 65% of churn was in the first 14 days, which I found genuinely interesting). I'm applying for data analyst and junior data scientist roles and would love to understand what your team looks for in fresher hires.

If you have ten minutes and think my profile fits a referral, I'd be very grateful. Resume and project writeup here: [link]"

Consulting / non-tech roles (targeting a Big Four or strategy consulting firm)

"Hi [Name] — I'm Anjali, final year MBA from XLRI. I saw you recently made it to the [Firm]'s strategy practice, which is the track I'm targeting.

I reached the final round of XL-IMIT CaseComp this year (top 8 of 300+ teams) and have been doing structured case prep with a focus on operations and market entry frameworks. I'd love to hear how your firm's laterals round differed from campus hiring, if you have fifteen minutes.

If you think I'd be worth putting forward, a referral would genuinely help. Happy to share my resume in advance: [link]"

What to do after they respond

The worst follow-up move is replying immediately with "so can you submit my referral now?" The person responded because you gave them a reason. Keep giving them reasons.

If they offer a call: take it. Treat it like an informal interview. Research the person before the call — their team, what projects are publicly known, one or two thoughtful questions. Do not spend the call asking about the referral. Ask what their team does, what they looked for in their own hiring process, whether your prep seems on track. At the end, ask naturally: "If you feel my profile makes sense for a role here, would you be comfortable putting me forward?"

What to send them before or after the call:

  • A clean, tailored resume — not your generic one; put the most relevant experience at the top for this specific company and role
  • A short "brief": three to four sentences covering your target role, your strongest project, and one specific reason you want this company

The referrer needs to submit your name, email, and sometimes a sentence or two about why they're recommending you through an internal portal. The easier you make that, the faster it happens. Send them exactly what they need to fill that form; do not make them assemble it from memory.

Common mistakes — and how to fix each

Mistake 1: Leading with the referral ask

Asking for a referral in the opening message tells the person you care about the outcome, not about them. It makes the interaction feel transactional before any trust exists. Lead with a genuine question — about their experience, their team, what the interview process is like. The referral becomes a natural conclusion, not a cold opener.

Mistake 2: Mass-blasting a templated message

A message that starts "Dear sir/ma'am" or uses your college name as the only personalisation signals immediately that this is blast number 47. Interviewers and working professionals see hundreds of these. Sending ten personalised, researched messages will produce more replies than sending a hundred generic ones. Personalisation is not optional.

Mistake 3: Not including your resume or profile link

The person who might refer you needs to evaluate whether that is a sensible bet. Sending a request with no link to your resume or LinkedIn makes it impossible. Include the link in the first message. Don't make them ask for it.

Mistake 4: Targeting people outside your function

If you are applying for a backend SWE role, reaching out to someone in HR, design, or finance at that company gets you a low-quality referral at best. Someone in those functions cannot evaluate your technical profile, cannot vouch for you in any meaningful way to the engineering team, and has less incentive to put you forward. Target people working in the same function — backend engineering, data science, product — even if that makes the list shorter.

Mistake 5: Giving up after one unanswered message

A LinkedIn DM from a stranger often gets buried. A polite follow-up seven to ten days later is completely acceptable and expected. Keep it brief: "Hi [Name] — just bumping this in case it got lost. No pressure at all — hope the week's going well." One follow-up is fine. Two is the maximum. After that, move on; chasing does more harm than good.

Mistake 6: Not thanking them regardless of outcome

If someone responds, takes a call, or even declines politely — send a thank-you. Word travels in alumni networks. The senior who could not refer you this season might introduce you to someone else next month, or recall you positively when a new opening comes up. The students who treat professional courtesies as transaction-dependent are the ones who stop getting replies.

What to do this week

Day 1. Run the LinkedIn alumni search. Go to your college's LinkedIn page, click "Alumni," and filter by each of your five target companies. Write down five names per company — people who graduated one to four years ahead of you, working in a role similar to what you're applying for. That gives you a list of twenty-five candidates.

Day 2. For each name, spend two to three minutes: confirm they're still at the company, note what team they're on, find one specific genuine thing you can mention. Do not start writing messages yet.

Day 3–4. Write your five best personalised messages — one per company, to the person on your list most likely to respond. Do not send twenty messages at once. Quality over quantity: one good message per week is a better rate than five generic ones per day.

Day 5. Before hitting send, check your LinkedIn profile. A clear headline ("Final Year CS — Backend SWE | 2 Internships"), your best projects described with outcomes, and a profile photo. The first thing they will do after reading your message is click your name. If your profile is a rough draft, the message means nothing.

Send five messages. Set a reminder for ten days out to follow up on any that haven't replied. That is the whole system.


The referral gets your resume seen by a human. Everything that follows — the OA, the technical rounds, the interview itself — is on you. If you want to make sure your interview prep is actually ready before you start sending those messages, CareerClutch's mock interview tool lets you practice role-specific rounds and get specific feedback on what is working and what isn't — so when a recruiter calls after a referral lands, you are prepared to follow through.