Skip to content
Ramp

Senior Engineer, Backend, Procurement

New York, NY (HQ)Hybrid · United States
Senior · FullTime · Engineering
POSTED 10 NOVVERIFIED 1H AGO
Apply Ask
Role
0 days opentrue age
Closes in ~67d at the median (67d)
Posted 10 Nov · n=19
Payats field
$204k–280kposted
▲ +21% vs market median $200k
$185k$280k
Market p25–p75
$185k–$214k
Ramp p25–p75
$230k–$247kn=10
New York · n=107 · 365d to 11 Nov
CompanyRamp →
169open roles
Opened · 30d
+15
Closed · 30d
−19
7d of snapshots · 30d window
Market
2,796open · Senior Backend
Opened · 7d
+1415% of open
All backend
8,295open
All tracked boards · live 11 Nov · n=2,796
Distributed systems

About Ramp

Ramp is building the smart infrastructure for finance teams, embedded in the transaction flow of every dollar a business spends. We automate how over $275B in annualized spend flows in and out of 85,000+ companies: authorizing payments, flagging risk, categorizing spend, and closing books.

The problems are high-stakes, data-dense, and unforgiving.

We hire people with high agency and high urgency. We look for slope over intercept. We care less about where you trained and more about what you’ve built. At Ramp, everyone is a builder who owns problems end to end and makes consequential decisions that shape the outcome.

The median Ramp customer saves 7.5% and grows revenue 16% in their first year – far in excess of businesses operating without Ramp. We believe every ambitious company deserves the same.

If you want to build systems that directly shape how companies move and manage billions, Ramp is the place to do it.

About the Role

Buying software and services is still slow and fragmented at most companies. Employees don't know how to request what they need, approvals stall across finance, legal, and security, purchase orders live in a separate system from the bills that pay them, and finance teams spend month-end matching it all together by hand.

Ramp's Procurement team builds the system that connects every step of that process, from the first purchase request through sourcing, approvals, purchase orders, receiving, and matching bills and contracts back to what was ordered. Procurement sits upstream of payments and works closely with Bill Pay, Accounting, and ERP integrations, so the systems we build shape how money leaves a business long before a payment goes out.

We're looking for a senior backend engineer to own a core part of that system. You'll take responsibility for a product area such as the purchase order lifecycle, PO and bill matching, PO coding and accruals, or supplier and ERP integrations, set its technical direction within the team, and keep it healthy as customers and complexity grow. You'll work closely with product, design, and data partners to turn enterprise purchasing workflows into software that is flexible, auditable, and simple to use.

What You'll Do

Own the design and evolution of a core Procurement system, such as purchase orders, receiving, or PO, bill, and contract matching, from technical design through launch, monitoring, and iteration

Build flexible request, intake, and approval workflows that handle the policies, approval chains, and audit requirements of complex organizations

Design data models that keep purchase orders, receipts, bills, and accounting data accurate and traceable from request to payment

Build and improve integrations with ERPs and supplier systems that stay consistent through retries, partial failures, and edits on either side

Help build AI-assisted features, such as automated PO coding and intelligent matching, that reduce manual work for finance and procurement teams

Drive technical direction for your area, connecting long-term system health to the team's roadmap

Work cross-functionally with product, design, and data, and with partner teams across Bill Pay, Accounting, to ship features across the full procurement lifecycle

Raise the engineering bar through design reviews, code reviews, and mentorship

What You'll Need

Experience designing, building, and operating production backend systems, including APIs, data models, and asynchronous workflows

A track record of owning a system or product area end to end: spotting problems before they are assigned, proposing the fix & working with relevant stakeholders, and shaping the area's technical direction over time

Strong system design judgment, especially around data correctness, auditability, and keeping complex workflows understandable

Product sense: you care about the customer problem, can work through ambiguous enterprise requirements, and push back when the spec is wrong

Clear communication and a collaborative approach to technical decisions across product, design, and engineering

Source · RampFirst seen 11 NovOriginal ↗