Positioning From Scratch
How to interview honestly when your background is half-fit. Two common shapes — feature-PM-going-platform and platform-PM-new-to-regulated — and the language that turns a gap into signal.
Start from where you actually are
Almost no candidate has every box ticked: 5+ years PM, platform experience, regulated experience, crypto conviction, vendor management chops, strategy-doc track record. Most strong hires for this seat have two or three of those, not all six. The interview is not where you pretend; it's where you connect what you do have to what the role needs.
When an interviewer asks about a missing experience, they almost always want one of two things: (a) can you reason about it without having lived it? or (b) do you know what you don't know? Both are answerable. Neither requires fabrication.
The two common shapes
Most candidates for this role land in one of two backgrounds:
| Shape | What you have | What's the gap |
|---|---|---|
| Feature PM going platform | End-user instinct, shipping cadence, metrics fluency | Internal-customer mindset, API-as-product, backward-compatibility discipline |
| Platform PM new to regulated | Internal-customer chops, infra fluency, strategy-doc craft | KYC/AML, sanctions, regulators, Travel Rule, compliance partnership |
| Compliance/Ops adjacent | Deep domain, regulator-readiness | Platform PM craft, eng partnership, prioritization at scale |
Each has a clean reframe. Pick yours and stop trying to be the other.
If you're a feature PM going platform
The platform shift is real but learnable. The mental moves that distinguish a platform PM from a feature PM:
- You don't ship UI; you ship APIs and docs. Your PRD is half spec, half developer guide.
- Your customer is a peer PM with a roadmap. They can fork you. Adoption is sales.
- Backward compatibility is sacred. Feature PMs deprecate easily; platform PMs version everything.
- The metric is adoption + velocity, not engagement. "How many teams launched something on my platform this quarter?" beats DAU.
- Strategy is upstream of roadmap. Platform PMs write the doc that sets two-year direction; feature PMs respond to quarterly priorities.
Concrete bridge language: "I've spent two years owning [feature]. The thing I learned doing it is that the bottleneck for shipping in our area was that each team rebuilt the same identity-verification path. The platform problem is what I want to work on next — internalizing that the customer is the next PM, not the end user, was the biggest shift in my head."
Pick one feature you shipped. Re-tell the story with "the team next to ours" as the protagonist instead of the end user. If you can't, you've found the gap. Practice it five times before the loop and you'll be fluent.
If you're a platform PM new to regulated
This is the more common shape and the easier reframe. Platform craft transfers; the regulated overlay is mostly vocabulary and a different shape of constraint. Things to internalize fast:
- Regulators are a stakeholder, not the boss. They constrain. Operations and Compliance interpret the constraint into policy. Your platform encodes the policy.
- "Approved" is a state. An onboarding flow has a regulatory-approval state distinct from a code-deploy state. You can deploy a configuration that policy hasn't blessed; you must catch that in CI, not at the regulator.
- Audit beats analytics. Every state transition needs an immutable, replayable log. This is not optional; this is the product.
- Velocity within the perimeter is the goal. The shape of your platform's value is "fast inside the lines."
Concrete bridge language: "I've built two platforms — internal data platform and an experimentation platform. The pattern that translates is: encode the constraint as data, not as a gate. For onboarding, the constraint is jurisdictional KYC policy. I want to learn the regulatory vocabulary fast so I can have a real conversation with Compliance about which checks belong in the platform's policy engine versus which belong in a vendor's decision logic."
The crypto-fluency question
The JD names "passion for Bitcoin and crypto" explicitly. If you don't have a long track record in crypto, this matters less than it reads. What interviewers usually want:
- You've used the company (or a comparable exchange). You have an account. You've completed KYC. You've made a trade.
- You can name two or three things you find compelling about the space. "Self-custody," "permissionless markets," "settlement finality" are all real answers.
- You can name a wrinkle that distinguishes crypto onboarding from fintech onboarding (Travel Rule, source-of-funds on-chain, wallet-attestation, sanctions screening including wallet addresses).
You don't need to have run a node or held BTC since 2013. You do need to sound like you've engaged with the product.
Don't bluff conviction. "I'm not a maximalist but I've used the product, I've completed KYC twice across two exchanges, and the platform problem you're hiring for is one I'd want to work on at any regulated fintech — crypto adds the Travel Rule and on-chain attestation wrinkles, which I find interesting" is stronger than fake passion.
The language of honest gaps
Stock phrases that work. Memorize the shape, fill the slot:
| Situation | Language |
|---|---|
| You've never shipped a platform | "I've shipped features that became reusable inside my team. The platform discipline I'm building toward is [X]. Closest reference point: [Y]." |
| You've never worked in regulated | "I haven't worked with regulators directly. My closest reference point is [GDPR work / privacy review / SOX]. Want me to reason about [KYC question] from first principles?" |
| You don't know a vendor name | "I haven't used Persona. I've read about it; my mental model is that it's an IDV provider with a workflow builder and a decision API. Is that close enough to keep going, or do you want to grade me on specifics?" |
| You're light on years | "I'm at four years rather than five. The compounding has been steep — most of my recent work is platform-shaped. I'd rather be measured on the work." |
Building your one-paragraph narrative
Have a single paragraph rehearsed. Four beats:
- Edge — the unfair advantage you bring (specific, not generic).
- One project — the most recent, most relevant. What changed because of it, measurably.
- Bridge — point at one specific line of the JD that's the work you want next.
- Honest gap — the thing you'd be ramping on, and your concrete plan for closing it in 90 days.
Example skeleton (Platform PM coming from fintech-adjacent):
"I'm a Platform PM. My edge is that I've built two internal platforms — a data platform and an experimentation platform — and the second one displaced a hand-rolled stack that three teams had been maintaining. The displacement only worked because I treated the migration as a sales process: tier-one customers got white-glove, tier-two got self-serve, tier-three got docs. The line in the JD about turning isolated onboarding flows into a unified platform is exactly that shape of work. The gap is regulated: I haven't shipped a KYC platform, only adjacent compliance tooling. My plan: spend the first 30 days deep with Compliance, partner with a senior regulator-facing eng on policy modeling, and shadow two ops escalations a week so I learn the failure modes before I make any."
What not to do
- Don't fake years. Recruiters will check, eng leads will smell it, and the trust-debt costs you everything.
- Don't list every onboarding term in the JD back at them. Vocabulary without judgment reads as a cram.
- Don't apologize three times. Once is clean; three times signals you don't believe you should be in the room.
- Don't badmouth Compliance teams from a prior job. Even if true. Especially in this domain.
- Don't claim crypto conviction you don't have. Curiosity is enough; faked passion isn't.
You're going in honest, prepared, and curious. That's the posture. The content fills in.