Relativity software engineer interviews, as three candidates describe them, mix a recruiter screen, a practical coding round built around a book class, object-oriented fundamentals, and a manager conversation.
$121K
Avg. Base Comp
$138K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Candidates who describe the Relativity software engineer process (two internship-level and one .NET developer report) point to practical coding built around object-oriented basics rather than hard algorithm puzzles. Two internship candidates were asked to write a book class. One was then asked to build a book list that stores books and to compare two book lists by value. The other spent most of the round on the time and memory complexity of their own solution and on how to improve it.
The .NET developer candidate had a technical call that leaned on theory. They were asked to explain the SOLID principles and the four OOP fundamentals out loud, and the live coding portion was described as very easy. An internship candidate was also asked about polymorphism, inheritance and queues, plus a robot kitchen design prompt about taking, assigning and handling orders.
In practice, rehearse small class designs, edge cases, test cases and complexity explanations spoken aloud. Searching with dictionaries, sets and arrays was described as easy-to-medium difficulty. The screens and manager rounds focused on resume and past experience, and one candidate mentioned the software development pipeline. All three reports ended without an offer, and two described long silences before an email rejection, so ask about timelines early. The evidence is small and mostly internship-level, so senior candidates should treat it as a guide to fundamentals, not a full picture.
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 Relativity process.
First was a recruiter call. Then I received an invitation to a technical interview, which included a simple coding task, some questions about databases, and basics of object-oriented programming. Finally, there was a call with the manager, which was something like going through my CV.
Questions asked: Queues, SOLID, ACID, concept of object-oriented programming
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 Relativity
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| String Shift | |
| Random SQL Sample | |
| Minimum Change | |
| Find the First Non-Repeating Character in a String | |
| Upsell Transactions | |
| Top 3 Users | |
| Raining in Seattle | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Bagging vs Boosting | |
| Scrambled Tickets | |
| Size of Joins | |
| Project Pairs | |
| Flight Records | |
| Download Facts | |
| Prime to N | |
| The Brackets Problem | |
| Largest Salary by Department | |
| Daily Retention Summary | |
| P-value to a Layman | |
| First Touch Attribution | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a short opening call with a recruiter or HR contact. It mostly covers your resume, whether your background matches the role, and some behavioral questions. One candidate was invited to the next stage right away. Have a concise account of your projects ready.
Two internship candidates report being asked to write a book class. One was asked to build a book list and compare two lists by value, then discuss testing and improvements. The other was questioned mostly on time and memory complexity. Expect to explain edge cases and optimizations, not only write working code.
Candidates report conceptual technical questions. The .NET developer was asked to explain SOLID and the four OOP fundamentals. An internship candidate was asked about polymorphism, inheritance, queues and a robot kitchen design prompt. Prepare a concrete example for each concept.
Two candidates describe a final conversation with a manager. One says it covered previous experience and the software development pipeline. Prepare to discuss past work and how you ship software. Outcomes in these reports were rejections, and two candidates mention delays or no detailed feedback afterward.
