Referral Ask
When To Use
A role opened where a former colleague works, and you are not sure you can ask. They have seen your work, and you have not spoken for a long time. This skill answers two things: is the relationship ready for this ask today, and if it is, how do you ask so that no is as easy as yes?
When Not To Use
If this would be your first message to them in years, start with Reason to Write, which carries no ask. If they have offered a conversation and you want to learn about the team first, use Informational Interview Questions and come back here afterwards.
Inputs
- The person: how you know them, what work of yours they saw first hand, and when you last spoke
- The role: title, level, the link to the ad, and whether you have applied or will
- Your Target Role Brief, and the row from your Career Evidence Inventory you would most want them to remember
If you have none of this, I start from the person, the role and your last conversation, and mark the output as a first draft.
Approach
Referrals follow relationships, a common careers-service convention: someone who refers you puts a little of their own name beside yours, so they need to know your work and to have heard from you lately. A large experiment on one professional network (A Causal Test of the Strength of Weak Ties, Science, 2022) linked moderately weak ties to more job moves. It is specific to that platform, and it promises nothing about any one ask. For an experienced person "they know my work" is often yes and "we have spoken recently" is often the no. The failure this prevents: a referral request that lands after six silent years and leaves a good former colleague working out how to decline.
Workflow
- Ask at most three questions: when you last spoke and what recent means to you, what they saw of your work first hand, and whether you have applied or will.
- Run four checks, each yes or no with its evidence: you have spoken recently; they know your work first hand; the role fits your Target Role Brief; you have applied or will.
- Any "no" gives "not yet", said plainly, with what would change it: a catch-up first, sharing something you made, or applying first. Stop here and do not write points.
- All yes: write points that ask whether they would be comfortable referring you, not whether they will. Name the role and why it fits, in your words.
- Add what makes yes simple and no easy: the link to the ad, a two line summary they could forward (role, level, the one thing you are known for, taken from an evidence row), and "no problem at all if not".
- Check the points: two or three, no pressure, no deadline pushed onto them. You write the message and send it.
Output Format
# Referral Ask Check
**Person:** [name, how you know them] · **Role:** [title, level, link to the ad]
## The four checks
| Check | Yes / No | Evidence |
|---|---|---|
| We have spoken recently (recent means [your definition]) | [yes / no] | [when, about what] |
| They know my work first hand | [yes / no] | [what they saw] |
| The role fits my brief | [yes / no] | [which criterion] |
| I have applied or will | [yes / no] | [date] |
## Outcome
[Ready / Not yet] · [if not yet: what would change it]
## Points to make (only if ready)
1. [The role and why it fits, in your words]
2. [Would you be comfortable referring me, and what I can send]
3. [The easy no: "no problem at all if not"]
## Two line summary they can forward
[Role and level] · [the one thing you are known for, from evidence row [ID]]
## Decision
You decide whether to ask now or wait by [date]; the other person decides whether to refer you.
Done When
- All four checks are answered yes or no, with evidence
- A "not yet" names the step that would change it
- Points appear only when every check is yes, and the ask is a question with an easy no
- The summary holds nothing an evidence row does not show
Quality Bar
- The checks describe the relationship and the role, never the other person
- No promise that asking leads to a referral or an interview
- Points, in your words to write; the easy no is always in them
- Never an ask to someone you have not spoken to, and never a deadline put on them
- You decide whether to ask and write it yourself; the two line summary says only what an evidence row shows.
Next
Run pmjob-recruiter-screen (Recruiter Screen Prep) to be ready when the process starts.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: pmjob-referral-ask3description: Runs a Referral Ask Check on the relationship and the role, says "not yet" plainly when it is, and when ready gives points for asking whether a former colleague would be comfortable referring you, with an easy no and a two line summary they can forward. Use for "run pmjob-referral-ask", "should I ask for a referral", "can I ask a former colleague to refer me", "is it too soon to ask", "how do I ask for a referral", "a role opened where my old manager works", "referral request points", part of the Claude Guide for Product Interviews Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/pmjob-referral-ask6---78# Referral Ask910## When To Use11A role opened where a former colleague works, and you are not sure you can ask. They have seen your work, and you have not spoken for a long time. This skill answers two things: is the relationship ready for this ask today, and if it is, how do you ask so that no is as easy as yes?1213## When Not To Use14If this would be your first message to them in years, start with Reason to Write, which carries no ask. If they have offered a conversation and you want to learn about the team first, use Informational Interview Questions and come back here afterwards.1516## Inputs17- The person: how you know them, what work of yours they saw first hand, and when you last spoke18- The role: title, level, the link to the ad, and whether you have applied or will19- Your Target Role Brief, and the row from your Career Evidence Inventory you would most want them to remember20If you have none of this, I start from the person, the role and your last conversation, and mark the output as a first draft.2122## Approach23Referrals follow relationships, a common careers-service convention: someone who refers you puts a little of their own name beside yours, so they need to know your work and to have heard from you lately. A large experiment on one professional network (A Causal Test of the Strength of Weak Ties, Science, 2022) linked moderately weak ties to more job moves. It is specific to that platform, and it promises nothing about any one ask. For an experienced person "they know my work" is often yes and "we have spoken recently" is often the no. The failure this prevents: a referral request that lands after six silent years and leaves a good former colleague working out how to decline.2425## Workflow261. Ask at most three questions: when you last spoke and what recent means to you, what they saw of your work first hand, and whether you have applied or will.272. Run four checks, each yes or no with its evidence: you have spoken recently; they know your work first hand; the role fits your Target Role Brief; you have applied or will.283. Any "no" gives "not yet", said plainly, with what would change it: a catch-up first, sharing something you made, or applying first. Stop here and do not write points.294. All yes: write points that ask whether they would be comfortable referring you, not whether they will. Name the role and why it fits, in your words.305. Add what makes yes simple and no easy: the link to the ad, a two line summary they could forward (role, level, the one thing you are known for, taken from an evidence row), and "no problem at all if not".316. Check the points: two or three, no pressure, no deadline pushed onto them. You write the message and send it.3233## Output Format34```markdown35# Referral Ask Check36**Person:** [name, how you know them] · **Role:** [title, level, link to the ad]37## The four checks38| Check | Yes / No | Evidence |39|---|---|---|40| We have spoken recently (recent means [your definition]) | [yes / no] | [when, about what] |41| They know my work first hand | [yes / no] | [what they saw] |42| The role fits my brief | [yes / no] | [which criterion] |43| I have applied or will | [yes / no] | [date] |44## Outcome45[Ready / Not yet] · [if not yet: what would change it]46## Points to make (only if ready)471. [The role and why it fits, in your words]482. [Would you be comfortable referring me, and what I can send]493. [The easy no: "no problem at all if not"]50## Two line summary they can forward51[Role and level] · [the one thing you are known for, from evidence row [ID]]52## Decision53You decide whether to ask now or wait by [date]; the other person decides whether to refer you.54```5556## Done When57- All four checks are answered yes or no, with evidence58- A "not yet" names the step that would change it59- Points appear only when every check is yes, and the ask is a question with an easy no60- The summary holds nothing an evidence row does not show6162## Quality Bar63- The checks describe the relationship and the role, never the other person64- No promise that asking leads to a referral or an interview65- Points, in your words to write; the easy no is always in them66- Never an ask to someone you have not spoken to, and never a deadline put on them67- You decide whether to ask and write it yourself; the two line summary says only what an evidence row shows.6869## Next70Run pmjob-recruiter-screen (Recruiter Screen Prep) to be ready when the process starts.7172## About the makers7374This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).