RudderStack Interview Questions
& Process

You start with an intro call where they give you a lot of info about the company, domain, product, and your potential area of ownership. Then there's a take-home assignment which is a product problem. You'll need to do research, understand the product and domain, and come up with a solution that includes a strategic, executable roadmap with a continuous discovery and release process. After that, you'll have a CPO/peer interview to review your take-home assignment. Finally, a CEO interview to check for culture, values, and quality fit.

So basically, after my third round with Rudderstack, I got ghosted. I actually connected with someone who's an AE there to get in touch with the SDR manager who'd be my boss. First, there was a 15-minute screening call, then a 30-minute chat about Rudderstack's value prop, where I had to study their product more. The third round had four interviews back-to-back in two hours, which I thought went pretty well. After that, the process just stopped. I've been waiting weeks for a response and have moved on. Good luck to RS, but this is a really unprofessional way to reject candidates or handle the interview process.

This was quite possibly the worst interview process I've been through. It took about two weeks to complete. There were three rounds in total. The first two were technical, and the last one was with a manager. The people interviewing were really knowledgeable and nice to talk to. I felt like I did a great job in all of them. The feedback I got from them was also positive. I was really excited about the job because I liked the company's goals and the work they were doing. However, after the final round, they let me go because of my background. I think they should check backgrounds before even interviewing, because I had to explain mine in every session. They could have just said no earlier. It feels like all those hours I spent in interviews were pointless.

The hiring process wasn't very clear and I didn't get much useful feedback. They called the job Product Engineer, but the interviews felt more like for a Software Engineer role, and they didn't lay out what they expected. Before the last interview, they told me to have a drawing tool ready. When I asked if I should prep specific diagrams like UML, they said if the conversation went that way, I should know UML. This made it tough to figure out how much and what kind of prep was really needed. In the final round, talking was hard because of strong accents, and it was a long (2-hour) interview with two engineers at once, making it more tiring than useful. The worst part was the feedback. After putting in a lot of time and going through several rounds, I got a generic rejection email the next day from a 'noreply' address, with no extra details. I was hoping for at least some quick, helpful feedback given how much time I spent.