To ask for a job referral that gets acted on, ask someone who can speak to your work, tie the ask to one specific posting, send the job link and your resume in the same message, and write the two or three lines they will paste into the referral form so they do not have to. Ask before you apply, not after. That is most of it. The rest of this post covers why referrals are worth the effort, who to ask in what order, three messages you can adapt for a friend, a former colleague and a cold connection, and what to do once they say yes.
Why referrals matter, in numbers
The best evidence comes from employers' own hiring records. All of it is either old or comes from a company with something to sell, so the dates and caveats are in the table.
| Source | Finding | Caveat |
|---|---|---|
| New York Fed Staff Report 568 | Referred candidates were "more than twice as likely to be interviewed and, conditional on interview, about 40% more likely to receive an offer" than job board applicants | One large US corporation, employee records 2000 to 2011. The authors make no causal claim |
| Same study | Referred candidates were 6% of applicants, 21% of interviewees, 27% of offer recipients and 29% of hires | Same company |
| Burks, Cowgill, Hoffman and Housman, Quarterly Journal of Economics, 2015 | "Referred applicants are more likely to be hired and more likely to accept offers" | Nine large firms in call centers, trucking and high tech |
| LinkedIn Labor Market Report, January 2026 | "Applicants are 3.6x more likely to get hired if they are connected to an employee on LinkedIn" | LinkedIn platform data, no method stated for this figure |
| SHRM on Lever data, 2016 | "1 in 16" referrals hired, against 1 in 152 applicants from careers sites and postings | August 2015 to July 2016, about ten years old |
Compare that with cold applications. In the same New York Fed study, 6.0% of job board applicants were interviewed. Ashby's 2026 report puts the interview rate on its customers' applications at 3.6% for technical roles and 4.7% for business roles.
Two things follow. A referral is the strongest single lever a job seeker has, and it is also expensive: it costs your contact time and some reputation, so you will make a handful of asks for every few dozen applications. Our job search strategy guide sets out how to run both tracks in the same week.
Employers want referrals too. At the company in the New York Fed study, an employee whose referral led to a hire received a bonus for many positions, ranging from $500 to $4,000 between 2000 and 2011, with a mode of $1,000. GitLab's handbook describes a referral bonus for its employees today. You are asking a favor, but often one your contact is paid for.
Who to ask
Not every contact can give you a referral, and the employer decides what counts. GitLab publishes its rules in its hiring handbook, which makes it a useful example of how a formal program draws the line:
- A referral is "someone you have worked with in the past, or have developed a close personal relationship with."
- An endorsement is a weaker recommendation for someone who has already applied, such as an acquaintance or "friend of a friend" the employee "can't speak to" in terms of character or skills.
- Cold outreach: if someone the employee does not know asks to be referred, GitLab tells employees to say they are "unable to refer them due to our referral policy" and to encourage them to apply directly.
Other employers set different rules, but the logic is common: a referral is a statement from someone who knows you. That gives a natural order of who to ask.
| Order | Who | Why |
|---|---|---|
| 1 | Former colleagues and managers who saw your work | They can make a real referral and describe what you did |
| 2 | Friends, classmates and people who know you well | They can vouch for you, if less for your work |
| 3 | Alumni and second-degree contacts | Start with a conversation, then ask |
| 4 | Employees you have never met | Ask for information or an endorsement, not a referral |
The New York Fed study also found that "most referrals take place between a provider and a recipient with similar characteristics," including the same division and staff level. In practice, the best person to ask is often someone who does the job you want, or did it with you. Building those relationships before you need them is the subject of our networking tips for job seekers.
Before you ask anyone, check that you fit the role. GitLab tells its employees that candidates "don't need to meet all requirements" but that "alignment with the majority is essential." A contact will hesitate to refer you to a job you plainly do not fit, and asking puts them in an awkward spot.
Message: someone you know
Use this for a friend, a classmate or anyone who knows you personally but has not worked with you. Keep it to one message with everything in it.
Subject: Referral for [Role] at [Company]?
Hi [Name],
Hope [something specific: the new house, the marathon, the new team] is going well.
I'm applying for [Role] on the [Team] team at [Company]: [job link], job ID [number]. It's close to what I do now at [Current employer], where I [one result with a number].
Would you be comfortable referring me? I've attached my resume and written a short blurb below that you can paste into the referral form. If you don't know the team or would rather not, no problem at all, and I'd still love ten minutes on what it's like to work there.
Blurb: [Your name] has [X] years in [field], most recently [role] at [employer], where [result]. They have worked with [two or three of the posting's required skills]. We know each other from [how].
Thanks, [Your name]
Why it works: the posting is named, so they do not have to search for it; the resume and blurb are attached, so the referral takes them minutes; and there is an easy way to say no.
Message: a former colleague
A former colleague can make the strongest referral, because they can describe your work. Remind them of it. Name the project and what you did.
Subject: [Role] at [Company], would you refer me?
Hi [Name],
It's been a while since we worked on [project] together at [Company] in [year]. I still use [something you learned from them or did together].
I saw [Company] is hiring a [Role] ([job link], job ID [number]) and it lines up closely with what we did on [project]: [one sentence on the match].
If you're comfortable with it, would you refer me? You've seen my work first hand, which I think would carry more weight than my application alone. I've attached my resume, and here are three lines you could use:
[Your name] and I worked together on [project] at [Company], where they [specific contribution with a number]. They are strong at [skill from the posting]. I'd work with them again.
Happy to jump on a quick call if it's easier. Either way, it would be good to catch up.
[Your name]
If you have lost touch for years, send a short catch-up note first and make the ask a few days later. It reads less transactional.
Message: a cold connection
With someone who does not know you, a direct referral request will often get a polite no, and at some employers it has to. Ask for something smaller first: fifteen minutes or a single question. Make the referral question a second step, once they know something about you. Have a short elevator pitch ready for that first call so they learn the essentials quickly. LinkedIn added an "Ask for a referral" option to job postings in 2018, but it is built around people you are already connected to.
First message:
Hi [Name],
I'm a [your role] at [employer] and I'm looking at the [Role] opening on your team at [Company] ([job link]). I noticed you [something specific: wrote a post on X, moved from a similar role, studied at the same school].
Could I ask you one question about the team? What does the [Role] spend most of the first few months on? Or, if you have fifteen minutes this week or next, I'd be grateful for a quick call.
Thanks, [Your name]
After a useful conversation:
Thanks again for the time yesterday, [Name]. What you said about [specific point] made me more sure the role fits: [one sentence].
I'm planning to apply this week. If you felt comfortable passing my application to the recruiter, or referring me if your process allows it, I'd be grateful. If not, I completely understand, and the call alone was very helpful. My resume is attached in case it's useful.
[Your name]
The second message offers two versions of help, so they can pick the one their employer's rules allow.
After they say yes
The referral is only as good as the paperwork behind it. Make it easy and make sure it is recorded.
- Send everything in one place. The job link and ID, your resume as a PDF, your LinkedIn URL, the blurb, and your location and email as you want them on the application. GitLab's internal instructions for entering a referral list the candidate's first and last name, email, a social media link such as LinkedIn, relationship to the referrer and location as required, and its handbook recommends "uploading a current version of the candidate's resume".
- Let them submit before you apply, or apply through their link. In Greenhouse, the employee who submits a referral is automatically set as the referrer. GitLab treats a candidate who has already applied and whose application "has been reviewed and progressed" as an endorsement rather than a referral. Ask your contact which route they use, and follow it.
- Tailor the resume to the posting. The referral gets you a look, not a pass. Lead with the experience that matches the posting, and use its words for skills you actually have. Our guide to tailoring a resume has the method.
- Watch your email. Some employers' systems will ask you to complete or confirm an application after a referral is entered. Whatever arrives, act on it the same day.
- Follow up once, after about a week. GitLab says referrals can be expected to be reviewed by the hiring team within 5 business days. Other employers are slower. A short note to your contact is fine; do not ask them to chase the recruiter more than once.
- Do not expect feedback through your contact. GitLab's handbook states that its talent team "is unable to provide candidate-specific feedback to Referrers." Your contact may know no more than you do.
- Close the loop. Thank them whatever happens, and tell them how it turned out. At GitLab, a referral counts for 6 months within the same job family, and the handbook asks employees to "stay in touch with your referrals if you want to refer them in the future." The same contact may refer you again.
Mistakes that waste a referral
- Asking for a "general" referral. Many programs need a specific requisition. GitLab's handbook says plainly that "general referrals are not accepted."
- Asking for a role you do not fit. It costs your contact credibility, and they will remember.
- Sending the same message to ten people at one company. Often only one referrer is credited. At GitLab, "the first Team Member to have submit the candidate will be considered their Referrer." Pick one person per employer.
- Leaving the work to them. No link, no resume and no blurb means the referral waits until they find time, which may be never.
- Overstating your skills in the blurb. List only skills you can discuss in an interview. The referral gets you into the room, and the interview tests every line.
Where ApplyEze fits
ApplyEze does not replace referrals. It handles the cold-application side of a search: it matches postings to your target roles, writes a resume and cover letter for each one, and completes applications on 12 platforms, including Greenhouse, Lever and Ashby, in a visible browser on your own machine. Use it for volume, and spend the time it saves on the handful of referral asks that matter most. Keep the postings you have been referred to out of any automated queue, so the referral is the application on record. Our post on the hidden job market covers why both tracks matter, and how many applications it takes to get a job covers the volume side.