Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Nav

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Nav | Offres d’emploi chez Nav | Salaires chez Nav | Avantages sociaux chez Nav
      Entretiens chez NavEntretiens d’embauche pour Ruby On Rails Developer chez NavEntretien chez Nav


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Ruby On Rails Developer

      15 juil. 2018
      Candidat à l'entretien anonyme
      Draper, UT
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 1 jour. J'ai passé un entretien chez Nav (Draper, UT) en juin 2017

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      How would you optimize Ruby for performance?
      1 réponse
      avatar
      Réponse 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