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

      Geckoboard

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Geckoboard | Offres d’emploi chez Geckoboard | Salaires chez Geckoboard | Avantages sociaux chez Geckoboard
      Entretiens chez GeckoboardEntretiens d’embauche pour Front End Engineer chez GeckoboardEntretien chez Geckoboard


      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. Indeed, Inc. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Indeed, Inc.

      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 Front End Engineer

      16 avr. 2019
      Employé (anonyme)
      Londres, Angleterre

      Autres retours d’entretien d’embauche pour un poste comme Front End Engineer chez Geckoboard

      Entretien pour Front End Engineer

      7 nov. 2016
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via une autre source. J'ai passé un entretien chez Geckoboard (Londres, Angleterre)

      Entretien

      The first step was a phone interview, which was fairly casual and involved questions about the way I work and the reasons I was interested in the role. This was followed by a face-to-face interview in the office, split into two parts: a technical interview and a more general interview. The technical interview involved talking through a project I'd recently worked on and then a short coding exercise. In the second part, I was asked about my previous experience and future goals, and got to talk about the product, the way teams work, learning and development, etc. The interview was fairly relaxed and felt more like a conversation than a test, giving me a chance to learn more about the company and role I was applying for. Overall, the application process was very positive and welcoming, and was definitely a lot less stressful and pressured than interviews I've had in the past.

      Questions d'entretien [1]

      Question 1

      What do you think of the product?
      Répondre à cette question
      2

      Candidature

      J'ai postulé via une agence de recrutement. J'ai passé un entretien chez Geckoboard

      Entretien

      First steps were a phone interview where they asked basic concepts of JS and about previous work experience. It was mostly a "get to know you" conversation with some easy tech questions at the end. Then was a coding task. I am not usually a fan of these considering the amount of time they take and because I don't feel they give good insight into the candidate's skill or knowledge. You are basically looking at someone's code in a silo with zero context other then the problem assigned. But, it looked simple enough so I completed it anyways. I completed the challenge and then was told they would not continue the interview process, but without any reason. They gave virtually no feedback from my submission which frustrated me because they expect you to spend up to 4 hours on the coding task, yet will not give the professional courtesy of constructive feedback afterward. I had no opportunity to explain my choices and have no idea what they liked or did not like from the assignment. Overall it was a very frustrating interview process for me. I spent a good amount of time on a very vague coding challenge and didn't receive the professional courtesy of constructive feedback for the time I put into my submission.

      Questions d'entretien [1]

      Question 1

      - explain closures in JS - create a meter UI component using any tech you'd like.
      Répondre à cette question
      3
      avatar
      Réponse de Geckoboard
      7y
      While this was a while ago it's nevertheless disappointing to read and I'm sorry you didn't receive feedback following your task. We have a strong culture of feedback and intentionally make sure to provide constructive feedback to all candidates who complete a task with us and feedback at every stage of the process. Unfortunately, when partnering with agencies we're not always in control of what feedback is passed along, but, we are mindful of this when choosing which agencies we work with and have stopped working with agencies for this reason, too. As an aside to this, I wanted to also share that the tasks we ask candidates to complete, is actually used again in the final round where we complete a pair programming exercise together. We recognise that interviews can feel artificial and being familiar with the piece of code (i.e. code you've written) we feel gives you the best chance to demonstrate your skills, how you work and equally gives you the best opportunity to get a feel for what it's like working with our team.