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

      Ergatta

      ¿Esta es tu empresa?

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Ergatta | Empleos en Ergatta | Sueldos en Ergatta | Prestaciones en Ergatta
      Entrevistas en ErgattaEntrevistas para el cargo de Software Engineer en ErgattaEntrevista en Ergatta


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

      6 may 2022
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Me postulé a través de una agencia de empleos. El proceso tomó 3 semanas. Acudí a una entrevista en Ergatta en sep 2020

      Entrevista

      I had five separate interviews, three of which were behavioral and two technical. For the behavioral interviews I met with each of the cofounders Tom, Al, and Pras and we chatted about some of my past work and what I found intriging about Ergatta. The first technical interview I had was with Pras, the CTO. It was a pair programming session where we refactored some code and wrote a few unit tests. It was simple and approachable and Pras was helpful rather than critical. I didn't feel amazing about my preformance but that's how it goes sometimes. The second technical interview I had was with one of the Android Engineers. We didn't really dive much into code but talked more about system architecture and brainstormed how I'd write this or that sort of UI. It took around 3 weeks from hearing about Ergatta to getting an offer. And I've loved it ever since.

      Preguntas de entrevista [2]

      Pregunta 1

      What excited you about Ergatta?
      Responder pregunta

      Pregunta 2

      How would you draw a line graph in Android?
      Responder pregunta
      1

      Otras evaluaciones sobre las entrevistas para el cargo de Software Engineer en Ergatta

      Entrevista para Software Engineer

      6 may 2022
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Me postulé en línea. Acudí a una entrevista en Ergatta en jul 2019

      Entrevista

      The interview process was very laid back and relaxed. I was allowed to attack the problem however I wanted, discussing what I was thinking as I went. I was free to google whatever syntax I needed as well. The CTO asked probing questions with certain choices, and some even helped me alter my path. It definitely felt like the "why" was more important than "what" I coded. Just as equally important was how I could discuss my thoughts and the problem with others. I can only hope all future interviews are as open, welcoming, and even educational as this one was.

      Preguntas de entrevista [1]

      Pregunta 1

      "Why did you choose that code structure?" "What do you think about this alternative? Why would it be better/worse?"
      Responder pregunta
      1