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

      Nav

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Nav | Empleos en Nav | Sueldos en Nav | Prestaciones en Nav
      Entrevistas en NavEntrevistas para el cargo de Ruby On Rails Developer en NavEntrevista en Nav


      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 Ruby On Rails Developer

      15 jul 2018
      Candidato de entrevista anónimo
      Draper, UT
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Me postulé a través de un reclutador. El proceso tomó 1 día. Acudí a una entrevista en Nav (Draper, UT) en jun 2017

      Entrevista

      I was referred to them by a recruiter and was called in for an in-person interview. I had to sign-in, and could tell there were a few other people interviewing that week. I had a round of about 5 interviews that lasted most of the day until about 4:00pm. They said the reason I didn't get the job was my pair programming session. That surprised me a bit, because I thought I did really well at that. I think the real reason I didn't get the job was because I had a clumsy answer to one of their people-skill / culture-fit questions. Most of the employees seemed happy, and a few made some jokes that had me laughing pretty hard. They value pair programming a lot. Maybe a bit too much. I like to pair program occasionally, but I'm most efficient when I'm able to deep-dive into a project and go into the zone with my headphones on. I can do both, but I lean towards headphones-style development for 80% of my time, which is why I think I wasn't the best culture fit for them.

      Preguntas de entrevista [1]

      Pregunta 1

      How would you optimize Ruby for performance?
      1 respuesta
      avatar
      Respuesta de Nav
      7y
      Thanks for your feedback. We do value the pair programming a lot and we have had a lot of success with our engineering hiring model. Sounds like that our way of work in current stage of life didn't match the style of work that makes your most successful. As we continue to grow our engineering team, watch for future positions and if anything interests you we should have a conversation about how we operate then. Good luck on your search. Levi King, CEO