The Friday memo, and 65 hours to answer it.

Composite framing. This is not the story of a specific Marqee member. "Rachel" is a stand-in for a category of senior growth operator we see often: seven years across two consumer-subscription companies, one clean promotion, a title one step below the one she's ready to hold. Every specific — the Friday drop, the anchor points, the Sunday mock — is the shape a real strategist runs on a real weekend, minus the specific person and the specific employer.

Two things Rachel is wrong about, and one she's right about.

Rachel walks into the intake call at 6pm on a Tuesday. She has seven years of growth work behind her — three years leading paid acquisition at a consumer subscription business, four before that on a lifecycle team at a slightly bigger one. Her current title is Director of Growth. The title she wants next is Head of Growth, at a company small enough that "Head of" is a real seat and not a courtesy.

Her strategist, David, spends the first forty minutes listening. Rachel is fluent about her funnels, careful about the numbers she claims, and honest about the two roles she interviewed for last quarter without help. She got to the final round in both. She lost one to an internal candidate. She lost the other on the take-home.

David doesn't dwell on the loss. He asks her to send him the take-home she wrote, and the feedback she got. He tells her, plainly, that a Head-of-Growth search in this market almost always ends in a task interview — a written memo, a strategy deck, or a live case — and that if the last search ended on a take-home the next one probably will too. That's the surface they're going to prepare for from week one, not week five.

Rachel is right about the title band. She's wrong about two things: she thinks she wants a Series B, and she thinks she wants US-remote. David pushes back on both. Series B growth roles at consumer-subscription companies are usually one-person functions with no budget, which she'd hate. And US-remote in this segment has thinned out — the warmer market right now is Series C-to-pre-IPO, hybrid in three cities. They land on a target list weighted toward Series C companies in New York, Boston, and remote-friendly Toronto, with one Series B kept on the list as a control.

Ten companies, and a hidden workstream.

David runs the shortlist Monday morning. Ten companies land in the top of the sheet. Two get cut by Tuesday — one for a founder who's known to shuffle the growth seat every eighteen months, one for a recent round that came in flat and cut ad spend the same week. Eight names carry forward.

What Rachel doesn't see on her tracker is the second workstream David quietly starts on Wednesday: a folder titled task-interview library. It's a set of five real-shape prompts — the kinds of memos and cases these companies actually assign — pulled from David's own memory and from three peer strategists in the network he checked with over Slack. Rachel doesn't know it exists yet. She'll see it in week three.

The first tailored résumé lands in her review queue Wednesday afternoon. It leads with a lifecycle rebuild she led two years ago — the one hidden two bullets down in her original deck — because five of the eight target roles are lifecycle-heavy, and because that project has a real number attached that she can defend under pressure.

The first door opens, and the shape of the loop appears.

David writes six outreach drafts on Tuesday of week two. Four go to recruiters. Two go to warm referral candidates — the ex-manager on the board of company one, and the former direct report at company seven — with the same script Marqee uses across the board: ask for context first, don't ask for the intro until the second message.

Rachel approves the drafts with one voice edit each. The four recruiter notes go out Wednesday. The two referral pings go out Thursday. By Friday morning, company two's recruiter — the one who ran Rachel's failed loop three months ago — replies with the sentence David was hoping for: "Rachel, we actually just re-opened the VP Growth req. Would love to reconnect."

David flags it in his end-of-week note. Company two is now the front-runner not because it's the best role, but because the recruiter is already warm and the loop is a known quantity. He also notes, quietly, that a known-quantity loop means a known-shape take-home. He goes back to the task-interview library and pulls the prompt that matches company two's last cycle.

Three doors open, and one of them names the memo.

By Wednesday of week three, Rachel has three live conversations: company two (the re-opened role, phone screen Tuesday), company one (warm intro converted to a recruiter call, Thursday), and company four (recruiter reached her cold on LinkedIn after seeing the tailored résumé David pushed to her profile).

Company two's phone screen lasts thirty-five minutes and ends with a sentence David has been waiting for: "We'll get you set for a hiring-manager round next week. Round three will be a written strategy memo. We'll send the prompt on a Friday and it'll be due Monday morning. Just so you can plan."

The panel is scheduled. It's on the Tuesday two weeks out. The memo will drop on the Friday before, at some point after 4pm. Rachel calls David the next morning to talk through it. He tells her the truth: this is the interview. Nine hiring managers out of ten decide on the memo, and the panel confirms.

David does two things that day. First, he tells Rachel to move nothing else that week — no company-one prep on the memo weekend, no company-four screen booked for the following Monday. Second, he opens the task-interview library and starts building the scaffolding: a memo template in Rachel's voice, a framework doc that David will not send until Rachel has drafted her own, and a mock schedule sitting in Rachel's calendar as a hold — Sunday, 10am to noon.

4:47pm on Friday: the prompt lands.

The recruiter's email hits Rachel's inbox at 4:47pm on Friday. The subject line is polite. The attached PDF is one page. The ask is not one page: a five-page strategy memo, written to the CEO, on how she would rebuild the growth engine in the first two quarters, with a specific stated budget and a specific stated retention floor.

Rachel screenshots the prompt and drops it in her Marqee thread by 4:52pm. David sees it inside three minutes because his Friday afternoon is deliberately kept light for exactly this reason — Fridays are when memos, take-homes, and expedited-loop asks land, and a strategist who's fully booked at 5pm on Friday is a strategist who can't do the weekend work that decides the search.

What a DIY weekend looks like, and what this weekend looks like.

Before we walk the hours, here's the reason we frame this piece around the task-interview weekend at all. A memo like this one is where most senior candidates lose the role, and it's almost always for the same reason.

The hour-by-hour of the weekend.

Here is what actually happens on Rachel's side of the loop, from 4:52pm Friday to the Monday morning submit. Times are approximate; the sequence and the judgment calls are the shape of every task-interview weekend we run.

Tuesday morning, and the sentence she doesn't have to invent.

The panel starts at 10am on Tuesday. Four people on the other side: the recruiter Sam, the CEO, the CMO, the product lead. Rachel opens with a one-minute frame — the three anchor points in order, plain, no throat-clearing — and hands the room over to questions.

The CEO opens with the exact question David rehearsed on Sunday. Rachel uses the sentence from the cue card almost word-for-word, and then departs from it into her own phrasing because she's calm enough to riff. The CMO pushes on the retention floor. Rachel defends it. The product lead asks a question about the lifecycle experiment scaffold and Rachel finds herself, thirty seconds in, arguing for a version of the plan that's slightly bolder than what she wrote — a version David flagged as an option in the cue-card margin.

The panel runs long, which is the signal every strategist wants. Sam pings David the same afternoon: "team is meeting Wednesday. I think we're in a good spot." David sends Rachel a short note. Two sentences. Don't refresh the inbox. Go be a person tonight.

The follow-up thank-yous go out Wednesday morning under Rachel's name, drafted by David, one per interviewer, each one referencing a specific moment from the panel. This is a step almost every senior candidate skips. It's cheap and it works.

The offer, the counter, the sentence the CEO liked.

Sam calls Rachel Friday of the same week with a verbal. The number is inside the band David and Rachel talked about at intake, but at the low end of it. Base is where they hoped; equity is under. Sign-on is not on the table.

Rachel wants to say yes. She's tired. David does not tell her to say no. He tells her to say "thank you, I'm excited, I'll come back to you Monday with a couple of specifics" — and to go be a person for the weekend.

Monday morning they write the counter together. Two asks, not five. Equity up meaningfully; a defined 90-day review with a written path to expanded scope. No sign-on. No relocation. Nothing that reads as extractive from a first-in-seat hire. The counter is warm, not aggressive, and it references the memo directly — Rachel closes with the sentence the CEO reacted to on Tuesday, reframed as a promise about the first 90 days.

The company accepts the equity ask and the review cadence inside 48 hours. Rachel signs on Wednesday. The search is done. The task-interview weekend, six weeks earlier, is the reason.

What you'd see on your side.

Your tracker looks the way Rachel's tracker does. Shortlist on Monday, tailored materials in your review queue by Wednesday, outreach going out under your name, and — if the loop tips into a task interview — a strategist who was ready for it in week one, not scrambling in week four. On the weekend the memo drops, you'd see three touchpoints on your calendar with David's name on them, one shared doc, and a cue card in your inbox by Sunday night. You wouldn't see a template. You wouldn't see a boilerplate memo with your name pasted at the top. You'd see your own draft, made better by an editor who reads for the CEO's real question, not the prompt's surface phrasing.