Most people struggle to ask for developer referrals because they ask for too much, too early. The best approach asks for guidance first and shares proof of work. The referral ask comes only once fit is clear.
Here it is as three rungs. Good is a personalized message. Better is a guidance-first sequence with two scripts. Best adds a follow-up cadence and a plan for when someone says no.
Table of Contents
- Good: personalize every message in 60 seconds
- Better: ask for guidance before the referral
- Best: follow up on a schedule and learn from a no
- Which rung fits your situation
- FAQ
- Reliable resources
- Related guides in this series
Good: personalize every message in 60 seconds
Before sending any message, include these three specifics:
- Why this company/team (product, tech stack, mission)
- Why this role matches your current skills
- One link proving your work quality (project/case study)
Those three specifics improve the quality of the replies you get.
Do:
- Personalize every message
- Keep messages short
- Show proof of work (GitHub/demo)
Don’t:
- Spam multiple people at the same company
- Send generic copy-paste messages
- Ask for a referral before showing fit
What it buys: a message that reads as written for one person. What it costs: about 60 seconds of research per message.
Better: ask for guidance before the referral
Follow this sequence:
- Ask for guidance first
- Share relevant project proof
- Ask for referral only if fit is clear
Script: first message
“Hi
Script: referral ask (follow-up)
“Thanks for the guidance, it helped a lot. I updated my resume/project based on your advice and applied to
What it buys: the referral ask arrives after the person has seen your work and given advice. What it costs: two messages, and time to act on their advice in between.
Best: follow up on a schedule and learn from a no
Use this cadence:
- Day 0: Initial short message
- Day 4-5: Value-add follow-up (updated project link or short insight)
- Day 10: Final polite follow-up
If there’s no response after that, move on professionally.
If they say no, ask one question: “What would make my profile stronger for your team in the next 4-8 weeks?”
That answer gives you practical direction and can reopen the conversation later. What it buys: every contact ends with either a referral, feedback or a clean close. What it costs: up to 10 days per contact, and you need something new to share on day 4-5.
Which rung fits your situation
| Situation | Use |
|---|---|
| You’re writing any outreach message | Good: the three specifics |
| You haven’t shown this person your work yet | Better: ask for guidance first |
| They gave advice and you’ve acted on it | Better: the referral ask script |
| No reply after your first message | Best: the day 4-5 and day 10 follow-ups |
| They said no | Best: ask what would make your profile stronger |
FAQ
When should I ask for a referral?
Only once fit is clear. Ask for guidance first and share relevant project proof. Then ask for the referral.
How many times should I follow up on a referral request?
Twice. Send a value-add follow-up on day 4-5 and a final polite one on day 10. If there’s no response after that, move on professionally.
What should I do if someone says no to a referral?
Ask what would make your profile stronger for their team in the next 4-8 weeks. It gives you direction and can reopen the conversation later.