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

      Find.co

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Find.co | Offres d’emploi chez Find.co | Salaires chez Find.co | Avantages sociaux chez Find.co
      Entretiens chez Find.coEntretiens d’embauche pour Lead Engineer chez Find.coEntretien chez Find.co


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

      4 déc. 2025
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Find.co en déc. 2025

      Entretien

      The interview process started off well. The conversations with the business and product teams were normal, clear, and professional. They explained their goals, the challenges ahead, and what they expected from the role. The behavior and leadership tests were excelent. At that stage, everything felt straightforward and aligned with a healthy hiring process. The shift came during the technical interview. The technical lead immediately created an uncomfortable and unproductive dynamic. Instead of having a real discussion about approaches, trade-offs, or system design, he treated the conversation as a test of whether I could guess the one answer he personally believed was correct. Every solution I presented (including methods used successfully by large, mature companies) was rejected without any technical reasoning. It wasn’t an evaluation of engineering thinking, it was an ego exercise. When I asked him directly what he thought was wrong with the alternatives, he couldn’t explain it. There was no technical depth behind the pushback, only stubbornness. It became clear that the behaviour wasn’t about standards or quality but about needing to “win” the discussion. What made the situation even more striking was the salary range they are offering for this role. They are paying top-tier money for problems that are actually simple and widely solved in the industry. The mismatch suggests that the company’s engineering leadership has likely paralysed their growth. If basic issues require high-cost hiring just to move forward, it points to deeper problems in decision-making, architecture, and technical direction. From this interview alone, it was obvious that the engineering leadership is not competent and is significantly overvalued inside the company. While the business and product teams seemed reasonable, the technical interaction revealed a culture where ego outweighs skill, collaboration, and real problem-solving. I wanted to give it a try and not pay attention to the glassdoor reviews, but after this experience I am not shocked with the public feedback.

      Questions d'entretien [1]

      Question 1

      They asked how to scale their central WordPress installation so it can handle heavy, but legitimate, traffic while reliably pushing data to several localized WordPress sites. They described the API as behaving like it’s under constant strain, almost as if it’s being abused, and said that none of the usual solutions caching, CDN usage, or replication, has improved stability.
      Répondre à cette question