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, performance, reliability) without involving PE.
• Participate in on-call rotation — and more importantly, use every incident as a signal to eliminate the root cause, not just resolve the symptom.
• Lead across the company — PE doesn't just review designs or show up when called. We proactively initiate cross-team architectural reviews, and we take full ownership of company-wide reliability and scalability initiatives: identifying the problem, proposing the solution, aligning the stakeholders, and staying in until it's done.

We don't hire for a checklist. We hire for the instincts that make someone exceptional on this team.

The mindset we're looking for:

• You can't walk past something broken without wanting to fix it — and you don't stop at the workaround. You find the root cause and eliminate the class of problem.
• You think in systems, not tasks. You understand that "fixing the bug" is step one; making it so the bug can't happen again is the job.
• You move with urgency but without chaos. You know when to go fast and when to slow down and do it right.
• You treat product teams as your users. You build for them, communicate with them proactively, and measure success by how much faster they can ship. But you're also an owner — when something is broken or blocking, you don't wait to be asked. We win when our customers win.
• You leave things better than you found them. Every system you touch, every process you encounter — you move it forward. Not always dramatically, but always directionally. You picked it up in a certain state; you leave it in a better one.
• You are equally comfortable reading a database query plan, reviewing a system design doc, writing a Terraform module, and jumping into an incident at 2am.

Experience profile:

• 2+ years of software engineering experience shipping high-quality architectures for critical systems
• Strong software engineering fundamentals — you write clean, well-tested, production-ready code
• Hands-on experience with distributed systems at production scale
• Experience with at least one major cloud provider (AWS preferred)
• Familiarity with observability practices (SLOs, error budgets, alerting, dashboards)
• Track record of leading technical projects end-to-end, including cross-team coordination
• Comfortable using AI tooling and coding agents as part of your everyday engineering workflow — we expect our engineers to leverage these tools to move faster and think bigger

Bonus (not required):

• Experience with cellular or multi-tenant architecture patterns
• Prior work on workflow orchestration systems (Temporal)
• Contributions to developer experience or internal platform tooling
• Experience in fintech, payments, or regulated industries (FedRAMP, SOC 2)