Ramp's Software Engineer interviews typically begin with a short recruiter screen covering background and motivation for joining Ramp. In one 2026 report, that screen focused almost entirely on day-to-day use of AI coding tools like Copilot, Cursor, and Claude rather than general background questions.
Most candidates next receive an automated online coding assessment, often on CodeSignal, sent within a day or two of applying. Reported tasks vary: one report describes a progressive four-level bank-system build (accounts, deposits, transfers, then scheduled payments); another describes a two-hour object-oriented storage-system exercise; and a separate SWE Intern report describes a four-question progressive assessment centered on a DBMS design. Several candidates, including one who reported a perfect score on a stack-based problem, were rejected by automated email within hours, with no recruiter conversation.
Candidates who advance describe varied next steps. One report describes a 45-minute live coding round building a calendar component with overlapping events and an editable, click-to-edit form. Another describes a 60-minute system-design-lite discussion of a hotel-reservation schema, with the interviewer probing concurrency handling. A separate report, for a forward-deployed engineering variant of the role, describes a graph-traversal problem requiring real HTTP requests and error handling.
Full onsite loops, where reported, typically add two to four further rounds: additional coding sessions (in one case, extending an existing codebase), a project or architecture deep dive, and a behavioral round covering teamwork and, in one report, disagreement with leadership. A smaller number of reports describe a distinct AI-enabled coding round evaluating how a candidate uses AI assistance under pressure rather than testing memorized solutions.
Outcomes in this set skew heavily toward rejection or no offer, often delivered with little explanation. The two candidates who reported positive outcomes — a Frontend Software Engineer and a Software Engineering Intern — both described collaborative, think-out-loud pair-programming rounds where interviewers helped when they got stuck, rather than a race against the clock.
Synthesized from 39 candidate reports by our editorial team.
