Product Director
Rise Works
भूमिका के बारे में
Director of Product, Ramps & Identity (Fintech · Global Payments) Location: Remote - United States only (must reside in the U.S.) Eligibility: Must be authorized to work in the United States Team: Product Reports to: CTO (you'll work directly with the CTO) Direct reports: Multiple engineering leads, each owning a product area About Rise Rise is a global payments and payroll platform built for the way modern teams actually work - across borders, currencies, and rails. We make it easy for companies to pay full-time employees, contractors, and freelancers anywhere in the world, in either fiat or digital assets, with the compliance, tax, and identity infrastructure handled underneath. Two things make that possible: ramps - how money gets into and out of Rise, across banking rails, card networks, and stablecoins - and identity - how a customer proves who they are, once and then never has to do it again.
This role owns both. Our Culture We're a lean, high-trust, high-ownership team. We hold a high bar for correctness, security, and accountability - the work is meaningful precisely because the stakes are real.
We value: Ownership over hand-offs. You'll own these product lines end to end and have the autonomy that comes with that. Depth over decks.
We expect product leaders to understand the rails, the ledger, and the failure modes - not just the roadmap. Directness and low ego. We give and receive candid feedback, write things down, and prefer clarity over politics.
What You'll Do Working directly with the CTO, you'll own product for Rise's ramps and identity surfaces - the two systems every customer touches first and trusts most. This is a hands-on, technical product role, not a coordination seat: you'll set direction, sit in the architecture discussions, negotiate with providers, dig into the funnel data yourself, and be accountable for the outcomes. Multiple engineering leads report to you, each owning a product area - so you're accountable for delivery, not just for the plan.
Ramps: money in and money out Own the end-to-end product for funding and payout - ACH, wires, SEPA, local rails in the markets we serve, and stablecoin and crypto on/off-ramps. Own the customer experience of moving money: time to first successful deposit, payout success rate, settlement times, and the clarity of every state in between (pending, held, returned, failed). Drive rail and provider strategy: evaluate, select, and negotiate with banking partners, PSPs, and on/off-ramp providers, and own the business case for each - coverage, cost per transaction, FX spread, settlement speed, and reliability.
Lead new market and new currency expansion - which corridors we open next, what rails they require, and what it takes to launch them. Own the economics: transaction cost, FX, fees, and margin on money movement, with a clear view of unit economics per corridor and per rail. Reduce failure and friction - returned payments, rejected transfers, mismatched beneficiary details, reconciliation breaks - and turn recurring support load into product fixes.
Set direction on the hard parts underneath the surface: how balances stay correct, how a duplicate or timed-out payment is handled, how we reconcile against providers, and what happens when one fails. You don't need to build these - you do need to reason about them and decide what gets prioritized. Define and own provider redundancy: what happens when a rail or provider goes down, and how quickly we route around it.
Identity: turning verification into product Own what we build on top of verified identity. Our compliance team owns collecting and adjudicating KYC and KYB; you own what that verified identity becomes for the customer - onboarding that pre-fills itself for anyone we already know, credentials a customer can present to a partner instead of starting a new application, counterparties who can recognize each other without exchanging documents, and verified status that unlocks higher limits and new products automatically. Rebuild onboarding around what we already know.
Verification is where we lose people - every step a returning or already-verified customer has to repeat is a step you should be deleting. You own pass rates and time-to-verified. Build the attestation layer as a real product: what Rise vouches for, how a customer sees and controls it, how it stays current, and what happens when it expires or is withdrawn.
Build federation - the surface that lets a customer take their Rise-verified status to a partner, protocol, or counterparty, and lets us accept identity that was established somewhere else. This is greenfield and it's yours to define. Ship business identity as more than a form: an org, its owners, its signers, and its counterparties, modeled once so that adding a new entity, a new payer, or a new market doesn't mean starting from zero.
Turn verified identity into leverage elsewhere in Rise - limits that lift themselves, products that unlock without an application, payouts that clear faster because we already know who's on both ends. Give customers something to look at: clear status, clear reasons, and a path forward when something is pending or fails. Trust is a UX problem as much as a controls problem.
Product leadership Lead a group of engineering leads, each accountable for a product area. You set the priorities, hold the bar on quality and pace, keep the areas coherent with each other, and own what ships and when. Grow those leads: give them room to own their product, back their judgment, and be the person who makes their work land with the rest of the company.
Own the roadmap across both areas: strategy, prioritization, sequencing, and the trade-offs, with the CTO as your closest partner. Write clear, specs and decision records that engineers can build from. Work directly with compliance, finance, operations, support, and engineering - these products sit at the intersection of all of them.
Be the internal and external voice for these products: partner c