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

      NAUTO

      Est-ce votre entreprise ?

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


      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

      16 sept. 2017
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez NAUTO en mai 2017

      Entretien

      Phone call with Recruiter, engineer of team, take home coding challenge and finally an on-site. Each person seemed very hesitant until they reviewed the actual code. I prefer real world demonstration instead of knowledge based questions or non-practical problems. One thing I didn't like was interviewing with an engineer who wasn't part of the company. He bragged about working at Google for many years but at the same time, mentioned how much he hated working there. The other thing that got me was him stating that he's older and knows more than me, kind of putting me down at that point. Somewhat neutral to the whole process. It was somewhat quick.

      Questions d'entretien [1]

      Question 1

      A few knowledge based questions that you either know or you don't. One of the engineers that interviewed me didn't work for the company and asked me how to solve issues with Vanilla HTML/CSS while being extremely vague about the problem despite asking multiple clarifying questions. The response were too vague as well and not clear throughout.
      1 réponse
      3

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

      Entretien pour Software Engineer

      12 août 2019
      Employé (anonyme)
      Palo Alto, CA
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en personne. Le processus a pris 3 jours. J'ai passé un entretien chez NAUTO (Palo Alto, CA) en août 2019

      Entretien

      The interview experience was very fast and time consuming for me. This was good because it helped make a decision quickly within a week. First, the onsite interview directly. The recruiter was really friendly and gave me a tour of the place. Then we had lunch with the Director of Engineering, the CTO, and a few engineers where it was a general get to know you type of interview while eating a good meal. This was for about half an hour to 45 min. Then, afterward there were two technical interviews. Each 45 min long with a different interviewer. The first was very interesting. It was to analyze code (happened to be the language I was comfortable with) and figure out what it was doing, what was wrong with it, and how to improve it. This can very intimidating and difficult for those who don't code often or those who don't have experience in the field in question. They really want to see how you think and analyze the code even if it uses a strange API that you have not seen. It was on paper too so you can just point on the paper what you need to do. For me, this was just medium difficulty and a lot of experience and intuition played a part for me in this interview, but it was very interesting and educational. I don't think I got everything right, but it was certainly enough and the interviewer was very encouraging all the way. The second was just a coding challenge on the whiteboard, standard algorithm/data structure problem (medium/hard difficulty on leetcode). Very nice interviewers overall. Talked a lot about what they did and do for Nauto and it was very informational and nice to talk with. Then, had two half hour interviews with the recruiter and Director of Engineering, both very friendly and it was just your average HR interview questions. So overall, great. Afterwards, I met a few more engineers to talk with, no technical stuff. Got an offer within a week.

      Questions d'entretien [1]

      Question 1

      Read code that has problems and uses an API (you don't know what) and figure out what you it does, whats wrong with it, and how to improve it.
      1 réponse
      2

      Entretien pour Software Engineer

      30 mars 2017
      Candidat à l'entretien anonyme
      Offre refusée
      Expérience négative
      Entretien facile

      Candidature

      J'ai passé un entretien chez NAUTO

      Entretien

      The interview was fairly straightforward. Standard whiteboard questions e.g. determine whether a string is a palindrome, hash collisions etc. However, the team is very disorganized and left me waiting in a conference room for almost half an hour while they tried to find a substitute interviewer for someone who was not available.

      Questions d'entretien [1]

      Question 1

      How does a to i conversion work?
      Répondre à cette question
      3