Software Engineer applicants have rated the interview process at Relativity with 2.8 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 56% positive. To compare, the company-average is 51.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 20 days to get hired, when considering 38 user submitted interviews for this role. To compare, the hiring process at Relativity overall takes an average of 24 days.
Common stages of the interview process at Relativity as a Software Engineer according to 38 Glassdoor interviews include:
Phone interview: 24%
One on one interview: 24%
Group panel interview: 16%
Skills test: 9%
Presentation: 9%
Drug test: 5%
Background check: 4%
Other: 4%
Personality test: 4%
IQ intelligence test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Relativity (Chicago, IL) in Mar 2020
Interview
Format of the interview: all digital due to current health concerns.
Overall:
-The recruiter was pretty cool. He really pushed you for success.
-The first coding portion was relaxed. He gears you to the right direction.
-The system design interviewer was really engaging. I asked if system design would be something the position I applied for would be doing. He said no.
-The second coding interview portion wasn't as engaging as the first. It felt as if the dev didn't want to be there.
-The behavioral portion felt scripted, but was an okay experience.
In depth of what I went through:
1.) Phone screening 15-30 min call
a.) Talk about resume and who you are.
b.) Explain a project.
c.) Why you're leaving your current position.
2.) 5 question hackerrank 2.5 hour time limit.
a.) 1-3 leetcode style coding
i.) String manipulation problem
ii.) makes sure you can read directions and code the problem
iii.) Involving a stack. this <<>>{} question
b.) subjective question
c.) object oriented programming (has no test cases)
2.5.) Heads up of the onsite 5 min call
3.) Onsite split to 5 sessions 3.5 hour
a.) Coding
i.) how to prevent multiple transactions in one: threading and locks
ii.) working with API
iii.) some sql
b.) System Design (challenging)
c.) Another Coding (easier)
i.) data structure
ii.) 2d Array cell class of dead or alive. if 3 neighbors cells are alive then set that cell to alive. if 2 or 3 neighbors dead then set that cell to dead.
iii.) OOP - writing a class that flips the logic of the if statement from ii
d.) Behavioral
i.) a bunch of behavioral questions read from a list of questions.
ii.) questions on previous experience
e.) debriefing
i.) thoughts on the interview
Review and practice medium-level data structures and algorithms (DSA), ensuring strong problem-solving skills. Revisit system design basics, clearly articulate design decisions, trade-offs, and reasoning behind each architectural choice made. Overall it was a basic DSA and Sustek design questions for any standard Softare Engineer job.
I applied online. The process took 4 weeks. I interviewed at Relativity in Dec 2021
Interview
Technical questions were based on foundational OOP concepts and key software development fundamentals. "Insight" interview questions were tied to the company's core values - easy to look up ahead of time on the company's website.
I applied online. The process took 2 weeks. I interviewed at Relativity in Jul 2021
Interview
First I had a 30 minute phone screen with recruiter. The next week, i had a 30 minute phone screen with an engineering manager. Both of these interactions were positive.
Then i had a 3 hour panel interview with 3 engineers (2 coding challenges) and a manager and this is where I had a horrible experience.
I was told that i could do the challenges in any language i wanted but the program they used was not set up properly. When i switched to a language i was more comfortable writing in, the boilerplate code was not copied over. So, i wrote hybrid code since i wasn't as comfortable writing in the language that they had set.
The first interviewer was 15 minutes late and i had to email the hiring director since no on was on the Zoom call with me. Despite the lateness of the first engineer, i was expected to finish the task in the original allotted time. The second engineer gave me an algorithm challenge. The third engineer asked mostly architectural questions. The manager asked more behavioral questions related to the company's values.
Interview questions [1]
Question 1
Describe a situation where you could have done things differently and why