Outreach that gets a reply — sent by a real person, never a bot.
Your strategist maps the recruiters, the referral paths, and drafts the message. You personalize it, time the send, and press send. This track is the craft of side-door outreach, referral discovery, and submitting on official company sites correctly — to ATS-standard.
Course modules
Work top to bottomThe side door & what your send is worth
Why a human-sent message clears filters a bot can't, and where outreach fits the operating model.
Every search runs two channels at once. The front door is the official application on the company's careers site — necessary, but it lands in a queue with hundreds of others. The side door is a direct, human message to a recruiter or a referral — it pulls your member out of that queue.
Your job on this track is the side door, plus submitting the front-door application correctly so the two reinforce each other.
Mass-blasted outreach gets spam-flagged, throttled, and burns the member's account reputation. A real person sending a tailored, low-volume message is why it lands — it reads as human because it is, it stays inside platform terms of service, and it protects the member's name.
What you're protecting
- Deliverability — low volume, varied wording, no link-spam, so messages reach the inbox.
- The member's reputation — every send carries their name; one careless blast can get them muted by a recruiter for good.
- ToS compliance — we never scrape, auto-connect, or bulk-DM. Human pace, human judgment.
Channels & finding the right person
Pick the channel a recruiter actually reads, and identify the one human worth messaging for this role.
Match the channel to who you're reaching and how warm it is. Default order of preference:
Channel decision order
- Direct work email (when verifiable from a public source) — highest open rate, reads as professional, leaves a paper trail. Best for a specific in-house recruiter or hiring manager.
- Professional-network message — best for a cold-but-relevant connection; a short connection note + a follow-up once accepted. Keep it human and brief.
- Application/ATS "message recruiter" — use when the posting exposes it; lowest friction, ties directly to the application.
- Reply on a job-post thread — only if the recruiter publicly invited replies. Never hijack an unrelated post.
Your strategist surfaces a shortlist of people connected to the role. You choose the one with the most leverage and the lowest friction:
- In-house recruiter / talent partner for that team — usually the best first contact: they own the req and can move a candidate forward.
- Hiring manager — higher leverage but busier; reach them when you have a strong, specific fit story or a warm thread.
- A future teammate — great for referral discovery (next module), softer for a cold ask.
Run this before any recruiter draft leaves your screen:
- Still there? Confirm the recruiter currently works at the company (titles and people change fast).
- Right scope? They recruit for this function/level, not an unrelated team.
- Verified channel? The email or handle comes from a legitimate public source, not a guess.
- Applied first? The member has an official application on file to reference.
Writing the message that earns a reply
Subject lines, the opening hook, the single ask, and personalization that proves you read.
Five parts, under 120 words total. Longer than that and you've buried the ask.
- Subject — specific and human: role + a concrete hook. "Senior Data PM — shipped 2 platform launches at scale".
- Hook (1 line) — why this company/team, proving you read the posting and aren't blasting.
- Fit (2 lines) — the two most relevant proof points, mapped to the role's top requirements. Numbers beat adjectives.
- The ask (1 line) — one clear, low-effort request (see next lesson).
- Close — name, one link (résumé or profile), no wall of attachments.
The fastest way to kill a reply is to ask for too much. One ask, sized to the relationship's warmth:
- Coldest: "Is this role still open / who owns it?" — a tiny information ask.
- Warm: "Would a quick look at my application help?" — references the front-door submit.
- Warmest: "Open to a 10-minute call this week?" — only when there's real signal.
Your strategist gives you a solid 80% draft. Your edits make it land. Add one detail no template could have — a recent product launch, a shared background, a specific line from the posting — and cut anything generic.
Pass the "could this go to anyone?" test
- If you could send the message unchanged to a different company, it's too generic. Add the irreplaceable detail.
- Cut flattery the member wouldn't actually say. It has to sound like them.
- One genuine reason beats three vague compliments.
Timing & the follow-up sequence
When to send, how long to wait, and the 2-follow-up cadence that doubles replies without nagging.
Send to be read, not buried. General guidance — always defer to the recruiter's local timezone:
- Best window: Tuesday–Thursday, mid-morning (≈9–11am their time), after the inbox-clearing rush.
- Avoid: Friday afternoons, Monday before 9am, and weekends — low attention, easy to lose.
- Send fresh, not stale: reach out within a day or two of the member applying, while the req is active.
Most replies come from a follow-up, not the first message. Two follow-ups, then stop. Each one adds value — never just "bumping this up."
The sequence
- Day 0 — Initial message. The full note from Module 03.
- Day 4–5 — Follow-up 1. Short. Re-state fit in one line and add one new proof point or a relevant update. Keep the same thread.
- Day 10–12 — Follow-up 2 (last). Brief, gracious, leaves the door open: "I'll leave it here — happy to reconnect if timing changes." Then stop.
How you respond to a reply protects the relationship for next time:
- "Yes / let's talk" — confirm fast, propose two concrete times, loop the member's concierge.
- "Not now / not a fit" — thank them warmly, ask to stay in touch for future roles. A graceful "no" keeps the door open.
- Silence — that's a soft no after two follow-ups. Log it, move on, never escalate.
Mapping the path in
Find who can refer your member — first-degree, second-degree, alumni, and community ties.
A referred application is read by a human with internal credibility attached. It's the highest-conversion channel in the search — which is exactly why the ask (Module 06) must be handled with care.
Your job in this module: build a clean map of who could plausibly refer, ranked by how warm and how well-placed they are.
Your strategist surfaces candidate connections; you verify and rank them. Work outward by warmth:
- First-degree — people the member already knows at the company. Always the first ask.
- Second-degree — a mutual connection who can make a warm intro. Ask the mutual, not the target, first.
- Alumni / shared background — same school, past employer, bootcamp, or program. Shared ground lowers the barrier.
- Community ties — relevant professional groups or networks the member genuinely belongs to.
Referral mapping touches the member's network and third parties. Stay member-first:
- Member consent — confirm the member is comfortable approaching a given contact before any ask goes out.
- Their account, their data — work from the member's own connections; we don't scrape or sell the network.
- Confidential searches — if the search is confidential, treat the contact list with extra care and escalate any doubt.
The ask & referral etiquette
How to make the referral ask easy to say yes to — and the etiquette that keeps relationships intact.
A referral asks someone to spend their own credibility. Lower the effort to near zero: hand them a ready-to-forward blurb, the role link, and a one-line "why me." Never make them write it.
The etiquette that keeps doors open
- One ask per contact. If they decline or go quiet, don't re-ask. Respect it.
- Never make them lie. If they barely know the member, ask for a softer "pass along," not a personal vouch.
- Close the loop. Always thank them and tell them the outcome — referred-and-hired or not. That's how the relationship survives for the next role.
- The member's voice. The ask goes from the member, in their tone — you draft and the member (with their concierge) sends.
Applying on official company sites — correctly
The front-door SOP: clean ATS fields, the right files, and the parsing gotchas that sink good candidates.
Always apply through the company's own careers site / official ATS — never a sketchy third-party repost. Run this every time:
- Confirm the source — the posting is live on the official careers page and the req is still open.
- Use the tailored, approved résumé for this role (the concierge has signed off on it).
- Upload the right format — a clean, parse-safe PDF unless the form requests .docx. No tables/columns that break parsing.
- Let it parse, then correct — after upload, fix every mis-parsed field rather than trusting auto-fill.
- Answer screener questions truthfully — work authorization, location, comp range — exactly as the member instructed. Never fabricate.
- Capture the confirmation — save the req ID and confirmation so outreach can reference it.
Common parsing failures to catch
- Multi-column / table layouts parse out of order — dates and titles end up scrambled. Use a single-column résumé.
- Headers/footers and text boxes often drop entirely. Keep contact info in the body.
- Mis-mapped fields — the ATS auto-fills "company" into "title". Read every field after parse.
- Date format mismatches — normalize to the form's expected format.
- Duplicate/old profile — if the member has an existing ATS profile, update it rather than creating a conflicting one.
Every submit is logged to the member's dashboard: role, company, date, confirmation/req ID, and which résumé version went out. Proof-of-work is part of the promise — the member can see exactly what was done on their behalf, and when.
Honesty guardrails in every send
The non-negotiables: no fake humans, no guarantees, FTC disclosure, consent, member-first.
- Never present a draft as someone it isn't. Messages go in the member's real voice with their knowledge — we don't pose a draft as a different person, and we don't invent people.
- Never overclaim, never claim "human" we don't deliver. Position: strategist-led, with real human accountability on every send. Both are true; say both.
- Never guarantee outcomes. No promising interviews, offers, or salaries — to recruiters or members. FTC-safe language only.
- Disclose appropriately & respect consent. Work from the member's account with their approval; their data stays theirs.
- Member-first, always. Even with our recruiter network, the candidate is the client — never the product.
Run this on every outreach message and every application before it leaves:
- Verified — right person, right channel, every claim true and checkable.
- Voice — sounds like the member; nothing they wouldn't actually say.
- One ask — single, low-effort, no implied guarantee.
- Consent — member approved this contact and this send.
- Logged — recorded to the dashboard for proof-of-work.
Some moments need a strategist or escalation, not an outreach send:
- Confidential search — member doesn't want a current employer to know. Pause and confirm the approach.
- A recruiter responds with a problem — dispute, complaint, or anything legal-adjacent. Hand to the concierge.
- Member distress — if a member is struggling, care comes before the next message.
Practical: run a real outreach play, end to end
A graded scenario — map, draft, edit, time, and send (in sandbox) — then the track assessment.
You'll be handed a sample member and target role. Working with your strategist's tools, you'll map the recruiter and one referral path, edit the drafted messages, choose the timing, submit the front-door application in the sandbox, and run the pre-send checklist. A reviewer grades against the SOPs in this track.
A 12-question assessment covering channels, the message, cadence, referral etiquette, the official-site submit SOP, and the honesty guardrails. Pass at 80%. Combined with the required Operating Model module, this earns your Outreach Specialist certification.