Ramp · OA → Phone screen
Not reportedRamp SWE New Grad OA and Phone Screen: 7 Experiences
Ramp general SWE new grad OA reports, Aug 2024 to Jan 2026: 7 candidates, mostly four-level build tasks like banking, cloud storage and rate limiting.
At a glance
- Process: an online assessment where one system grows over four levels (01, 03, 06); one candidate reached a technical phone screen (02). Report 06 said the OA lasted 90 minutes.
- Asked recently: banking with payments and account merges (01, Jan 2026), a "where is this user now" flight lookup (02), cloud storage in 2 of 7 reports (03, 06), a per-IP rate limiter (04), snake-to-camel case (05) and worker records with salaries (07).
- Difficulty: report 06 spent about ten minutes on each of the first two levels and thirty on each later one, mostly debugging; 01 passed every test case but did not know the cutoff.
- Practise first: Accept or Decline Queries, User Airport From Flight History and Convert Snake Case Variables to Camel Case.
Coverage: seven general SWE new grad candidates, report dates August 2024 to January 2026; six online assessments and one technical phone screen. None names an Android or backend role; those are in Ramp Android, Mobile and related coding interviews.
What came up
Cloud storage was the only task two candidates shared, and they remembered different operations. One candidate can sit in several rows.
| Topic | Reports | Last seen |
|---|---|---|
| Four-level OA that grows one system | 3 of 7 | Jan 2026 (report date) |
| Cloud storage | 2 of 7 | Aug 2025 (report date) |
| Banking accounts, payments and merges | 1 of 7 | Jan 2026 (report date) |
| User location from flight records | 1 of 7 | Sep 2025 (report date) |
| Per-IP rate limiting | 1 of 7 | Apr 2025 (report date) |
| String conversion | 1 of 7 | Nov 2024 (report date) |
| Worker attendance, ranking and pay | 1 of 7 | Aug 2024 (report date) |
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Cloud storage system with four levels | 2 | Aug 2025 (report date) |
| Progressive Banking System | 1 | Jan 2026 (report date) |
| User Airport From Flight History | 1 | Sep 2025 (report date) |
| Accept or Decline Queries | 1 | Apr 2025 (report date) |
| Convert Snake Case Variables to Camel Case | 1 | Nov 2024 (report date) |
| Worker management: registration, ranking, promotions and salary | 1 | Aug 2024 (report date) |
The banking, cloud-storage and worker tasks have no live FastPrep problem at the moment, so they are not linked.
7 detailed candidate timelines, loops, and screens
All dates are report dates.
01: Banking features across four levels
Report date: January 17, 2026 · Stage: Online assessment · Reported result: Pass
The candidate listed four cumulative levels of a progressive banking system:
- Build a banking system.
- Rank accounts by outgoing transactions.
- Support payments with cashback and let callers check payment status.
- Merge two accounts while retaining their balances and transaction histories.
The level-three wording also referred to scheduling payments. The post did not give signatures, a cashback rate, timing rules or examples. In a later reply, the author said they had passed all test cases but did not know the passing-score cutoff.
02: Where is the user now?
Report date: September 29, 2025 · Stage: Technical phone screen · Reported result: Fail
The flight-history task supplied flights with a departure airport, departure time, arrival airport, arrival time and user ID. Given a user ID and a time, the task was to return the airport where that person was located.
The author did not explain what to return during a flight or at an exact departure or arrival time. A commenter asked about these cases, flight ordering, overlaps and users without records, but the author had not answered. Those questions do not establish the interview's required behavior.
03: Cloud storage with user limits and compression
Report date: August 9, 2025 · Stage: Online assessment · Reported result: Fail
The candidate reproduced an in-memory file-storage task with four levels. It stored file names and sizes without using the real filesystem. The matching practice exercise is Cloud Storage Compression and Decompression.
- Add files, copy them and look up file sizes. Duplicate destination names failed; missing copy sources failed too.
- Search by both filename prefix and suffix.
- Add users with different capacity limits.
- Compress and decompress files.
The post gave C++ signatures and return rules for the first level. Adding or copying returned a Boolean; looking up a missing file returned an empty optional value. It included a failed copy from a missing path and a failed attempt to add an existing name.
Later levels were summarized by their features rather than fully reproduced. The candidate's text listed 30 seconds and 4 GB of memory for the supplied environment.
04: Accept or reject requests for each IP
Report date: April 19, 2025 · Stage: Online assessment · Reported result: Waitlist
The task was a per-IP sliding-window rate limiter, matching Accept or Decline Queries. It took ordered millisecond timestamps, corresponding IP addresses, a request limit and a window length, then returned a sequence of 1 and 0 decisions.
Rejected requests did not count toward later totals. Each IP had its own history. In the example, two requests from one IP at times 1000 and 1005 were both accepted with a limit of two over ten milliseconds; a request from another IP at 1010 was independent.
The post described a dictionary of timestamp queues, removing expired accepted requests before checking the next one. It also claimed input sizes up to 100 million requests, a window up to one billion milliseconds and a four-second Python limit. The exact left-edge inclusion rule was not stated.
05: Snake case to camel case
Report date: November 17, 2024 · Stage: Online assessment
This candidate reported Convert Snake Case Variables to Camel Case. Their short statement turned abc_dce into abcDce and explicitly preserved underscores at the beginning and end.
The same task also shows up in Ramp's Android and Mobile reports.
06: Four cloud-storage levels in a 90-minute assessment
Report date: October 4, 2024 · Stage: Online assessment · Reported result: Pass
The candidate described implementing a cloud storage system across four levels. The same Ramp practice family includes Cloud Storage System, Part 2: Largest Files, which covers prefix-based file ranking. They spent roughly ten minutes on each of the first two and thirty minutes on each later level, with much of the time going into debugging.
In a later author reply, they said the assessment lasted an hour and a half. When asked whether n_largest needed to include subdirectories, they said they thought it did, while noting that they did not remember the details clearly.
The post does not reproduce the full operations. Its levels should not be filled in from report 03.
07: Attendance, rankings, promotions and salary
Report date: August 22, 2024 · Stage: Online assessment
The candidate supplied a worker-record implementation:
- Worker Management, Part 1: Office Registration: add unique worker IDs with position and compensation; alternate entry and exit registrations; total completed sessions only. Unknown workers produced an invalid result.
- Worker Management, Part 2: Top Workers: rank workers of a requested position by completed time, breaking ties alphabetically by ID. Workers with no completed session had zero time.
- Worker Management, Part 3: Promotions and Salary: activate a promotion on the first entry at or after its start time. Reject another pending promotion. Calculate interval salary from completed sessions and the compensation applying to each session. Lifetime time totals included earlier positions.
Registrations arrived in increasing time order. The post ended with salary calculation and did not describe a further extension.
Patterns across the reports
- Cloud storage over four levels. Reports 03 and 06 both describe a four-level cloud-storage OA. Report 03 named file operations, prefix and suffix search, user limits and compression; report 06 talked about timing and tentatively recalled that
n_largestincluded subdirectories. - Levels build on each other. Reports 01, 03 and 07 all describe later levels adding features (cashback and merges; user capacity and compression; promotions and salary) on top of earlier code.
Common questions
What is the Ramp new grad OA like?
One system built up over four levels, such as banking (01) or cloud storage (03, 06); report 06 said it lasted 90 minutes.
How long does each level of the Ramp OA take?
Report 06 spent about ten minutes on each of the first two levels and about thirty on each of the last two, much of it debugging.
Do you need to pass every test case on the Ramp OA?
Report 01 passed them all and moved on but did not know the cutoff; report 03 failed after describing all four levels.
What does the Ramp new grad phone screen ask?
Report 02 got a flight-history lookup: given a user ID and a time, return the airport where the user is.
Keep practicing
- Accept or Decline Queries: the per-IP rate limiter from report 04.
- Find a User's Airport from Flight History: the phone-screen task from report 02.
- Ramp bank requests with delayed cashback: another Ramp banking task with cashback, from other Ramp reports.
- Ramp coding question bank (sign-in needed).
- Ramp interview guide and Ramp hiring insights: stages, practice problems and recent hiring signals.
- Ramp Android, Mobile and related coding interviews and the Experience feed.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.