Root Inc. Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 16 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Root Inc..
Root Inc.
Software Engineer
Senior Difficult Neutral experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Take home Onsite Panel
Interview formats
Behavioral Technical Coding System Design
First, an intro call with the CTO to check basic fit. Then, a technical phone interview with two developers. After that, a take-home coding test. If that goes well, you'll have an on-site programming session with three developers, followed by an interview with the whole company. The initial phone chat is just for info and to see if you should continue. The technical interview covers computer science topics. Later stages focus on Ruby or Swift based on the role (backend or mobile).
Confirmed questions5 questions
- Can you model a deck of cards?
- What is duck-typing, and what are its pros and cons?
- What security considerations should be made when designing a web application?
Root Inc.
Software Engineer
Entry Easy Negative experience No offer 5 rounds
Interview process
Recruiter call Take home Phone screen Onsite Background check
Interview formats
Technical Coding System Design Behavioral
Applied online and got a recruiter call soon after. The recruiter was friendly and shared company details, then gave a GitHub link for a take-home assignment. After submitting the project, I had a technical phone interview covering OOP, Ruby, and Node.js. The final stage was an onsite interview focused on the submitted project. I also had a lunch interview where the interviewers seemed unfamiliar with each other, boasted, and didn't engage much. Then, there was a technical discussion about an architectural problem involving mobile apps, servers, APIs, and efficient data handling. I received a rejection a week later with no specific feedback and the recruiter was unhelpful.
Confirmed questions5 questions
- How would you track driver history from an input file?
- Can you model a deck of cards for the game Blackjack?
- Explain mixins in Ruby.
Root Inc.
Software Engineer
Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Take home Technical screen Onsite
Interview formats
Coding Technical System Design Group
The interview started with a phone screen about my background and experience. After that, I got a coding assessment, which was straightforward but a good challenge. It's important to break down the problem well, and tests are a plus. The next step was a one-hour technical screen with two developers where I had to model things over the phone, with them adding complexity to test my OOP understanding and other concepts. Expect it to take the full hour, and you get to ask questions at the end. The final stage was a half-day on-site, including a paired programming session with my code sample, a non-technical lunch, and an hour-long architecture discussion with whiteboarding. The company takes about 24 to 48 hours to decide. I got an offer the next afternoon. The process doesn't require a specific language, as I got an offer without writing any Ruby, but using Ruby might lead to a better offer. The offer I received was good.
Confirmed questions1 question
- Can you explain how you would model a deck of cards?
Root Inc. Software Engineer Interview Questions
Quoted word for word from Root Inc. interview reports.
“What is the thread count in Node.js?”
Read reports →“What is the difference between strong and weak references?”
Read reports →“What is duck-typing, and what are its pros and cons?”
Read reports →“Explain mixins in Ruby.”
Read reports →“What security considerations should be made when designing a web application?”
Read report →“How would you model a deck of cards?”
Read report →“How would you track driver history from an input file?”
Read report →“Can you model a deck of cards?”
Read report →“Can you design a system that takes lines of text as input and produces a sorted, formatted output?”
Read report →Formats, difficulty and experience
Across all 16 Root Inc. interview reports.