Advanced Software Engineer
Posted Aug 28, 2026 · We last checked this listing on Oct 6, 2026
Likely interview questions for this role
Written from this job description, not a generic list. Each one notes what the interviewer is really checking.
About your past
Relativity says its engineers use AI tools to design and ship software faster. How do you use AI coding tools today, and where do you not trust them?
What they are checking: Whether they use AI assistance with judgment, checking its output rather than shipping whatever it writes.
Tell me about a cloud-native service you built that had to handle large amounts of data. What were the hard parts?
What they are checking: Whether they have real experience with scale, which matters on a platform processing huge legal data sets.
Tell me about a time you disagreed with a technical decision on your team. What happened?
What they are checking: Whether they can push back with reasons and then commit once a decision is made.
How have you helped newer engineers on your team grow?
What they are checking: Whether they act as a technical leader at the advanced level, not just an individual contributor.
What would you do
RelativityOne holds sensitive legal data for law firms and government agencies. How does that change how you write and review code?
What they are checking: Whether they treat security and data isolation as part of everyday engineering, not someone else's job.
You find a bug that could have shown a user documents they should not see. What do you do?
What they are checking: Whether they escalate a possible data exposure immediately and transparently instead of quietly patching it.
About the work
How would you design a service that processes millions of documents for a litigation matter without losing any?
What they are checking: Whether they think about durability, retries and idempotency where losing a single document has legal consequences.
Walk me through how you would find the cause of a slow API endpoint in production.
What they are checking: Whether they use metrics, traces and logs systematically rather than guessing at fixes.
How do you decide how much testing a change needs before it goes out?
What they are checking: Whether they match testing to risk, which matters when accuracy is critical for customers.
How do you approach breaking a large legacy component into smaller services?
What they are checking: Whether they can modernize carefully without disrupting customers relying on the existing system.
Practice this interview out loud.
Offer builds a real interview for this exact role at Relativity from your resume and this job description, asks the questions one at a time, and tells you what landed. The first one is free.
Practice this out loudThe full job description
As published by Relativity.