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

      Autify

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Autify | Offres d’emploi chez Autify | Salaires chez Autify | Avantages sociaux chez Autify
      Entretiens chez AutifyEntretiens d’embauche pour Backend Engineer chez AutifyEntretien chez Autify


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

      16 mars 2023
      Candidat à l'entretien anonyme
      Tokyo
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Autify (Tokyo) en févr. 2023

      Entretien

      I stopped at 2nd stage. Overall here is the Interview Process: 1. Coding test using Hackerrank with 60 minutes time contains 3 questions. 2. Take home assignment building app in 1 week.

      Questions d'entretien [1]

      Question 1

      1. Coding test 3 questions in 60 minutes. 2. Take home assignment in 1 week.
      Répondre à cette question

      Autres retours d’entretien d’embauche pour un poste comme Backend Engineer chez Autify

      Entretien pour Backend Engineer

      9 nov. 2024
      Candidat à l'entretien anonyme
      Tokyo
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Autify (Tokyo)

      Entretien

      1. HR Interview - Relatively easy process, as they explain about the company and want to understand your motivations for joining their company. 2. Programming Assignment - They ask me to design a website fetcher script that runs on command-line, without using any built-in tools like wget or curl etc... - I designed it using JavaScript, the script downloads the html, css, jpg, icon assets of the webpage in order to be able to load offline. - There was small request to add the --metadata option, which when present, it would allow to print the metadata information to the url site you are checking. - They requested to make a github repository and submit the link to them 3. Technical Interview - 2 Engineers performed my interview. - Initially they asked me questions related to my skills, which I explained without any issues - Then a whiteboard system design questioning was performed by another engineer, which I designed a reasonably good system based on the contraints provided. - I did not appreciate the 2nd engineer constantly pretending like he doesn't understand what I'm saying, I don't know if he's english was the problem or just was in a bad mood.

      Questions d'entretien [1]

      Question 1

      Overview We want to build a web application where users can type in a web address, and store the current value offline. Think about web archive as an example. For example: I would type in https://www.google.com and hit "Save". Your application would scrape the website and sabe it so the user could then download the files, and access it on their local machine. Please use the whiteboard to draw & explain your answers Setup - Draw an infrastructure diagram of what you would want the production infrastructure setup to look like - How would a user's request travel through your system? Questions - How would you save costs & scale the system if the usage changed throughout the day? - If you were to scale up to 10000 users a day where would the performance & scalability bottlenecks be? - What would you do to fix this? - How about 1 mil users? - What do you see as the disadvantages and advantages of your proposed architecture? - What would you put in place for disaster recovery?
      Répondre à cette question
      1