A referral gets you read, not hired

What a referral actually changes

The mechanism is dull. An employee opens an internal form, types your name, pastes a job ID, uploads your resume, and writes two or three lines about why. After that, your application carries their name in the recruiter’s queue. Order of reading is the whole product.

So “can you refer me” is not “can you get me in”. If the resume does not make the case alone, a referral only puts a weak case in front of fresher eyes. At one company a referral is close to a one-time asset, and spending it on a draft is the expensive mistake.

Say so if you have already applied. At some companies a later referral lands as a duplicate, and the employee sees that too.

The colleague and the stranger are two different asks

Someone who has worked with you is not giving a referral. They are giving a testimonial, and it has weight because it has detail: what you shipped together, the week it went wrong. You have three or four of these people and the list refills slowly. Do not spend one on a company you are only curious about.

From a stranger, whose name you found on the careers page, you want something smaller: your application moved up, plus one honest line saying they do not know you but the background looks right for the role. Plenty of people write that sentence, because they can defend it.

Across a border there is one more problem. Your last employer may mean nothing to the reader. Say what it does before you say its name: “a logistics platform of about [N] people in Taipei” travels, and the brand alone does not.

Who to ask is rarely the most senior person

Instinct sends you to the VP of the department, because the VP looks like the one with power. But the higher the seat, the more cold messages arrive, and a VP will usually not open the referral form at all. They forward you to a recruiter, which is a path you could have walked yourself. The person who is actually useful is mid-level, on the team with the opening or the one next to it. They can read the posting and tell what it means, they have the referral link, and their inbox is not full.

Finding them is unglamorous. Search the company name plus a job title on LinkedIn, then sort the results twice: once by alumni, once by people you may know. Two lines are sitting there that most people forget. The first is anyone who studied where you studied, a few years ahead. The second is a former colleague who left for that company, and that one is much stronger, because they know what your last job was like and can write a comparison in the referral box instead of restating your resume back at the recruiter.

Two people to avoid. The first is the hiring manager for the role: asking them to refer you is asking them to evaluate you first. You have upgraded a small favour into a decision, and they have no reason yet to make it. The second is the company’s own recruiter. A recruiter is not a referrer, they are the receiving end. Saying hello to them is useful, but it is not a referral and does not do what a referral does.

Ask one person per team. Send three messages into the same group and all three names show up beside yours in the same queue, which does not read as a network. It reads as spraying.

The first message should not be the day you need something

Weak ties work because their world does not overlap yours, so they can see openings you cannot. But weak ties expire. If you have not spoken to a university classmate in three years and the first line in the thread is “could you refer me”, they will not be offended. They will file you under people who surface when they need something, and reply slowly, or not at all.

Where you can, do it early. This is not a networking project. It is a handful of very small acts: a line when someone changes jobs, a real reply to a post you actually finished reading, signing up when their company runs a public talk. Each one costs under ten minutes. Six months later, when you ask, the thread above your message is not blank.

If you are already too late, do not perform. Admitting the gap works better than pretending there isn’t one: “It’s been a long time — I know we last spoke [N] years ago, so let me be direct about why I’m writing.” Naming the awkwardness in the first line is what lets the other person relax. The worst version is three messages of small talk before the point, because that tells them this is going to take a while.

Alumni groups, university communities and industry Slack or Discord servers are the same instrument. Someone who has answered other people’s questions in a channel asks for a referral with a completely different hit rate. The record is sitting in the channel, which means it is credibility you do not have to claim about yourself.

Make it a three-minute favour

• The exact role: title, requisition number, and the link from the company’s own careers page. The form asks for the ID, and making them hunt for it hands the work back.
• One PDF resume, named Lin-Wei-Chen-Data-Analyst.pdf. Not a drive link, not “happy to send it if you’re interested”. They should never have to ask you anything.
• Three lines in the third person they can paste into the referral box unchanged. That box is the part everyone puts off.
• One sentence on why this role, not why you need a job. The first can be forwarded. The second has to be translated.
• An exit: “If it isn’t a fit, say so and I won’t ask again.” Making the no cheap is what makes the yes easy.

What the message looks like

Short, with no sentence about how much you want the job. Write it in the language of the posting, which is usually English:

“Hi Mireia — we haven’t met. I saw you’re on the Data Platform team at [Company], and I’m applying for Data Analyst, req 41209 (link). I spent four years in supply-chain analytics at a logistics platform of about [N] people in Taipei, and cut month-end close from [N] days to [N]. Resume attached as a PDF. Under it are three lines you can paste into the referral form if you’d rather not write your own. If it isn’t a fit, say so and I won’t ask twice.”

The three lines underneath: “Wei-Chen has spent four years in supply-chain analytics and owns the month-end close model at a logistics platform in Taipei. He rebuilt the pipeline behind it and cut the close from [N] days to [N]. He is applying to Data Analyst, req 41209, because it is the move from reporting into modelling he was already making.” Leave [N] wherever you are unsure. A number you invented sits next to their name, not yours.

Do not open with “could we jump on a quick call”. Thirty minutes is a bigger favour than a referral, and asking for the bigger one first is how a small yes becomes no reply.

A LinkedIn connection request carries three hundred characters, which will not hold the message above. Write the note as one sentence — “Applying for Data Analyst req 41209 on your team, may I send you the details?” — and paste the full message into the thread once they accept. If you can work out the company’s email format, email is usually faster than LinkedIn. A work inbox gets opened every day and LinkedIn does not.

The two weeks after they hit submit

What normally happens next is this. They fill in the form, you get an automated confirmation, sometimes not even that, and then silence. Whether the referral buys a faster reply depends on how many openings the recruiter is carrying at once, not on how enthusiastic your referrer was. One or two weeks of nothing is normal, and it is not evidence that they forgot to send it.

Do not apply again yourself. Most systems treat a second entry from the same email address as a duplicate. Some block it outright, some keep both, which means the recruiter sees that you applied twice for one role. Someone submitted it for you. Your side of the work is finished.

If you check in, check in once and keep it small: “Just checking in, no rush at all — did the referral go through on your end?” You are asking whether anything jammed on their side, not asking for the outcome. The outcome is with the recruiter, and pushing your referrer to go and ask is borrowing from them a second time.

Once you are interviewing, reporting after every round is noise, but the final round is worth one line. They may be pulled in as an interviewer, or the recruiter may ask them how they know you. Knowing where you got to is what keeps that answer from stalling.

The credibility you are borrowing

Referrals are signed. Miss an interview, or let a number on your resume collapse under two follow-ups, and the record keeps their name beside yours. Many companies pay a referral bonus, so their money is in it too. After a yes: reply fast, arrive early, and tell them how it ended, especially when it ended badly.

A no is usually not a verdict on you. They started nine weeks ago, the quota is gone this quarter, the policy requires having worked with you. “Understood, thanks for the fast reply”, and stop. One more push turns a polite stranger into someone who cannot read a room.

No answer is an answer. Wait a week, send one line, then stop. Ask someone else, or simply apply. The resume you would have sent with a referral is the same resume; if it is good enough, someone opens it anyway.

What the person on the other end is calculating

Referral bonuses are common, and the money does not land when they press submit. The usual structure pays after you start, then again some months later, and pays nothing if you leave in between. So the order of what they care about is: will you show up to the interview, will you accept, will you last. Writing “I really need this job” answers none of those three questions. Writing why you are moving in this direction answers all of them at once.

The bonus also explains rules that otherwise look arbitrary. Some companies pay nothing, or half, for a referral of someone the employee has never worked with, so a polite no can simply mean the risk is theirs and the reward is not. It says nothing about your background. The reverse happens too: when a role is urgent, some companies raise the bonus for a while, and reply rates from strangers improve for exactly that stretch. A warm reply is not always about your resume.

Knowing the money exists is not permission to treat someone as a vending machine. For most engineers and product managers the bonus is not a life-changing number, and what they are putting up is their name. An ask written in the posture of “they’re getting paid for this anyway” leaks through the sentences, and people read it.

The fastest way to calibrate is to swap seats. The first time someone you barely know asks you for a referral, you will notice you do not care how badly they want the job. You care whether they made it easy: is the resume attached, is the requisition number there, do you have to invent the referral text yourself, will they reappear in three days to ask again. Every part of it that irritates you in that moment is the part you should be handling for someone else now.

When a referral only gets you rejected faster

Spending a favour on a role you cannot pass is the most wasteful use of one, and the rejection is filed under their name too. In the cases below, the question to ask is not “can you refer me” but “what is this role actually looking for?” Your contact can answer the second one, and that answer is worth more than a referral. It tells you which opening to apply for instead, or how long to wait before coming back.

• Work authorisation is a hard gate. If the posting requires the right to work locally and you do not have it, a referral gets you screened out sooner, not sponsored. Ask about that first, and ask about the referral second.
• An evergreen posting that has been up for months was never opened to fill one seat. It is building a pool, and a referral into it mostly sinks in the same pool, no different from applying yourself.
• There is an internal candidate already, or the team is under a hiring freeze. Neither is visible from outside, but your contact often knows. “I would hold off on this one” is the most valuable sentence they can give you.
• You are two levels off the posting. One level is a stretch worth arguing for. Two levels is a window a recruiter closes in thirty seconds, and those thirty seconds go on your referrer’s record.
• You have already been rejected for this exact role. The system remembers, and a referral does not route around it.

The second time at the same company

Turned down by one person, can you ask someone else at the same company? Yes, but not the same day and not the same team. Leave a gap, change the department, change the role, and from outside it reads as two unrelated things. Three people in one week about one opening is one thing, and they find out over coffee.

If the referral went in and a form rejection arrives within days, the problem is almost never the referrer. It is that the resume and the role do not line up. That is worth one question back: “Can you see the status on your side? Where did it stop?” Some companies show their employees which stage a referred candidate was held at, and that is information you can almost never get from outside.

Coming back to the same company six months later is usually a fresh game, and this time you have something to say: which role you applied for, what you have added since. For someone who already helped once, the second ask is easier than the first. You did not make them look bad, and they remember that.

There is one more second time worth doing that almost nobody does. Tell them how it ended. If you got the offer they will find out eventually; if you did not, they may never know. The note that says “didn’t get it this time, but thank you for the time you spent” is the entire reason you can ask again.