Ramp logo

Ramp Interview Questions

Reconstructed from 37 verified candidate reports across 14 questions. Nov 2025 – Oct 2026.

This page is a live view of every Ramp interview question AceOffer has indexed — pulled from candidate reports, not invented from job descriptions or one founder’s memory. Every question shows how many times it’s been reported and when it was last seen. The catalog gets a refresh pass every month.

AceOffer is not affiliated with, endorsed by, or sponsored by Ramp. Questions are reconstructed from interview experiences candidates shared, not from Ramp materials.

37
candidate reports
14
distinct questions
6
round types
Monthly
refresh cadence

Key facts

  • •14 distinct Ramp interview questions indexed
  • •37 candidate reports across the catalog
  • •Most reported: URL Maze: Find the Exit over a Flaky HTTP API — 8× (last seen October 2026)
  • •Reports span Nov 2025 – Oct 2026
  • •Refreshed monthly · last updated October 2026

Browse Ramp interviews by topic

The Ramp loop, from candidate reports

Most reported Ramp rounds are practical coding tasks rather than algorithm puzzles. Some candidates start with an online assessment: a four-level progressive problem for general roles, or a React task for frontend roles. The most reported technical screen is a 60-minute CoderPad round, the URL maze, and reports say its traps are in the HTTP handling rather than the graph search. Onsite coding rounds are data-processing problems, such as finding a user's location from flight records and detecting recurring transactions. The onsite also has an AI live coding round: you get a repository, use the AI tools of your choice, and build a finance feature from a request written as if by a product manager, with the interviewer playing that role. A project presentation round is used to judge seniority and is reported with a short system design question at the end. One report describes a recorded video screen of behavioral prompts.

What does Ramp ask in each interview round?

Ramp interviews span 6 distinct round types, broken down below. Counts reflect distinct questions per round, not number of times asked. Frequencies on individual question cards show how many candidates reported getting that specific question.

Online assessments: four-level progressive problems (a banking system, a task manager, a recipe manager) for general roles, React tasks (Wordle, a hidden URL) for frontend roles, and, in one report filed under Ramp, a rate limiter.
6 questions

Most-reported: Frontend OA: Wordle in React (5 reports)
Data-processing coding: a user's location from flight records, recurring transaction detection, and, in one report filed under Ramp, a spreadsheet with formulas.
3 questions

A project presentation used to judge seniority, reported with a short design question at the end, and in one phone screen a low-latency hotel reservation design.
2 questions

A 60-minute CoderPad screen, most often the URL maze, with follow-ups that add HTTP errors and access keys.
1 question

The AI live coding round: build a finance matching feature in a given repository with the AI tools of your choice.
1 question

A recorded video screen of behavioral prompts (one report), including why Ramp and how you use AI day to day, and "tell me about a time" questions onsite.
1 question

Which Ramp interview questions come up most?

These are the Ramp questions reported most across the loops we’ve indexed, sorted by candidate-report frequency.

The full index is below, or browse the Ramp catalog →

Every Ramp interview question we’ve indexed

All 14, grouped by round and sorted by how often candidates reported them. Each links to the question, its reported follow-up count, and when it was last seen.

OA (6)

Coding (3)

System Design (2)

Phone Screen (1)

Tech Deep Dive (1)

Behavioral (1)

What passing candidates do
  • •Retrying failed requests in the URL maze. Reports say some server errors succeed on retry, and skipping them loses the exit.
  • •Exploring the data yourself. URL maze interviewers give little clarification on purpose, and several candidates recommend printing the raw response before parsing it.
  • •Getting the main path working before error handling. One report calls the screen tight on time.
  • •In the AI coding round, agreeing a minimum spec with the interviewer before prompting, then planning what to delegate to the assistant.
Where candidates lose points
  • •Using the assistant's output without showing you understand it. One candidate was rejected in the AI coding round with that feedback.
  • •Running long in the project presentation. One candidate ran out of time and was told the talk was hard to follow.
  • •Debugging your own code when the frontend OA's tests fail out of the box. One report traces the failure to the project's module setup; another says only that the tests would not pass.

Get the full Ramp catalog

Every question. Every candidate-reported follow-up. The mistakes that sink people, and what passers do instead. Monthly refresh.

More company interview guides
Prefer to study first? Free reading guides & references — including the AI Training Papers reading guide.

Know someone interviewing at Ramp?

Send them this guide: 14 questions from 37 candidate reports, with the rounds, the follow-ups and what passers do.

Is this helpful?