What LiveRamp software engineer candidates report: a recruiter screen, a coding round (BFS/DFS or whiteboard game logic), system design and behavioral conversations, plus communication problems with recruiters.
$153K
Avg. Base Comp
$192K
Avg. Total Comp
4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe LiveRamp's software engineer interviews as a mix of coding, design and conversation, and they report that the format is not always clear in advance. The one report that ended in an offer describes a phone screen about background and skills, followed by an onsite with a whiteboard minesweeper game-engine problem, a system design round and a behavioral session. That candidate said the team responded quickly with a decision.
A senior-level candidate who did not get an offer reports a different surprise. The recruiter described the next round as a non-technical career conversation with the hiring manager, but it opened with a BFS/DFS coding question. The candidate had skipped LeetCode practice and struggled. The practical lesson is to prepare for a coding round even when a stage is described as a conversation, and to ask the recruiter to confirm each round's format.
An internship candidate, whose experience may differ from full-time loops, reports an online assessment with an unusually broad design prompt and two back-to-back coding interviews. These mixed LeetCode-style problems with geometry and math, and one asked for a Minecraft implementation. Another candidate describes tightly scripted recruiter and hiring-manager interviews with little room for follow-up questions, so keep answers concise and self-contained. Two candidates report slow or absent communication after the interviews, so ask about next steps and timing at the end of each stage.
For preparation, practice graph traversal, implementing small game or state-machine problems on a whiteboard, and explaining design trade-offs aloud. Also practice a clear walkthrough of your past work.
Synthesized from 4 candidate 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 Liveramp process.
I went through a pretty standard interview loop at Liveramp for a software engineer role. It started with a phone screen where they asked about my background and skills, followed by some follow-up questions to dig deeper into my experience. Nothing too surprising there — just the usual way to get a sense of who I am and what I can do.
The onsite was where things got more technical. I did a whiteboarding session where I had to code up a minesweeper game engine, which was a solid algorithmic problem that tested my ability to think through game logic and state management under time pressure. Beyond that, there was also a system design round and a behavioral session mixed in. The interviewers seemed genuinely interested in the work and the team came across as great — they were responsive and got back to me quickly with their decision. Overall, if you're prepping for this, expect to spend real time on coding problems and be ready to talk through your design choices clearly.
Prep tip from this candidate
Focus on LeetCode-style algorithmic problems and be prepared to implement non-trivial logic like game engines on a whiteboard. Practice system design separately — they test both, so don't neglect the architecture side.
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 Liveramp
Describing a data project and its challenges
| Question | |
|---|---|
| Counting File Lines | |
| Simple Movie Database | |
| Minimum Moves to 2048 | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Subscription Overlap | |
| Top 3 Users | |
| Find Bigrams | |
| Last Transaction | |
| Random SQL Sample | |
| Longest Streak Users | |
| Size of Joins | |
| String Shift | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Get Top N Frequent Words | |
| Like Tracker | |
| Weighted Keys | |
| Duplicate Rows | |
| Youtube Recommendations | |
| Find the First Non-Repeating Character in a String | |
| Flight Records | |
| Raining in Seattle | |
| Type-ahead Search |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter call covering their resume, background and skills. One candidate was told the next round would be non-technical, and that turned out to be wrong. Ask the recruiter to confirm in writing what each later round will cover. Recruiter responsiveness may vary, so ask about timing.
Candidates describe a conversation with a manager about past work. One senior candidate reports that it opened with a BFS/DFS coding problem despite being described as non-technical. Another describes a tightly scripted question list with little follow-up. Prepare a concise career story and keep coding practice ready.
The candidate who received an offer reports whiteboarding a minesweeper game engine, which tests game logic and state management. An internship candidate reports LeetCode-style, geometry and math problems. Candidates typically describe algorithmic coding, so practice graphs, BFS/DFS and implementing small simulations while explaining your approach.
The offer-receiving candidate reports a system design round and a behavioral session as part of the onsite. An internship candidate reports an abstract design prompt in the online assessment. Prepare to discuss design trade-offs clearly and scope ambiguous prompts before diving into implementation. Depth may vary by level.
