The Referral Request Run, From Matched Employee to a Logged Source

This is the run for getting a real employee referral onto as many of your live postings as possible, in the right order, without the application being logged as a cold apply or costing your referrer their credibility. It is for job seekers working many employers at once, not one dream company. For each posting it gives you a refer-first or apply-first call, a packet you can paste, a check that the referral source actually logged, and a repair path for when it did not.

What does a referral actually buy you?

A referral mostly buys you a recruiter's review. Referred applicants get interviewed at roughly 2.2 times the rate of job-board applicants, and the gap after the interview is much smaller. So the most important thing is getting the referral source recorded on your application. What the vouch says matters less.

The benchmarks below come from different datasets with different denominators. Read each row on its own, and do not multiply rows together.

In the same Fed study, referred candidates who reached an interview had an offer rate 14 percentage points higher. That is real, but it is a smaller edge than doubling your odds of being looked at in the first place. Gem's benchmark set, covering 165 million applications and 1.2 million hires, puts the referral-to-hire conversion at 11 times that of inbound applicants.

What is not established: nobody has published funnel figures that separate a strong vouch from a weak networking lead. If you see a claim that a close-colleague referral converts at some specific multiple of an acquaintance referral, ask where it came from.

A referral buys a recruiter's review. If the source field still reads direct, the referral bought you nothing.

How do applicant tracking systems record a referral source?

An applicant tracking system (ATS) is the software an employer uses to receive and track applications. In most of them, a referral is a separate record that has to attach to your application. It is usually matched by email address and tied to one requisition. A requisition ID is the employer's internal number for a single opening, usually shown on the posting page or in its URL. When two records for the same person merge, the older one generally survives, so whichever action happened first tends to set your source.

No vendor documents "first action wins" as a rule. It is what happens by default when the oldest record survives a merge. Each employer can also configure its own system, so treat what follows as defaults and not guarantees.

• Greenhouse. The employee who submits a referral is automatically recorded as your referrer, and recruiters can manually reassign the source and credit (the "Who Gets Credit" field). With Auto-merge turned on, Greenhouse keeps the oldest candidate profile, and merges cannot be undone.
• Lever. Candidate records merge when email addresses match.
• Workday. Employers can set it to block a referral if the candidate has already applied to that requisition. It also supports endorsements: if the hiring team accepts an endorsement request, Workday creates a referral record. A referral made through Refer a Candidate only counts once its business process event is complete.
• SuccessFactors. After a merge, referral data is combined into the master profile.
• Cornerstone. The employer sets how long referral credit lasts, in calendar days. Applications after that window lose the referrer.

Which system will you hit most?

In Refolk's index of professional profiles, recruiter skill tags show which systems the people screening you actually work in. This is a proxy, not a census of which ATS each employer runs.

The Greenhouse sample leans toward tech and consumer brands such as Meta, Snowflake, Warby Parker and Datavant. The UK figure is 26 times smaller than the US one, but a sample of 9 is too small to support any conclusion about UK employers. The practical move is the same everywhere: read the application URL. It usually shows Greenhouse, Lever or Workday, and that one word tells you which rules below apply.

How long does a referral stay valid?

Treat every referral invite as a timer. Documented windows run from 30 days to 6 months, and some employers refer you to the company rather than to a single requisition. That means the posting's age and the invite date together decide what you do next.

How to read the rows:

• Google. Employee write-ups describe a referral to the company, not to one requisition. The invite lasts 30 days and covers up to 3 jobs, after which "the candidate will have to ask for another referral." This comes from employee blogs and forums, not an official Google page. Treat it as likely, and confirm with your referrer, who can see their own form.
• ADP. Only a referral made through the unique referral link counts, and a referral is blocked if you were already referred to ADP in the previous 6 months. A second referrer cannot reset that clock.
• Teleperformance. A submitted referral stays valid for 3 months.
• Cornerstone employers. The window is whatever the employer configured. Ask the referrer what their portal says.
• Google reapply. Google's help pages say you must wait 90 days before reapplying to the same job. This matters if you are tempted to withdraw and start over.

On a company-level referral, the scarce thing is the slots, not the link. If you get 3 applications on one invite, put them on the roles you fit best, not your three most ambitious ones. This is where a fit score saves you a wasted slot. Refolk scores how well your actual history matches each posting, so you can rank the employer's open roles before you spend the invite.

Refer-first or apply-first: how to make the call per posting

Refer first whenever you have not applied yet. Apply first only when the employer is known to run an endorsement flow, or when the posting is aging and your referrer cannot submit before you would apply anyway.

Sources disagree here. One widely read guide says to always refer first. GitLab's handbook says that if you have already applied and your application "has been reviewed and progressed by TA, this is considered an endorsement." That means applying first does not always lose the referral, but it can turn it into something weaker. Since merges usually keep the oldest record, I default to refer-first and treat apply-first as the exception.

If you already applied

Posting six is the hard case: you already applied, the referral link is three weeks old, and your contact knows you from one call. Do not reapply and do not withdraw. Use the repair route the system supports.

For posting six, also check the invite date against the window. If the link is past a 30-day window, ask for a fresh one before your referrer does anything. And make the vouch match the single call. That is covered in the next section.

How to pick a referrer by relationship tier

Ask people who have seen your work first, alumni second, and second-degree introductions third, and let each referrer describe the relationship honestly. The tier decides whether the referral reads as a vouch or a networking lead, and recruiters can tell the difference from the form.

Two terms first:

• Vouch. A referral from someone who can speak to your work: they say you are good, and they know why.
• Networking lead. A referral from someone who knows of you but not your work. In practice it is a sourcing tip: it gets you looked at, but it carries no endorsement.

Internal referral forms are built to capture which of these the recruiter is getting. Common fields are your relationship to the candidate, why you fit, the date, and bonus eligibility. GitLab asks referrers to explain how they know the candidate and to give "a comprehensive outline of why they are qualified." Meta's form, according to a community answer, asks how well the referrer knows your skills on a four-level scale: never worked together, just by reputation, worked occasionally, very well. The same unverified answer says "never worked together" is treated as a low-value referral and does not earn a bonus. No large employer publicly documents bonus eligibility tied to a vouch rating, so treat that detail as plausible but not established.

The tiers, in order

1. People who have seen your work. Former colleagues, managers, clients, collaborators. They can write a real vouch and pick an honest high rating.
2. Alumni. From your school or a past employer. They can rarely vouch for your work, but they reply more often than strangers, and the shared history gives them a reason to help.
3. Second-degree introductions. Someone who knows both of you introduces you. Ask the introducer to say how they know you, which gives the referrer something true to write.

Reply-rate evidence is thin. There is no peer-reviewed or large neutral study. One vendor platform in India reports that ex-colleagues reply at 3.7 times the rate of a cold message to a stranger, and alumni at 3.4 times. A second vendor reports that generic "I noticed you work at X" messages get 1 to 3% reply rates, while specific ones get 15 to 30%. Broadcast asks also do poorly: one referral platform's data, cited second-hand, puts social-media referral shares at just 14% of hires. Treat these as direction, not targets, and track your own reply rate by tier in the tracker.

If you know nobody at the company, start at tier 2 and make the ask about one requisition, not "any openings." Accept that a stranger's referral will probably be logged as a networking lead. It can still get your application reviewed, which is most of the value. But do not ask that person to rate you higher than they honestly can.

What a high closeness rating proves: the referrer has direct evidence of your work. What it looks like when it lies: a "very well" rating from someone whose LinkedIn history never overlaps with yours. That costs the referrer credibility with their own recruiters.

The referral request run, step by step

Work the whole pipeline in one pass: audit, assign referrers, decide the order, send packets, apply, confirm, repair, and keep the referrer updated. The time estimates assume a pipeline of live postings you have already chosen.

Notes on the steps that go wrong most

Step 1. The email column is the one people skip, and it causes the most damage later. If you have applied to different employers from two addresses, record which address went where.

Step 4. Writing a tailored resume for every posting is the part that turns a 20-minute packet into an evening's work. Refolk writes the resume from your own history and tailors it to each posting, so the packet's resume matches the requisition the referrer is submitting against. Then send the packet below.

Hi [Name],

Thanks again for offering to refer me. Everything the form should ask for is below.

Role: [Posting title]
Requisition ID: [ID from the posting page or URL]
Posting link: [URL]
Email I will apply with: [exact address]
Already applied: [No / Yes, on DATE, with the address above]

Resume tailored to this role: attached

Three lines for "why they fit" (edit anything that isn't how you know me):
1. How we know each other: [Worked together on X at Y / Met on one call about X]
2. What you have seen: [one specific piece of work or result]
3. Why this role: [one line tying that to the posting's main requirement]

If the form asks how well you know my work, please pick the level that matches line 1.

Once you submit, could you send me the invite link? I'll apply from it the same day. Between day 3 and day 7 I may ask you to check that I show up under your referrals.

Step 6. In Greenhouse, a candidate only shows under My Referrals if they "have a source of 'Referral' and credited to you as the Referrer." In Workday, a referral is not a referral until its business process event is complete, so "I submitted it" and "it counts" can be two different days.

Step 7. Repair is a request to a recruiter, not something you do yourself in the portal. Greenhouse recruiters can reassign source and credit, and UW-Madison documents that recruiters can enter or edit a missed referral in Workday.

How the referral run goes wrong

Most referral failures are invisible. The referrer thinks they referred you, you think you were referred, and the source field still reads direct. Each failure below comes with the check that catches it.

1. Applying first on Greenhouse or Lever. Your direct application is the older record, so after the merge your source stays direct. False positive: the recruiter sees a "Referral" label somewhere on your profile, but the source field still says direct. Check: the referrer looks under My Referrals. If you are not listed with source Referral, it did not land.
2. Different email on the referral and the application. The referral detaches from your application and sits as an orphan record. Check: compare the address on your confirmation email with the one in your packet, character by character.
3. Expired invite. Applying after a 30-day window logs you as a cold applicant, and nothing warns you. Check: the invite date is in the tracker, and you ask for a fresh invite at day 25.
4. Withdrawing to start over. At Google, a reapply to the same job runs into a 90-day wait, and other employers may block the reapply outright. Check: before withdrawing anything, find written confirmation that the employer requires you to have no active application.
5. Vouch inflation. Someone who knows you from one call rates you "very well." Recruiters treat it as a sourcing lead anyway, and the referrer's credibility with their own team drops. Check: the rating on the form matches line 1 of your packet.
6. Spending a company-level referral on the wrong roles. At employers that refer to the company, like Google per employee reports, all 3 slots go on stretch roles and the strong-fit role has none left. Check: rank the open roles by fit before you apply to any of them.
7. Reading a bonus-ineligible referral as a failure. At Amazon's hourly program, which pays a referral bonus of up to $125 and requires the employee's badge login, you are ineligible if you are already in the process or under recruiter review. Your candidacy is unaffected, so do not withdraw to "fix" the referral. Check: separate "does the referrer get a bonus" from "is my application being reviewed."

A note on ADP-style rules: if you were referred in the previous 6 months, a new referrer cannot help, and their submission will be blocked. Check your own history with that employer before asking anyone.

Closing the loop and keeping the tracker current

Message your referrer at every stage change (screen, onsite, offer, rejection), at about 5 minutes each, and keep the tracker as the single record of where each referral stands. Referrers who hear back are the ones who refer you again.

The closest evidence here is about references, not referrals. In a survey of 1,002 US hiring decision-makers, 68% said they were less likely to give a reference if the only time someone reaches out is when they need one. I would expect the same instinct from referrers, but that has not been measured directly.

Hi [Name], quick update on the [Role] referral (req [ID]):
I [had my recruiter screen / have an onsite on DATE / received an offer / heard it's a no].
[One line on what helped, or what you learned.]
Thanks again for putting your name on it. I'll keep you posted.

Keep these columns in the tracker for every posting:

• Requisition ID, ATS, posting date
• Applied (yes or no), date, email used
• Referrer, tier, backup name
• Refer-first or apply-first, and why
• Invite date and window end
• Day 3 to 7 confirmation result
• Repair requested (yes or no), and outcome
• Last stage update sent to the referrer

Re-check the facts rather than trusting this page forever. Referral windows, slot counts and endorsement settings are employer configuration, and they change. When a posting's portal behaves differently from the defaults here, ask the referrer what their form shows and update your row.