Applied through the website. Received a code challenge exam on HackerRank. Did the 3 practice problems on HackerRank quickly. Went to do the real test afterwards.
The challenge level raised dramatically compared to the practice problems. Also, it's 75 minutes for 4 problems!
I spent 30 minutes solving the first one. I could have done it quicker, but I wasn't familiar using HackerRank and I was rushing. After solving the first problem, I knew I couldn't finish the rest in time, so I gave up.
I don't like time constraints on the coding challenge. It's probably another thing that caused me to take longer to complete the first problem; I was rushing. Most of the time, quick coding only produces inefficient junk. I'm not a quick coder, but I get my coding projects done quickly and efficiently because I start/plan early. Hopefully, if an HR sees this, they can improve it.
HackerRank coding challenge
The following metrics were computed from 13 interview experiences for the Peloton Software Engineer role in New York, New York.
Peloton's interview process for their Software Engineer roles in New York, New York is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Peloton's Software Engineer interview process in New York, New York.