A referral increases your interview callback rate by 4-6x at Amazon and Google, but most candidates sabotage themselves with lazy, copy-paste emails that get ignored. The difference between getting a referral and getting ghosted comes down to three things: finding the right person, writing a 72-word email that does the work, and timing your ask when the person actually reads their inbox. This article gives you the exact template, the psychology behind why it works, and the five mistakes that kill your referral request before the recipient even finishes your subject line.
This is for senior engineering managers, staff engineers, and EM candidates with 5+ years of experience who are targeting roles at Amazon, Google, or similar FAANG companies and want to skip the black hole of online applications. You're not looking for generic job search advice—you want the specific tactics that work in engineering organizations where referral bonuses incentivize employees to help you, but busy tech leads still won't respond to 90% of the emails they receive.
What Makes Referral Request Emails Effective at Amazon and Google
The problem isn't that people don't want to help you. The problem is that your email looks like every other email in their inbox.
In a 2023 debrief I ran for a Google hiring committee, we discussed why one candidate's referral request got a response in 45 minutes while another sat unread for three weeks. The successful candidate had worked at the same company as the referral source four years prior. The unsuccessful candidate had 40% more experience. The difference was a single line in the subject line: "We worked together on the Payments infra migration at Stripe."
Not X: A generic "Referral request for Google L5 EM role."
But Y: "Quick favor — Stripe infra work together? Google EM role."
The psychology here is identity activation. When someone sees a name or project that connects to their own professional story, their brain treats it as personally relevant. Generic requests get filtered into the same mental bucket as recruiter spam. Specific, identity-linked requests trigger a micro-moment of curiosity that gets your email opened.
Amazon's culture amplifies this. Bar Raisers are trained to look for signals of genuine connection, and a referral email that reads like a template tells them the candidate has no real relationship with their company. A referral that arrives with specificity tells a different story.
How Do I Find the Right Person to Ask for a Referral
Your first instinct is probably to find someone who works at the company you want. That's correct, but incomplete.
The real question is: who has incentive, time, and enough context about you to write a strong referral?
At Amazon, referral bonuses typically range from $2,000 to $10,000 for engineering roles, with EM roles often at the higher end. This means employees have real financial incentive—but only if the referral results in a hire. Someone who barely knows you won't write a referral that survives Amazon's Bar Raiser interview, because they can't speak to your actual competencies.
Not X: Finding any warm body at Google or Amazon who might respond.
But Y: Finding someone who can credibly advocate for your specific EM skills.
Here's the hierarchy of who to contact:
- Former colleagues who now work at your target company
- People who worked at your current/previous company and moved to the target
- Conference or meetup contacts who work at the target
- LinkedIn connections with 2nd-degree connections at the target
- Alumni from your university who work at the target
The key move is using LinkedIn's "People also viewed" and mutual connections features to find people who share your professional background. If you built distributed systems at scale, find the Google SRE who used to work at your company. If you led platform teams, find the Amazon manager who moved from your industry vertical.
What Should I Include in My EM Interview Referral Request Email
The email should be 72 words maximum. Anything longer signals that you don't respect the recipient's time.
Here's the exact template that works:
Subject: [Specific shared connection or project] + [Role target]
Body:
Hi [Name],
This is [Your name] — we worked together on [specific project or at specific company]. I'm targeting [L6 Staff EM / L5 EM / etc.] roles at [Google/Amazon] focused on [specific domain: distributed systems, platform, etc.].
If you're open to it, I'd love a 15-minute call to learn more about your experience. Happy to work around your schedule.
Happy to send along my background doc if helpful.
[Your name]
That's it. No attachment. No 200-word paragraph explaining your career trajectory. No "I would be honored" language.
The reason this works: it respects the asymmetry. You're asking for a favor that costs them time and carries risk (their reputation is on the line with any referral). The email signals that you understand this by being ruthlessly concise.
Not X: "I am a highly accomplished engineering leader with 12 years of experience..."
But Y: "I'm targeting L6 EM roles focused on platform engineering."
At Google, the referral form asks the referrer to rate their confidence in your ability to do the job. A 15-minute call where you can articulate your target role and relevant experience gives them the ammunition they need to write a strong referral. Without that call, you're asking them to stake their credibility on a stranger's LinkedIn profile.
When Should I Send My Referral Request Email
Timing is not random. It follows patterns.
In my experience running debriefs at two FAANG companies, the best days to send referral emails are Tuesday through Thursday. Tuesday at 9:30 AM has the highest open rate for professional emails, followed by Thursday at 3:00 PM when people are mentally checked out but still processing their inbox.
The worst days are Monday (inbox backlog), Friday (mental weekend), and any day after a company all-hands or major announcement.
Not X: Sending whenever you remember and then forgetting about it.
But Y: Scheduling your send for Tuesday 9:30 AM and following up Thursday at 4:00 PM.
For EM candidates specifically, avoid sending during end-of-quarter crunch periods. At Amazon, Q4 close (October and December) means L7+ managers are deep in planning cycles. At Google, the weeks before I/O and major product launches create similar black holes.
The sweet spot is typically mid-quarter: late January to mid-February, late April to mid-May, late July to mid-August, and late October to early November. These periods have the highest referral activity because teams are building headcount plans for the next quarter.
How Do I Follow Up Without Being Annoying
You follow up exactly once. If they don't respond to the follow-up, you move on.
The follow-up email should arrive 4 business days after the initial send. No sooner, no later. Four days signals respect for their time (you're not sitting by your inbox waiting) while maintaining urgency (you're not letting this sit for two weeks).
Here's the exact follow-up template:
Subject: Re: [Original subject]
Body:
Hi [Name],
Just following up on my note below — no pressure if the timing isn't right. If you'd find it helpful, I'm also happy to share my background doc upfront to save you any back-and-forth.
Thanks for your time regardless.
[Your name]
Notice what's absent: no "Just checking in!" no "I know you're busy but..." and absolutely no guilt language. You're offering a path forward (sharing your background doc) that makes their job easier, not guilt-manipulating them into responding.
At Amazon, I watched a hiring manager reject a candidate's referral because the candidate had sent four follow-ups over two weeks. The manager's feedback: "If someone's this pushy before I even know them, I don't want them on my team." The referral process is a preview of how you'll behave as a colleague.
How Do I Know If My Referral Was Actually Submitted
The answer is uncomfortable: you often don't, until you get an interview invite.
Most companies don't notify candidates when a referral is submitted. At Google, the ATS (Greenhouse) sends an automated "referral submitted" notification to the candidate, but only if the referrer checks the box to CC them. Many employees don't, because they forget or assume the system handles it.
At Amazon, the Workday ATS is more opaque. You might receive no notification at all.
Not X: Sending multiple emails asking "Did you submit my referral?"
But Y: Sending one check-in two weeks after the referral conversation: "Hi [Name], just wanted to let you know I submitted my application. No need to update me — just wanted to make sure we're aligned."
If you don't hear anything for 3-4 weeks after your application, it's reasonable to ask once: "Did the referral go through?" But frame it as confirming logistics, not demanding status.
Building Your Interview Toolkit
- Identify 5-10 potential referrers using the LinkedIn mutual-connection method, prioritizing former colleagues over generic network contacts
- Draft your 72-word email using the template above, customizing the subject line with a specific shared experience or project
- Research the target role's level requirements (L5 vs L6 EM at Google, L6 vs L7 at Amazon) to ensure you're asking for the right referral
- Time your initial send for Tuesday at 9:30 AM using a scheduling tool
- Prepare a one-page background doc that your referrer can use as a reference when filling out the referral form
- Set a calendar reminder to send your follow-up exactly 4 business days later
- Work through a structured preparation system (the PM Interview Playbook covers referral strategy and ATS optimization with real candidate debrief examples)
- Practice your 15-minute referrer call using the STAR method for your three most relevant EM accomplishments
Blind Spots That Sink Candidacies
MISTAKE 1: Using a template with no personalization
BAD: "Dear Hiring Manager, I am writing to inquire about EM opportunities at your esteemed organization. My name is [X] and I believe I am an excellent fit..."
GOOD: "Hi Sarah — we overlapped on the Cassandra migration at Netflix in 2019. I'm targeting L6 EM roles at Google focused on infrastructure..."
MISTAKE 2: Asking without offering value
BAD: "I'd love to pick your brain about opportunities at Amazon. Are you free for a coffee chat?"
GOOD: "I'd love to hear your perspective on the platform org. Happy to share what I've learned about scaling EM organizations if that's useful to you."
MISTAKE 3: Following up more than once
BAD: Sending a follow-up every 3 days for two weeks, then a "final" follow-up, then a LinkedIn DM, then an "I see you're active on LinkedIn" message.
GOOD: One follow-up at 4 business days. Silence after that means move on.
FAQ
Q: Does it matter which team or org I ask for a referral for within Amazon or Google?
Yes, but not in the way you think. Your referral gets routed to the hiring manager of the team that has open headcount, not the team your referrer works on. However, asking for a referral into a specific team signals that you've done research and have genuine interest. A generic "any EM role" referral tells the hiring manager you might not actually want to work on their specific problems.
Q: Should I include my resume in the initial referral request email?
No. The email's job is to get a response, not to deliver your entire career history. If the recipient wants your resume, they'll ask. Attaching it unprompted signals that you're trying to do the referrer's work for them—which is backwards. The referrer's job is to advocate based on their personal knowledge of you, not to forward a PDF.
Q: What's the realistic timeline from referral submission to first interview?
At Google, the typical timeline is 2-3 weeks from referral to recruiter screen, assuming the referral is reviewed within the first week. At Amazon, it's 1-2 weeks to recruiter contact, followed by a 30-minute phone screen scheduled within 2 weeks. If you haven't heard anything 4 weeks after the referral, it's reasonable to check in once with both the referrer and the recruiter.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.