Software Engineer, Production Engineering

Production Engineer

Production Engineering is Ramp's infrastructure ownership layer. We exist to make Ramp faster, more reliable, and more scalable — and we do that by being embedded in the problems, not adjacent to them.

A few things that define how we operate:

• One team, one company, one objective. There is no "infra team" and "product team" — there is Ramp. We share the company's goals as our own. When a product team struggles with reliability or scalability, that is our struggle.
• If reliability or scalability is at risk, we own it. We don't wait to be invited, and we don't ask whose code it is. If a system is slow, if it breaks, if it won't scale — that's ours to lead, regardless of where it lives in the stack.
• We go first, and we go fast. When the path isn't obvious, we don't wait for someone else to find it. We move with urgency, propose the solution, align the stakeholders, and stay in until it's done — not until our ticket is closed.
• We lead the way. We find the next problem before it finds us. And when we solve it, we don't just fix it for ourselves — the patterns and standards we establish become the foundation the rest of Ramp builds on. That's not a side effect of the job; it's the job.
• We stay calibrated. Speed means nothing if we're moving in the wrong direction. We regularly stop and ask honestly whether what we're working on is still the highest-leverage thing we could be doing — the discipline that makes sure our effort compounds toward what actually matters.

You cannot build the future of finance on shaky infrastructure.

Production Engineering is organized into teams — but we think about teams differently. Teams are mutable. We build them around what needs to be done, not around what we need to do given the teams we already have. The structure below reflects our current priorities; it will evolve as Ramp does.

Right now, we operate across four areas:

• Compute — the foundation everything runs on: container orchestration, networking, load balancing, edge infrastructure, and the deployment systems that get code from engineers' laptops to production reliably and at scale
• Storage — databases, caching, object storage, and the data infrastructure that underpins everything
• Workflows & Messaging — the systems that power Ramp's financial workflows and event-driven architecture
• Internal Infrastructure — the platform that makes every builder at Ramp faster and more autonomous: observability, cost attribution, and CI/CD systems that give teams visibility into what they build and what it costs

Production Engineers at Ramp are full software engineers who happen to specialize in infrastructure. You write production code, you own systems end-to-end, and you drive technical outcomes across the organization — not just within your team.

Day to day, you will:

• Build and operate critical infrastructure across Ramp's compute, storage, messaging, and observability stack — owning the systems that handle real financial transactions at scale.
• Drive architectural change — not just flag problems. When you surface a reliability or scalability issue, you own the path forward: you propose the solution, find the owners across engineering, and stay in until it's resolved.
• Partner with product teams at the design phase — reviewing architectures, embedding golden paths, and making it easy to build correctly the first time.
• Build Ramp's next level of scale — you'll be a hands-on contributor to the most consequential infrastructure shift happening right now: our move to a cellular architecture, enabling Ramp to scale, reach international markets, operate in highly regulated and constrained environments (e.g. FedRAMP), and deliver on enterprise-grade SLAs.
• Enable AI-native engineering — as Ramp builds increasingly AI-powered products, PE is the team that makes sure the platform can support them. You'll proactively partner with product teams on AI infrastructure patterns, define the golden paths that turn one-off solutions into reusable foundations, and stay ahead of emerging challenges before they become blockers.
• Build developer tooling and self-service infrastructure — so that other teams can answer their own questions (cost,…