Real, anonymous reports from people who interviewed for Software Engineer at LiveRamp, newest first and distilled into what to expect across the loop.
After a hiring manager call, I went straight into two technical interviews back to back. The first one felt like baseline DSA practice, where I worked through basic structures and typical coding questions. The second technical round stepped it up to medium-level DSA, and it also pulled in questions tied to projects I had listed on my resume.
My recruiter start already felt shaky. I had a conversation about kicking things off, but it quickly turned into mismatched signals, including moments where the recruiter seemed unfamiliar with the role and even made small jabs about where I lived. They told me the next stage would be a career-history deep dive rather than technical, so I didn’t do the usual coding prep.
The interview process typically starts with a coding assessment, followed by a series of technical interviews that may include phone screens and an onsite loop. The timeline can vary, but many candidates report a fast-paced sequence with multiple rounds occurring in quick succession.
Candidates can expect a mix of coding questions that range from basic to hard-level problems, often resembling LeetCode-style challenges. The emphasis is on demonstrating problem-solving skills and explaining thought processes clearly during live coding sessions.
Some interviews include system design components where candidates may be asked to design systems or discuss past projects in depth. This part of the interview assesses both technical knowledge and the ability to communicate design choices effectively.
There is a behavioral component where candidates discuss their experiences and how they align with the company's values. These interviews often focus on personality fit and communication style rather than technical skills.
Candidates have reported mixed experiences with recruiter communication, ranging from organized and clear to chaotic and unprofessional. Issues such as scheduling conflicts and lack of follow-up can create frustration during the process.
While many candidates felt the interview process was structured, the feedback after rejections was often minimal or unclear, leaving some feeling frustrated about their performance and the reasons for not receiving an offer.
