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

      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

      Fetch

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Fetch | Ofertas de empleos en Fetch | Sueldos en Fetch | Beneficios en Fetch
      Entrevistas de FetchEntrevistas para el puesto de Senior Android Engineer en FetchEntrevista de Fetch


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      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 de primera mano.

      Búsquedas de empleo

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

      Entrevista de Senior Android Engineer

      8 jun 2026
      Candidato de entrevista anónimo
      Chicago, IL
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. Acudí a una entrevista en Fetch (Chicago, IL) en may 2026

      Entrevista

      The interview process started with the recruiter/screener that had reached out to me on LinkedIn. Unlike most screening interviews, this one included rapid-fire technical questions which was fine, but kind of took me by surprise since most recruiters don’t get into the technical stuff so much. I guess I did well enough to make it to the next round. The second round was a live-coding (in Android Studio) round. I did not get a great vibe during this round (didn't seem very friendly), but at least it was in Android rather than in HackerRank or something similar. By the end of this round I was starting to form a negative opinion of the company/people working there. I made it past this round and onto the last stage. Last came what they call a "virtual onsite" round which was scheduled for 5 hours which seemed kind of extreme. It started with a cross-functional/behavioral round, then an engineering manager round, then a system design round, and finally another live-coding in Android Studio round. I enjoyed the cross-functional round and I was starting to rethink my earlier hesitations about the company after this round. The engineering manager round wasn't quite as pleasant, but it wasn't awful either. The system design round went well enough and I found the interviewer to be patient and helpful in that round. Then finally another live-coding Android Studio round. This is where I fumbled. This round completely turned me off from the job. At one point I was asked if I had ever used Jetpack Compose (been using it for years) which I found to be very rude. There was just an air of smugness and condescending on display in this round that you try and avoid when picking your next landing spot.

      Preguntas de entrevista [1]

      Pregunta 1

      Recruiter screening included rapid fire questions around Android and Kotlin, specifically some questions around coroutines. First live-coding round was a simple enough login screen/view model that needed to be wired up to an already coded repository/data layer. The system design round was quite involved for the time allotted and included designing an edit receipt screen. The final live-coding round was to fix bugs in a screen that showed some images and then to implement some image compression logic (you can use AI to help, but you’ll have to explain the prompt and output). The part that tripped me up was they expected me to speak to the Big O time complexity of the image compression algorithm. It had been mentioned that the interview process didn’t include any kind of leetcode rounds and so I falsely assumed this meant no discussions of Big O notation so I hadn’t studied this at all before the interview.
      Responder pregunta

      Las mejores empresas en cuanto a «Remuneración y beneficios» cerca de ti

      avatar
      Honeywell
      4.0★Remuneración y beneficios
      avatar
      Apple
      4.2★Remuneración y beneficios
      avatar
      DONE by NONE
      3.8★Remuneración y beneficios
      avatar
      HubSpot
      3.6★Remuneración y beneficios