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.3% 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:
One on one interview: 24%
Phone interview: 24%
Group panel interview: 16%
Presentation: 9%
Skills test: 9%
Drug test: 5%
Personality test: 4%
Background check: 4%
Other: 4%
IQ intelligence test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Relativity (Chicago, IL) in Mar 2019
Interview
1. Applied directly in the company website after seeing the opening in Glassdoor
2. Recruiter called in just a couple of days and explained the process.
3. Online coding test was given and I was asked to take it within 3 to 4 days. The coding test was for 2.5 hours. Totally 5 questions. I would rate them as moderate type questions.
4. After getting selected in it, was sponsored to fly in to the chicago office. It was completely paid by Relativity including the stay.
5. The onsite interview was having three rounds.
a. Core values - Generic HR questions
b. Manager discussion - Your recruiting manager will be asking questions about your experience.
c. White boarding interview - This is bit extensive. It has three sections. OOPs questions, SQL questions, design questions. this will be for 1.5 hours. So get ready
6. Was informed by the recruiter in a few days that I was selected.
Overall, I feel the selection process was faster and all the people I met in the process were so friendly.
Interview questions [1]
Question 1
Cant say the exact question. But be ready with basic OOPS, SQL and design questions. Also practice medium pace questions in hackerrank. This would help a lot.
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