Short, specific messages get replies; long, generic ones do not. Message engineers and recruiters about one named role, show one piece of relevant proof, make a small ask, and make referring you easy by sending the job link and a two-line summary. Expect a low reply rate and send steadily.
What people tell me
I keep hearing that referrals are the best way to get interviews, but I do not know anyone at the companies I want. I have sent a few LinkedIn messages to engineers and recruiters, mostly "Hi, can you refer me?" with my resume attached, and almost nobody replies. I do not want to seem desperate or annoying, and I am not sure whether I should message recruiters, engineers or hiring managers.
A composite of the messages behind this question, with personal details left out.
Key takeaways
- Never open with "can you refer me" to a stranger. Ask about one specific role and show one relevant piece of proof.
- Keep the first message under about 80 words. Make it readable on a phone in ten seconds.
- Engineers on the team give better referrals; recruiters are faster at moving you into a process.
- Make referring you effortless: job link, job ID, two-line summary and your resume ready.
- A 10 to 20 percent reply rate is normal. Send a few thoughtful messages a day and follow up once.
Why most messages get ignored
From the receiving side, most cold messages look the same: "Hi sir, I am looking for opportunities, please refer me", with a resume attached and no role mentioned. The person would have to find a job that suits you, read your resume, decide whether you are good, and risk their reputation. That is too much work for a stranger.
A referral is a small professional favour. Your job is to make it small, safe and easy.
Who to message
| Person | What they can do | Best ask |
|---|---|---|
| Engineer on the team | Refer you, tell you what the team values | "Could I ask two quick questions about the role?" or a referral for a specific opening |
| Recruiter or talent partner | Move your application into a pipeline quickly | "I have applied for role X; here is why I fit" |
| Hiring manager | Decide on interviews directly | Only for small companies or very specific fits; keep it brief |
| Alumni from your university | More likely to reply, shared context | Advice first, referral later |
| Engineers you have interacted with online | Warm connection | Mention the interaction |
Alumni and people whose posts you have genuinely engaged with reply at noticeably higher rates than complete strangers.
The anatomy of a message that gets answered
- A specific reason you chose them. Same university, their post, their team.
- One specific role, ideally with a link or job ID.
- One piece of proof that matches the role.
- A small, clear ask they can say yes to in a minute.
- An easy exit, so they do not feel cornered.
Template: asking an engineer for a referral
Hi, I noticed you work on the payments team. I have applied for the Junior Backend Engineer role (job ID in the link). I recently built an order service in Node.js and PostgreSQL that handles idempotent payments, repo here. If you think I would be a reasonable fit, would you be open to referring me? Completely fine if not. Thank you either way.
Template: asking for advice first
Hi, we studied at the same university a few years apart. I am applying for frontend roles and your team's work caught my eye. Could I ask you two short questions over message about what the team looks for in juniors? No call needed.
Template: recruiter follow-up after applying
Hi, I applied for the Associate Software Engineer role last week. I have built two production-style React apps, one used by a small non-profit. I would love to be considered for the next round of screening. Resume attached for convenience.
Each of these is under about 80 words. That is deliberate.
Making the referral easy once they say yes
Send everything in one message:
- The exact job link and job ID
- A two-line summary they can paste into the referral form
- Your resume as a PDF, named sensibly
- Your email address
Then say thank you and let them know the outcome later, whatever it is. People who get updated are much more likely to help again.
How many to send
Cold outreach is a numbers game played with care. A reasonable rhythm is 3 to 5 thoughtful messages a day, five days a week. That is 60 to 100 a month. If one in ten replies and a portion of those turn into referrals, you get several referrals a month, which is far better than anonymous applications alone. The pipeline blog post explains how to track this like a funnel.
A 4-week outreach plan
| Week | Focus | Target |
|---|---|---|
| 1 | Fix your LinkedIn headline, about and featured projects; build a list of 40 target companies | Profile that matches your messages |
| 2 | Alumni and warm contacts first; advice-style messages | 15 to 20 messages |
| 3 | Specific referral requests for open roles | 20 to 25 messages |
| 4 | Follow-ups, thank-yous, recruiters for roles already applied to | 15 to 20 messages plus follow-ups |
Before you start, make sure your profile holds up when they click on it. The LinkedIn and personal branding roadmap covers what they will look at first.
Following up
If there is no reply after 5 to 7 days, send one short follow-up: "Just bumping this in case it got buried. No worries if the timing is not right." After that, stop. A third message rarely helps and can hurt.
Common mistakes
- Only "Hi" or "Hello sir" as a first message. Many people will not reply to a message with no content.
- Asking for "any role". It pushes the work onto them. Always name a role.
- Attaching a resume with no context. They will not open it.
- Copy-pasting to 200 people. It shows. Personalise the first line at least.
- Asking for a referral from someone who cannot assess you. Advice first builds trust; referral second is natural.
- Guilt-tripping or pressure. "Please, I really need this" makes people uncomfortable, not helpful.
- Disappearing after they help. Always close the loop.
What a reply rate tells you
| Reply rate over 30 or more messages | Likely issue |
|---|---|
| Below 5 percent | Messages too generic or too long, or profile does not match |
| 5 to 15 percent | Normal. Keep going and refine your proof line |
| Above 15 percent | Working well. Increase volume carefully |
If you are still stuck
For what actually moves the needle on LinkedIn, read LinkedIn for engineers: what actually works, and if you are wondering whether posting helps too, see does posting on LinkedIn help engineers get work. You can join Sefism for free, start with credits and your first roadmap on the house, and as a member ask your own question if you want a second pair of eyes on your outreach messages.
Was this answer helpful?
Read next
- LinkedIn for Engineers: What Actually Works, and What Is FolkloreLinkedIn for software engineers, checked against what LinkedIn has said about its rebuilt feed and what large studies found: a profile that recruiters find, posts people stop for, formats, timing, and which popular tips are folklore.
- A Job Search Is a Pipeline, Not a PerformanceThe job search strategy that works is a pipeline, not a string of hopeful applications. Thirteen heuristics for the mechanics you control: tailoring, referrals, how many to keep live, tracking the funnel, interviews, follow ups and offers.
Your situation is not quite this one?
Members get written answers to their own questions, a roadmap built for them and feedback on their projects. Early access is open: sign up and your account is active shortly after. Prefer to talk? A free call works too.