Ramp Software Engineer interviews typically run 4–6 rounds: online assessment, recruiter screen, technical coding screens, system design, project deep dive, and behavioral. The process takes a few weeks and is distinguished by unconventional OA formats like puzzle-style challenges and practical system-building tasks.
$118K
Avg. Base Comp
$300K
Avg. Total Comp
4-5
Typical Rounds
2-4 weeks
Process Length
We've seen enough Ramp candidate experiences to say with confidence: the most disorienting part of this process isn't the difficulty — it's the unpredictability. Multiple candidates encountered a capture-the-flag style application step involving base64-encoded strings, hidden URLs, and DOM-digging before they ever spoke to a human. One candidate spent 20-25 minutes following a chain of web pages to find the word "treasure" and submit a CodeSandbox link — and still got a generic rejection. This isn't a fluke. It's a deliberate screening gate, and candidates who go in expecting a standard LeetCode warm-up will be caught off guard.
Beyond the unusual entry points, a clear pattern emerges in the technical substance: Ramp cares far more about practical implementation than algorithmic depth. The OA questions we've seen — a DBMS design built across progressive sub-questions, a rate limiter, a Wordle-style app built from a live DOM request, a calendar with overlapping events in 45 minutes — are all closer to real product work than anything you'd find on a standard interview prep list. React, TypeScript, DOM manipulation, and systems-style thinking come up repeatedly. The one candidate who accepted an offer specifically noted that the OA rewarded "careful thinking instead of memorizing patterns."
What's less visible but equally important is the AI interview, which multiple candidates flagged as a newer and still-evolving part of the loop. The emphasis seems to be on fluency with AI-assisted workflows rather than raw output — Ramp appears to be probing how you work with AI tools, not just whether you can code without them. Pair that with behavioral questions about disagreeing with leadership and holding controversial opinions, and it's clear Ramp is screening for a specific kind of direct, opinionated engineer. The process can feel disjointed — engineers running late, rounds that feel checked out — but the signal they're looking for is consistent throughout.
Synthetized from 9 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Ramp process.
The process felt pretty standard overall, but with one twist that stood out: the “AI enabled” coding round. I started with a technical screening that was mostly coding and focused on basic data structures and algorithms, nothing overly deep but definitely something you had to solve cleanly under pressure. The recruiter had given me a little insight into the kind of problems to expect, and the themes were along the lines of graph questions and some API design, so I went in knowing it would be more practical than pure LeetCode grinding. There was no whiteboarding, and the system design piece was much lighter than I expected, almost trivial compared with what you see at some other companies.","After that, the onsite had a couple more coding rounds, a project deep dive, and a behavioral interview. The behavioral questions were straightforward and centered on past projects and teamwork, so nothing unusual there. The most interesting part was the AI round, which seemed like they were still figuring it out; the emphasis was on coding under pressure and using AI properly rather than just writing everything from scratch. I didn’t feel like I needed to go extraordinarily deep on algorithms, but I did need to be comfortable with practical problem solving and explaining my thinking clearly. In the end I didn’t get an offer, and honestly the process felt more like a test of how you work through real problems than a hardcore algorithm screen. If I were preparing again, I’d focus on being fast and clean with basic DS&A, practicing graph-style coding problems, and getting comfortable talking through an AI-assisted coding workflow.
Prep tip from this candidate
Practice practical coding problems with a graph/API-design flavor, and be ready for an AI-assisted coding round where the signal is how you use the tool under pressure, not just whether you can solve it from memory. Also prepare a concise project deep dive and standard behavioral stories about teamwork.","
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Ramp
Assess and create an aggregation strategy for slow OLAP aggregations.
| Question | |
|---|---|
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| Customer Orders | |
| String Shift | |
| Random SQL Sample | |
| Closest SAT Scores | |
| Prime to N | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Over 100 Dollars | |
| Raining in Seattle | |
| First Touch Attribution | |
| Hurdles In Data Projects | |
| Scrambled Tickets | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Last Transaction | |
| Size of Joins | |
| Minimum Change | |
| Top 3 Users | |
| Address Schema | |
| Download Facts | |
| Permutation Palindrome | |
| Top 5 Turnover Risk |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates encounter an unusual application-stage challenge, such as a decode-style puzzle or capture-the-flag prompt that leads to a URL and a small coding task in CodeSandbox. This acts as an initial screening gate before any human contact.
A standard phone call with a recruiter covering your background, interest in Ramp, and high-level experience. Frontend stack familiarity (React, TypeScript) and communication skills are often probed here.
An automated take-home coding assessment sent shortly after the recruiter screen, typically with a 3-day deadline. Problems are practical and systems-oriented, such as designing a DBMS, building a rate limiter, or implementing a storage system with OOP design, rather than pure LeetCode-style puzzles.
A live coding round with an engineer covering medium-to-hard algorithmic problems or frontend-focused tasks in React and JavaScript, including DOM manipulation, state management, and data aggregation problems. Some candidates also encounter a multi-part practical coding task simulating real product work.
A series of back-to-back rounds including additional coding interviews (sometimes an AI-assisted coding round), a system design interview, a deep dive on a past project, and a behavioral/leadership interview covering topics like disagreements with leadership, motivation for joining Ramp, and experience with AI tooling.