The opportunity
The Issuing team owns the Stripe card issuing product end to end from the APIs and backend services that power spend cards, debit cards, and charge cards, to the dashboard and embedded components that businesses use to manage their card programs. We build the infrastructure and…
What you'll do
Define and drive the technical strategy for Issuing, including multi-year: architecture decisions across backend services, APIs, and user-facing surfaces.
Own end-to-end technical solutions for critical systems, authorization flows,: spending controls, cardholder management, and card program configuration, ensuring they are reliable, scalable, and operationally sound.
Identify and lead infrastructure investments that unlock new issuing models,: including geographic expansion, new card program types, and platform-level extensibility.
Collaborate closely with product managers, design, and cross-functional: partners across Issuing, Authorization, Clearing and Settlement, and Balances to drive cross-cutting initiatives from design through launch.
Make principled build-vs-reuse decisions and produce clear technical roadmaps: that balance near-term delivery with long-term platform health.
Advise engineering and product leadership on technical trade-offs and their: downstream implications for the business.
What they're looking for
- + years of industry software engineering experience, with demonstrated impact: at a staff or equivalent scope (leading initiatives across multiple teams or systems).
- Proven track record designing and shipping large-scale user-facing products: with distributed backend systems that are both highly available and financially correct.
- Experience leading cross-functional engineering projects end-to-end: from requirements through architecture, delivery, and post-launch iteration.
- Strong API design instincts and the ability to build simple,: developer-friendly interfaces over inherently complex financial and regulatory requirements.
- Ability to influence technical direction and align multiple teams without: direct authority, with excellent written and verbal communication across engineers, product, and leadership.
- High ownership mindset—comfortable with ambiguity, able to define the problem: and the plan, not just execute a predefined spec.
- Clear, precise communication on complex technical topics for both technical and non-technical audiences.
- Experience building or operating real-time transaction processing systems: with strict latency and correctness requirements (authorizations, payments, ledgering, settlement).
