Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Indigo

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Indigo | Offerte di lavoro di Indigo | Stipendi di Indigo | Benefit di Indigo
      Colloqui di IndigoColloqui per Staff Software Engineer presso IndigoColloquio di Indigo


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Staff Software Engineer

      28 mar 2022
      Candidato anonimo a colloquio
      Boston, MA
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 2 mesi. Ho sostenuto un colloquio presso Indigo (Boston, MA) nel mese di feb 2022

      Colloquio

      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?

      Domande di colloquio [4]

      Domanda 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.
      Rispondi alla domanda

      Domanda 2

      Q2 - Game of life, print out game state after each step.
      Rispondi alla domanda

      Domanda 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.
      Rispondi alla domanda

      Domanda 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.
      Rispondi alla domanda