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

      Cloudbeds

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Cloudbeds | Offres d’emploi chez Cloudbeds | Salaires chez Cloudbeds | Avantages sociaux chez Cloudbeds
      Entretiens chez CloudbedsEntretiens d’embauche pour Frontend Engineer chez CloudbedsEntretien chez Cloudbeds


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

      5 févr. 2020
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Cloudbeds en nov. 2019

      Entretien

      The interview process has a lot of steps and I'm not so sure it accurately assesses candidates at all. The first step is a standard recruiter phone screening. The recruiter was nice and seemed to want people to succeed. Next is the coding test (Codility). The coding test actually was not bad. It tested Vue and JavaScript validation, which are real-world examples. After that is a one-way video interview. It is awkward and catches you off guard. I expected it to be behavioral questions, instead, it was JavaScript trivia such as defining reactive programming, what are the benefits of TypeScript, or describing the Flux architecture pattern. Basically anything from the job's posting's "You’ll Succeed With" AND "Nice to Haves" was asked in this one-way interview. If you pass that, you move onto three separate video interviews. I interviewed with a developer, manager, and VP of engineering. The first two were from Ukraine, so it had to be scheduled early in the morning for US candidates. The developer was focused on a lot on the "Nice to Haves" section of the job posting and JavaScript trivia (hoisting). The manager was more focused on agile scrum, teamwork. He tried really hard to get me to bad mouth my current employer, asking about bad things up to 4 times. The VP of engineering rapid fires questions about work history, technology, and teamwork. The way the emails made it seem, you "advance" to the next stage for the next interview, but I'm pretty sure the three interviews are treated as a group. It gives you hope when you "advance" to the final round, only to later receive that rejection letter. This interview process is a large time and effort to invest. It can seem like things are going okay. I feel that the interview processes didn't reveal the type of person they were looking for. Are they looking for developers with experience building software or developers that can define and answer questions on JavaScript trivia and know all of the libraries? After interviewing, I didn't get a sense if I would like or dislike working there, it was all kind of neutral. I suppose it is okay that they ended up rejecting me, but still disappointing due to the time put into this whole process.

      Questions d'entretien [1]

      Question 1

      What testing methods and libraries do you know?
      Répondre à cette question
      3