The Referral Request That Gets Answered: Package, Message, Follow-Up

Here is a referral request that busy engineers receive every week:

"Hi, I am a final-year student looking for opportunities. Can you please refer me in your company? I am attaching my resume."

To act on it, the engineer has to open the careers site, search for roles that might suit a fresher, guess which one, download the resume, read it to see whether it is any good, fill in the form, and write something about a person they know nothing about. That is twenty minutes of work for a stranger. Most people close the message.

Now imagine the same engineer receives the role title, the job ID, a direct link, a two-line summary with a live project link and a suggested note they can paste. Referring now takes about a minute, and they can see at a glance that the person is serious. This article builds that message.

• What goes into a referral package, and where to find the job ID.
• How to write the first message, with examples for different connections.
• A follow-up rhythm that is persistent but polite.
• How to use community referral threads.
• How to learn from your own response rate.

Prepare this once per role. Keep it in a document you can paste from, or as a single shareable link.

Role: Software Engineer I, BackendJob ID: 4821937Link: [direct link to the posting on the company's careers page]Name: [Your full name]Email: [your email]Phone: [your phone]  (share privately with the referrer only)Location: Bengaluru; open to relocate within IndiaResume: [link to PDF, or attached]Two-line summary:2026 B.Tech (ECE) graduate building backend services in Java and Spring Boot.Built a payment service that retries safely without double-charging: [demo] [code].Suggested note for the referral form (edit freely):"[Name] reached out about the backend role after reading my post on webhookretries. We haven't worked together, but their payment-retry project(idempotency, retries, tests) is closely related to our work and worth a look."

Most careers pages show a job ID, requisition number or reference code on the posting, or in its web address. For roles on public applicant-tracking job boards, the number at the end of the posting's address is usually the job's ID. If you cannot find one, send the exact title and the direct link; that is enough for the referrer to find it.

Many referral forms have a box where the employee describes the candidate. Writing a draft for them saves the most time, and if you keep it honest about how you know each other, it protects their reputation too. Do not write "I know [Name] well" or "worked with them" unless it is true. "We haven't worked together, but…" is honest and still helpful.

Short. Specific about them. One piece of proof. Easy to say no. Under about 120 words.

Hi Kavya, I'm a 2026 ECE graduate from [college] too. I saw you're on thebackend team at [company], and there's an opening for Software Engineer I,Backend (job ID 4821937). I've been building a payment service with safe retries(demo and code: [link]), which seems close to your team's work.Would you be comfortable referring me? I've put everything you'd need below,including a note you can edit. Completely fine if not, and thanks either way.[referral package]

Hi Arvind, your post on handling duplicate webhooks was useful: I used thesame idea of storing processed event IDs in my own payment project ([link]).I'm applying for Software Engineer I, Backend (job ID 4821937) at [company].If you're open to referring me, everything you'd need is below. No pressure at all.[referral package]

Hi Meera, thanks again for the chat last week. I took your advice and addedintegration tests with Testcontainers ([link to commit]). A role has opened thatmatches what we discussed: Software Engineer I, Backend (job ID 4821937).Would you be comfortable referring me? Details below.[referral package]

What these have in common:

• The connection or their work first, in one specific sentence.
• The exact role and ID.
• One link to proof of work.
• An easy exit: "completely fine if not".
• No guilt, no flattery, no life story.

Avoid "sir", "kindly", "please help me", long descriptions of your situation and messages that start with "I hope this finds you well".

Draft the message yourself, then:

Edit this referral request. Keep it under 120 words and keep my voice.Rules: the first sentence must be about the person's work or our sharedconnection, using only what I wrote; keep exactly one project link;keep the job ID; end with an easy way to say no.Remove: flattery, "kindly", "I hope this finds you well", and anythingthat sounds desperate. Do not add facts about me or them.[paste draft]

• Thank them immediately, and confirm whether you should apply now or wait for a link.
• Complete any application link quickly, the same day if possible.
• Record the referral in your tracker: who, which role, the date.
• Update them once when you hear something: an assessment, an interview, an offer or a rejection. A short "I didn't get through, but thank you for referring me" is remembered.

People miss messages. One polite follow-up is normal; more becomes pressure.

Day 0     Send the requestDay 5-7   One follow-up, ideally with something newDay 12-14 A final, short note that closes the loopAfter     Stop. If appropriate, ask a different person for the same role

Follow-up with something new:

Hi Kavya, following up on my note about the Software Engineer I role (4821937).Since then I've added load-test results to the project README: [link].Totally understand if you're busy or not comfortable referring.

Final note:

Hi Kavya, last note from me on this. If a referral isn't possible, no problemat all, and thanks for reading. I'll keep following your posts on the backend work.

Then move on. Never send a third follow-up for the same request, and never message the same person on several platforms on the same day.

For your highest-priority roles, a gentle sequence across a couple of weeks works better than one cold message, because each step gives the person a reason to recognise you:

1. Engage first (day 1 to 3): a useful comment on something they posted (article 14).
2. Connect (day 3 or 4): a note mentioning what you commented on, with no ask.
3. Ask (a day or two after they accept): the referral message and package.
4. Follow up once (about a week later), with something new.
5. One other channel, once (if they list a public work email or are active on another platform): a single, short note, not a copy of the whole message.

Each step must add something real. If it feels like you are tracking them, you are doing too much.

Some communities run threads where employees offer referrals and candidates post requests, for example periodic referral threads in developer subreddits such as r/developersIndia, and anonymous professional networks where employees post from verified company accounts. Each has its own rules and format; read them first.

What works in these posts:

• One specific company and role (with the job ID), not "any company".
• Two lines of background with one link to proof of work.
• Everything the referrer needs, or a clear way to request it privately. Do not post your phone number publicly.
• Under about 100 words.

Looking for a referral: [Company], Software Engineer I, Backend (job ID 4821937)2026 grad, Java/Spring Boot. Built a payment service with idempotent retriesand tests: [demo] [code]. Resume and details by DM, happy to share anything needed.

Do not repeat the same post in many threads on the same day, and thank anyone who helps, publicly if the community allows it.

After 15 to 20 referral requests, look at your tracker. Mark each message as replied or not, and by type (alumni, someone whose work you read, prior contact, cold). If your reply rate is low, look for patterns:

Below are [N] referral request messages I sent, with names and companies removed,each marked REPLIED or NO REPLY and labelled by connection type.1. What do the replied-to messages have in common that the others lack?2. Group the no-reply messages by likely problem: too long, generic opening,   no proof link, unclear role, asked too early, wrong person, other.3. Rewrite the weakest message as it should have been sent.4. Give me one rule to apply to every future message.Base your answer only on these messages; say if the sample is too small to tell.[paste anonymised messages]

Small samples mislead, so treat the result as a hypothesis to test over the next ten messages, not as a verdict.

• "Please refer me" with nothing else.
• No job ID or link, so the referrer has to search.
• A long message about your struggles. Kind people may read it; most will not.
• A dishonest suggested note ("I've known them for years").
• Following up three or more times, or on several platforms at once.
• Asking many people for the same role at the same time.
• Disappearing after being referred. Always thank and update.

Hi [first name], I'm a 2025 [branch] graduate from [college if shared, or"I read your post on X"]. There's an opening for [exact role] (job ID [ID]) at[company]. I've been building [one project, one line] ([link]).Would you be comfortable referring me? Everything you'd need is below, includinga note you can edit. Completely fine if not.Role / Job ID / LinkName / Email / Phone (private) / LocationResume: [link]Two-line summary: [stack] + [project with result and link]Suggested note: [honest, two sentences]

"[Name] contacted me about the [role] opening; we've exchanged a couple ofmessages but haven't worked together. Their [project] ([link]) shows [specificrelevant skill, e.g. safe retry handling with tests], which is relevant to this role."

Hi [name], following up on my note about [role] ([job ID]). Since then I've added[new feature] to the project: [link]. Completely understand if a referral isn'tpossible.

• Next: Cold Emails to Hiring Managers and Founders, Done Respectfully covers reaching the person who owns the role.
• For job application emails and cover letters, see How to Write a Cover Letter and Job Application Email That Gets Replies.
• For editing messages with AI while keeping your voice, see How to Use AI for Emails and Documents Without Losing Your Voice.