← Back to Directory

Ramp

Small

Most of these Ramp write-ups come from Software Engineers (24), then Frontend Engineers (9). The most reported rounds are the technical phone screen (25), the system design round (3), the online assessment (2) and the behavioral / leadership round (1).

33 interview notes · updated Jun 2026

Ramp·Frontend Engineer·Technical Phone Screen

Jun 2026
Ramp frontend interview with a genuinely tricky DOM traversal problem. The core task was building a custom query selector from scratch, which I did not see coming.
  • A URL is split into individual characters and embedded inside specially nested DOM elements. Write a custom query selector that walks the DOM tree, finds the relevant elements, and reconstructs the URL by concatenating the characters in order. The selector syntax must support a wildcard '*' that matches zero or more characters in element names.

“I spent the first few minutes just trying to understand the setup.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Jun 2026
Ramp coding round focused on a banking system design problem that kept growing in scope. The core ask was straightforward but the follow-up on ranking and efficiency is where things got interesting.
  • You're building a banking system with CREATE_ACCOUNT, DEPOSIT, and TRANSFER operations. Now add a TOP_ACTIVITY query that returns the top N accounts ranked by total outgoing transaction amount, with ties broken alphabetically. How do you design this efficiently, and what data structure backs it?

“The basic operations were fine, I got through those pretty quickly.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Jun 2026
Technical phone screen at Ramp for a software engineer role, centered almost entirely on building a web crawler. The problem looked straightforward at first but they kept pushing on the retry logic and error handling until things got uncomfortable.
  • Implement a basic web crawler that fetches a list of URLs via HTTP GET and returns parsed results or per-URL errors to the caller.
  • How would you design a retry policy for failed HTTP requests, and how do you decide between immediate retries and exponential backoff?
  • How do you distinguish between errors that should trigger a retry versus ones that should fail immediately?
  • How would you test the retry logic in your crawler?

“The core implementation part was fine.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Jun 2026
Ramp SWE interview that went sideways in the debugging phase. The coding part itself was manageable but I lost a chunk of time missing an API key hiding in the output, and a bug at the end meant the interviewer just cut it short and used the remaining time for Q&A.
  • Given a working solution that hits a URL, extend it to handle different HTTP status codes like 503 and 401 gracefully.
  • While running your solution against a new endpoint, some responses include a key in the body. Use that key to construct the appropriate headers and make a follow-up request.

“This part was fine, not much to say.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Jun 2026
Ramp SWE interview that went deep into system design for a task scheduler. The bulk of it was extending an existing API with user quotas and time-windowed assignments, which sounds manageable until you're actually in it.
  • You're given a task scheduler with basic CRUD operations (add, update, get, search, list). How would you extend it to support user registration with a quota on simultaneously active task assignments?
  • Design an assign_task operation that creates a time-bounded assignment for a user. It should return false if the user or task doesn't exist, or if the user is already at their quota of active assignments at the given timestamp.
  • How would you implement get_user_tasks to return all task IDs currently active for a user at a given timestamp?
  • What edge cases would you handle for time-based assignments, specifically around zero-length or past-dated assignments and assigning the same task to the same user multiple times?

“The quota part tripped me up more than I expected.”

View Post

Ramp·Frontend Engineer·Technical Phone Screen

Jun 2026
Ramp frontend interview had me building a stripped-down Wordle clone in React, including fetching the target word from an API and wiring up per-letter feedback logic. The unit tests were provided upfront and your code had to pass them, which honestly shaped how I structured the whole thing.
  • Build a simplified Wordle game in React where the target word is fetched from an HTTP endpoint, user guesses are accepted, per-letter feedback is shown (correct position, present but wrong position, absent), and the game ends on a win or after six attempts. The implementation must pass provided unit tests that mock the endpoint.

“This was more involved than I expected for a phone screen.”

View Post

Ramp·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Ramp for a software engineer role. The whole thing was one big question about building a hotel booking aggregator, and it went pretty deep into caching tradeoffs and upstream API behavior. Felt like a solid interview but also the kind where you realize halfway through that you've been thinking about it slightly wrong.
  • Design a hotel reservation aggregator like Expedia that searches and books rooms across multiple hotel chains. Cover real-time availability, atomic booking confirmation, and cancellation/refund flows.
  • Should the aggregator call upstream hotel APIs on every availability read, cache the results, or pre-allocate a block of inventory in advance? Walk through the tradeoffs.
  • How do you handle the tail latency problem when your cached or pre-allocated room pool is exhausted and you have to fall back to a live upstream API call?
  • How would you partition and refresh the availability cache, and what's your failure handling strategy when an upstream hotel API is slow or completely down?

“I started with the search flow and availability reads, which felt natural, but I underestimated how much time the interviewer wanted to spend on the booking confirmation part.”

View Post

Ramp·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Two-part round at Ramp for a software engineering role. The first half was a deep dive on a past project and the second half threw a real-time analytics system design at me that I wasn't fully expecting. Pretty technical throughout, no fluff.
  • Walk us through a past project end-to-end: the problem, your design choices, what you personally owned, and what the outcomes were.
  • Design a real-time service that tracks page visit counts over a rolling 1-minute window for a website. Cover how you'd ingest events, handle windowing semantics, count at scale, deal with approximation tradeoffs, store recent window data, and expose the results to dashboards and alerting.

“I picked a project I knew cold, which helped.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Jun 2026
Did a coding round for a Software Engineer role at Ramp. The problem was a URL-based maze navigation thing, kind of niche but manageable once I figured out the structure.
  • Given a maze exposed as a URL API where you can query neighboring cells, find the exit using code.

“Started by just poking at the URL manually to understand what it returned before writing a single line of code.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Jun 2026
Ramp SWE interview with a practical HTTP crawling problem. Less about clever algorithms and more about writing real working code that handles the messy parts, retries, deduplication, parsing, concurrency. Felt like a production task someone pulled straight from their codebase.
  • Given a starting URL, implement a crawler that follows URLs returned in HTTP responses until it finds one containing the string 'congrats'. Return that URL.

“My first instinct was to reach for recursion and I sketched that out, but the interviewer kept nudging me toward the practical stuff.”

View Post

Ramp interview FAQ

What rounds are in the Ramp interview?

Candidates most often report a technical phone screen (25 write-ups), a system design round (3), an online assessment (2) and a behavioral / leadership round (1).

What does the Ramp technical phone screen cover?

Across 25 technical phone screen write-ups, the most tagged question topics are System Design (29 questions), Technical Trade-offs (26) and API & Integrations (22).

Ramp interview guides by role

24 notes

Ramp Software Engineer interview questions