How to ask a stranger for a referral (and actually get one)
Asking a stranger for a referral feels presumptuous. It isn’t — referrers get paid (typically $2,000-$10,000) when their referrals get hired, and even when there’s no bonus, employees often enjoy bringing in good talent. The challenge isn’t whether to ask, it’s how to ask in a way that makes saying yes easy. Here’s the structure that converts.
Part of our referral playbook. For warm-relationship asks, see how to ask for a referral on LinkedIn.
The realistic conversion rate
Cold outreach for referrals — to someone who has never heard of you — converts at roughly 8-12% with a strong message, dropping to 1-3% with a poor one. That means: send 10 cold asks, expect 1 referral. Don’t take individual non-responses personally; the volume game is real.
What strangers respond to
1. Specificity about the role
“The Senior Backend role on your team” works. “Any opening” doesn’t. The specific-role anchor signals you’ve done homework and have a real, narrow ask.
2. Quantified relevance
Numbers cut through. “5 years in Go, last 2 years on payments infrastructure at a 4M MAU company” conveys more in 15 words than “experienced backend engineer passionate about distributed systems” does in 60.
3. A specific tie to them
Strangers respond to evidence you’ve looked at them, not just their company. Reference their conference talk, their public PR, their LinkedIn post. One line is enough. Without this, you’re indistinguishable from the 40 other cold DMs they got this week.
4. A small, specific ask
“Refer me” or “flag my application to the hiring manager” are bounded asks. “Help me get a job” is unbounded and ignored. Specificity compresses the social cost of saying yes.
5. An explicit out
“Totally understand if not” or “either way, thanks for considering” lowers the social cost of declining — which paradoxicallyincreases reply rate. People reply to messages they feel they can decline gracefully; they ignore messages that put them on the spot.
The template that puts all five together
Hi [Name] — saw your talk at [conference] on observability at scale. The point about cardinality budgets resonated; I’ve been having the same debate at my current job.
Quick ask: applying for the Senior Backend role on your platform team. 6 years in Go, last 2 years building the observability platform at [current company] (cut MTTR 40%, slashed Datadog spend $1.2M/yr). The JD overlaps almost exactly with my last year. Would you be open to flagging my application to the hiring manager?
Either way, thanks for the talk — it’s informed how we think about our metric retention policy.
Why this works:
- Specific tie to them (the conference talk + a specific point that resonated)
- Specific role (Senior Backend, platform team)
- Quantified relevance (years, metrics)
- Small specific ask (flag the application)
- Explicit out (“either way”)
- Under 130 words
The mistakes that drop conversion to near-zero
Generic openers
“Hi Maya, hope you’re doing well!” signals zero research. The receiver knows there’s a template behind this. Replace the generic opener with something specific from their public profile in the first line.
Listing every skill you have
“I’m skilled in React, Vue, Angular, Node, Python, Go, Rust, K8s, AWS, GCP, Azure...” reads as scattershot. Two or three skills mapped specifically to the JD beat ten skills listed indiscriminately.
Apologising for asking
“Sorry to bother you” signals the ask is unwelcome. Asking strangers for referrals is normal; act like it. (See networking without being pushy for the full tone guide.)
Long preambles
Three paragraphs about your background before the ask. The recipient closes the message before getting there. Lead with the ask; provide context after.
Pure flattery with no relevance
“Your company is amazing and I’d love to work there” without specifics about you or the role is the most-ignored archetype. Add quantified relevance to the JD, or skip the message.
How to pick the right stranger to ask
Order of decreasing leverage:
- Someone on the exact team at your seniority or above. They know if the role is real and what the bar looks like.
- The hiring manager directly, especially at smaller companies. At Series-B and earlier, this is often the most effective channel.
- A senior engineer in an adjacent team. Can flag the application internally even without direct visibility into the role.
- An IC in the broader org. Lower leverage but volume-friendly — many companies allow employees to submit referrals across teams.
Skip: VPs you’ve never met (too senior to engage with cold DMs), former employees (can’t actually submit referrals), anyone whose last activity on LinkedIn is from 2+ years ago (won’t see your message).
Timing
Tuesday-Thursday, 9-11 AM their local time. Send to LinkedIn for cold contacts; cold email has high spam-filter risk and looks more transactional. For the full email-vs-DM decision, see referral email vs LinkedIn DM.
What to do if they say yes
Reply within 4 business hours. Send: a clean PDF resume, the exact JD link, and a 3-sentence pitch they can paste into the internal portal. Make their job zero-effort.
What to do if they say no
Short, warm thank-you. “Completely understand — appreciate you considering it. Best of luck with your work.” Keep the relationship intact; one polite no today becomes a yes later.
What to do if they go silent
One follow-up at 5 business days, one at 14, then stop. See how to follow up.
Doing this at scale
ResumesTailor surfaces real contacts inside target companies (with role + seniority filters), drafts the outreach using your resume and the JD, and tracks responses so you can iterate. Free tier: 3 companies per month.
Related
- The referral playbook
- 12 LinkedIn templates
- Networking without being pushy
- Build a pipeline before you need it
Try ResumesTailor. Build, tailor, and get referred — all in one place. Start free →