← Back to Directory

Ramp interview notes, page 1 of 7

Small

Most of these Ramp write-ups come from Software Engineers (52), then Frontend Engineers (10). The most reported rounds are the technical phone screen (44), the system design round (8), the online assessment (5) and the behavioral / leadership round (2).

62 interview notes · updated Oct 2026

Ramp·Software Engineer·Online Assessment (OA)

Apr 2026
Ramp OA for a software engineer role. The recipe problem was the same one floating around on 1point3acres, so if you've done your homework you'll recognize it immediately.
  • Design a system to manage recipes and support version rollback functionality.

“The key click for me was separating the Version class from the Recipe class early.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Apr 2026
Ramp coding round for a software engineer role, one problem the whole time. They gave me an existing recipe manager and asked me to extend it with versioning and rollback. Seemed manageable at first but the rollback edge cases took a while to get right.
  • You're given a recipe manager service with basic CRUD. Extend it so every create or edit appends a version record to the recipe's history, and implement a function to return the full ordered version list for a given recipe.
  • Implement a rollback function that restores a recipe to a previous version's state, appends a new version entry attributed to the literal string 'rollback' rather than the calling user, and handles all the failure cases cleanly without mutating state on conflict.

“The versioning part itself wasn't bad.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Apr 2026
Ramp coding screen for a software engineer role, basically a from-scratch OOP design question around a banking system. Pretty straightforward concept but the edge cases pile up fast and that's clearly where they're separating candidates.
  • Build a simple banking system from scratch that supports creating accounts, depositing funds, and transferring between accounts. Each operation takes a timestamp. What data structures do you use and how do you handle edge cases like missing accounts, insufficient balance, or a transfer to the same account?

“I went straight for a dict keyed by account ID and stored balance as the value, which was fine.”

View Post

Ramp·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Two-part round at Ramp for a software engineer role. First half was a deep dive into a past project, second half was a live system design problem I didn't fully see coming. The system design portion was more specific than I expected and required some real-time streaming knowledge.
  • Walk us through a past project end-to-end: the problem, your design choices, the trade-offs you made, what you personally owned, and what the outcome was.
  • Design a real-time service that counts page visits on your website within a rolling 1-minute window. Walk through ingestion strategy, window semantics, counting approach, storage, and how you'd surface the data to dashboards or alerting systems.

“They let you pick the project, which sounds like a gift but actually made it harder.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Apr 2026
Did a technical screen for a Software Engineer role at Ramp that was basically a task scheduler design problem. Pretty contained scope but they wanted you to talk through your design choices out loud, not just code.
  • Design and implement a task scheduler service with add, update, and get operations. Each method receives a timestamp parameter. add_task should return a unique sequential ID, update_task should return a boolean indicating success or failure, and get_task should return a JSON string with the task details or null if not found.
  • Walk through your choice of underlying data structure and explain how you'd handle unique ID generation for the tasks.

“The timestamp parameter being passed everywhere but not actually used threw me off at first.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Apr 2026
Ramp SWE interview with a URL-based maze problem. Pretty niche question, not the usual LeetCode grind, but BFS got it done.
  • You're given a maze as a set of URLs where each URL represents a cell and hitting the endpoint tells you which directions are open. Find the exit using the API.

“Started by poking at the URL to figure out what responses looked like before writing any code.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Apr 2026
Ramp SWE interview with a data-processing coding question. Pretty straightforward premise but I fumbled around longer than I should have before landing on the right approach.
  • Given a list of flight records (each with fields like user ID, flight ID, departure time, arrival time, origin, and destination), write a function that returns the user ID with the highest number of flights. Ties can be broken arbitrarily.

“My first instinct was to overthink it.”

View Post

Ramp·Frontend Engineer·Online Assessment (OA)

Apr 2026
Ramp frontend engineering challenge where the task was to locate and retrieve a hidden flag value from either the DOM or a URL response. Pretty practical exercise, less algorithmic than I expected.
  • Given either a DOM fixture with a hidden flag embedded in the markup or a URL whose response contains the flag, write code to retrieve the flag value regardless of which source it comes from.

“The DOM side was fine, querySelector and dataset access are muscle memory at this point.”

View Post

Ramp·Frontend Engineer·Online Assessment (OA)

Apr 2026
Ramp frontend OA where the whole challenge was less about coding and more about figuring out why the test suite wouldn't even load. Niche problem, but kind of interesting once you realize what's actually going on.
  • A source file uses CommonJS exports but the test runner expects ESM imports, causing the entire suite to fail before any assertion runs. Diagnose the root cause and decide whether to fix the export syntax or strictly follow the comment in the file that says to only replace one specific string.

“The comment in the file was pretty explicit: replace this one string, touch nothing else.”

View Post

Ramp·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed for a Software Engineer role at Ramp and got hit with a dynamic programming scheduling problem that looked deceptively simple at first glance. The core challenge was figuring out how to optimally spend a limited number of day-off conversions to maximize streak bonuses on top of base wages.
  • Given a schedule of workdays and days off over n consecutive days, a fixed wage per day worked, a streak bonus earned when two consecutive days are both worked, and a budget of at most k conversions from day-off to workday, find the maximum total earnings possible.

“Took me an embarrassingly long time to realize the streak bonus structure is what makes this non-trivial.”

View Post