Day-Of Tactics

Pre-loop checklist — the morning of

• Reread 01-the-role and your one-paragraph narrative from 02-positioning-from-scratch.
• Skim 14-domain-context quick-recall flashcards.
• Skim 05-deep-dive-secondary KYC vocab one more time.
• Open the the company app on your phone. Glance at the onboarding state. Look at the products.
• Have ready: 3 specific JD lines you can reference; 5 questions to ask them; one project story you can tell crisply.
• Water nearby. Paper and pen. Quiet space if remote.
• Five minutes of slow breathing before the first round. Don't underrate.

Structural moves for PM rounds — the cadence

Every PM-round answer follows roughly the same shape. Burn this into muscle memory:

1. Clarify. Restate the problem. Ask 1-2 sharpening questions. ("Is this Consumer KYC or KYB?" "What segment / region matters most?")
2. Decompose. Sketch the problem space. Show structure before solutions.
3. Segment. Identify whose problem this is. Internal teams? Compliance? End users? Each gets a different answer.
4. Prioritize. Pick the dimension you'd attack first. State why.
5. Metric. Name how you'd know it worked.
6. Risks. Two specific failure modes and how the design handles them.
7. Ship. First version, sequenced; what's in v1 vs v2.

If you can hold this cadence under pressure, you sound senior even when the content is shaky. If you can't, you sound junior even when the content is great.

The "platform answer" structure — what distinguishes you

For any platform design question, walk through these five beats, in this order. Practice until it's reflex:

1. What platform exists? What are the primitives today, what's missing.
2. What's the gap? Specific capability we don't have, named.
3. Who's the customer? The internal team that's blocked. Named, with their use case.
4. What's the metric? How you'd know the platform improved.
5. What's the rollout? Shadow-mode / canary / staged ramp. Audit posture along the way.

This is the single most distinctive answer shape for a Platform PM. Feature PMs answer "what would you build." You answer "what would you build that the team next door would use."

Design-round survival

• Whiteboard a system, not a flow. Boxes (services, stores, queues), arrows (data flow), and one external (vendor or consumer team).
• Name what's versioned. The policy doc? The event schema? The API? Senior signal.
• Name the audit story. Every state transition emits an event. Mention it.
• Name two failure modes. Don't wait to be asked.
• Name the rollout shape. Shadow-mode → canary → ramp. Show you've thought about getting safely from now to then.
• Sandbox and test-mode are a deliverable. Mention this. Most candidates don't.

Metrics-round survival

• State the population first. "Activation rate" means nothing until you say "of which applicants, over which window, excluding what."
• Cohort. Aggregate metrics hide the truth.
• Name two paired metrics and two guardrails. Never propose a single metric in isolation.
• p95 / p99, not averages. Latency averages lie.
• "Why are these numbers different?" runbook. Mention how you'd handle source-of-truth disputes.

Behavioral-round shape

• STAR. Situation / Task / Action / Result. Practice in 2 minutes.
• Pick stories that show Platform PM moves: a migration you drove, an adoption project, a disagreement with eng or Compliance, a wrong decision you reversed.
• Name what you'd do differently. Self-awareness is more persuasive than a clean victory story.
• Don't badmouth past Compliance. Especially in this domain. Reframe constraints respectfully.
• "Crypto conviction" question: show engagement with the product (you've completed KYC; you've made a trade); show interest in the platform problem (the JD line that pulled you in); show curiosity, not faked passion.

Traps to avoid

• Conflating platform with feature. When asked to design something, your first sentence is about the internal customer, not the end user. If it's not, restart.
• Dodging compliance. Don't say "I'd let Compliance figure out the regulatory part." Show you'd partner. "I'd loop Compliance in at design, encode the policy as data, and treat their tooling as a platform deliverable."
• Over-promising velocity. "I'd ship in 4 weeks" without sequencing or migration plan sounds junior. Senior is "first 90-day wave, named partner, named unlock."
• Generic answers. "Activation, retention, NPS" is a beginner stack. Name the specific metric for the specific platform problem.
• Faking depth. If they ask about a vendor / regime / tool you don't know, say so cleanly: "I haven't used Persona; my mental model is X — is that close enough?"
• Three apologies. Acknowledging a gap once is honest. Three times signals you don't belong in the room. You do.
• Long answers. Cap at 90 seconds. If they want more, they'll ask.

Recovery moves when stuck

• Re-clarify. "Let me make sure I understand the question — are we talking about Consumer KYC or KYB?" Buys time, often reveals you had it right.
• Sketch out loud. "Let me think about this in three parts — the customer, the primitive, the metric." Structure is a life raft.
• Reach for a known pattern. Vendor abstraction, rule engine, audit firehose, flow builder, tier-with-grandfathering, sandbox. One of these usually applies.
• Name the trap. If you're stuck because the question is ambiguous: "I think the trap here is X. Want me to assume Y or Z?"
• Say what you don't know. "I haven't faced exactly this — my closest reference point is X. Can I reason from there?"
• Reset. If you've rambled, stop. "Let me restart that more cleanly." This is fine. Interviewers respect it.

What to ask them

End every round with one question. Have 8-10 ready. Pick by who's asking. A starter set:

1. "Which downstream team is most blocked on the current onboarding architecture?"
2. "How does Compliance get involved today — early, late, or somewhere in between? Where do you want to move that?"
3. "What's the current implicit SLA for time-to-launch a new market, and who owns it?"
4. "Is there a single IDV vendor today, or a waterfall? How is vendor health monitored?"
5. "What's the relationship between the platform team and the consumer Growth team?"
6. "What would I be expected to ship in the first 90 days?"
7. "What's the most painful thing a new PM in this seat usually trips on?"
8. "How would you describe the company's posture on regulator engagement — more proactive or more responsive?"
9. "What does the operating cadence look like — what's a typical week?"
10. "What's the team's biggest unsolved problem right now?"

The closing statement

At the end of the loop's final round, have one sentence ready:

That's it. No begging, no oversell. You're closing because you want it; they know you want it because you said so once, cleanly. Now you wait.

Good luck. You're closer than you think.