I'm not sure what each interview was named, so the naming below is my own. All interviews below were on Zoom. 1. Recruiter interview: The recruiter told me to let her know if I had any questions along the way. I emailed her a couple times during the process with questions and she straight up didn't respond, so I gave up on that and just pushed through. One time when I actually had to email her colleague to make sure she received my email, she finally responded and said that she did respond to my previous emails and that they probably went to my "spam" box. Wrong. Nothing in my junk email and the funny thing is that she said this in the same email thread when here responses were obviously missing. This was especially frustrating because several years before this a Peloton recruiter reached out to me and scheduled a phone call. She went missing and then finally rescheduled with some excuse. She missed that phone call and never responded to further emails. Ghosted - nice one Peloton. 2. Initial technical interview (CoderByte)(1 hour): This was a very easy React based technical interview. I somehow didn't really ace it, but they passed me anyways to my surprise. 3. Hiring manager interview (45 min): This was more of a conversation. It went well for me and I thought maybe that would hold some weight, but it didn't. 4. Panel interview - 4a. Technical interview deep dive (CoderByte)(1 hour): This was where things fell apart for me. I interviewed for a senior level role which is actually a lot lower level than my current role (my last senior role was over 10 years ago). The interview threw me off because it was a strangely architected part of an app that consisted of "models" (classes with methods) and one giant test file. The code was object oriented. There were about 15 different models each in different files, with very similar functionality and subtle different naming. It was really convoluted, and the test file was probably about 500 lines. One of the interviewer seemed to enjoy a lot of the awkwardness and really exploited it. I've experienced interviewing many times in the past, and dealing with this interviewer personality is really a setup for failure (I looked at his LinkedIn and he also has about 10 years less experience than me). It was a déjà vu experience because I felt like I had dozens of time before... some kind of evil engineering ego driven hater energy. I think the expectation was that I would be able to parse through the entire challenge questions, the entire test file and models and then remember everything about them and piece it all together. I failed at that and in the end, the feedback was that they were looking for someone with more test experience. Ironically, I have over 15 years testing experience in extensive kinds of tests and frameworks. - 4b. Product (30 min): I'm not sure what the point of this one as the interviewer didn't explain it at all and it was a different person from the calendar invite. I thought he would explain that too, but instead he got right after it. It was your standard "tell me a time when you" interview. You could probably just make up stuff here and still pass. - 4c. QA / SDET (30 min): I didn't expect this one too be so intense as I wasn't interviewing for an SDET role, and really I think testing is mostly straightforward and really depends on the team your working on. I've never had an interview like this one. - 4d. System design (1 hour): This one was supposed to be system design. It was kinda, but was more of a conversation. I felt like I was being interviewed by junior engineers, but perhaps maybe because I'm so old and have been in staff / principal / lead levels for so long. At times I wanted to just take the wheel because the interviewers just seemed confused. In the end I was rejected. The recruiter pretty much checked out, but I was able to get some feedback from the hiring manager. I felt most like-minded with the hiring manager, but probably a lot more experience than even him... so, it was a mistake to interview here, I just wanted to be on a platform team. I thought it was funny to be rejected for this, but it definitely goes to show what a poor interviewee I am and a lot of room for improvement, despite the horrible interview process from Peloton.