Handle extended team-matching uncertainty

# Overview This plan assumes Friday (Day 0) is when you learned the two teams had not responded. It spans 14 calendar days (~10 business days) and balances persistence with professionalism. It leverages light, value-forward touchpoints; establishes objective escalation triggers; and includes proof-of-value (POV) assets tailored to a Data Scientist. Key principles: - Single-point-of-coordination: keep the primary recruiter as hub; do not cross-wire multiple recruiters on the same thread. - Add value with each touch: every follow-up includes a small, relevant asset or insight. - Time-box uncertainty: pre-commit to milestones (checkpoints, escalation, and widening outreach) so you avoid drift. # 14-Day Plan (Day 0 = the Friday update) - Day 0 (Fri): - Reply to primary recruiter: reaffirm interest, summarize fit, ask for decision timeline, share a concise POV one-pager (see below). Request permission to share a sanitized notebook/case study if helpful for the teams. Propose a Day 3 check-in. - Send tailored thank-you notes to each hiring manager (if you met them) with a concrete 30/60/90 focus for their problem space. - Day 1–2 (Sat–Sun): - Prepare and stage POV assets (links ready but not all sent at once). - Set up a tracker (sheet/CRM) with columns: Team, Recruiter, Last Touch, Next Touch, Status (Green/Yellow/Red), Risk/Notes, Artifacts Sent. - Day 3 (Mon): - Light nudge to primary recruiter: ask if the teams need additional evidence; offer a short technical artifact (e.g., 2–3 slide mini-deck on experiment design or model monitoring). - If a secondary recruiter is attached to a specific team, send a separate, brief availability update (do not CC across teams) and include a one-sentence value recap + link to a relevant asset. - Day 4 (Tue): - If at least one team acknowledges, pause on that thread for 2–3 business days while you nurture others. - If both are silent: request clarity on where you stand in their funnel (e.g., top-tier/hold) and ask whether to explore additional teams. Offer 2–3 other team profiles you’d be excited about (signals flexibility, reduces their routing work). - Day 5 (Wed): - Send a targeted insight to each team based on your conversation (e.g., a 150-word note on metrics you would prioritize or a sketch of an AB test design). Keep it lightweight; avoid speculative strategy documents. - Day 6 (Thu): - If still no tangible next step from any team: ask recruiter for a timeboxed next checkpoint (e.g., “Can we tentatively target a by-Friday update?”). - Internally mark both teams as Yellow if no response; Red if zero acks since Day 0. - Day 7 (Fri): - Decision point: broaden intra-company outreach if no scheduled next step. Ask recruiter to introduce you to 1–2 additional teams that match your profile (provide a short blurb and keywords). - If you have active external pipelines, signal to recruiter you’re progressing elsewhere; request a realistic timeline (this sets an implicit hold date without ultimatums). - Day 8–9 (Sat–Sun): - Prepare a short demo video or notebook README walkthrough for a sanitized DS project (3–5 minutes). Queue but don’t blast. - Day 10 (Mon): - Escalation threshold A: if you have had no meaningful update (no next interview scheduled or explicit feedback), ask recruiter to loop in their recruiting lead or the hiring managers for clarity. Keep tone cooperative. - If recruiter agrees, proceed. If they discourage, ask for a firm by-Day-12 decision checkpoint. - Day 11 (Tue): - Share your demo link with the most engaged thread only, or as a single attachment to the recruiter for distribution (avoid overwhelming teams). - Reconfirm availability for the next 5 business days. - Day 12 (Wed): - Escalation threshold B: if you have a competing process approaching final round or an offer window, formally communicate timeline constraints. Request confirmation whether to continue pursuing these teams or pivot to additional teams internally. - Day 13 (Thu): - If momentum remains low, broaden externally (more applications/referrals) while keeping the door open. Update the recruiter that, to manage timelines, you’re progressing in parallel elsewhere and would appreciate any acceleration if possible. - Day 14 (Fri): - Final checkpoint: summarize status across all threads to the recruiter, thank them for the partnership, and agree on next touch (or close the loop if no fit now, asking to be considered for future openings). Archive threads with a polite pause message. # Cadence, Channels, and Guardrails - Cadence: - 1–2 touches per thread per week, max. Prefer 3–4 business days between nudges unless time-sensitive (offer clock). - Always include new value (insight, artifact, clarified availability). - Channels: - Email primary; LinkedIn only if you already have rapport or email stalls >7–8 business days. - Guardrails: - No reply-all across different teams. - Keep artifacts short and skimmable; do not attach large codebases. Use links with permissions set to “view only.” - Stop sending new material after 3 value drops unless explicitly requested. # Proof-of-Value (POV) Artifacts for a Data Scientist Use 1–2 of these per touch (rotate): - One-pager: 30/60/90 for the team’s domain (e.g., experimentation roadmap, model monitoring KPIs). - Sanitized notebook (link): demonstrates EDA → baseline → evaluation with a clear README (2–5 minutes to skim). - Mini-deck (2–3 slides): AB test design, power analysis, or metrics framework for a plausible feature. - Metric design brief: north-star vs guardrail metrics with example trade-offs. - Short Loom/video (3–5 minutes): quick walkthrough of a prior project’s impact and learnings. - Business impact snippet: a 150-word story with measurable impact (e.g., “drove +3.2% CVR via causal uplift model; MDE and guardrails outlined”). # Message Templates Keep these concise; personalize placeholders. 1) Recruiter update (Day 0) Subject: Thank you + next steps Hi [Name], Thanks for the update. I remain very excited about the Data Scientist role. Based on my conversations with [Team A/B], here’s a brief one-pager on how I’d add value in the first 90 days. Happy to share a short, sanitized notebook if helpful. Could we target a quick checkpoint on [Day 3/Mon] to align on next steps and timeline? Thanks again, [Your Name] 2) Team thank-you with value add (same day) Subject: Thank you + initial ideas Hi [Hiring Manager], Great speaking this week. Based on our chat about [problem], I’d focus first on [metric/experiment/design]. Here’s a concise 2-slide sketch outlining approach and success measures. Open to feedback and happy to dive deeper if useful. Best, [Your Name] 3) Light nudge with artifact (Day 3 or 5) Subject: Quick follow-up + brief artifact Hi [Name], Sharing a brief [notebook/mini-deck] illustrating how I’d approach [relevant task, e.g., AB test design for feature X]. If the team needs any additional context from me, I’m happy to provide it. I’m available [windows]. Thank you, [Your Name] 4) Clarify status and broaden (Day 4–7) Subject: Status check and routing Hi [Name], Checking in to understand where I am in the funnel with [Team A/B]. If timing is tight for them, I’d welcome intros to other teams focused on [ML experimentation/modeling/analytics]. Here’s a short blurb on my profile and interests to make routing easy. Appreciate your guidance, [Your Name] 5) Escalation (via recruiter) (Day 10+) Subject: Timeline alignment and support Hi [Name], To help me manage timelines, could we loop in [recruiting lead/HM] for clarity on fit and next steps? I remain highly interested and can be flexible this week if that helps scheduling. If an intro isn’t ideal, could we set a by-[date] checkpoint? Thanks for partnering on this, [Your Name] 6) Offer-timeline disclosure (Day 12+) Subject: Courtesy heads-up on timelines Hi [Name], I’m progressing with another process that may finalize by [date]. This remains my top choice; if there’s a path to expedite or route to additional teams, I’d be grateful. Please let me know what’s feasible, and I’ll plan accordingly. Best, [Your Name] # Escalation Triggers and Ladder Triggers (use the first that applies): - T1: No material update (no scheduled next step or actionable feedback) after 5 business days since last touch. - T2: Explicit stall acknowledged by recruiter (“still interviewing others”) persisting beyond 1 week. - T3: You have a competing offer or near-final stage elsewhere with a decision date within 5–7 days. - T4: You’ve provided 2–3 targeted POV assets and availability, but no decision signal. Ladder: 1) Ask primary recruiter to escalate to recruiting lead or HM for clarity (Day 10). 2) If recruiter confirms interest but scheduling remains blocked, propose a brief calibration call with HM (15 minutes) instead of a full round. 3) Director-level escalation only with recruiter’s blessing or an existing relationship; frame as seeking guidance, not bypassing process. # Decision: Wait vs. Broaden Outreach Use a simple status model: - Green: Response within 48–72 hours, clear next step → wait and nurture; no extra widening. - Yellow: Acks but vague timing after 3–5 business days → softly broaden within the company (ask for 1–2 new team intros). - Red: No acks or updates after 5–7 business days, or explicit stall → broaden within the company and externally; set a hard checkpoint date. Decision points: - Day 4–7: If Yellow or Red, request additional team matches. - Day 7–10: If still no scheduled next step, expand external outreach (light), maintain one-touch-per-week cadence internally. - Day 12+: If timelines conflict (offer pressure), ask for accelerate-or-park decision; otherwise continue broader search. # Risks and Mitigations - Risk: Appearing pushy. - Mitigation: 3–4 business days between nudges; each touch adds value; ask permission to share artifacts; keep messages <150 words. - Risk: Cross-thread confusion among recruiters. - Mitigation: Hub-and-spoke via primary recruiter; avoid multi-team CCs; maintain a tracker. - Risk: Over-disclosing strategy or sensitive IP. - Mitigation: Sanitize data; keep methods high-level; watermarked view-only links. - Risk: Bypassing the recruiter. - Mitigation: Request recruiter’s blessing before director/HM outreach; frame as seeking alignment. - Risk: Opportunity cost of waiting. - Mitigation: Pre-set checkpoint dates (Day 7, 10, 12) to trigger widening. # Minimal Tracker Schema (to operationalize) - Columns: Team | Recruiter | Last Touch (date) | Next Touch (date) | Status (G/Y/R) | Trigger met? (T1–T4) | Artifacts Sent | Notes. - Rule: Do not contact a thread earlier than its Next Touch unless an offer timeline changes. This structure keeps momentum, protects relationships, and reduces drift while giving you objective checkpoints to escalate or broaden at the right time.