Relativity Software Engineer Interview Questions
& Process

So for this role, they wanted me to review and practice medium-level data structures and algorithms (DSA), making sure I had strong problem-solving skills. I also had to revisit system design basics, like being able to clearly explain design choices, trade-offs, and the reasoning behind any architectural decisions made. Pretty much, it was standard DSA and system design questions for a regular Software Engineer job.

I went through 2 interview stages: a phone screen and a short live coding session. The first round was pretty relaxed, with behavioral questions and two English questions. I was quickly invited to the next stage. Then, there was a coding interview, where I had a few tasks involving class implementation and basic searching. They suggested I'd be moving on, but then completely ghosted me, and I received an automated rejection email after a month. I admit I didn't perform well in the interview, but I feel they could have at least informed me about their decision sooner than a month later. Getting an automated email during the interview process after resume screening is also quite unexpected. During those two rounds, the interviewers were nice and seemed helpful (though round 2 was a bit chaotic, which might have also been my fault).

I got a call from the recruiter to do a phone screen, which I passed. Then there was a HackerRank challenge that I thought was easy and passed. After that, I was invited for an onsite interview. The first part of the onsite was with a junior engineer where we talked about general stuff like learning and my projects. I mentioned my compiler project, but since I applied for web development, they were more interested in fun projects. The second interview was with a manager, and it was all behavioral, asking about my internships. I can't recall much, but I tried to be straightforward with my answers. The technical part of the onsite wasn't too hard. It had OOP questions and a whiteboard coding problem about shape classes. They also asked me to design YouTube, and I suggested using the YouTube API to get video URLs and download them locally, which I think is the real-world approach. However, they wanted me to build a web crawler instead. I ended up emailing the recruiters to check on my status and found out they were moving forward with other candidates. It's probably for the best. The office was cool, but the work-life balance seemed off based on the junior engineer's description of after-work gatherings.