The ad says“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”
The ad says“Familiarity with observability practices (SLOs, error budgets, alerting, dashboards)”
The ad says“Experience with cellular or multi-tenant architecture patterns”
The ad says“Experience with at least one major cloud provider (AWS preferred)”
The ad says“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”
The ad says“Familiarity with observability practices (SLOs, error budgets, alerting, dashboards)”
The ad says“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”
The ad says“Contributions to developer experience or internal platform tooling”
The ad says“Hands-on experience with distributed systems at production scale”
The ad says“Familiarity with observability practices (SLOs, error budgets, alerting, dashboards)”
The ad says“Experience in fintech, payments, or regulated industries (FedRAMP, SOC 2)”
The ad says“Experience in fintech, payments, or regulated industries (FedRAMP, SOC 2)”
The ad says“Contributions to developer experience or internal platform tooling”
The ad says“Experience with cellular or multi-tenant architecture patterns”
The ad says“Familiarity with observability practices (SLOs, error budgets, alerting, dashboards)”
The ad says“Experience in fintech, payments, or regulated industries (FedRAMP, SOC 2)”
The ad says“Familiarity with observability practices (SLOs, error budgets, alerting, dashboards)”
The ad says“Experience in fintech, payments, or regulated industries (FedRAMP, SOC 2)”
The ad says“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”
The ad says“Prior work on workflow orchestration systems (Temporal)”
The ad says“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”
The ad says“Prior work on workflow orchestration systems (Temporal)”
Values
The ad says“Experience with at least one major cloud provider (AWS preferred)”
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
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
Benefits
Comprehensive medical, dental, and vision insurance
One Medical Membership
401(k) including an employer match
Monthly wellness stipend
Parental leave
Unlimited PTO
Pet Insurance
WFH stipend
Relocation support to move to NYC
Preferred experience
We don’t hire for a checklist. We hire for the instincts that make someone exceptional on this team
You move with urgency but without chaos. You know when to go fast and when to slow down and do it right
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
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 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
Familiarity with observability practices (SLOs, error budgets, alerting, dashboards)
2+ years of software engineering experience shipping high-quality architectures for critical systems
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
Experience with at least one major cloud provider (AWS preferred)
Hands-on experience with distributed systems at production scale
Track record of leading technical projects end-to-end, including cross-team coordination
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)
