RTS Labs Interview Questions
& Process

The interview process involved 3 rounds. The first was a recruiter call, the second was with the current PM team, and the third and final round was a presentation of a PM case study. This final presentation was supposed to be to the PM team, head of HR, director of engineering, CRO, and CEO, although the CRO and CEO did not attend. I noticed the Glassdoor reviews and when I asked the recruiter about the negative reviews, she said they were mostly from a scam to make the company pay to remove them, essentially dismissing them. The recruiter also mentioned that the PM team is very new, with the most experienced person having only been there 6-7 months. She explained that the company is just starting to leverage PMs, so these are not backfills but new roles. However, a quick LinkedIn search showed previous Project Managers at the company, and those I contacted did not have a favorable view. I'd advise proceeding with caution.

Reached out to directly on LinkedIn for this role. There were 3 rounds of interviews. The first was a phone interview for about 30 minutes, which went well. A week later, I had another interview via Google Meet, and that also went well. The final interview was a group presentation, which was recorded because someone couldn't make it. I had to follow up after a week and a half to ask about my application status and was told they thought I already knew I wasn't moving forward. The whole thing took about a month. Communication was kind of iffy until the end when it was terrible. 2/5, wouldn't really recommend.

I put in my application online and then got a call back from RTS in just a few days to schedule a phone interview. The phone screen was actually pretty technical, more so than I was expecting given my past experiences with phone screens, which were usually more laid-back and just for introductions. About two weeks after that, I went in for an in-person interview. Luckily, I brought my laptop because the interview was mostly a live coding challenge. They would have provided a computer, but I felt more comfortable using my own setup. The whole thing was divided into three parts: two different coding tasks and then a case study. It took up the full three hours I had booked. I had a bit of a tough time with the first coding challenge, but I made sure to explain my thought process to the two developers who were interviewing me. They mostly let me work on my own but stepped in to offer guidance when I needed it. I really liked how flexible the interview was and felt at ease with the interviewers. I think by discussing my approach and interacting with them, I managed to show what I could do, even though I stumbled a little on understanding the requirements for the first coding challenge.

The interview process was pretty straightforward but took a while to get through. The HR person was a bit disorganized but generally laid-back. It kicked off with a phone screen, then a live coding task, followed by a case study. Everything was fairly basic, not particularly tough, and I was expecting a bit more. After that, I met with the CEO, who's a pretty cool guy. All in all, I thought it went well until he asked about my salary expectations. I suspect my desired salary was higher than they intended to pay, but I'm already well-compensated and wasn't desperate for this role. They mentioned they'd let me know within a few days, but I never heard back. That was it.