Me postulé a través de un reclutador. El proceso tomó 1 semana. Acudí a una entrevista en Peloton Interactive (Seattle, WA) en jun 2021
Entrevista
A recruiter reached out to me via LinkedIn about different SRE roles open at Peloton. The interview process included an initial phone screen with the recruiter followed by an hour long zoom call with the team. The interviewers were nice and it was very pleasant talking to them. I was asked a few typical SRE basic questions around linux, networking and a coding problem which I think went pretty well. I was told by the Engineers that they are going to forward the feedback to the recruiters asap and the process will continue. Unfortunately, a week passed and I never heard back from the recruiter. Upon reaching back, I was told to wait for an update and it has been two weeks since then, very disappointing to see the recruiters ghosting you. It seems like Peloton has great engineers but the recruiters are not quite professional and I would recommend staying away from the company in the future.
Preguntas de entrevista [1]
Pregunta 1
Explain in much detail what happens when you enter a website in the browser and hit enter.
Explain how would you troubleshoot a slow linux machine.
Palindrom string coding question.
Me postulé en línea. El proceso tomó 4 semanas. Acudí a una entrevista en Peloton Interactive (New York, NY) en sep 2024
Entrevista
The interviews are as follows
* HR Call
* Debug k8 deployment, easy finished in 15 minutes
* Debug Docker container and simple coding exercise
* Personality and work experience
* System Design, but more of a Q&A
Overall I really enjoyed the interview process and the people I interviewed with and the company.
Overall my only problem was with the sys design interview, there were some questions around multi-cluster and some very specific scenarios that I didn't have experience in. I really wished they would have asked questions like that in the first interview and saved us both a lot of time.
Overall the questions were "what program/method did you use to solve x", like what did you do for CI/CD, if you say something other than Argo you probably got it wrong.
Preguntas de entrevista [1]
Pregunta 1
How would you secure a k8 application?
What would you do if you had a workload that very resource heavy but was used very infrequently?
How would you test a cluster upgrade during a blue/green cluster upgrade?
how do you secure secrets?
how do you deploy applications to k8
application scaling
Me postulé a través de un reclutador. El proceso tomó 1 semana. Acudí a una entrevista en Peloton Interactive (Atlanta, GA) en oct 2023
Entrevista
The interview process seemed straightforward from the recruiter's email. During the interview, I was advised there would be more rounds of technical interviews. The interviewer was knowledgeable and genuine. We went through the practical Kubernetes questions. I felt I did great since I completed the interview with only one mistake. After a couple of days, I received an email advising I would not be moving forward. I have not received feedback on what was lacking nor a call from the recruiter.