Real, anonymous reports from people who interviewed for Software Engineer at Ramp, newest first and distilled into what to expect across the loop.
I experienced a very fast, automated coding-pad style workflow that ended quickly with rejection.
I went through a CodeSignal OA that mixed plain coding with a React assessment, and I didn’t make it past that stage.
Candidates typically start with a timed online assessment, often using CodeSignal, which includes algorithmic and sometimes React-focused tasks. Success in this round is crucial, as passing all test cases is often required to advance.
Following the OA, candidates can expect one or more technical interviews that may include live coding, problem-solving discussions, and system design questions, often with a focus on data structures and algorithms.
Behavioral interviews are a standard part of the process, often assessing past projects, teamwork, and alignment with company values. These may be conducted via video or live formats.
Candidates frequently report receiving automated or generic rejection notifications after assessments or interviews, with little to no specific feedback provided, which can be frustrating.
The overall interview experience is described as high-pressure, with a strong emphasis on performance and minimal tolerance for mistakes across all rounds, making consistent excellence essential.
Candidates suggest that thorough preparation for both coding and behavioral aspects is critical, as the process can be unforgiving, and unconventional prompts may arise during interviews.