# Interview Prep Briefs & Interviewer Intel — Job Seeker Pipeline

Covers the workflow for when an interview gets scheduled for a role the pipeline tailored. Canonical example: Lumen Digital Experience Strategist screen, 2026-08-04 (brief built 2026-07-31).

## 1. Build the brief from the submitted artifacts, never from memory

Pull, in this order:
- The per-job JSON in `/root/.hermes/staging/<job>_<date>/` (exact bullets they hold)
- The submitted cover letter (depth disclosures the interviewer may probe)
- The tailoring memo in the vault (honest gaps left visible, open questions nobody answered — those become questions TO the interviewer)
- The JD text (`jd.txt` in the staging dir)

Everything in the brief must be consistent with what was submitted. The interview is lost by drifting off the resume into claims that can't be supported, or by apologizing for calibrated depth disclosures that already passed the screen.

## 2. Identify and classify the interviewer FIRST

Ask Rob for the invite name or LinkedIn URL. **LinkedIn profile URLs block extraction** — don't burn time on web_extract/browser. Instead `web_search` `"<name>" <company> LinkedIn` and classify from the search-result title/snippet (headlines carry role + focus, e.g. "Senior Recruiter @ Lumen | Marketing & Communications Recruiting").

Classification drives the whole brief's weighting:

| Interview type | What it actually is | Brief core | De-prioritize |
|---|---|---|---|
| **Recruiter screen** | Pattern-match: resume matches req, comp works, communication, red flags | 90-sec positioning, comp answer, why-left/why-back, availability, consulting-question | Technical deep-dives, platform specifics |
| **Hiring manager** | Scope, judgment, team fit | STAR stories mapped to JD bullets, the open questions from the tailoring memo | Comp detail (defer to offer stage) |
| **Practitioner/peer** | Depth probe — will test the familiar-tier tools (e.g. AEM ContextHub) | Depth-map say-it-this-way table, honest calibration | Positioning fluff |

If the interviewer is unknown, note it and prep recruiter-screen weighting as default. One question for any recruiter screen: *"Who would I meet next?"* — the name unlocks a targeted round-2 brief.

## 3. NEVER script a "why did you leave" answer without confirming the real story with Rob

Hard rule, learned 2026-07-31: the first Lumen prep brief scripted "left in the April 2023 restructuring" — inferred from dates and industry context. Rob corrected it: **he left Lumen by choice for a +$35K raise and broader scope at Trimble.** A fabricated departure narrative contradicts what he'll say naturally, wastes the strongest version of the story, and can collide with what references/former coworkers know. Ask "why did you actually leave X?" before drafting any departure answer. Same rule applies to gaps, title changes, and consulting-chapter framing.

## 4. Boomerang-candidate framing (returning to a former employer)

Recruiter screens at companies with layoff history probe flight risk. Structure:
- **Departure:** the real reason, one sentence, confident. A raise/promotion leave is a *strong* answer — the market valued him higher, no performance cloud. Don't volunteer the dollar figure unless probed.
- **Why back:** "this role specifically" close — name what the role owns that he was adjacent to. That framing IS the flight-risk answer (the unasked question: "will he leave again for the next raise?").
- Never editorialize about the former employer's troubles (stock, layoffs, churn) — "I follow the company" is enough.

## 5. Recruiter-screen comp answer pattern

When the JD posted a band: name the band back. *"I saw the posted range — $X to $Y for Colorado — and that works as a frame. Given [tenure/stack], I'd expect the upper half, but I'm flexible on structure."* Signals homework done and no offer-stage surprise. Specific anchor number only if pressed. Never volunteer a number first; leverage talk is offer-stage.

## 6. Working org intel from public sources

No official org chart exists for most targets. Reconstruct a working chain from: company IR/exec-bio pages (C-suite), press releases (new SVP/VP hires), and LinkedIn headlines via web_search (directors/managers). 2026-07-31 example: two searches surfaced the likely Lumen HM (Director, Digital Experience — headline verbatim matched the JD's mandate) plus the CMO chain and two peer managers. **Label all of it as inferred** — titles/reporting lines shift, restructures happen; tell Rob to verify through his ex-coworker network rather than treating it as gospel. When a likely HM is named, check whether their public positioning (headline, posts) matches a story in Rob's background — if so, that story gets promoted in the brief.

## 7. Inbound DM from the hiring team (post-application or cold-inbound)

When a hiring manager or company recruiter DMs Rob about a role (SOVRA / Chaitra Srinivasa, 2026-07-31 — inbound HM DM for a role tailored the same day):

1. Treat as referral-grade signal; application cost already paid.
2. Reply with the tailored resume attached if the role is already tailored; **skip the cover letter** — the DM reply does its job.
3. Answer their exact asks (usually resume + availability): 2–3 concrete windows with time zone, and tell Rob to adjust to his real calendar before sending.
4. Check proposed windows against in-process interviews for conflicts first.
5. Draft, don't send — LinkedIn DMs go from Rob's account. Name the exact vault file to attach.

## 8. Ex-coworker network outreach (pre-interview intel)

When Rob has former colleagues at the target company, the pre-screen ping asks for intel, not sponsorship:
- Who owns the team / who is the HM (make it specific if org intel already surfaced a name — "is this role on X's team, and what's she like — UX-led or MarTech-led?" gets faster answers than "who owns web experience?")
- Growth vs backfill; team posture
- Send 1–2 days before the interview, 2–4 direct DMs max (shotgun reads anxious), don't ask for a referral submission once already in process (can tangle the application), accept offered intros.

## 9. Recruiter screen with salary max disclosed upfront

Some recruiters surface the comp ceiling in the scheduling email rather than waiting for the screen. This is a comp-screening subtype distinct from the "posted band" pattern in §5.

When the recruiter's invite says "the maximum we can offer is $X":
1. **Decide your posture before the call, not during it.** Three paths: accept $X as your number, negotiate on the call (hard without leverage), or decline. Rob's call — if $X is below his floor, the call is a fit-check, not a negotiation.
2. **Accepting $X cleanly is a signal, not a weakness.** Recruiters measure candidate drama. Saying "I'm comfortable with that number given the fit" removes her negotiation burden and moves the conversation to the role itself. This is especially powerful at PE-backed companies where budget ceilings are real.
3. **Do NOT negotiate in a 30-minute mutual-fit screen unless she opens the door.** A recruiter screen is not an offer call. Starting with "can we get to $X+5" before she's decided to forward you makes you high-drama.
4. **If $X is below your floor, the $X ceiling is a gift — it's telling you the role isn't ready.** A PE-backed company that can't pay market for a Manager-level AI marketing role is either underfunding the seat or doesn't have the mandate to ship. Both are red flags worth surfacing in your post-call debrief.

## 10. Recruiter emotional motivators (what the recruiter actually needs)

A recruiter screen is not a skills test. It's a risk-assessment call. The recruiter is evaluating three emotional questions:

1. **"Will this candidate embarrass me in front of the hiring manager?"** Her #1 fear. She forwards you → you can't articulate your experience → the HM loses confidence in her judgment → she looks bad.
   - Your move: speak in specifics, not buzzwords. Have a 30-second story with a measurable result ready for every major bullet. Prove you can represent yourself, which means you'll represent her well.

2. **"Will this candidate make my life easier or harder?"** She's measured on time-to-fill, quality of hire, and pipeline efficiency. Candidates who drag out salary negotiations, go dark, or accept then back out are nightmares.
   - Your move: be decisive about comp. If you like the role, accept the number and move forward. Speed and decisiveness are signals of low drama. Recruiters champion low-drama candidates internally.

3. **"Can I sell this candidate to the hiring manager as different from the other ten?"** For narrow roles (AI + marketing + B2G), she sees lots of "I'm passionate about AI" candidates and very few who can describe a working agent they built.
   - Your move: lead with concrete artifacts — "I built a lead qualification agent in n8n that runs in under a minute" — not "I'm excited about AI innovation." The builder identity is your differentiator.

## 11. Pitch differentiation: recruiter screen vs. hiring manager

The pitch length and structure must match the interviewer type. A hiring-manager pitch is a 5-minute structured speech. A recruiter pitch is a 2-minute conversational confirmation that you're real.

| Element | Recruiter screen (~2 min) | Hiring manager (5 min) |
|---|---|---|
| Opening | 30 sec: "I'm a builder with 10 years at Lumen/Trimble/PMI, last 2 years building AI agents in Claude/n8n/Zapier with governance built in" | 30 sec: same opening, but add the "why this role" frame |
| AI governance | 30 sec: "I build three things from day one — data classification, human-in-the-loop checkpoints, disclosure standards" | 2 min: expand into how this removes the trust barrier for government audiences |
| 90-day plan | **Do NOT mention.** Recruiter doesn't need to know this. | 2 min: days 1–30 listen, days 30–60 ship first agent, days 60–90 build governance framework |
| Military frame | 15 sec: "Special Forces veteran — public service isn't abstract for me" | 1 min: expand into why accountability and trust matter for B2G |
| Comp | 10 sec: "I'm comfortable with $X given the fit" | Only if asked — defer to offer stage |
| Close | Ask what the HM is looking for beyond the JD | Ask the 4 HM questions (see §12) |

**Pitfall — do not send a 30/60/90 plan to a recruiter.** It reads as presumptuous at the screen stage. She's filtering for "can you talk, are you real, will you not embarrass me." A 30/60/90 doesn't answer those questions. Save it for the hiring manager interview as a leave-behind. Exception: if the call goes exceptionally well and she explicitly asks "is there anything you'd like me to include?" — then offer it.

## 12. Four questions to ask the recruiter

Don't wing the "do you have questions for me" moment. Have these written down:

1. **"What's the one thing the team is struggling with right now that this role is supposed to fix?"** — Reveals whether they have a real problem or are hiring to a headcount plan.
2. **"Who does this role report to, and what's their background?"** — Shows you're thinking about sponsorship and decision-making authority.
3. **"What's the budget authority for AI tools and experiments in the first 90 days?"** — Separates real mandate from title-only. If they say "we'd need to justify every purchase," that's a signal.
4. **"What does success look like at 6 months from your perspective?"** — Forces her to quantify. If she can't answer, the role is undefined.

## 13. Post-recruiter-screen follow-up email

Send same day, within 2 hours of the call. Short — she'll read it in 15 seconds between calls.

**Subject:** Great speaking with you — Rob Blake / Marketing Innovation Manager

> Hi [Name],
>
> Thanks for the time today and for being straightforward about the salary range — that transparency is refreshing and it's why I'm still interested.
>
> A couple of things I wanted to reinforce from our conversation: I'm a builder first, which is why the SOVRA role stands out. I design and ship production AI agents in Claude, n8n, and Zapier with governance and human-in-the-loop checkpoints built in from day one — not experiments. The government agency audience makes that posture non-negotiable, which is exactly why I want to do this work.
>
> On the [salary] — I'm comfortable with that number given the fit and what I see in the role. I'm here because I want to build, not because I'm negotiating a figure.
>
> What would be most helpful from me next? I'm happy to walk through specific agent builds I've shipped, provide references from stakeholders at Lumen or Trimble, or whatever else moves this forward on your end.
>
> Looking forward to it.
>
> Rob Blake  
> [phone]  
> LinkedIn.com/in/robkblake

**Why this works:**
- Reinforces the builder identity (her differentiator hook for the hiring manager)
- Accepts comp cleanly (removes her negotiation burden)
- Ends with an offer to provide more (makes her job easy)
- Short — recruiter-readable in under 20 seconds