Ask for referrals with context
A short guide to finding relevant contacts, making a clear ask, and tracking replies.
A referral can help someone notice your application, but it cannot guarantee an interview. Start with a role that fits your eligibility, then ask a relevant contact with a short, specific message.
Choose who to contact
Look for an engineer who works near the team or product you are applying to. A shared school, open-source project, meetup, or technical interest can give you a natural reason to write. Do not assume someone's title or seniority tells you whether they can refer.
Send a clear message
Include your name, the exact role, one relevant piece of evidence, and a low-pressure question. Use this draft as a starting point:
Hi [name], I’m a final-year CS student graduating in 2027. I’m applying for [role link]. I built [specific project result] using [relevant skill], which seems close to [role requirement]. Would you be comfortable sharing advice or referring me if you think the fit makes sense? I can send my resume and any details you need. Thanks either way.
Personalize the first sentence. Do not claim a match you cannot explain. Share your resume only when the person asks or when the referral process needs it.
Follow up once
If there is no reply, wait about a week and send one short follow-up. Then move on. A quiet inbox does not tell you why someone did not respond.
Track the outcome
Use one row per conversation. Track the date, role, person, channel, response, referral status, and application outcome. Review your own response patterns monthly; there is no reply rate that every job search should expect.
Do and don't
- Keep the request specific and easy to decline
- Connect your evidence to one requirement in the role
- Respect the person's time and privacy
- Thank them, even if they cannot help