Ramp interview, decoded.

Ramp's engineering loop is practical from the first step. The online assessment is a CodeSignal test of about 90 minutes in levels that unlock one after another, and candidates describe the problems as long more than hard: a bank with transactions, methods that work on a file system. The live rounds that follow ask you to pull data from an API, parse JSON or CSV and shape the result, in about an hour, and a March 2026 account says there were no LeetCode-style questions at all. Since late 2025 candidates also report an onsite round where you are given credits for Claude Code or Cursor and expected to build with the AI.

Ramp was founded in New York in March 2019 by Eric Glyman, Karim Atiyeh and Gene Lee. It sells corporate cards, bill pay and procurement software, and its job ads say more than $200B a year in spend runs through 70,000 companies on it. In June 2026 it raised $750M at a $44B valuation, with annualized revenue above $1B.

Free · 2 minutes · no account

The questions for your exact Ramp role and level.

See the questions Ramp asks ↓Run a free mock interview →

Interviewing at Ramp? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Ramp hires

The roles and the background

On 25 September 2026 Ramp had 155 open roles, 37 of them in engineering, and 119 based in New York. The rest sit in London, San Francisco, Toronto and a few remote US roles. Engineering hires across core product, credit, fraud and identity, bill pay and procurement, the developer API, applied AI and forward deployed engineering, plus interns in backend, frontend, iOS and Android. Most roles are hybrid, and the ads cover relocation to New York or San Francisco.

02

What is the Ramp interview process?

Round by round

Ramp does not publish its interview process, so the stages below come from candidate reports between late 2024 and September 2026. Glassdoor puts the average at about 19 days. The format changed in the second half of 2025, when the AI coding round appeared, so ask the recruiter which rounds you will have.

01
Online assessment
About 90 minutes on CodeSignal, in levels

One system built in parts, each part unlocking when the last one passes. Candidates name a bank with transactions and a set of file system methods. The problems are long more than hard, so pace matters. The section below goes through them.

02
Recorded video questions
Four short questions on Hireflix, two minutes each

Light behavioural questions with 30 seconds to prepare and one retake each.

Internships
03
First coding round
About 60 minutes, live

A practical problem: call an API, process what comes back, manipulate the data, or parse files in JSON, text or CSV. Candidates describe it as far from LeetCode.

04
Final round: coding
Two coding interviews

More of the same practical shape, often a class-based system you extend as requirements change. For frontend roles the problems are React: a calendar view, a simplified Wordle.

05
AI coding round
Onsite

You get credits for Claude Code, Cursor or a similar tool and are expected to build with it. Reported since November 2025 and still on InterviewDB in August 2026. Ask the recruiter what the rules are.

06
System design
Onsite, for experienced hires

Reported for experienced candidates: a tracking system on the backend, a layout component on the frontend.

07
Leadership interview
A conversation, in the final round

Ownership, pace and how you work with the team. Ramp's careers page asks of every hire whether they would join that person's company.

03

What Ramp screens for

What every round is really testing

Ramp publishes six values on its about page, and its job ads add a hiring line of their own: slope over intercept, meaning how fast you are growing counts more than where you start.

  • Grow without fear
  • We win when customers win
  • Amp it up
  • We're one team
  • Ramp is built for everyone
  • Take ownership
04

Ramp interview questions

Candidate-reported themes

The coding problems recur across reports, so they have their own section below. The behavioural questions follow Ramp's values and the slope-over-intercept line in its ads.

Behavioural & motivation

  • Tell me about something you owned from start to finish, including what went wrong.
  • What have you learned fastest in the last year, and how did you do it?
  • Describe a time you shipped something quickly and fixed it in production instead of waiting for it to be perfect.
  • Why Ramp?
  • Tell me about a time a customer's problem changed what you built.

Technical

  • Practical data handling: Calling an API, parsing JSON, text and CSV, and transforming the result
  • Object-oriented systems: A bank, a subscription or flight tracker, a spreadsheet: classes you extend as rules are added
  • Payments basics: Transactions, balances and money handled without rounding errors
  • Building with AI tools: Driving Claude Code or Cursor well enough to ship in an hour
  • React: A calendar view and a Wordle-style game for frontend roles

These are the reported themes — your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level.

Predict my Ramp questions →
05

Ramp coding interview: the problems candidates report and how to solve them

Reported problems and how to solve them

These come from candidate reports on Reddit and Glassdoor between November 2024 and September 2026, and from InterviewDB's list of Ramp questions. The problems are practical and long, so the approach below is about structure and pace more than a clever algorithm. Write code that runs, and test it as you go.

  • The bank problem (online assessment): A bank that grows level by level: accounts, deposits, transfers, then rules such as scheduled payments or cashback. Model accounts and transactions as classes from the first level, keep amounts in integer cents, and keep a history of transactions so later levels that ask for it do not force a rewrite. A September 2026 candidate's advice was to study payments and object-oriented design.
  • File system methods (online assessment): Methods to add, read, delete and list files, with sizes, then queries on top. Pick one data structure for the tree at level one, usually a dictionary keyed by path, and write every later method against it.
  • Pull data from an API, process it, reshape it: The shape of the backend live round. Fetch, handle paging and errors, parse the response into plain objects, then filter, group and aggregate. Say out loud what you would do with a malformed record before you hit one.
  • Parse files in JSON, text and CSV: Reported for backend roles in November 2024. Know your language's standard parsers cold, handle a header row and a trailing newline, and keep parsing separate from the logic that uses the data.
  • Code a simplified Wordle in React: Reported for a senior engineer in August 2026. State for the guesses and the current input, a pure function that scores a guess against the answer letter by letter, and a component that renders the grid from state. Handle repeated letters correctly; that is where most versions break.
  • A calendar view in React: Reported on InterviewDB as recently as September 2026 and named by a candidate who was asked it. Lay out a month or week grid from dates, place events in their slots, and handle events that overlap or cross a day boundary.
  • Build a feature with Claude Code or Cursor: The AI round. Read the whole problem first, give the tool a small, clear first task, and check every change it makes before you build on it. Interviewers watch how you steer and verify, so talk through each prompt and what you expect back.

InterviewDB also lists Subscription Tracking (21 reports, last in August 2026), Flights Tracking, Spreadsheet, CSV Queries, Currency CLI and Rock Paper Scissors. The problem statements are behind its paywall, so they are named here and not described. The pattern across all of them is the same: a small system with rules added in stages.

06

Pay

What the offer looks like
New grad, US$228K total ($174K base)
Software Engineer, US$300K total ($200K base)
Senior, US$510K total ($235K base)
Staff, US$786K total ($281K base)

Levels.fyi figures for Ramp software engineers across the US, read on 25 September 2026: a median package of $385K from 125 submissions, with stock vesting 25 percent a year over four years. Ramp posts New York base ranges on its ads, for example $168K to $275K for core product, $189K to $330K for enterprise product and $275K to $400K for a travel tech lead. London roles post £106K to £150K, and interns are paid $12.5K a month. Calibrd benchmarks the pay on any posting you scan against its level and location.

07

How to prepare for a Ramp interview

In order
  1. Do one CodeSignal-style progressive problem end to end in 90 minutes: a bank or a file system, level by level, without rewriting at each level.
  2. Practise the backend round's shape: call a public API, parse the JSON, then group and aggregate the result, all inside an hour.
  3. Get fluent with Claude Code or Cursor before the onsite, and practise checking what the tool writes as fast as it writes it.
  4. Handle money as integer cents and be ready to explain why.
  5. Frontend roles: build a Wordle and a calendar grid in React once each, with the tricky cases (repeated letters, overlapping events) working.

This guide covers Ramp's software engineering loops, including internships. Sales, which is its largest hiring area, runs a different process. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Knowing the questions isn’t the same as answering them out loud. Run a Ramp mock: spoken answers, coached on the spot. Your first mock is free.

Run a Ramp mock →
08

FAQ & sources

The short answers
What is Ramp's interview process?

Ramp does not publish its interview process, so the stages below come from candidate reports between late 2024 and September 2026. Glassdoor puts the average at about 19 days. The format changed in the second half of 2025, when the AI coding round appeared, so ask the recruiter which rounds you will have. Online assessment: One system built in parts, each part unlocking when the last one passes. Candidates name a bank with transactions and a set of file system methods. The problems are long more than hard, so pace matters. The section below goes through them. Recorded video questions: Light behavioural questions with 30 seconds to prepare and one retake each. First coding round: A practical problem: call an API, process what comes back, manipulate the data, or parse files in JSON, text or CSV. Candidates describe it as far from LeetCode. Final round: coding: More of the same practical shape, often a class-based system you extend as requirements change. For frontend roles the problems are React: a calendar view, a simplified Wordle. AI coding round: You get credits for Claude Code, Cursor or a similar tool and are expected to build with it. Reported since November 2025 and still on InterviewDB in August 2026. Ask the recruiter what the rules are. System design: Reported for experienced candidates: a tracking system on the backend, a layout component on the frontend. Leadership interview: Ownership, pace and how you work with the team. Ramp's careers page asks of every hire whether they would join that person's company.

What does Ramp look for in candidates?

Ramp publishes six values on its about page, and its job ads add a hiring line of their own: slope over intercept, meaning how fast you are growing counts more than where you start. Grow without fear We win when customers win Amp it up We're one team Ramp is built for everyone Take ownership

What questions does Ramp ask in interviews?

The coding problems recur across reports, so they have their own section below. The behavioural questions follow Ramp's values and the slope-over-intercept line in its ads. Tell me about something you owned from start to finish, including what went wrong. What have you learned fastest in the last year, and how did you do it? Describe a time you shipped something quickly and fixed it in production instead of waiting for it to be perfect. Why Ramp? Tell me about a time a customer's problem changed what you built. Practical data handling Object-oriented systems Payments basics Building with AI tools React

What coding questions does Ramp ask?

These come from candidate reports on Reddit and Glassdoor between November 2024 and September 2026, and from InterviewDB's list of Ramp questions. The problems are practical and long, so the approach below is about structure and pace more than a clever algorithm. Write code that runs, and test it as you go. The bank problem (online assessment): A bank that grows level by level: accounts, deposits, transfers, then rules such as scheduled payments or cashback. Model accounts and transactions as classes from the first level, keep amounts in integer cents, and keep a history of transactions so later levels that ask for it do not force a rewrite. A September 2026 candidate's advice was to study payments and object-oriented design. File system methods (online assessment): Methods to add, read, delete and list files, with sizes, then queries on top. Pick one data structure for the tree at level one, usually a dictionary keyed by path, and write every later method against it. Pull data from an API, process it, reshape it: The shape of the backend live round. Fetch, handle paging and errors, parse the response into plain objects, then filter, group and aggregate. Say out loud what you would do with a malformed record before you hit one. Parse files in JSON, text and CSV: Reported for backend roles in November 2024. Know your language's standard parsers cold, handle a header row and a trailing newline, and keep parsing separate from the logic that uses the data. Code a simplified Wordle in React: Reported for a senior engineer in August 2026. State for the guesses and the current input, a pure function that scores a guess against the answer letter by letter, and a component that renders the grid from state. Handle repeated letters correctly; that is where most versions break. A calendar view in React: Reported on InterviewDB as recently as September 2026 and named by a candidate who was asked it. Lay out a month or week grid from dates, place events in their slots, and handle events that overlap or cross a day boundary. Build a feature with Claude Code or Cursor: The AI round. Read the whole problem first, give the tool a small, clear first task, and check every change it makes before you build on it. Interviewers watch how you steer and verify, so talk through each prompt and what you expect back.

How do I prepare for a Ramp interview?

Do one CodeSignal-style progressive problem end to end in 90 minutes: a bank or a file system, level by level, without rewriting at each level. Practise the backend round's shape: call a public API, parse the JSON, then group and aggregate the result, all inside an hour. Get fluent with Claude Code or Cursor before the onsite, and practise checking what the tool writes as fast as it writes it. Handle money as integer cents and be ready to explain why. Frontend roles: build a Wordle and a calendar grid in React once each, with the tricky cases (repeated letters, overlapping events) working.

Prep for a real Ramp role

Practise your Ramp interview, out loud.

Paste a real Ramp posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Ramp prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Ramp Interview: CodeSignal, AI Coding Round, Pay — Calibrd