Technical Program Manager, Infrastructure

We're Stripe. Here's what that means.
We build the financial infrastructure for the internet. Companies of every size — from Fortune 500s to two-person startups — run their payments, revenue, and growth through us. Our mission fits in one sentence: expand the internet's economic potential. Saying it is easy. Doing it is the hard part, and that's where you come in.
The team
Stripe's infrastructure teams keep the lights on for everyone else. They build the secure, fast, dependable layer that every product sits on top of. The goal is simple — make sure developers, whether they started last Tuesday or have been here since the early days, have tools that actually work the way they're supposed to.
The role: Technical Program Manager, Infrastructure
This job puts you at the center of the technical initiatives that touch multiple engineering teams at once. We need someone who can own planning, drive communication, and push large projects across the finish line — projects that make our internal platforms better for the people who use them every day. You'll work closely with engineering and product leads, cutting through hard problems so teams downstream can ship without constantly tripping over the same issues.
Most of your time will be spent with Service Infrastructure — the group behind the frameworks, async systems, and tooling Stripe engineers touch constantly. They also run the company-wide refactoring projects that keep things scaling without falling apart, and you'll be right in the middle of that.
What the job actually looks like
You represent the internal customer. Talk to teams, figure out where they're getting stuck, and notice the patterns nobody else has bothered to connect. Turn complaints into requirements. Push for fixes that solve the real problem, not the symptom.
You write things people actually read. Proposals, status updates, technical docs — all of it needs to be clear enough that people don't have to ask three follow-up questions. Good writing here means faster decisions everywhere else.
You run the migrations nobody wants to own. Working with Engineering Managers, Tech Leads, and other TPMs, you'll scope the work and keep it moving even when ten things are happening at once and none of them are simple.
You stay close enough to the tech to be useful. Sit in on design discussions, anticipate where things will break before they do, help weigh trade-offs honestly. Nobody's asking you to write production code — but you'd better understand the system well enough to ask the question that stops a bad decision before it ships.
You build process that's worth the time it takes. Set up metrics that mean something, bring in approaches that have actually worked elsewhere, and keep adjusting instead of running the same playbook on autopilot.
You make the teams around you sharper. Coach where it helps. Push back where it's needed. Part of this job is raising the bar on how teams execute, not just tracking whether they hit a date.
You handle ambiguity without freezing up. Not every path forward is obvious, and you'll need to build buy-in anyway — sometimes through data, sometimes through sheer persistence.
You let evidence drive the call, not instinct. Combine metrics with a real understanding of the space to help leadership make decisions they can stand behind.
You own the plan everyone's reading from. When a dozen teams need to move in the same direction, your documentation is what keeps them aligned.
You're the one tracking what could fall through the cracks. Timelines, dependencies, resourcing — across programs that span entire engineering orgs. If something's slipping, you're the first to know and the one fixing it.
Who we're hiring
There's no mythical perfect candidate, and we're not pretending otherwise. Meet the bar below, and we want to talk to you. Everything after that is a bonus, not a requirement.
You need:

5+ years in software engineering, systems engineering, or technical program management
Experience with developer tools or open-source work — you know what makes engineers love a tool or quietly hate it
Working knowledge of distributed systems, frameworks, and service-oriented architecture (you don't need to be the expert in the room, just fluent enough to follow it)
Sharp analytical instincts — you can take something messy and complicated and turn it into a clear recommendation
A real track record of running programs from idea to launch, including the parts where you had to challenge how things were already being done
Strong writing and speaking skills, and the ability to build trust whether you're talking to an IC or a VP
A history of improving process across teams, with opinions of your own about what works
The ability to work independently and move fast across teams, functions, and time zones without someone holding your hand

Nice to have, not required:

Comfort working in a space where the AI tooling keeps changing underneath you
Deep infrastructure background — databases, cloud compute, networking, or core services
A TPM style flexible enough to adapt to what each team actually needs
Specific experience as an infrastructure-focused TPM
Experience with distributed, multi-timezone teams
Genuine empathy for users — and the instinct to spot solutions they wouldn't have thought to ask for
An honest enjoyment of working across the whole org, not just your corner of it