I was contacted by a recruiting agency that worked closely with Peloton. There was no direct phone contact with Peloton until the in-person interview. They showed me the product and talked for a while, then sat me down for a pen-and-paper coding quiz. All the questions were the typical things you would find on Google coding challenges, CodeEval, and so on. None were exceptionally hard, but one or two were designed to see that you really knew Python well.
I did just fine, and stumbled on the question listed below, but even senior developers stumble there, apparently. In the end, the recruiter told me that they were really hoping for a more senior developer, but wanted to consider other (undoubtedly more affordable) options.
I was asked to write the simple Fibonacci sequence, so I did it recursively. They then asked me to do it dynamically, so I did. They then asked me to compare the runtime and space complexity of both, and state how much better the dynamic version was, if it was (obviously it was).
In the end, I felt like my time was wasted. I did more than fine on the test, and they are a really diverse group, so I couldn't imagine that it was a bad culture/personality fit. I think they just didn't want to pay for a senior developer and then realized that a recent grad just isn't going to be able to get done what someone with 10+ years of experience can do.
My advice would be to inquire strongly about what they are exactly looking for.
What does this print?
def paradox(): try: raise Exception("Here") except: return "There" finally: return "Or maybe there"
return "Or here?"
print paradox()
The following metrics were computed from 34 interview experiences for the Peloton Software Engineer role in United States.
Peloton's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Peloton's Software Engineer interview process in United States.