Why referrals change the math entirely
Referred candidates are hired at 4x the rate of cold applicants. They're twice as likely to get an interview, and they move through the process faster. At companies like Google, Meta, and Stripe, internal referrals bypass the initial ATS screening entirely — the resume goes directly to a recruiter's queue marked as a referral.
Most engineers know referrals matter. Most engineers don't pursue them because they don't know how to ask someone they've never worked with for one — without it feeling transactional or awkward.
Here's the exact approach that works. It's not about being connected. It's about being specific, useful, and low-friction for the person you're asking.
What a referral actually is (and isn't)
A referral is not a guarantee. It's an introduction that gets your resume into a different, higher-priority pile. The referrer is typically submitting your resume through an internal portal with a brief note. At most companies, they don't need to vouch for your work — they just need to believe you're a credible candidate worth introducing.
This distinction matters because it lowers the bar significantly. You don't need someone who knows your work deeply. You need someone who believes your background makes you a plausible fit for the role and is willing to spend 5 minutes on the internal portal.
Step 1: Find the right people to contact
Your goal is to find engineers or engineering managers at the target company who work in the same area as the role you're applying for. Not the CEO. Not a recruiter. Not someone in sales. An engineer or EM in the relevant team.
The best sources:
- LinkedIn — search "[Company Name] Software Engineer" or "[Company Name] Engineering Manager." Filter by 2nd-degree connections first. If none, 3rd-degree or no connection is fine.
- GitHub — look at contributors to the company's public repositories. Engineers who contribute to open-source projects are often more receptive to outreach from other engineers.
- Tech Twitter/X — engineers who post publicly about their work at a company are signaling openness to the community. A thoughtful reply to their post is a warmer entry than a cold LinkedIn message.
- Company engineering blog — authors of technical blog posts are visible, credible, and often open to discussion.
Find 3–5 people per company. You won't get responses from all of them — that's fine.
Step 2: Do your homework before reaching out
Before you send a single message, know:
- The exact role you're applying for (title, team, job ID if visible)
- One or two specific things about this person's work — a project, a blog post, a talk, a GitHub contribution
- Why you're a credible fit for the role in 2 sentences
This preparation is what separates a message that gets a reply from one that gets archived. Generic outreach ("I'm interested in working at Company X and saw you work there") is immediately recognizable and easy to ignore. Specific outreach is rare and actually interesting to receive.
Step 3: Send a message that's easy to say yes to
The message needs to do three things: establish relevance, be specific about what you want, and make the ask as low-friction as possible.
Here's the template that works:
Hi [Name],
I came across your post on [specific topic / your GitHub work on X / your talk at Y]. [One sentence that shows you actually engaged with it — not a compliment, a specific observation.]
I'm a [seniority] [role] with [X years] of experience in [relevant area]. I'm applying for the [exact role title] role on [team if known] and was hoping to connect.
If you have 15 minutes for a quick call, I'd love to hear what the team is like. Alternatively, if you think my background makes sense for the role, I'd really appreciate a referral — no pressure at all if that's not something you're comfortable with for someone you haven't worked with.
[Your name]
[Link to LinkedIn or portfolio]
Key elements of this message:
- "No pressure at all" — lowers the social cost of saying no, paradoxically making yes more likely
- Specific role title — signals you've done your homework and aren't mass-messaging everyone
- Two options — a call or a referral. Either one works for you. They can choose whichever is easier
- Under 150 words — respects their time. If it's longer, cut it
Step 4: The call (if they agree to one)
If they agree to a 15-minute call, this is not a job interview. Don't pitch yourself. Ask genuine questions about what the team is working on, what the engineering culture is like, what they look for in the role. Listen more than you talk.
Near the end, if it's been a good conversation: "Based on what you've described, I think my background in [X] would be a real fit. Would you be comfortable submitting a referral?"
Most people who agree to a call will agree to the referral if the conversation was good. You've now moved from a cold applicant to someone they've talked to.
Step 5: Make it easy for them to refer you
When they agree, send them everything they need in one message:
- The exact job ID or URL
- Your updated resume (tailored for this role)
- 2–3 sentences they can paste into the referral form about why you're a fit
That last point is underrated. Many referral forms ask the referrer to describe why the candidate is strong. Writing that blurb yourself — so they just have to paste it — removes the main friction point. Make it factual and specific, not generic praise.
What to do if you truly know no one
Cold outreach works — but it takes more messages to get the same number of responses. Three ways to warm it up:
Engage before you ask. If you find engineers from the target company on Twitter/X or LinkedIn who post publicly, engage with their content (thoughtfully, not just "great post!") for 2–3 weeks before reaching out. You're not a stranger anymore.
Contribute to their open-source. If the company has a public repo, even a small, genuine contribution — a documentation fix, a bug report with a proposed fix — gets your name in their codebase. Mentioning this in your outreach is concrete and memorable.
Attend their events. Many engineering teams host meetups, conference talks, or online AMAs. Showing up and asking a good question is a legitimate warm introduction.
Pair the referral with a strong application
A referral gets your resume into the right pile. It doesn't guarantee it passes. If your resume scores below 70% against the job description in the company's ATS, even a referred application may not move forward.
Before you ask anyone for a referral, run your resume against the job description using Applyr's free ATS checker. Fix the keyword gaps first — so when your referral puts you in front of a recruiter, your resume is ready to close the deal.
The combination of a referral (bypasses the initial filter) and a high-scoring resume (converts the recruiter view into an interview) is what actually gets you in the room.
→ Check your resume score before your referral goes in
See your ATS match % and keyword gaps — free, 8 seconds.