Positioning From Scratch
How to interview honestly for a Payments PM emerging-markets role when your experience doesn't perfectly map. The reframe is the same: name your gap, anchor to what you do bring, redirect to first-principles reasoning.
The three honest starting shapes
Most candidates for this role fall into one of three shapes. Naming yours is the first step — every interview answer flows from it.
| Shape | Likely background | The gap | The strength |
|---|---|---|---|
| A. Mature-market payments PM | Built card payments at a US/EU fintech | Hasn't shipped UPI/PIX/M-Pesa class rails | Knows the primitives, the vendor management muscle, the metrics fluency |
| B. Fintech generalist PM | Built lending, neobank, BNPL, or KYC product | Hasn't owned a payment rail end-to-end | Adjacent domain literacy, compliance-aware, customer-flow thinking |
| C. Non-payments PM (with motivation) | Built marketplaces, SaaS, growth, or platform PM | Doesn't yet have the payments vocabulary | Strong PM craft, prioritisation, exec comms, design-sense |
Almost no candidate has done exactly Payments PM in exactly the corridors the company cares about. The interviewers know this. They are looking for closest-match plus learning posture.
Shape A — Mature-market payments → emerging-market jump
This is the closest match. The interviewer's question in their head: "Do you understand that UPI is not just 'India's Venmo' — that the rail design, regulator posture, P2M economics, and merchant onboarding flow are fundamentally different from card payments?"
"I've owned card-rail conversion in EU and US — auth-rate work, 3DS2 step-up, BIN routing. I haven't shipped UPI or PIX. What I'd bring on day one is the metric and vendor discipline; what I'd ramp on in the first 60 days is the rail-specific mental model, especially the regulator-led design of UPI vs the market-led one of cards."
Show three specific things you know about emerging rails (e.g. UPI mandate flow for autopay, PIX MED return window, M-Pesa STK push UX). That signals you've done the reading. Don't pretend more.
Shape B — Fintech generalist → payments specialist
The interviewer's worry: "Will this person say 'we'll just integrate Stripe' to every problem?" Counter by showing payments primitives fluency without claiming hands-on rail ownership.
"I've shipped KYC and lending product — not a rail in production. I've been around payment ops enough to know what a soft decline is and why retry policy matters, and I've worked with PSPs at integration level. What I haven't done is own the AAR baseline directly. I'd want to spend my first month with the data, the routing config, and one PSP partner before I push hard on roadmap."
The "first month" answer is gold here. Senior payments PMs do exactly this — sit with the data first, don't propose a rail until they understand the existing baseline.
Shape C — Outside payments, motivated
Hardest shape, not impossible. The bar: show you've done real homework, have a thesis on why payments specifically, and can reason about rails at first principles. Don't pretend you have years.
"I'm not a payments PM today — I've been in [growth / platform / marketplaces]. I'm here because I've watched the rails in [country] evolve and I want my next decade in this. I've spent the last [X months] going deep — UPI's NPCI architecture, PIX's BACEN mandate, the cost stack. I'd come in light on shipped payments product but with the PM craft and the appetite. I'd want a payments-engineer partner from day one."
This is honest, and a fraction of hiring managers will respect it. Most won't. Pick your battles.
The crypto literacy overlay
this segment specifically — and crypto-adjacent payments roles broadly — care that you understand the fiat ↔ crypto seam:
- On-ramp: fiat in → crypto credited (the typical first-deposit flow).
- Off-ramp: crypto out → fiat in user's bank.
- Stablecoin settlement: USDC / USDT as a settlement rail in itself (especially cross-border).
- Travel Rule: the FATF requirement that crypto VASPs share originator/beneficiary info on transfers above a threshold.
- Wallet attribution: distinguishing self-custody withdrawals from exchange-to-exchange.
You're not expected to be a crypto-protocol engineer. You are expected to not be surprised by the words "Travel Rule" or "stablecoin rail." See 14-domain-context.
Honest scripts for common interview moments
"Tell me about your most recent payments product."
If you have one — lead with the metric you moved. "We added BIN-aware retry on soft declines in Brazil and lifted AAR 1.8pp on a $X/month volume base." If you don't — pivot to closest adjacent, name it as adjacent.
"What's the biggest payments-product decision you've owned?"
Pick one with reversal cost. PSP switch, rail launch, fraud-threshold change. If you don't have one — talk about a decision of similar shape in your adjacent domain, then name the analogy explicitly.
"What rails do you know best?"
Name two corridors specifically. Don't pad. "UK Faster Payments and Brazilian PIX — I've worked through PIX MED returns specifically. India UPI I've studied but not shipped."
"Why this segment specifically?"
Two beats: the fiat-crypto seam interests you (specific reason), and the portfolio model interests you (rails-by-method-by-geo is a richer PM job than single-rail ownership).
What not to do
- Don't bluff a corridor. If you've never touched UPI, do not improvise about VPAs. They will catch you in three follow-ups.
- Don't apologise five times. Acknowledge the gap once, cleanly, then move on. Repeated apology reads as low confidence.
- Don't conflate adjacent. "I built KYC" is not "I built payments." Name the analogy explicitly.
- Don't claim AAR numbers you didn't own. If you were adjacent to the team that moved AAR, say so.
- Don't disparage your current/last employer's payments work. The interviewer is taking notes on your loyalty.
A mock exchange
"Walk me through the last time you improved authorization rate."
"I haven't directly owned AAR — I was adjacent at [Company], where the payments PM ran retry-policy experiments and I owned the upstream KYC flow that gated first-deposit. What I learned from that adjacency is how much AAR work depends on issuer-level cohorting; the same retry rule that lifts AAR for Brazilian Elo issuers tanks it for European bank-issued cards. If you'd like, I'm happy to reason through how I'd structure an AAR improvement program here from scratch."
That's the move. Honest about scope. Specific about adjacent learning. Offers to reason live. The interviewer almost always says yes.