Glassdoor users rated their interview experience at Roon Labs as 100% positive with a difficulty rating score of 4 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Software Engineer and rated their interviews as the hardest, whereas interviews for Software Engineer and roles were rated as the easiest.
The hiring process at Roon Labs takes an average of 14 days when considering 1 user submitted interviews across all job titles. Candidates applying for Software Engineer had the quickest hiring process (on average 14 days), whereas Software Engineer roles had the slowest hiring process (on average 14 days).
I got contacted by a recruiter who scheduled an interview for one hour. The interviewer had a hostile attitude and I felt like a student during an oral exam, even the way he was speaking to me felt like if he treated me like a child. I had a feeling he must be a very difficult and stressful person to cooperate with. After all I didn't even get a rejection email.
I applied through a recruiter. The process took 2 weeks. I interviewed at Roon Labs (New York, NY)
Interview
The interview process at Roon Labs was, frankly, great. Spending time with various members of the team meant getting to understand the personalities at play, as well as being able to see the passion of the team as a whole.
The first interview was nearly wholly personality-based, and answering general career questions. Along with that, it was a great time to learn more about Roon, the projects they have on the go, and generally pick the brain of the interviewer (just as much as they are picking yours)
The next stage was a technical interview, which covered a broad range of topics across a variety of difficulty levels. Some were very easy, some were extremely complex. Overall I felt that all of the questions posed were very fair, and I learned a thing or two along the way.
After that was a final interview with a small panel which was a combination of personality, technical, and general team fit. This was also great opportunity to meet more members of the team and get a bit more insight into the projects.
By the end, I felt as though I had a pretty solid impression of what the position would entail, what the team was like, as well as the tone of the workplace. I was really quite happy with the process overall, loved talking with the team, and definitely felt drawn to the projects. When I was sent an offer, it did not take a lot of convincing to accept!
Interview questions [1]
Question 1
Tell us about some difficulties on a specific project you worked on
The coding challenge they gave was easily 8 to 12 of work before even being considered for a phone screen. In my opinion this is an inappropriate amount of time to demand of anybody so early on in the hiring process, even when they claim that it would "only" take 4 hours.
Interview questions [1]
Question 1
Re-implement Centipede on an arcade CPU emulator, reverse polish notation UNIX calculator