Blog / Candidates

How to Write a Referral Request That Actually Gets a Response

The person reading your request is a real employee putting their own name on the line for you. What you write is the only thing they have to decide whether that's worth doing.

A referral request on HuntYourPath is short by design — a target company, a target role, and a few words about you. That brevity is easy to waste. Here's what actually moves someone from scrolling past to hitting "offer to help."

Be specific about the role, not the company

"I want to work at Google" tells a referrer nothing they can act on — which team, which role, why you. "Backend engineer on a payments or infra team" gives them something to actually match against what they know is open. Specificity reads as someone who's done the homework, not someone mass-requesting every big name.

Say why this company, briefly and honestly

You don't need a cover letter's worth of reasoning. One real sentence — why this company, why now — does more than three generic ones. Referrers are putting their own credibility behind you; a request that reads like it could've been sent to fifty other companies unchanged doesn't give them much to stand on.

Lead with what's relevant, not everything

The "a few words about you" field isn't your whole resume. Pick the one or two facts that actually matter for this specific role — years in the domain, a relevant project, the thing that makes you a real fit rather than a generic applicant. If it doesn't help someone decide whether to vouch for you, leave it out.

Remember it's a request, not a demand

A referral is a favor someone is choosing to extend, not something owed to you for having posted. The requests that get responses read like they understand that — specific, honest, and respectful of the fact that a real person is about to spend their own social capital on your behalf.