Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Peloton Interactive

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Peloton Interactive | Empleos en Peloton Interactive | Sueldos en Peloton Interactive | Prestaciones en Peloton Interactive
      Entrevistas en Peloton InteractiveEntrevistas para el cargo de Senior Software Engineer en Peloton InteractiveEntrevista en Peloton Interactive


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Senior Software Engineer

      12 de nov de 2022
      Candidato de entrevista anónimo
      New York, NY
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Peloton Interactive (New York, NY)

      Entrevista

      2 Design (data and architecture) and 1 Coding round. This text box is asking me to enter min 30 words but I don't have that much hence writing this. Please ignore.

      Preguntas de entrevista [1]

      Pregunta 1

      // // We want to be able to give the user a breakdown of how much time, over the duration // // of the workout, they spent in each heart rate zone. // // I.e. we want to be able display the user a report like: // // Great job on your 30 minute HIIT class! Here's a breakdown of how much time you // // spent in each of your heart rate zones: // // PEAK: 7 minutes // // CARDIO: 10 minutes // // FAT BURN: 10 minutes // // WARM UP: 3 minutes // // To do so, we need to write a function to calculate how much // // time over the workout duration was spent in each heart rate zone. // // We'll use 4 standard heart rate zones, which we can represent as a list of pairs: // // WARM UP: 0 - 60 percent of the user's maximum heart rate (0, 60) // // FAT BURN: 60 - 75 percent of the user's maximum heart rate (60, 75) // // CARDIO: 75 - 85 percent of the user's maximum heart rate (75, 85) // // PEAK: 85 - 100 percent of the user's maximum heart rate (85, 100) // // If a user's heart rate falls on the border of the upper and lower range of a // // zone, we'll bucket them into the upper zone. For example, if we end up with a // // set of zones [(157, 185), (139, 157), (111, 139), (0, 111)], a heart rate of // // 157 will be considered in the (157, 185) heart rate zone. // // Write a function "timeInHeartRateZonesForWorkout" given: // // - an array of (time, bpm) integer pairs for a user // // - the ending time of the of the exercise (in seconds from start) // // - the user's maximum heart rate, which is used to calculate their heart rate zones // // The function should return an array of seconds the exerciser spent in each heart // // rate zone sorted from PEAK to WARM UP. If the exerciser did not spend any time in // // one of the four zones, return 0 for that zone. // // For example, given a array of times and beats per minute: // // [(0 70),(50 90), (60 120), (70 135), (100 150), (300 180), (400 75)], // // [(49 170),(50 90), (60 120), (70 135), (100 150), (300 180), (400 75)], // // a maximum heart rate of 185, and a workout duration of 500, the function should // // return [100, 200, 40, 160]. The exerciser spent 100 seconds in PEAK, 200 in CARDIO, // // 40 in FAT BURN, and 160 in WARM UP. // // Interviewer Notes: // // * all times and beats per minute are always positive, whole numbers // // * any time before the first data point is spent in the WARM UP zone
      Responder pregunta
      8

      Otras evaluaciones sobre las entrevistas para el cargo de Senior Software Engineer en Peloton Interactive

      Entrevista para Senior Software Engineer

      24 de may de 2023
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé en línea. Acudí a una entrevista en Peloton Interactive en abr 2023

      Entrevista

      Was asked a simple coding question. Was not on that day and wasn't able to nail the question. Never-the-less, I got 98% of the solution but was tripped up on a single test case with an off-by-one error I ran out of time trying to debug.

      Preguntas de entrevista [1]

      Pregunta 1

      Implement a list-based data structure that performs inserts and deletes in constant time.
      1 respuesta

      Entrevista para Senior Software Engineer

      22 de mar de 2023
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en Peloton Interactive en feb 2023

      Entrevista

      TLDR - Interview questions were average difficulty. Interview process was chaotic and left a bad impression of how the company operates. Applied online. Had a pleasant experience with the phone screen. Onsite was a different story. The process was pretty chaotic. It was clear when I spoke to interviewers that they had no interest in me as a candidate but were there to do this interview as a formality. Also the schedule and calendar invites that I received were not correct so I showed up in zooms that had no interviewers and in one case showed up at the wrong time.

      Preguntas de entrevista [1]

      Pregunta 1

      1 phone screen coding 1 on site coding 2 systems design 1 hiring manager interview
      Responder pregunta
      2

      Entrevista para Sr. Software Engineer

      8 de feb de 2023
      Candidato de entrevista anónimo
      Oferta rechazada
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 4 semanas. Acudí a una entrevista en Peloton Interactive en dic 2022

      Entrevista

      Recruiter interview: Typical recruiter screening interview. Technical Screening: A data structures type question tech screen Onsite: 4 onsite interviews (data structures, sys design, data modeling, behavioral). Overall the interview process was really great. They allow you to lookup syntax/documentation on Google in the coding questions. The system design and data modeling questions were open ended and they weren't looking for an exact match to their solution.

      Preguntas de entrevista [1]

      Pregunta 1

      - Typical data structures questions - For the data modeling and system design they used good questions related to Peloton.
      Responder pregunta

      Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti

      avatar
      Offshore Marine Services
      3.9★Remuneración y prestaciones