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

      Indigo

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Indigo | Empleos en Indigo | Sueldos en Indigo | Prestaciones en Indigo
      Entrevistas en IndigoEntrevistas para el cargo de Staff Software Engineer en IndigoEntrevista en Indigo


      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 Staff Software Engineer

      28 mar 2022
      Candidato de entrevista anónimo
      Boston, MA
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé en línea. El proceso tomó 2 meses. Acudí a una entrevista en Indigo (Boston, MA) en feb 2022

      Entrevista

      I was contacted regarding my staff-level application on February 7th and didn't conclude the interview process until March 28. Over the course of that first month I spoke with three internal hiring managers. Two of them had issues setting up a phone screen because they couldn't get their Greenhouse scheduling system to work, so my application was left on "requested interviewee availability" for 23 days (found this out from a contact I had at the company). One of the hiring managers was a contractor who stopped working for the company during my application. One of them sent me an email to schedule a phone screen with "recruiter to specify PHONE/ZOOM and delete this text" still in the email. I was really interested in the company's mission, so I reached out to another hiring manager I had spoken with the previous year to get this all resolved. My 2-paragraph cover letter detailing my love for the company's mission wasn't passed on to a single interviewer. After the final 6hr round of interviews, the hiring manager I was dealing with took a 4-day weekend and I didn't hear the feedback until 9am on Monday. First, I spoke with an engineering manager who asked about my work experience, how I practice empathy in the workplace, and went over the product. Engaging interview. I then had a Coderpad interview with the first question detailed below. I didn't finish the problem, but got "very positive" feedback (presumably for my ability to talk through the problem with the interviewer) and moved on to the final round of 6 straight hours of interviews. I1 - Spoke with senior technical director about my past projects and went into architecture on some things. Very engaging architectural discussion. I2 - Coderpad, Q2 detailed below. Two interviewers. I3 - Whiteboarding question detailed in Q4 below. Two interviewers. I4 - Engineering manager interview. Questions about my past experience with some inquisitive questions about a few projects I'd worked on. Another engaging interview. There were a couple unorthodox questions which I thought were pretty interesting - not very typical. I5 - Coderpad, Q3 detailed below. Two interviewers. I6 - Interview with senior product manager. Gave a demo of the product and was asked about past experiences with product teams, notably looking for challenges and conflict resolutions. Indigo has a shockingly bad hiring process. 9 hours of interviews, 3 of which were spent in Coderpad, and one of the least engaging whiteboarding sessions I've had in my career resulted in a response that I "wasn't technical enough" for their staff-level position. Why is Leetcode the core pillar on which they judge candidates for a position on this level? Why are three Leetcode problems necessary for someone with nearly 10 years of experience? Why were the in-depth architectural questions simply verbal discussions with the senior director and not in front of a whiteboard? Why weren't there more architectural questions? Why did Indigo blow so much money getting 14 people to speak with me over the course of 8 or 9 hours just to conclude that I don't know what I'm doing?

      Preguntas de entrevista [4]

      Pregunta 1

      Q1 - Given n non-negative integers representing an elevation map where the width of each bar is 1, compute how much water it can trap after raining.
      Responder pregunta

      Pregunta 2

      Q2 - Game of life, print out game state after each step.
      Responder pregunta

      Pregunta 3

      Q3 - Given an m x n 2D binary grid grid which represents a map of '1's (land) and '0's (water), return the number of islands.
      Responder pregunta

      Pregunta 4

      Q4 - Draw out a diagram for a service that will be talked to, with the service being a black box. Basically "how do microservices talk to each other" from what I gathered of the minimal back-and-forth I had with the interviewer. Pretty revealing that this is the only whiteboarding question I got for a staff-level position.
      Responder pregunta