Most referral requests fail for a dull reason: they hand the work to the other person. “Hi, can you refer me?” with no job, no resume and no reason leaves your contact to find a role, guess your fit and write the justification, so they put it off and forget. A message that names the job, attaches the resume and says in three lines why you fit can be acted on in two minutes, and that is usually the difference between a referral and silence.
What a referral does inside a company
When an employee refers you, they usually submit your details through an internal referral tool against a specific opening. Your application is then marked as a referral, which at many companies means a recruiter reviews it sooner and with more attention than an application from the general pool. That is the whole benefit. You take the same tests and interviews as everyone else, and a weak fit stays a weak fit.
A few mechanics are worth knowing:
- Referrals are usually tied to a job ID. “Refer me to anything suitable” makes your contact pick a role for you, and most will not.
- The form records the relationship. Many referral forms ask how the employee knows you and whether they have seen your work. A stranger can still refer you, but the referral will say so, which is why your pitch has to carry the weight.
- You may need to finish the application. Some systems email you a link to complete your profile, and the referral can sit unseen until you do. Check your spam folder for a few days afterwards.
- Order can matter. If you have already applied directly, or an agency has already submitted you, a later referral may not attach to your application. Tell your contact either way, and never let two people submit you for the same role.
- Employees are often paid for successful referrals, usually once the new hire has stayed for a set period. Your contact has a small incentive to help. You are not begging, and they do not owe you a favour.
Who to ask first
Work down this list, roughly in order of how much weight the referral carries:
- Former colleagues and managers now at the company. They can vouch for your work rather than your profile, and the referral form will show that.
- People on the hiring team. They know what the role really needs and can mention you to the hiring manager in person. Even if they do not refer you, a two-line answer about the team’s stack is worth having.
- Alumni from your college or a previous employer. A shared institution gives a stranger a reason to read your message.
- Second-degree connections, through a mutual contact who knows you both and can introduce you.
- Strangers in a related team. The lowest reply rate, but it can work when your fit is obvious and your message is precise.
Ask one or two people per company at a time. Ten employees of the same company receiving the same message on the same day looks like spam, and colleagues do talk to each other.
What to send: job ID, resume and a three-line pitch
Put everything in one message, so your contact can act without writing back to ask questions:
- The job link and ID from the company’s own careers site. Job board links sometimes expire or point to a duplicate posting.
- Your resume as a PDF, named something like
firstname-lastname-resume.pdfand updated for this role. - A three-line pitch they can paste into the referral form: who you are, the evidence that matches the role, and why this role. An illustrative example: “Backend engineer, four years, mostly Java and Spring Boot on payment services. Moved our settlement jobs from cron scripts to Kafka consumers and made reconciliation failures rare. Applying for SDE II on the payments platform team, which works on the same problems.”
- An easy way out: “If you would rather not refer someone you have not worked with, that is completely fine.” An easy no tends to make the yes easier.
Before sending, read the posting properly and check that you meet the stated minimum experience and the core skills. A referral for a role you plainly do not fit spends your contact’s credibility, and they will remember. The skills listed on each uHired job card are a quick source for the middle line of your pitch, as long as you pick the ones you can back with evidence. The guide to reading a job description helps separate hard requirements from wish lists.
Sample messages you can adapt
Keep each message short enough to read on a phone without scrolling. LinkedIn limits the length of connection-request notes, so if you are not connected yet, send a one-line note with the request and the full details once they accept.
To someone from your college you have never met
Hi Priya, I graduated from [college] in 2024, same branch as you. I saw the SDE I opening on your team (job ID [ID]), and my backend internship at a fintech startup lines up well with it. Would you be open to referring me? My resume is attached, and here is a three-line summary you can paste if that helps: [pitch]. Completely fine if not.
To someone on the hiring team you do not know
Hello Arjun, I noticed you work on the search team at [company]. I am applying for the Senior Backend Engineer role (job ID [ID]) and have spent three years on Elasticsearch relevance and indexing pipelines. If my background looks like a fit, would you consider referring me? Resume attached. If not, I would still value one line on what the team looks for most.
To a former colleague
Meera, hope the new role is treating you well. I am looking to move, and [company] is hiring a frontend lead (job ID [ID]). We worked together on the checkout rebuild, so you know how I work better than my resume does. Would you be comfortable referring me? Resume and a short pitch below. Coffee is on me next time either way.
The follow-up, once, after about a week
Hi again Priya, a gentle nudge on my note from last week about the SDE I role (job ID [ID]). I know referrals take time out of your day, so if it is not possible, no problem at all, and thank you for reading.
How not to be ignored
| Mistake | Why it fails | Do this instead |
|---|---|---|
| Sending “Hi” and waiting for a reply | It asks for a conversation before giving a reason to have one | Put the job, the ask and the pitch in the first message |
| Asking for “any suitable opening” | Your contact has to do the search and the judgement for you | Name one role and its ID |
| Pasting one message to fifty people | Generic wording is obvious, and it reaches people in unrelated teams | Add one specific line per person: the shared college, team or project |
| Following up every two days | It turns a favour into a chore | Follow up once after about a week, then stop |
| Asking them to “push” your application | They usually cannot, and it makes them answerable for an outcome they do not control | Ask only for the referral and leave the process to the recruiter |
| Overstating how you know them | The form records the relationship, and interviewers sometimes ask about it | Be exact: “we have not met; I am from your college” |
After someone refers you
- Thank them the same day, and complete any application link the system emails you.
- Prepare as if the referral did not exist. It got you read; the interviews are still yours to pass.
- Keep them posted at the milestones: a recruiter call, the final round, the result. One line each is enough. Some referral tools show the referrer your status, and hearing it from you first is a courtesy.
- Ask about the team, not your scores. It is fair to ask what the team works on or what its interviews tend to focus on. It is not fair to ask them to find out how you did.
- If you are rejected, tell them and thank them anyway. It keeps the door open for their next opening.
- If you are hired, thank them properly, and buy the coffee you promised.
Then return the favour when you can. Referring good people later is what keeps this kind of network working, for them and for you.
A referral routine for this week
- Pick five roles you clearly fit, using the stated experience and core skills as the filter.
- For each, find two people: a former colleague or alumnus first, a team member second.
- Write one three-line pitch per role. Reuse the structure, not the words.
- Send the messages on a working day and log each one with the date.
- If a posting is fresh and nobody has replied within two or three working days, apply directly rather than waiting, and tell your contacts you have done so.
- Otherwise, follow up once after about a week, then move on.
The guide to tracking applications and follow-ups covers how to log all of this so nothing slips, and the guide to applying early explains why a fresh posting should not wait for anyone.