Product Lead

Latitude is an early‑stage payments fintech building modern infrastructure for global money movement. We help businesses move value instantly, securely, and with full compliance-leveraging blockchain rails while delivering a seamless, enterprise‑grade experience.

Our team has built and scaled payments and financial infrastructure at Uber, Coinbase, Stripe, Amazon, and Facebook-bringing deep experience across fintech, marketplaces, and global‑scale systems. In January 2025, we raised an $8M seed round led by NEA, with participation from Lightspeed Faction, Coinbase Ventures, Paxos, Bitso, Solana Ventures, and others. We've since raised a $35M Series A led by Oak HC/FT, with participation from existing investors New Enterprise Associates (NEA), Coinbase, and Faction VC, and new investors Wilson Sonsini Goodrich & Rosati and OpenFX -bringing our total raised to $43M.

We're looking for our first Product hire: an experienced product leader who wants to own the product function end-to-end at a fast-growing fintech.

The Role

We're looking to make our first product hire; someone to work directly with the founders every day and own the roadmap, discovery, specs, launches - everything that makes a product successful.

Today, this is a hands-on role - not a management role. You will inherit a real product with real customers moving real money across a growing set of corridors, an experienced engineering team that ships fast, and a large backlog of decisions. As we scale, you'll build the product organization underneath you; today it's all hands on deck.

You'll work on two things at once: what ships this quarter, and where global money movement is going over the next three to five years. Which rails will matter, which regulatory shifts are coming, what we own versus rent. We need to build for now and the future.

Lastly, because we sell infrastructure to technical buyers, this role sits close to the metal. You should be comfortable reading an API spec, reasoning about the failure modes of a payment flow, and arguing about idempotency and reconciliation with engineers who will push back.

You'll have the opportunity to:

Own the roadmap. Set product direction across corridors, rails, and platform capabilities. Decide what we build, what we don't, and in what order — then defend those calls to the team, our customers, and our leadership.

Run discovery with technical customers. Talk directly to the engineers and operators who integrate with us. Turn what they tell you into specs precise enough to build from.

Define the core platform surfaces. Help create excellent payment orchestration, ledgering, payout and collection flows, partner integrations, public APIs, and much more.

Turn regulation into product. Payment rules change, and they change our architecture. You'll work with engineering, compliance, and our banking and fintech partners to translate new requirements into product decisions with clear tradeoffs and timelines.

Manage partner-facing product work. Every day we work with banks and financial partners. You'll scope integrations, negotiate capability gaps, and hold partners to their commitments.

Set the product bar. Establish how we write specs, run launches, communicate roadmap, and make decisions. You'll define what shipping excellent software looks like.

What We're Looking For

Required

6+ years in product, including senior or lead ownership of a technical product with real users. Titles vary; what matters is that you've been the person accountable.

Domain expertise in at least one of our core areas

Cross-border payments, FX, and international money movement

Domestic payment rails and scheme integrations (ACH, RTP, SEPA, SPEI, PIX, UPI, InstaPay/PESONet, or equivalents)

Crypto and stablecoin infrastructure, and on/off-ramps

Treasury, liquidity management, and ledgering

Identity, fraud prevention, and compliance

Experience shipping API-first or developer-facing products to technical buyers.

Comfort in regulated environments. You've shipped alongside compliance and legal constraints and treated them as design inputs rather than obstacles.