The 48-Hour Shortlist
Hour by hour: intake, search, calibration and a shortlist your manager says yes to.
- 01Hour 0: the 20-minute intake
- 02Hour 2: the first search
- 03Hour 6: calibrate with 5 profiles
- 04Hour 24: widen, don't lower the bar
- 05Hour 48: the shortlist that gets a yes
- 06The sprint checklist
Senior Product Manager, Payments. Hybrid in Austin, 3 days a week in the office. The hiring manager is the Head of Product. Goal: 5 to 7 people the manager agrees to meet, sent by hour 48.
Hour 0: the 20-minute intake
Book 20 minutes with the hiring manager on the day the role opens. Video or phone, not email. Run these questions in this order and type the answers as you go.
- 0 to 2
I have six questions. You'll get 5 profiles tomorrow to react to and a shortlist in 48 hours.
Sets the dates before anything else. The manager now knows a yes/no is coming. - 2 to 6
By day 90, what has this person shipped or fixed?
Follow up: "What's broken today that they will own?" Write down nouns: checkout conversion, failed card payments, a new payment method launch. - 6 to 10
If you could check only three things on a profile, which three?
Test each one: "Would you turn down a strong person who lacks this?" If the answer is no, it's a nice-to-have. - 10 to 12
What makes you say no in the first five minutes of a call?
These become your deal-breakers. Get two or three. - 12 to 15
Who from your past teams would you hire tomorrow, and why them?
Ask for their title, the kind of company, and the one thing that made them good. This is your benchmark profile. - 15 to 17
What's the base range, bonus and equity? Where's the ceiling? Is relocation paid?
Confirm the office days and how far people can live from the office. - 17 to 19
Who interviews, in what order, and which two slots next week can we hold for first calls now?
Get the slots into the manager's calendar before you hang up. - 19 to 20
Here's what I heard. Correct anything that's wrong.
Read the must-haves and deal-breakers back word for word.
The one-page output
Send this back within the hour and ask for a thumbs-up.
ROLE: Senior Product Manager, Payments LOCATION: Hybrid, Austin TX. 3 office days (Tue-Thu). Must live within commuting distance or move before start. No relocation package. FIRST 90 DAYS: Own checkout and payment methods. Launch pay-by-bank for US customers. Cut failed card payments at checkout. MUST-HAVES (all three): 1. 4+ years as a product manager owning a payments product (checkout, payment methods, acquiring or payouts) 2. Shipped integrations with processors, card networks or banks alongside engineering 3. Owned a metric tied to money moving: authorization rate, payment conversion, failed payments or cost per transaction NICE-TO-HAVES: B2B software, fraud or risk work, writes their own SQL DEAL-BREAKERS: project or program management only, with no product decisions; will not do 3 office days DO NOT APPROACH: our own staff; our two payment partners BENCHMARK: ex-colleague, PM at a mid-size processor, launched a wallet payment method, trusted by engineers COMP: base $165k-190k, 10% bonus, equity. Ceiling $195k. LOOP: 30-min manager call > 60-min product case > panel (engineering lead, design lead) > Head of Product DATES: 5 calibration profiles Wed 10am. Shortlist Thu 5pm. First calls held Mon 2pm and Tue 11am.
- Paste the one-page intake as your brief. Keep the must-haves, deal-breakers and "do not approach" lines in it.
- Keep the location line as written: hybrid in Austin, 3 days in the office.
Hour 2: the first search
Turn each must-have into what you would see on a profile. People rarely write "owned authorization rate". They write the work.
Write the first brief tight
- Must-haves and deal-breakers only. Leave the nice-to-haves as nice-to-haves.
- Location at commuting distance. You widen at hour 24, not now.
- Read the first 20 people before you change anything. Tag each one: fits all three, misses one, or wrong.
- Aim to read 30 to 50 people before calibration.
Senior Product Manager for payments, hybrid in Austin, TX (3 days a week in the office). Must have: 4+ years as a product manager owning a payments product such as checkout, payment methods, acquiring or payouts; shipped integrations with processors, card networks or banks; owned a money metric such as authorization rate or failed payments. Nice to have: B2B software, fraud or risk work, SQL. Avoid: project or program managers with no product ownership.
("product manager" OR "product lead" OR "product owner") AND (payments OR checkout OR acquiring OR payouts OR "payment methods") AND (authorization OR processor OR "card network" OR ACH OR chargeback) NOT ("program manager" OR "project manager")
- Paste the first brief. Open the Strong matches first. Each one says why it fits.
- Read the reasons on the Possible people. They name the must-have that's missing.
- Shortlist or pass on each person as you read. Ask for more people for the same role if you've read fewer than 30.
Hour 6: calibrate with 5 profiles
Send five profiles before you go wide. Five gets a reply the same day. Fifteen sits in an inbox.
Subject: 5 profiles for Senior PM, Payments: yes or no by 3pm? Hi Dana, Five profiles before I search wide. For each, reply yes or no and one reason. 1. Senior PM, Checkout, mid-size online retailer. Launched two payment methods, owns payment success rate. 2. Product Lead, Merchant Payments, processor. Led a card network integration. 6 years in payments. 3. Senior PM, Billing, B2B software. Owns invoicing and card payments, no processor work. 4. Product Owner, Digital Payments, regional bank. Strong on ACH and real-time payments, consumer only. 5. Engineer turned PM 2 years ago. Built the payouts system before moving to product. Reply like this: "1 yes, owns the metric. 3 no, billing is too far." Thanks, Sam
Read the answers
- Shortlist the five you sent. Pass the ones the manager turned down.
- Type the change from the answers and search again, e.g. "Must have owned authorization rate or failed payments. Billing-only PMs are a pass."
Hour 24: widen, don't lower the bar
The must-haves stay fixed. Widen where people can come from, never what they must have done. Change one thing, read 20 people, then keep or undo it.
1. Adjacent titles
Product Owner, Payments. Technical PM, Payment Platform. Product Lead, Checkout. Senior PM, Billing and Payments. Keep a person only if owning a payments product is still visible.
2. Nearby towns
Round Rock, Cedar Park, Georgetown, Pflugerville, Kyle. Everyone who can make 3 office days counts. Add people further away who are open to moving only if the intake said so.
3. Feeder companies
List who builds the same thing: payment processors, card issuers, digital payments teams at banks, checkout teams at online retailers, and software companies that take payments for their customers, such as restaurant, salon or property management software.
4. Earlier-career signal
Read past roles. A PM in lending today who spent three years on checkout before still meets must-have one. So does a solutions engineer who integrated processors and has since owned a product for four years.
5. Other words for the same work
Money movement, merchant onboarding, disbursements, payment orchestration, risk and disputes. Add the ones the strong profiles from calibration used.
From hour 24, reach out to the people you've shortlisted. Confirm interest, notice period and comp. You need all three for hour 48.
The same five moves work for any role. For a Clinical Nurse Educator in Phoenix: Staff Development Specialist as an adjacent title, Mesa and Chandler as nearby towns, teaching hospitals as feeders.
- Type one change at a time, e.g. "also include people within 30 miles of Austin, such as Round Rock, Cedar Park and Georgetown".
- Next change: "also include Product Owner and Technical PM titles if they own a payments product".
- Ask for more people for the same role when the Strong list runs thin.
- Get email and phone for the people you shortlisted so you can reach them today.
Hour 48: the shortlist that gets a yes
Send 5 to 7 people. Keep 2 or 3 more ready as backups and don't send them. In a thin market, send 3 good people over 7 weak ones and say so.
Per person: three lines, one risk, availability
- One header line: current title, kind of company, where they live and the commute.
- Three lines, one per must-have, in the intake's order. Facts from their history, no adjectives.
- One risk, stated plainly, so the manager can probe it on the first call.
- Availability: interest confirmed, notice period, comp against the band.
- 5 years as PM on checkout and payment methods.
- Led the move to a second processor with two engineering teams.
- Owns payment success rate for card payments.
How to send it
Subject: Shortlist: Senior PM, Payments (6 people) Hi Dana, Six people below, best fit first. All six meet the three must-haves and can do 3 days in Austin. Each has one risk listed. Reply with the names you want to meet by Friday noon. I'm holding Monday 2pm and Tuesday 11am for first calls. [person blocks] Sam
- Order by fit to the must-haves. Put the strongest first.
- Put the reply-by time and the held slots in the first lines.
- Send one email. No attachments to open.
- Get email and phone for anyone on the list you haven't reached yet.
- Send the shortlisted people to your ATS.
- Invite the shortlisted people to an AI interview. They book their own time, and the manager gets the recording, transcript and scores before the first call.
The sprint checklist
Tick as you go. Your ticks stay in this browser.
H0 Intake
H2 First search
H6 Calibrate
H24 Widen
H48 Shortlist
- Run this whole sprint on your next open role: paste the intake, read the Strong matches, shortlist, type changes, invite to an AI interview.
Run your next role in 48 hours
Paste your intake, read the Strong matches with their reasons, and send your manager a shortlist with interview recordings attached. Free trial: 7 days, 100 credits, no card.