.png)
Most recruiting friction comes from one ancient, unsolved problem:
Everyone is working from a different mental model of the role.
Hiring managers think they’re hiring “a strong engineer.” Recruiters think they’re hiring “a backend engineer, mid-senior, Python, maybe.” Candidates think they’re applying for “whatever this job posting is trying to say.”
And then we all act surprised when the funnel is messy.
A Role Launch Pack fixes that. It’s a one-page artifact that makes the role real—internally and externally.
What goes in a Role Launch Pack (the parts that actually matter)
1) The win condition
- “In 90 days, this person has ___.”
Not “responsible for.” Not “will support.” A real outcome.
2) The ideal candidate profile (in plain English)
- “They’ve done ___ before.”
- “They love ___.”
- “They struggle with ___.”
This is where you quietly stop hiring for vibes and start hiring for fit.
3) The tradeoffs
This is the cheat code.
- “This is not the job if you need ___.”
- “This is the job if you want ___.”
Tradeoffs increase trust and reduce churn.
4) The proof candidates will care about
Pick 3–5 proof points aligned to the role’s motivators:
- Who they’ll learn from
- What they’ll own
- How performance is measured
- What “good” looks like
- What the team has shipped recently
5) The interview loop (and why it exists)
Candidates don’t hate interviews. They hate random interviews.
Explain:
- “This stage tests ___ because the job requires ___.”
Now your process sounds like competence, not bureaucracy.
Why it works
A Role Launch Pack forces alignment before the role hits the market. It also becomes the source material for:
- Better job descriptions
- Better recruiter outreach
- Better hiring manager screens
- Better interview questions
- Better closing conversations
You stop inventing the message 30 times across 30 conversations. You write it once.
The “do it this week” version
- Schedule a 45-minute role kickoff.
- Bring recruiter + hiring manager + one high performer.
- Fill in the five sections above.
- Done. Ship.
Then: reuse it. Improve it. Don’t make it “a doc that lives in a folder.” Make it the backbone of the role.
If you want a repeatable system that makes Role Launch Packs—and everything downstream—feel easy, that’s baked into the Employer Brand Operating System.
