RhythmOne Interview Questions
& Process

I started with a recruiter chat where they explained the company. Then, I got a coding challenge to finish by the next day. I was told a manager call would follow if my code was good, but that didn't happen. Instead, I got an email for an onsite interview the next Monday. There, I had three sessions: first, a 45-min chat with a developer about my past projects and languages, asking about preferences. They asked one technical question: the difference between Ruby and Python. Second, another 45-min session with a developer who lent me his computer to find and answer an unanswered Python question on Stack Overflow, which didn't work out in the end. Third, I met with two SDET/QA folks who asked me to devise test cases for a string-handling method. Throughout, interviewers answered my questions honestly. Finally, the recruiter shared that the first two interviewers felt my technical skills weren't strong enough. It seemed like they wanted versatile developers, but I left unsure if they specifically needed Python proficiency.

The interview process kicked off with a call from the corporate recruiter. They checked out my experience and what I was looking for salary-wise to see if it was a match. Then, I chatted on the phone with the Lead Developer I'd be working under. After doing well in both those chats, I was invited for an in-person interview. This involved some hands-on tech tests and a white-boarding session. A few days later, I got a call to set up a Skype video call with the CTO. This meeting included technical assessments, discussions about concepts, a showcase and presentation of my previous projects, and a deep dive into the company's future plans. Next, I met with two other developers, one in management and one peer, who put me through a thorough round of technical tests and programming challenges that needed code to be submitted. The whole thing took a bit longer than expected, mainly because some people involved were traveling or on vacation. Once they were back, things moved along smoothly.

I had a phone screening with a recruiter, then a phone interview with the manager. After that, it was a tough stretch of 5 interviews back-to-back, each lasting 30 minutes. The whole experience was pretty rough because they weren't great at sticking to the schedule or keeping me informed about where I was in the process; they seemed disorganized. Having 5 interviews in a row was a bit much, especially since I spent the first 15 minutes of each just repeating my history and experience, and by the fourth one, I couldn't even remember what I'd already told them. If they'd planned better, maybe group interviews would have been more efficient, giving them a better sense of my skills from different angles without wasting so much time. After it was all done, I was told I'd hear back early the next week, but I didn't. I emailed, and the recruiter finally responded a week later, saying they wanted to hire me but had to sort out some legal stuff, making it sound really positive. They said I'd get something the following week, but then there was radio silence for several weeks. Considering I invested about 5 hours in this, I'd have hoped for the courtesy of being told I didn't get the job.

Started with an intro chat with HR, then got a homework assignment due in a couple days. After that, had a tech phone screen with the team lead. Then, I went on-site for a bunch of in-person interviews. Overall, it was a good time, people were chill and knew their stuff.