A senior PM search, six weeks in.

Composite framing. This is not the story of a specific Marqee member. "Sofia" is a stand-in for a category of senior product manager we see often: three-plus years at one mid-stage company, real platform experience, no warm network in the market they're trying to enter next. Everything below — the targeting call, the outreach drafts, the referral overrides — is the shape a real strategist runs, minus the specific person and specific employer.

The intake call and the first honest disagreement.

Sofia, a senior product manager, walks in with three years at a mid-stage fintech and a job description she's already convinced herself she wants: Director of Product. She's tired of shipping into a roadmap someone else wrote, and the title jump feels like the point.

Her strategist, Marcus, spends the first call disagreeing gently. He's run this exact kind of search half a dozen times. A director title with three years at one mid-stage company is a stretch application every time — she'll clear a phone screen at maybe one in twenty postings, and the ones she clears will pull her into panels she's not ready to convert.

Marcus's counter is different: go one level up in scope, not two levels up in title. Senior PM roles at bigger, more disciplined shops. Group PM or Lead PM at Series B/C companies with a real chance at a promotion path. Twelve target companies mapped in the first ninety minutes, not thirty. And the criteria isn't "sounds interesting" — it's "has a warm referral path we can actually walk."

Sofia pushes back. Marcus doesn't cave. They land on a compromise: two Director postings kept on the list as stretch swings; the rest built around the plan he described. The plan lands in her inbox before the end of the day.

Twelve companies become the actual list.

Marcus spends most of Monday running the shortlist. Twelve names go in the top of the sheet. He's not looking for openings yet — he's looking for shape. Which of these companies has a PM org he'd let Sofia walk into? Which has a director he can reach cleanly? Which has posted three PM roles in six months (a signal of build-out) versus one every eighteen (a signal of caution)?

By Tuesday, twelve becomes eight. Four companies are cut for reasons Sofia wouldn't have seen — a public performance issue, a founder who's known to churn PMs, a hiring freeze rumor a strategist in the network flagged, and one company where the last three PMs left in under a year.

What Sofia sees in her tracker on Wednesday morning is the clean version: eight companies, each with two to four warm role fits, each with a note explaining why it's on the list and which recruiter or PM leader the outreach is going to. No mention of the four cuts. Marcus doesn't hide them — she can see the "cut" tab if she wants — but he doesn't waste her attention on them either.

The first tailored résumé variant lands in her review queue by Wednesday afternoon. It's not a rewrite — it's a rearrangement, moving her platform work up above her feature work because five of the eight target roles are platform-heavy.

The side door opens on a Thursday.

Marcus writes five outreach drafts on Tuesday of week two. Each is in Sofia's voice — clipped, dry, specific — because he read six of her old Slack posts and a Medium piece she wrote in 2024 before he touched the keyboard. Voice matters more than most candidates believe. A recruiter reads one line before deciding whether to open the second.

Two of the drafts go to recruiters directly. Three go to referral candidates — the ex-colleague, the former manager, the ex-teammate — asking not for an intro but for a five-minute call about what the target team is actually building. Marcus's rule: never open the referral ask cold. Get context first; ask second, in the second message, only if the context conversation went well.

Sofia approves every draft with a light edit. The two recruiter notes go out Wednesday morning. The three referral pings go out Thursday. By Thursday afternoon, two of the three referral candidates reply — one with a "sure, let's chat Friday," one with an unprompted "I can just introduce you to our head of product if you're open."

That unprompted intro is the moment the shape of the search changes. Marcus flags it in his end-of-day note: this is now a warm-path search, not a portal-first search. Priorities shift.

The first phone screen, and a landmine avoided.

Rob, the recruiter at company one, replies on Thursday of week three. The role is open; he'd like a phone screen next week. Meanwhile the referral candidate from company two has now written a two-paragraph intro email to their head of product. And company five's recruiter — the one Marcus reached from a 2023 relationship — has quietly forwarded Sofia's résumé to the hiring manager without any prompting.

That's three doors in one week. Marcus's job now is triage: which two do they run at full speed, which one do they slow-play, which of the eight originals do they quietly deprioritize because the calendar is filling?

The landmine of the week isn't the interviews — it's a message from company four (the public fintech, a cold door on the original list) offering an "expedited process, take-home this week, panel next week." On paper, that's momentum. Marcus recommends passing. The role is a lateral, the team has shipped one product in eighteen months, and if Sofia takes their take-home she loses a week of prep for the two searches that actually matter.

Sofia agrees, reluctantly. Marcus writes the polite pass. Company four is off the list before Friday.

The strategist wants to send something Sofia wouldn't have.

On Monday of week four, Marcus writes a message he wants to send to the head of product at company two — the one whose team member is willing to make a warm intro. The intro exists. But Marcus's instinct is that Sofia should skip the intro and reach the head of product directly, before the warm-intro momentum cools.

This is the human-in-the-loop moment we make a big deal about. Marcus doesn't send it. He drops the draft into the approval queue, marks it "strategist recommends we go direct — override the referral flow" with two sentences of reasoning, and Sofia sees it in her tracker before her first coffee.

Sofia's initial reaction is to say no — she wants to honor the referral. Marcus books a five-minute call. On the call he explains: the referral is a person, not a channel. If they take the intro, the intro sets the pace, and the pace at company two is currently slow. If Sofia reaches out directly and mentions the referral by name in the note, she keeps the warm signal and controls the tempo.

Sofia approves. The note goes out at 4:12 that afternoon. The head of product replies inside an hour, with two calendar slots for Thursday.

Two real prep cycles, not eight fake ones.

By Saturday of week five, Sofia has three real conversations in front of her: two phone screens converted to panel loops (companies one and two), and one exploratory conversation (company five) that Marcus is coaching her to treat like a peer meeting, not an interview.

The prep doc for company one is twelve pages. It's not a script. It's a map: the team's recent product releases in order, the head of product's public writing summarised in her voice, the four questions Sofia is most likely to be asked based on the JD phrasing, three product-teardown questions Sofia should ask them, and a one-page pre-read on their competitive landscape.

They do a mock loop on Sunday morning. Marcus plays the head of product for forty-five minutes. He does not go easy. He asks about a platform migration Sofia hasn't led directly and watches how she frames what she has done. He interrupts twice. He asks the "why us, why now" question in three different phrasings.

The debrief takes another thirty minutes. Marcus's note isn't the interview itself — it's a two-line reframing of how Sofia talks about the internal-tools rebuild. She's been describing what she built. He wants her describing what she chose not to build, and why. That's the answer that lands with product leadership.

The one that mattered, and what happens next.

Sofia's panel at company one is on Tuesday of week six. Three interviewers, two hours. She walks in with the prep doc in her head, not her hand. The head of product opens with the platform rebuild question, exactly as Marcus predicted. Sofia answers it the way they rehearsed — starting with what she chose not to build.

The technical interviewer is harder. He asks about a distributed-systems decision Sofia was adjacent to but didn't own, and she catches herself about to bluff. She doesn't. She says who owned it, what her role actually was, and how she'd think about the decision now. Marcus told her in prep: never claim a decision you didn't make. Product leaders can smell it in four sentences.

Company two's first-round is Thursday of the same week. It's smaller — head of product plus one senior IC. Warmer. Sofia spends less prep on it and more on being present.

Thursday evening, Marcus writes the debrief. Two rounds, two signals: company one wants a second panel; company two moves her to a take-home. The take-home is scoped honestly (four hours of real work, not a twenty-hour trap). Sofia's calendar for the following week has two real second rounds on it. The search isn't over — it's now in the phase where prep and stamina start to matter more than surface.

What you'd see on your side.

Your tracker looks the way Sofia's tracker does. Shortlist on Monday, tailored materials in your review queue by Wednesday, approvals landing daily, outreach going out under your name, referral map growing in the background, and a strategist chat thread where you can push back the way Sofia did on the Director titles. You never see a bot draft your voice. You see a human draft it, mark their reasoning, and wait for your approval — even when they think you should override their own recommendation.