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

      Elliptic

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Elliptic | Offres d’emploi chez Elliptic | Salaires chez Elliptic | Avantages sociaux chez Elliptic
      Entretiens chez EllipticEntretiens d’embauche pour Full Stack Engineer chez EllipticEntretien chez Elliptic


      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 Full Stack Engineer

      17 mai 2026
      Candidat à l'entretien anonyme
      Londres, Angleterre
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Elliptic (Londres, Angleterre) en avr. 2026

      Entretien

      The interview process consisted of five stages. The first stage was an initial conversation with HR, where they explained the role and asked about my motivation, background, and general fit. The second stage was with the hiring manager. This was also fairly conversational and focused on my technical background, the technologies I had used, and how my experience matched the role. The third stage was a take-home coding test, which was expected to be completed within one hour. In my opinion, the time limit was quite unrealistic, and it would be very difficult to complete properly without using AI assistance. The fourth stage was a technical test review with a senior engineer and a junior engineer. This focused on discussing my solution, implementation choices, and the reasoning behind the code. The final stage was a system design interview, based on how the take-home test solution could be developed into a more production-ready system. I was rejected after the final stage, but the feedback I received was disappointing and unclear. I was told that my technical skills were excellent and that the technical parts of the process had gone very well, but the reason given for rejection was that I had not asked enough questions during the system design discussion. I did not feel this accurately reflected the interview. I asked relevant questions, and I had already been properly briefed on the task beforehand, so I understood the context and requirements. During the interview, I explained the design in detail, covered synchronous versus asynchronous processing, discussed database design, scalability, reliability, observability, error handling, and drew diagrams to support the explanation. I followed up with both HR and the hiring manager to better understand the decision, but I did not receive a clear answer. For me, the final feedback felt vague and disconnected from the actual interview performance. Overall, the process was technically detailed, but the final decision and feedback did not feel transparent.

      Questions d'entretien [1]

      Question 1

      They asked a system design question based on my take-home coding test: how I would take the solution and make it production-ready. This involved a whiteboard-style design discussion where I had to explain the architecture, scalability considerations, reliability, observability, error handling, testing strategy, and how the system could evolve beyond the initial coding test implementation.
      1 réponse
      1