1. LandOffer
  2. Blog
  3. All articles
  4. How to Send a Referral Request with the Job ID, Resume, and Evidence a Colleague Needs

Job search

How to Send a Referral Request with the Job ID, Resume, and Evidence a Colleague Needs

Prepare a useful referral request with one job ID, the right resume, and relevant evidence, while matching the ask to the colleague's actual knowledge.

10 min readLandOffer team

Send a referral request that gives the colleague one specific job, an accurate resume, and a few relevant facts they can assess. State how you know each other, disclose whether you already applied, and ask whether they are comfortable considering a referral under their company's process. A concise packet should reduce the work of understanding your candidacy without writing an endorsement on the colleague's behalf.

LandOffer publishes this guide and offers recent job discovery. We checked the linked university and employer guidance on October 12, 2026. The packet, messages, people, and roles below are fictional teaching examples; no request was sent. Referral policies vary, and a willing colleague cannot promise that a recruiter will advance an application.

Two former teammates review one role folio, an accurate resume, and bounded work evidence before considering a referral.

Decide what you are actually asking the person to do

A former teammate who reviewed your code has a different basis for recommending you than an alumnus you met yesterday. Both relationships can be valuable. The first may support a discussion of shared work; the second may support advice about a team or a recruiting process. Do not turn the second relationship into the first by describing an acquaintance as someone who knows your performance.

Berkeley's referral guidance recommends preparing before asking, checking whether a referral process exists, and allowing the contact to decide whether they feel comfortable. Its advice supports a request for consideration rather than an expectation of support. You can be direct about your interest while leaving the decision with the person whose name would accompany the recommendation.

If your immediate need is information, ask for information. Berkeley describes an informational interview as a conversation for learning about a field or organization. Do not advertise a conversation about someone's work and then make the entire exchange a demand for an internal referral. A clear question about the team's engineering responsibilities can be useful even when no referral follows.

Your materials should match that request. A colleague considering a specific referral needs the posting and your relevant evidence. Someone discussing career directions may need a short description of your interests and two thoughtful questions. Sending every document to every contact creates work without making the request more appropriate.

Verify the role before preparing the packet

Open the employer's current posting and record its title, job ID, location, and application link. A title alone is often ambiguous. Two teams can recruit Software Engineers in different offices with different experience requirements. The identifier lets the colleague find the intended opening without guessing which team or office you mean.

Check that the role is externally available and still appears open. Read the responsibilities as well as the requirements. Identify the parts of your background that support the actual work. A backend engineer who maintained internal data services should not summarize that experience as large-scale platform ownership merely because the new role uses the word platform.

Record your application history accurately. “I have not applied” and “I applied on October 7 using this email” give the contact different starting points. Do not hide an existing submission to make a referral seem easier. The employer may permit an endorsement on the existing application, require a referral before submission, or offer no applicable route at that stage.

GitLab's published process illustrates why this matters. It distinguishes referrals from endorsements, requires candidate approval, and uses a specific requisition. It also describes an endorsement when an application has already been reviewed and progressed. Those are GitLab's rules, not a universal template, but they show why the company process belongs beside the request.

Priya builds a packet a former teammate can inspect

Priya is a fictional software engineer with three years of backend experience. She wants to apply for Backend Engineer, requisition BE-214, at fictional Alder Systems. The posting asks for API implementation, relational data work, and collaboration during production incidents. Priya worked with former teammate Luis on a billing-service team; he reviewed some of her changes and participated in a shared incident.

Her first attempt says, “I'm a strong full-stack engineer and would love a referral to anything suitable.” That makes Luis choose both the role and the evidence. It also introduces a full-stack claim that her resume does not support. Priya replaces it with a single role and a small evidence map.

Role responsibility Priya's supported evidence What Luis actually knows Boundary retained
Build service APIs Implemented reconciliation endpoints and integration tests in Python Reviewed two related changes She did not design the entire billing platform
Work with relational data Wrote SQL checks for failed imports and investigated inconsistent records Discussed one import failure with her No invented data-volume or revenue metric
Collaborate on reliability Added diagnostic logging and updated a runbook after an incident Shared the incident review She assisted with response rather than leading the organization

The completed packet has five parts: the current posting link and BE-214 ID; a resume named Priya-Shah-Backend-2026-10-12.pdf; these three evidence points; her application state, not yet submitted; and a short request to confirm the appropriate sequence if Luis is willing. The filename is an illustrative convention, not an employer requirement.

Priya keeps the evidence map in her preparation notes and includes only a compact version in the message. Luis can understand the request without opening a long portfolio. If he wants more detail, she has the relevant examples ready. She does not send proprietary incident notes, customer records, or internal code to make the packet look more substantial.

The result is a defensible request, not a completed referral. Priya has selected a role, narrowed her claim, and supplied enough context for a decision. Luis still chooses whether he knows her work well enough and whether the opening fits the company's process. The packet does not convert his previous code review into an obligation. Priya also checks that BE-214 is the same Austin opening in the employer link and her notes; a similarly named role in another office would need a separate fit decision.

Use a short message with a specific, optional request

Priya's revised message to Luis reads:

Subject: Alder Backend Engineer BE-214 — referral consideration

Hi Luis, I hope you're doing well. We worked together on the billing service, including the reconciliation endpoints and import incident review. I'm interested in Alder's Backend Engineer role, BE-214, in Austin. The API, SQL, and service-reliability responsibilities align with that work. I've attached my current backend resume and included the employer posting below. I haven't applied yet. If you feel comfortable considering a referral, could you let me know the appropriate next step? No problem if you don't have enough context or the process isn't a fit. Thank you, Priya.

The opening reminds Luis of the relationship without exaggerating it. The role ID lets him find the requisition. The evidence is short enough to read in the message. The application state prevents a sequencing misunderstanding. The final sentence gives a clear way to decline without demanding an explanation.

This is also why a polished paragraph praising the company is not the central asset. Luis needs to understand what Priya is asking and what supports it. One genuine reason for the role is useful; a long company-history summary can obscure the practical information. Replace broad enthusiasm with a relevant responsibility and a fact from your work.

Attach the intended file, then open that attachment before sending. Confirm the contact information, dates, title, and role emphasis. A correct filename is not proof of correct contents. If you provide a portfolio link, check its public view and include only work you can share. Do not make the colleague request access to a private folder containing unrelated materials.

Change the request when the relationship changes

Priya also meets Maya, an Alder engineer, at a public technical event. They discussed data validation briefly, but Maya has never worked with her. Priya wants to learn whether BE-214 involves transactional service work or primarily analytics infrastructure. She sends a different fictional message:

Hi Maya, thank you for the discussion about data validation at Tuesday's event. I'm considering Alder's Backend Engineer role, BE-214. My experience is in Python services, SQL reconciliation, and integration tests. If you have context on the team, could you point me toward information about the service work it owns and whether the posting reflects its current needs? I haven't applied yet. I understand you haven't worked with me, so I'm asking for guidance rather than assuming a recommendation. Thank you, Priya.

Maya can answer a bounded question without vouching for Priya's performance. Priya includes the role ID because the question concerns that opening, but she does not attach an extensive packet before Maya has expressed interest in reviewing it. If Maya offers to consider a referral later, Priya can explain the same relationship honestly and provide the resume with permission.

The two messages produce different useful possibilities. Luis might consider a referral based on shared work; neither example establishes that an internal action occurred. Maya might clarify the role or identify the right public source. A useful response from Maya should not be recorded as a referral merely because it came from an employee. An introduction, advice, an agreement to review, and an internal submission are distinct events.

Two letters distinguish a request grounded in shared work from a request for guidance by someone who has not worked with the candidate.

Respond to the answer without rewriting the relationship

Suppose Luis replies that he is comfortable reviewing Priya's resume and asks whether she can describe the SQL investigation. Priya provides a short factual account: what inconsistency she investigated, which checks she wrote, how the team used the findings, and what she did not own. She answers the question instead of sending a prewritten endorsement for Luis to copy.

If he later confirms that he submitted a referral and tells her to expect an employer invitation, Priya records that as reported by Luis and waits for the stated next step. She has not independently inspected his internal dashboard. When an official invitation arrives, she checks the role, destination, and instructions before completing her application.

If Maya says the role mostly involves a different technical domain, Priya updates the fit assessment. The conversation can reasonably end with a decision not to apply. That is useful information even though it produces no referral. Thanking Maya for the clarification recognizes the help she actually provided.

If the colleague declines, thank them and stop asking for that referral. The contact may lack sufficient knowledge, face company restrictions, or simply prefer not to recommend someone. Do not answer a polite refusal with a longer argument about why they should feel comfortable. You can appreciate their time and continue through the available application route.

For a nonresponse, follow any timing the colleague provided. A single concise follow-up can clarify whether the request was seen, but repeated messages do not create consent. If a deadline is approaching, make an application decision using the employer's instructions and your actual state. Do not describe silence as approval to use the colleague's name.

Keep the packet useful and the record accurate

Before sending, make one final comparison between the current posting, the selected resume, and the evidence in your message. They should describe the same candidate and role. Remove a metric you cannot explain, a responsibility you did not hold, or a skill included only because it appears in the posting. A colleague should be able to ask an ordinary follow-up without uncovering a different story.

Keep the record small: requested, response received, permission given, internal action reported, invitation received, and application submitted. Add dates and evidence as those events occur. A drafted email is still a draft. A friendly reply is not an internal submission. A referral invitation still needs the candidate's required application steps.

Choose one current opening on LandOffer, verify it on the employer site, and build the five-part packet around evidence you can defend. Include the role ID, selected resume, three bounded evidence points, application state, and a request for the correct next step. Match the message to the actual relationship and let the colleague decide. The useful outcome is an informed next step, including an honest decision to use another route.

Sources and Further Reading