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

      Route

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Route | Offres d’emploi chez Route | Salaires chez Route | Avantages sociaux chez Route
      Entretiens chez RouteEntretiens d’embauche pour Software Engineer chez RouteEntretien chez Route


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

      20 déc. 2021
      Candidat à l'entretien anonyme
      Lehi, UT
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 3 semaines. J'ai passé un entretien chez Route (Lehi, UT) en sept. 2021

      Entretien

      Initial interview involved meeting virtually with a developer or two. The first half they selected two data structures and asked me to explain what they were, when/how they're used, etc. The second half of the interview they asked a basic whiteboard question where I had to solve some problem. Before we started they said I could approach the problem in one of two ways: I could have them silently watch the whole time without saying anything until I was done, or we could do it in more of a collaborative situation where we can all talk, ask questions and solve it together. I opted for the open-ended version where we kind of solved it together. Afterwards there was about 10 minutes left for me to ask whatever questions I had. The second round of interviews was basically the exact same as the first, just with different interviewers and different questions. The third round was with two more developers and was focused on architecture and system design. They mostly asked me to explain and discuss some things on my resume, and to diagram some of it on a virtual whiteboard. Overall it was a very positive experience. I'm not great at solving whiteboard challenges, so I'm glad it was a "collaborative" effort. I believe they were still evaluating on my ability to think through things and my ability to work collaboratively with others, so it's not an automatic fail if you don't get it right. I little to no experience with system design, so the third interview was a struggle for me and that's where I failed out. If you have some good understanding about a few things you've done in that regard, that part would probably go better for you than it did for me.

      Questions d'entretien [1]

      Question 1

      What is a hash map, and when would you and wouldn't you use it?
      Répondre à cette question
      2

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Route

      Entretien pour Software Engineer

      8 janv. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Route en mars 2024

      Entretien

      1. Hiring manager talk 2. Coding interview (leetcode medium bfs) 3. System design (past project discussion with an engineering manager) 4. Director call (cultural fit) Feedback was good, but no hire. Cause they were only hiring for one person.

      Questions d'entretien [1]

      Question 1

      Leetcode style BFS medium question
      Répondre à cette question

      Entretien pour Software Engineer

      18 avr. 2023
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Route

      Entretien

      Got to the technical screen interview and was asked to write code for a problem which could be solved with a graph traversal algorithm. Attempted to do what was asked but the interviewer kept interrupting and asking the same questions over and over, obviously trying to steer me to a specific solution in mind (which I believed to be incorrect, and explained why.) Interviewer finally got frustrated and told me to "get it through my head" that their solution was the right one. Bizarre experience.

      Questions d'entretien [1]

      Question 1

      Write a graph traversal/aggregation algorithm
      Répondre à cette question
      3

      Entretien pour Software Engineer

      1 nov. 2021
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Route

      Entretien

      Basic DSA questions and a coding challenge. I was not able to complete the challenge. I asked the interviewer how they would approach the problem afterward and first, they laughed, and then very vaguely explained an approach. I'm not sure they even knew how to solve the problem, so any advice given when I was stuck seemed to be more harmful than helpful. I may have just gotten a bad draw because the recruiter was very helpful and responsive.

      Questions d'entretien [1]

      Question 1

      Explain a hash map. Recursion question.
      Répondre à cette question
      3