My interview experience consisted of two rounds. The first round was really just a screen, and the second round consisted of one technical round and three behavioral rounds.

The technical round was tailored for someone with a Software Engineer background and not what I was expecting for a Data Engineer role. I have interviewed for Data Engineering positions at other companies, and generally, the technical round had a mix of easy-medium Python and medium-hard SQL questions, which is what I would consider more relevant for a Data Engineering position. My technical round consisted of a system design question and a medium-hard LeetCode question.

I would have rated this interview process a neutral experience, except for the fact that I had to constantly message the recruiter for updates. Even after my final round, I had to request an update on my interview status and ended up not hearing back from the recruiter.

This occurred over several weeks and gave me an extremely negative impression of Peloton. I hope this is due to the growing pains of Peloton and not a common occurrence.

My advice for Peloton is to create some sort of feedback process. I doubt anyone higher up knows about my negative experience, considering there was no way to provide any feedback. Since there is no way to provide feedback, it is probably why the recruiters are okay with not responding and providing a good interview experience.

Practice for Software Engineer questions, even though it's a Data Engineer role.

One system design question. One medium LeetCode question.