Code Story episode
S11 Bonus: Redefining the Merchant Lifecycle, Reducing Integration Friction, and Capitalizing on the Gen Z Tap-to-Mobile Shift with Tiffany Johnson, Chief Product Officer at NMI
Jul 31, 2025 · Season 11 · 22 min
Embedded Payments for your application
Tiffany Johnson is originally from Texas, but grew up in California. At a young age, she was a bit of an adrenaline junkie, partaking in skydiving, snowboarding, wakeboarding and gymnastics. In school, she fell in love with Econ, Mgmt, and Statistics - and eventually, fell into the payment industry by accident. Outside of tech, she has been married for 20 years with 3 kids. Her kids are all snow skiers, though she doesn't hold that against them as a snowboarder.
A few years ago, Tiffany was contacted about a new opportunity at a decades old company in the payments space. This company wanted to bring to market a solution around embedded finance, specifically for SaaS solutions - and Tiffany was the perfect product leader for the role.
This is Tiffany's creation story at NMI.
Sponsors
Paddle.comSema SoftwarePropelAuthPostmanMeilisearchMailtrap.TECH Domains (https://get.tech/codestory)Links
https://www.nmi.com/https://www.linkedin.com/in/tiffany-johnson-b339242/
Checkout our episode stacks on Stacklist! https://stacks.codestory.co/
Advertising Inquiries: https://redcircle.com/brands
Privacy & Opt-Out: https://redcircle.com/privacy
More episodes
Keep listening
Topics
Explore related conversations
Fractional CTO vs full-time CTO: which does your startup need?
A practical comparison of a fractional CTO and a full-time CTO: cost, scope, when each makes sense, and the questions to ask before you hire either one.
Scaling an engineering team from 5 to 50
How to scale a startup engineering team from 5 to 50 people: when to add managers, how communication breaks, what process to add at each size, and what to leave alone.
Engineering metrics that matter (and the ones that don't)
Which engineering metrics to track at a startup: DORA metrics, quality and reliability signals, what they tell you, and why measuring individual output backfires.