LiveRamp Software Engineer Generalist New Grad interview questions

OA -> Hirevue -> HR x2 -> Technical The first 4 rounds were straightforward and nothing special. It was the last round that I had a negative experience. I was told by the coordinator that the interview was Behavioral and would be focusing on learning about my experiences and LiveRamp itself. They told me to prepare projects to talk about for the interview. However, the 1-hour interview was 95% technical focusing specifically on React and Algorithms. 5% on LiveRamp and my questions. Not sure if the coordinator confused me with some other candidates. Overall, their responses varied from people. Some were slow and some were fast. The team I talked to didn’t seem like they knew what they were looking for.

Applied online for their Generalist New Grad role around the middle of November. Received a coding challenge the next day with a time limit of 3 days to complete it. After completing the coding challenge, I didn't hear back for about 2 weeks. I shot a follow-up/cold email to a recruiter with information I found off LinkedIn. Never heard a response from her personally but got an invite to a 30-minute phone screen the next day with an engineer. The 30-minute phone screen was a technical question and went well. Follow-up for the 30-minute phone screen was very quick and got an invite to a 1-hour phone screen about an hour after the 30-minute screen ended. The 1-hour phone screen was a mix of background/behavioral questions and another technical question. I felt I answered the technical question reasonably well but unfortunately was not a match. I received a rejection email 2 days after my 1-hour phone screen. Oh well, they seem to be doing interesting stuff. Overall, the process was incredibly fast (except the 2 weeks period between the coding challenge and the first phone screen). Coding Challenge: 3 questions: First question - LeetCode Easy. Simple coding question that took about 15 minutes with half of that just reading the question itself. The question format is they give you a story and you have to extrapolate the problem from that. Second question - LeetCode Easy/Medium. The second question was a dynamic programming problem to come up with an algorithm. On the coding test, they say that an optimal solution runs in O(n). I was only able to come up with worst-case O(n^2). However, I optimized throughout the code and explained my thought process in the comments. I'm not sure there is an O(n) solution. Third question - Explain your answer to question 2 in English and in terms that someone could easily understand. The second part of the question was to explain why you want to work at LiveRamp. Total Time: 2 hours 30-Minute Phone Screen: The person I was scheduled to talk to couldn't make it, so I talked to someone else. They were very nice and made me feel relaxed and made the interview feel conversational. Great experience overall. We dived right into a technical question after brief intros. Was a graph problem. After coming up with an algorithm, we dived into run-time complexities, space complexities, and optimizations. For this, just know your basic graph traversal algorithms and you should be fine! At the end, he asked me if I had any questions for him and he went into great detail in trying to answer them as best as he could. Total Time: 30 minutes 1-Hour Phone Screen: The person I talked to was similarly fairly nice. However, he was not as charismatic as the first interviewer and sometimes I was left wanting for more, such as when I was confirming parts of the question he asked. We started with about 30 minutes of behavioral questions and background questions. He asked why I wanted to work at LiveRamp over other SF companies and also about my previous internship and the work I did there. At one point, I felt like he was grilling me to an extent that wasn't necessarily normal and kept trying to get me to answer questions about my project that I wasn't necessarily relevant towards and didn't know the answers to. This was followed by 30-minutes of a technical question. Instead of an algorithmic question, this time was focused more on how I would build a potential graph in order to optimize for queries. We discussed trade-offs and run times. Total Time: 1 Hour Overall, it was a positive experience and I definitely learned a lot. They were extremely fast once human interaction came into play (e.g. post-coding challenge). Thanks for not keeping candidates hanging. Will definitely consider re-applying in the future as they seem to be doing some very cool stuff!