In this guide
- Why a Referral Is the Highest-Leverage Move in Job Searching
- How Referral Programs Actually Work at Google, Microsoft, Amazon
- Step 1: How to Find the Right Person to Ask
- Warm vs. Cold Referrals: What's Possible Without Connections
- The LinkedIn Outreach Strategy That Gets Responses
- Message Templates That Actually Work
- What to Send With Your Referral Request
- After You Get the Referral: What Happens Next
- 6 Referral Mistakes That Get Indian Engineers Ignored
- FAQ: FAANG Referrals India
Karan had been applying to Google India for two years through the careers portal. No responses. Not even a recruiter email. He finally found a friend of a friend — Rohan, a senior SWE at Google Bangalore — through a LinkedIn mutual connection. He sent Rohan a message, Rohan referred him, and within two weeks Karan had a recruiter call scheduled.
Two years of applications. One referral. One call in two weeks.
The frustrating part is that Karan could have done this two years earlier. He just didn't know how. This guide is that how.
1. Why a Referral Is the Highest-Leverage Move in Job Searching
The referral advantage has two parts. First, it bypasses ATS screening — referred candidates are often manually reviewed by a recruiter regardless of whether the resume would have passed the automated filter. Second, it signals social proof — the referring employee has implicitly vouched for you, which carries weight in a world where hiring decisions involve significant risk.
2. How Referral Programs Actually Work at Google, Microsoft, Amazon
Google India
Google's employee referral program allows employees to submit a candidate's resume directly into the hiring system with a recommendation note. The recruiter assigned to that role then reviews the referred candidate as a priority. Employees can refer anyone — they don't need to know you personally. They do need to believe you're a credible candidate, because weak referrals reduce their credibility over time.
Microsoft India
Microsoft's referral system is similar. Employees submit your profile through an internal portal and the recruiter receives a tagged notification. Microsoft employees who refer 3+ successful hires per year get additional recognition — the incentive to refer good candidates is real.
Amazon India
Amazon's referral process is slightly more structured. Referred candidates go through the same ATS but are flagged for faster review. Amazon's culture of "bar-raiser" interviews means the referral is less powerful than at Google or Microsoft in terms of bypassing screening — but it still meaningfully improves visibility.
Top Indian Product Companies
Flipkart, PhonePe, Swiggy, CRED, Zepto, Razorpay, and Meesho all have formal referral programs with monetary bonuses (₹25,000–₹1,50,000 depending on role level). At these companies, referrals are extremely powerful — the hiring teams are smaller and internal recommendations carry more personal weight.
3. Step 1: How to Find the Right Person to Ask
The most common mistake: asking the most senior person you can find. Wrong approach. You want someone at the right level in the right team who can credibly say "I've reviewed this person's profile and think they'd be a strong candidate for [specific role]."
-
1Identify the specific role and team you're targeting. Don't ask for a generic "Google SWE" referral. Find a specific job posting, read the team description, and target someone in that team or an adjacent team.
-
2Search LinkedIn for people at that company in your target location. Filters: Current company = [Google/Microsoft/etc.], Location = [Bangalore/Hyderabad], Title contains "Engineer" or "Software." Sort by 2nd-degree connections first.
-
3Prioritize 2nd-degree connections before cold outreach. A mutual connection is a warm signal. You can ask your mutual connection to introduce you. Even a "I'm connected to [X] who I know from [Y]" in your message makes it warmer.
-
4Look for people who are: SDEs (not Directors or VPs), at your target company for 2+ years, active on LinkedIn in the last month. Directors and VPs are harder to reach and often have less visibility into the referral process for individual contributor roles. SDEs know the process, have recent interviewing experience, and are generally more responsive to cold outreach from peers.
-
5Look for IIT/NIT alumni from your college. Alumni networks are strong in India. A shared college is an instant warm connection. LinkedIn's Alumni feature shows exactly which company employees went to your college. Start here before cold outreach.
4. Warm vs. Cold Referrals: What's Possible Without Connections
Warm Referrals (Best)
A warm referral comes from someone who knows you — a former colleague, a classmate, someone you've worked with on a project, someone you've had a genuine conversation with. The referring employee can say "I've worked with this person and can vouch for their technical skills." This carries significantly more weight than a cold referral.
Semi-Warm Referrals (Good)
Someone you share a connection with, someone from your alma mater, someone you've engaged with meaningfully on LinkedIn (commented on their posts, discussed technical topics). You're not strangers, but you don't have direct work experience together.
Cold Referrals (Possible, Lower Success Rate)
Outreach to someone with zero prior connection. This can work, but it requires a very tight, personalized message and a resume that clearly shows you're a credible candidate. Many employees ignore generic cold referral requests. The templates in section 6 are specifically designed for cold outreach.
5. The LinkedIn Outreach Strategy That Gets Responses
Step 1: Optimize Your LinkedIn Profile First
Before you send a single message, make sure your LinkedIn profile is strong. The person you're reaching out to will click it within 10 seconds of receiving your message. If it looks sparse, outdated, or generic, they won't respond — even to a good message.
- Headline: Not "Software Engineer at TCS" — instead: "Backend Engineer | 4 years | Java, Distributed Systems | Targeting FAANG / top product companies"
- Photo: Professional, clear, recent
- About section: 3–4 lines on your stack, experience, and what you're working toward
- Featured section: GitHub profile or a deployed project link
- Experience: Updated with impact-focused bullet points (same as your resume)
Step 2: Send a Connection Request First (Without a Note)
Sending a connection request without a personalized note has a slightly higher acceptance rate than sending one with a note — counterintuitive but well-documented. Once they accept, you can then send a message. This is the recommended approach for cold outreach.
Step 3: Wait for Acceptance, Then Message
If they accept within 7 days, send the referral message (see templates below). If they haven't accepted in 7 days, send a brief, low-pressure InMail. If no response to either, move on. Do not follow up more than once.
6. Message Templates That Actually Work
These templates are designed to be short, specific, and easy to say yes to. The golden rule: make it possible to respond positively in under 60 seconds. If your message requires them to write a long reply, ask clarifying questions, or make a significant time investment, the response rate drops to near zero.
Template 1: Warm Outreach (Mutual Connection)
I came across your profile through [Mutual Connection's Name], who suggested I reach out. I'm a [X]-year backend engineer (Java + distributed systems) currently at [Current Company], and I'm targeting SWE roles on [Google/Microsoft/Amazon]'s [specific team or domain, e.g., payments/infrastructure] team in Bangalore.
I've been preparing seriously for the past [X] months — strong in DSA (solved 200+ LeetCode) and system design. I've attached my resume.
Would you be open to referring me for the [specific role title] role (Job ID: [ID])? No pressure at all — I completely understand if it doesn't feel like the right fit to refer.
Thanks, [Your Name]
Template 2: Cold Outreach (No Prior Connection)
I saw your post on [technical topic they posted about / your work at Company X] — really appreciated your take on [specific point].
I'm a [X]-year SWE with a background in [backend/mobile/infrastructure] and I'm actively targeting SWE roles at [Company]. I've prepared seriously — 200+ LeetCode, strong in system design — and I'm specifically interested in the [team/domain] team.
I know this is a cold ask — would you be open to referring me for the [Job Title] role ([Job ID])? Attaching my resume for context. Completely understand if not.
[Your Name]
Template 3: Alumni Outreach (Same College)
Fellow [IIT Kanpur / NIT Trichy / etc.] alumnus here — I saw you're at [Company] and wanted to reach out.
I'm a [X]-year SWE currently at [Current Company], targeting backend SWE roles at [Company]. I've been preparing seriously and feel ready for the process.
Would you be open to referring me for the [Job Title] position? I've attached my resume — it'd mean a lot, and of course no obligation at all.
[Your Name]
7. What to Send With Your Referral Request
- Your resume (PDF, 1 page). Always attach it in the first message. Forcing them to ask for it is friction. They will often decide in the first message whether to refer you — have your resume there.
- The specific job title and Job ID. The employee needs this to submit the referral internally. Making them find the job posting is friction. Do their work for them.
- Your LinkedIn profile URL. They will check it. Make sure it's up to date before you send anything.
- Optionally: a GitHub or portfolio link. If you have a strong project, a 1-line mention + link can make the difference between a yes and a no.
8. After You Get the Referral: What Happens Next
Once someone agrees to refer you:
- Send a clean, final version of your resume immediately. Don't say "I'll update it and send tomorrow." They are doing you a favor — make it frictionless.
- The employee submits your profile through the internal portal. You don't do anything at this step. Timeline: 1–3 days for submission, 1–3 weeks for recruiter contact.
- A recruiter will reach out via email or LinkedIn. Respond within 24 hours, every time. A recruiter who reaches out twice and gets no response will move on.
- Thank the person who referred you — immediately and again after you get the recruiter call. Even if you don't get the role, a genuine thank you and update maintains the relationship. They may refer you again for a different role, or to a different company.
Got the referral? Now you need to ace the interview.
The referral gets you the call. Prepflix gets you the offer.
DSA prep, System Design, and mock interviews — the complete system. 1,572+ engineers placed. Watch the free training to see exactly how it works.
Watch Free Training →9. The 6 Referral Mistakes That Get Indian Engineers Ignored
- Asking for advice, mentorship, AND a referral in the same message. Every additional ask reduces your response rate. Ask for one thing: the referral. If they want to chat first, they'll say so.
- Generic messages with no personalization. "Hi, I'm an engineer looking to join Google. Can you please refer me?" gets zero responses. The message must include their name, a specific role or team, and at least one signal that you've done your research.
- Asking for a referral before applying through the portal. At some companies (Amazon, in particular), you should apply through the portal first and then ask for a referral to flag your application. Check the company's specific process.
- Sending 50 identical messages at once. This is immediately obvious and signals low effort. Send 5–10 highly personalized messages. Higher quality, lower volume, higher response rate.
- Following up more than once. If someone doesn't respond in 7–10 days, one follow-up is acceptable. Two follow-ups moves you from "aspirational" to "annoying." Move on and target someone else.
- Not being ready to interview immediately. A referral can sometimes move faster than you expect. If you ask for a referral and receive a recruiter call within a week but you haven't done your DSA prep, you've wasted both your time and your referrer's goodwill. Be ready before you ask.
10. FAQ: FAANG Referrals India — Answered Directly
Do I need to know the person in real life to get a referral?
No. The referral system exists precisely because companies know that talent often comes through weak ties — friends of friends, alumni connections, online communities. Many employees at Google and Microsoft have referred people they've only interacted with via LinkedIn. What matters is that you present yourself credibly enough that they feel comfortable submitting your profile.
Will the employee know if I get rejected?
At most companies, referring employees receive a notification when the candidate they referred is hired or if the process is complete. They typically do not receive detailed feedback on why a candidate was rejected. This means the "embarrassment" risk of referring a candidate who doesn't pass is low — but repeated poor referrals can affect their referral reputation internally over time.
Can I get more than one referral for the same role?
Generally no — once one referral is in the system, a second one for the same role doesn't add meaningful value. However, you can get referrals for different roles at the same company simultaneously, or for different companies in parallel.
What if I don't have any LinkedIn connections at the companies I want to work at?
Start building them now. But also: your current company's alumni network, your college network, engineering communities on Twitter/X, Discord servers for DSA and system design, and Prepflix community alumni (many of whom are now at Google, Microsoft, Flipkart, and PhonePe). The network exists — you just haven't mapped it yet.
Pranjal spent 6+ years at Microsoft India and has helped 1,572+ engineers navigate the job search process — from resume to referral to offer. He founded Prepflix to give engineers from service company backgrounds the network advantage and preparation system that product company insiders get by default.