NewApply for you — a dedicated human applies to 1,000+ jobs on your behalf
10 min read

How to Ask for a Referral and Tailor Your Application Around It

Ask the person who can see the requisition, hand them a link plus three lines they can paste, then tailor the resume anyway. A referral changes who reads your application, not whether it gets read.

Ask the person closest to the opening, give them something they can forward in under a minute, and tailor your resume to that specific requisition before you send it. Most advice stops at the asking, which is why so many referrals go quiet after the introduction. A referral moves your application into a different queue and puts a name next to it, but a human still opens the file and reads it against the job description. If that file is the same generic version you send everywhere, the referral has spent someone's credibility to get you a more careful rejection.

Who should you actually ask?

Rank the people you know by how close they sit to the requisition, not by how senior they are.

The best person is someone on the hiring team or one desk away from it. They know whether the role is genuinely open, whether the posting reflects what the manager wants, and they can put your name in front of a person rather than a form. Second best is anyone else at the company, because most internal referral portals accept a submission from any employee and flag it for the recruiter.

A VP you met once at a conference is usually worse than a peer-level engineer on the team, even though the title is more impressive. The VP has no context on the opening and will forward you to a recruiter who receives forwards all day.

If you do not know anyone at the company, say so honestly and look for the nearest real connection: a former colleague who worked there, someone from your program, a person whose work you have actually followed. A cold message that admits it is cold and stays short does better than one performing a friendship that does not exist.

What do you send the person referring you?

Make the favor small enough that saying yes takes less effort than saying no. Send four things in one message:

  1. The exact link to the posting, plus the requisition number if the posting shows one. Companies often run several similar reqs, and "the data analyst role" is not enough to find the right one.
  2. Your resume as a file, already tailored to that posting.
  3. Three or four lines they can paste into the referral form or an email to the recruiter, written in their voice, not yours.
  4. One sentence on why this role specifically, so they can answer a manager who asks.

That third item is the one people skip and the one that decides whether the referral happens this week or never. Referral forms almost always have a free-text box asking how the employee knows you and why they recommend you. If your contact has to compose that from scratch, your request joins a list of things they will do later.

Something like this works: "I worked with Priya for two years at Latimer, where she owned our billing reporting. She rebuilt the pipeline that the finance team still runs on. She is applying to req 48221 and I think she would be a strong fit for the analytics team."

They will edit it. That is fine, and it is much faster than starting from a blank box. The same logic applies to whether you attach the file at all, which depends on what you are actually asking the person for.

Should you apply before or after the referral?

Ask your contact, and default to letting them submit first.

At most companies the referral form creates the application, or links to one you have already filed. If you apply through the careers page first and your contact then submits a referral, the two records usually get matched and nothing is lost. But at some companies the referral bonus only pays when the referral is logged before the candidate applies, which means applying first can quietly cost your contact money. Nobody will tell you this after the fact.

So the sequence that never goes wrong is: get the tailored resume to your contact, ask "do you want to submit this through the internal portal, or should I apply and send you the confirmation," and follow whatever they say. One extra question removes the whole problem.

Does a referral get you past the ATS?

This is where the referral gets oversold, usually by people selling referrals.

A referral does not delete your application from the applicant tracking system. Your resume is still parsed into the same database, still stored against the same requisition, and still surfaced to the recruiter with the same fields everyone else has. What changes is priority and framing. Referred applications typically carry a flag, often land in a separate view the recruiter checks first, and arrive attached to an employee's name, which is a real advantage when a recruiter has several hundred applicants and time for a few dozen.

What the referral does not do is make a recruiter read a resume that does not visibly match the job. When they open your file, they are checking the same things they check for everyone: do the titles line up, are the required tools on the page, does the experience reach the level the req asks for. A referral buys you a careful read. It does not supply the evidence that read is looking for.

Two practical consequences. First, the parsing still has to work, so the layout rules do not relax because you know someone. Columns, text boxes, headers, and graphics can still mangle your file on the way in, and it is worth running the version you hand over through an ATS resume checker before your contact submits it. Second, the content still has to match, which is the next section.

How should you tailor the resume you hand over?

Treat the referral as a reason to tailor harder, not a reason to skip it.

Start by pulling the required skills, tools, and titles out of the posting your contact pointed you at. For each one, find the bullet in your history that proves it, and rewrite that bullet so the term appears in it naturally. If nothing in your history proves it, leave it out. The mechanics are the same as tailoring a resume for any ATS, with one addition: your contact may read this file, and possibly forward it to the manager with a comment. It should be a version you would be comfortable discussing in a hallway.

Two things worth doing specifically for a referral:

Lead with the overlap your referrer would name. If they are going to tell the recruiter you rebuilt their billing pipeline, that project should be visible in the top third of the page, not buried in the fourth bullet of your second job. The written referral and the resume should tell the same story, because a mismatch between them reads as exaggeration.

Fix the summary to match the target title. If the req says "Senior Analytics Engineer" and your summary says "data professional," you have made the recruiter do translation work on a page that is meant to save them time.

Doing this for one referral is easy. The friction shows up when you are running a real search and every application needs its own version, which is where most people fall back to sending one file everywhere. That is the part LetMeApply handles: its resume tailoring reworks which bullets lead and which terms surface for each posting, without inventing experience you do not have.

What if they refer you to a different role than you wanted?

Take the conversation, decide on the role separately.

Employees sometimes refer you to the opening they know about rather than the one you asked for. If the alternative is plausible, ask your contact what the team is actually like and what the manager is hiring for, then decide. If it is not a fit, say so early and kindly, because being referred into a role you do not want and then withdrawing costs your contact more than declining up front.

You can also ask them to hold the referral. "I would rather wait for something closer to the platform side. Would you let me know if that opens up?" keeps the relationship intact and keeps the referral available.

How do you follow up without nagging?

Give it a week, then ask your contact once whether the referral went in. That single question resolves most silences, because a surprising number of referrals are never actually submitted. People mean to do it and the tab closes.

If it was submitted and there is no news after another two weeks, ask the recruiter directly rather than routing everything through your contact. Your contact did the favor already, and turning them into your status page is how you use up the goodwill you just earned.

Then keep applying. A referral is a good shot, not a plan, and waiting on one is how a search stalls for a month. It belongs inside your normal application volume, not instead of it.

Frequently asked questions

Is it rude to ask for a referral from someone I barely know?

No, as long as you make it easy to refuse and easy to accept. Keep the message short, say plainly how you know them or found them, name the specific role, and attach the file. What reads as rude is a long message that hides the ask until the end, or one that assumes a relationship you do not have. Most employees are happy to refer strangers when the person is clearly qualified, partly because referral bonuses exist.

Should I mention the referral in my cover letter?

Yes, in the first sentence, and use the person's full name and their team. "Priya Raman on the analytics team suggested I apply for req 48221" gives the recruiter something verifiable. Do this only if the person has agreed to be named. Putting someone's name on an application they did not endorse is the one version of this that will actually damage a relationship.

What if the referral does not lead to an interview?

Thank your contact anyway and tell them the outcome. Referrals fail for reasons that have nothing to do with you, including reqs that get frozen or filled internally before the posting comes down. A person who hears how it ended is far more likely to refer you again than one who never learns what happened.

Does a referral help if I am underqualified for the posting?

It helps you get read, not hired. If the req asks for eight years and you have three, a referral usually produces a faster and more explicit no. The better use of that contact is asking which opening on their team you would actually be competitive for.

How many referrals should I be asking for?

Fewer than you think, and with more care each. Referrals draw on relationships that do not regenerate quickly, so spending one on a role you are lukewarm about is a bad trade. Two or three well-chosen asks, each with a tailored resume behind it, beats a dozen scattershot messages that all get the same attachment.

Related articles

Should You Attach Your Resume to a Networking Email?

Attach it when the person can act on it today, leave it off when you are asking for a conversation. Which version to send, what happens when your file gets forwarded into an ATS, and the five-sentence email that works.