Introduction: when a referral requires a specific job req
If you are asking for a referral and the portal requires a job requisition (req) number, you cannot rely on “refer me generally.” Many companies only allow employees to submit referrals tied to a specific job posting, and recruiters often triage applicants by req. That means your referral request needs to be precise, easy to execute, and aligned to the role you can convincingly interview for.
This tactical guide gives you exactly what to say when a contact’s referral requires a specific job req. You will learn how to identify the right req, how to collaborate with your contact without creating work for them, what to do when two reqs fit, and how to keep your request professional even if you are not sure which role is best.
Important: Your goal is not just to get “a referral.” Your goal is to get referred to the right req so your resume is reviewed in the correct funnel and your interview story matches what the team needs.
Why “refer me generally” usually fails
Most referral systems are designed around compliance, reporting, and hiring workflows. That is why they commonly require a posting, a req ID, or a job link.
Here is what happens when you ask to be referred without a req:
- Your contact gets stuck. They cannot submit anything without a req, so your message becomes a back-and-forth.
- You look unfocused. Recruiters and hiring managers interpret broad interest as low clarity or low commitment.
- Your resume lands in the wrong place. Even if a recruiter forwards you internally, you may be associated with a role that does not match your background.
- Your behavioral interviews get harder. If you apply to a role you cannot clearly support with STAR stories, you will struggle to show fit.
A better approach is to do the upfront work and bring your contact a short list of roles you can credibly pursue.
What you need before you ask for the referral
Before you message your contact, gather a small “referral-ready packet.” This reduces friction and increases the chance they actually submit the referral.
Your referral-ready packet
Bring these items in your first message or in a quick follow-up:
- Req link(s) and req ID(s): Ideally 1, optionally 2.
- Role title and location: Some companies have identical titles across locations.
- A 2 to 3 sentence fit statement: Your most relevant experience and the job’s core needs.
- Your resume: PDF is usually safest.
- Any required portal fields: Email, phone, LinkedIn URL, and work authorization if relevant.
If you want to sanity-check whether your resume is aligned before you ask, you can run it through a free resume score tool like https://primly.io/resume-score. The point is not to chase a perfect score. It is to catch obvious mismatches and missing keywords that could weaken your referral.
How to pick the right req with your contact
If you pick the correct req, you make it easy for your contact and you increase your odds of landing interviews that match your actual strengths.
Step-by-step: choosing the best req
- Start with the job family you can interview for today
- Choose roles where you can tell 3 to 5 strong STAR stories that map to the job’s core responsibilities.
- Avoid roles where your experience is adjacent but not demonstrable.
- Match your strongest evidence to the posting’s “must-have” bullets
- Highlight 3 “must-haves” you can prove with outcomes.
- If you cannot prove them, do not rely on the referral to compensate.
- Prefer roles that are actively hiring
- Look for postings that are recent, clearly scoped, and not overly generic.
- If a req looks like a “pipeline” role, ask your contact if it is real and actively staffed.
- Choose the req that best matches the team’s work
- If your contact is on a specific team, prioritize that team’s req when possible.
- A referral is stronger when the referrer can credibly say, “This person fits our work.”
A quick filter you can use
If two reqs look similar, choose the one where you can answer these in one sentence each:
- “I have done this work before.”
- “I can show results.”
- “I can explain my approach.”
- “I can name the tools or methods.”
If you cannot do that, you are likely stretching.
What to say: scripts when a referral portal needs a req number
Use these scripts as templates. Keep them short, specific, and respectful of your contact’s time.
Script 1: you already have the exact req
Send this when you have one clear match.
- Message:
- “Hi [Name], thanks again for offering to refer me. The referral portal needs a specific req. Would you be comfortable referring me to [Job Title], req [REQ-12345]? Here is the link: [URL]. I am a strong fit because [2 sentence fit]. I attached my resume as a PDF. If there is anything else the portal needs, I can send it right away.”
Why it works: You remove ambiguity, supply the req, and give a concise fit narrative your contact can reuse.
Script 2: you found two good reqs and want their guidance
Send this when two postings are genuinely reasonable.
- Message:
- “Hi [Name], the referral portal needs a req number. I found two roles that match my background, and I would love your advice on which is more active or better aligned with the team.
- Option A: [Job Title], req [REQ-11111]: [1 sentence why you fit]
- Option B: [Job Title], req [REQ-22222]: [1 sentence why you fit]
- If you think one is clearly the right target, I will go with that. If both are viable, I would prefer the one that is hiring now.”
Why it works: You limit the decision to two options and ask a practical question your contact can answer.
Script 3: you do not have a req yet, but you want to make progress
Send this when you need help locating the right posting.
- Message:
- “Hi [Name], quick question. I am ready to apply, but the referral portal requires a req number. Is there a specific posting you recommend for [role type] on your team, or should I send you 1 to 2 links I find and you can tell me which is best?”
Why it works: You show initiative while still giving them an easy next step.
Script 4: the company has many similar reqs and you want to avoid the wrong one
Send this when titles are duplicated across orgs, levels, or locations.
- Message:
- “Hi [Name], I see multiple postings for [Job Title] with different reqs. To make sure I choose correctly, can you confirm which org or location your referral should target? I can then send the exact req link and ID.”
Why it works: You avoid a misfire where the referral goes to the wrong organization.
When two reqs fit: how to decide without over-applying
Applying to multiple reqs can help, but it can also create risk. Some companies automatically merge applications or flag duplicates. Others let you apply to several roles, but recruiters still want a clear “primary” target.
Use this decision rule
If you have two good reqs, pick the one that best satisfies these criteria:
- Closest match to your strongest achievements: The role where your best STAR stories map cleanly.
- Most specific scope: Clear responsibilities and must-haves, not vague.
- Best internal alignment: The team your contact knows, or the team closest to their network.
If you still cannot decide, ask your contact one focused question:
- “Which req is most likely to lead to interviews in the next few weeks?”
That question is easier to answer than “Which role should I do with my life?”
If you want to pursue both reqs
Do it deliberately.
- Ask your contact to refer you to one primary req.
- Apply to the second req without a referral, unless your contact explicitly offers to refer you twice.
- Keep your story consistent. Recruiters dislike hearing that you are “open to anything.”
What to do if your contact can only refer to one req
Some portals limit employees to one active referral per candidate, or employees prefer to refer only once.
Here is the right way to respond:
- “Totally understand. Let’s use [REQ-12345] as the primary. If another role becomes a better fit later, I can follow up and we can decide then.”
This keeps the relationship clean and avoids pressure.
How to align your referral ask with behavioral interviews
A referral can help you get seen. It does not replace interview performance. In fact, a referral can raise expectations because the hiring team assumes someone vouched for you.
Build STAR stories that match the req you choose
Once you pick the req, create a small STAR library aligned to that posting.
Aim for:
- 1 story about driving results (metrics if you have them, otherwise clear outcomes)
- 1 story about handling ambiguity
- 1 story about collaboration and conflict
- 1 story about ownership and accountability
- 1 story about learning quickly or ramping up
Then map each story to a bullet in the job description.
Example: STAR story mapped to a req
If the req emphasizes cross-functional execution, your STAR might look like this:
Notice what this does: it makes your referral target credible. You are not just “interested.” You have evidence.
If you want to tailor your prep to the company you are targeting, reviewing real interview experiences can help you anticipate the behavioral themes you will be evaluated on. You can use https://primly.io/community to find free interview reports by company and then practice STAR stories around those themes.
Common pitfalls and how to avoid them
Pitfall 1: sending your contact a long list of reqs
If you send five links, your contact will often do nothing. Give them one clear choice, or two at most.
Fix: “Here is the one I am targeting. Here is a backup if needed.”
Pitfall 2: asking for a referral before you are ready to apply
If your resume is not ready, you might waste the referral window. Some referrals expire or are time-bound.
Fix: Make sure your resume is final, your LinkedIn is consistent, and you can apply the same day.
Pitfall 3: picking a req based on prestige, not fit
A referral does not make you a match for a role two levels above your experience. It can even backfire if you look mis-leveled.
Fix: Choose the req where your recent work most closely matches the responsibilities.
Pitfall 4: vague fit statements
“Passionate about the mission” is fine as a closing line. It is not a fit argument.
Fix: Lead with role-relevant evidence. Tools, scope, stakeholders, outcomes.
Follow-up etiquette: how to nudge without damaging the relationship
If your contact agreed to refer you and you have not heard back, follow up politely.
Follow-up script (after 5 to 7 business days)
- “Hi [Name], quick follow-up on the referral for [Job Title], req [REQ-12345]. No rush, I just wanted to confirm you have everything you need from me. Happy to resend the link or resume.”
If they still do not respond, stop after one more nudge. You can proceed with a normal application and keep the relationship intact.
Actionable checklist: your next 30 minutes
- Find 1 to 2 target postings and copy the req IDs.
- Write a 2 to 3 sentence fit statement for each.
- Choose 3 STAR stories that best match the primary req.
- Send your contact a message using Script 1 or Script 2.
- Apply promptly once your contact confirms.
Conclusion: make the referral easy and the interview inevitable
When a referral requires a specific job req, your job is to reduce friction and increase clarity. Bring the req ID, keep your request tight, and choose the role where you can back up your interest with strong STAR stories. If two reqs fit, collaborate with your contact using a simple either-or question, then commit to one primary target.
Do this well and you get more than a referral submission. You get a clean, credible candidacy that is easier for your contact to support and easier for recruiters to move forward.