Ramp Software Engineer Intern Online Assessment Experience
Interview Experience
I think I got the online assessment (OA) for free by mass applying. Many people said they got 45 minutes, but mine was 90 minutes for the code signal 4 parts. It was progressive; you had to solve one
Full Details
I think I got the online assessment (OA) for free by mass applying. Many people said they got 45 minutes, but mine was 90 minutes for the code signal 4 parts. It was progressive; you had to solve one problem before moving on to the next (to pass all). The problems were DB Design questions. I personally found the whole thing very difficult. Maybe I'm just bad at it. Please give me some points! I'm 17 points short of 200. The following content requires more than 200 points. You can already view it. The problems are very long and daunting. I only filmed the fourth problem. The problems are basically the same as those in https://www.1point3acres.com/bbs/thread-1141157-1-1.html https://www.1point3acres.com/bbs/thread-1141157-1-1.html
About This Question
This is a candidate experience report from a ramp interview for a swe role (intern level) during the oa round reported in 2025.
Difficulty rating: Hard
More Ramp Interview Questions
About Ramp Interview Reports
This question was reported by a candidate who interviewed at Ramp. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Ramp are the higher-signal extractions to take from this report.
For broader preparation context, the Ramp interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Ramp reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Ramp Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Ramp reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.