Skip to content
Ramp

Senior Engineer, Backend, Bill Pay

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
Ruby/RailsLLMsDistributed 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

Paying vendors is one of the most manual, error-prone jobs in finance. Invoices arrive by email and PDF, get keyed in by hand, wait on approvals, and then have to be paid on time, by the right method, for the right amount, and recorded correctly in the books. A single mistake can mean a late fee, a duplicate payment, or an unhappy vendor.

Ramp's Bill Pay team builds the accounts payable system that automates that work end to end: bill intake and parsing, approvals, payment execution by ACH, check, card, and international transfer, vendor credits, and sync to customers' accounting systems. Bill Pay is one of Ramp's fastest-growing products, and businesses rely on it every day to move large amounts of money.

We're looking for a senior backend engineer to own a core part of that system. You'll take responsibility for an area such as payment execution, bill intake and AI-powered extraction, approvals, or accounting sync, set its technical direction within the team, and keep it correct and reliable as volume grows. You'll work closely with product, design, and payments partners to make accounts payable faster and more trustworthy for finance teams.

What You'll Do

Own the design and evolution of a core Bill Pay system, such as payment execution, bill intake, approvals, or accounting sync, from technical design through launch, monitoring, and iteration

Build payment workflows that move money correctly across ACH, check, card, and international rails, with strong safeguards against duplicate, late, or incorrect payments

Build AI-powered AP automation, including invoice extraction, auto-coding, and agents that reduce manual review for finance teams

Design data models that keep every bill, approval, payment, and credit accurate and traceable through to the general ledger

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

Improve the reliability, performance, and observability of Bill Pay systems as customers process larger payment volumes

Drive technical direction for your area and 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 and shaping its technical direction over time

Strong system design judgment, especially around correctness, idempotency, and reliability in systems where mistakes have real financial impact

Product sense: you care about the customer problem, not just the ticket, and you balance speed with quality

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

Nice to Haves

Experience with accounts payable, payments, money movement, or other financial systems

Experience building integrations with ERPs or accounting systems, such as NetSuite or QuickBooks

Experience applying LLMs, OCR, or other automation to document processing or financial workflows

Source · RampFirst seen 11 NovOriginal ↗