LiveRamp logo
LiveRampSoftware Engineer
Updated May 2, 2026

LiveRamp Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at LiveRamp, newest first and distilled into what to expect across the loop.

Get your personalized LiveRamp Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Build my free plan
Hot & recentNewest first
6 months ago
Average Positive India

I was told the process would be three rounds, with two coding-focused interviews plus an HR conversation. The first round was centered on DSA and problem solving, and they walked me through two medium LeetCode-style questions. The next technical round was similar but slightly heavier: one medium coding question and more DSA/problem-solving.

The part that really hurt was the time issue in that second round. I started on the medium problem, but the interview timed out before I could finish, and I didn’t clear the stage afterward. Because the technical rounds were the core of the evaluation, there wasn’t much room for recovery once the clock hit zero.
8 months ago
Average Neutral United States

After a recruiter call, I got pulled into a straightforward sequence that looked like hiring-manager conversations paired with technical rounds. The flow I saw was recruiter contact first, then an initial technical interview, a second technical interview, and finally another hiring-manager discussion where they covered a mix of topics beyond just coding.

What stood out was how tightly the process was run until scheduling fell apart for me. In my case, the schedule was botched and I was thrown into a coding interview with essentially no prep. When I asked about the hiring-manager interview, it got canceled minutes before it was supposed to start, and I never got a real explanation or meaningful follow-up. A few days later I received a generic rejection.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences
  • Difficulty, sentiment and outcomes
  • New reports added every week
See all experiences
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Interview Structure & Timeline

The interview process typically starts with a recruiter call, followed by one or more technical interviews, and often culminates in an onsite loop. Candidates have reported varying experiences with scheduling, including some facing significant delays or cancellations.

Recruiter callTechnical interviewsOnsite loop

Technical Coding Rounds

Most candidates experience multiple coding rounds that focus on data structures and algorithms, often using LeetCode-style questions. The time pressure in these rounds can be intense, and candidates noted that incomplete solutions can negatively impact their chances.

Data structuresAlgorithmsLeetCode

System Design & Behavioral Interviews

In addition to coding, candidates often participate in system design discussions and behavioral interviews, which are separate from technical assessments. These rounds emphasize communication and problem-solving skills beyond just coding ability.

System designBehavioralCommunication

Assessment Formats

Candidates have encountered various assessment formats, including online coding challenges, timed tests, and even presentations. Some found the assessments to be unusually difficult or not reflective of typical software engineering tasks.

Online assessmentTimed testsPresentations

Communication & Feedback

Many candidates expressed frustration with the lack of communication and feedback throughout the process, particularly after interviews. This often left them feeling uncertain about their performance and the overall evaluation criteria.

CommunicationFeedbackTransparency

Overall Difficulty & Experience

While some candidates found the technical challenges manageable, others described the overall experience as chaotic or unprofessional due to scheduling issues and operational friction. The perception of the interview difficulty varied widely among candidates.

DifficultyCandidate experienceOperational issues