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

      WorkFlex

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur WorkFlex | Offres d’emploi chez WorkFlex | Salaires chez WorkFlex | Avantages sociaux chez WorkFlex
      Entretiens chez WorkFlexEntretiens d’embauche pour Senior Software Engineer chez WorkFlexEntretien chez WorkFlex


      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 Senior Software Engineer

      20 mars 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez WorkFlex en févr. 2026

      Entretien

      Applied for a remote full-stack engineering role. The process started with a timed 2.5-hour coding challenge (Java Spring Boot + Angular), submitted via private GitHub repository. Received detailed written feedback from the engineering team on both backend and frontend — feedback was specific, constructive, and positive overall. Was then invited to a recruiter screening call. During the call, the recruiter discussed specific contract details: named the EOR partner for my country, confirmed the annual salary, explained the benefits package including equity and a monthly wellbeing budget, described the onboarding process, and outlined the next interview rounds. The tone was clearly "closing" — as if I was already moving forward. The recruiter said she would confirm the next interview date the following day. The next afternoon — less than 24 hours after discussing compensation, contract structure, and onboarding timelines — I received a one-paragraph rejection email referencing other candidates with stronger English skills. No follow-up call, no second interview, just a template. The gap between what was communicated during the screening and what arrived the next day was significant. A word of caution for candidates based in countries where the company has no legal presence: the cost of hiring through a third-party employer service may work against you behind the scenes, even if your technical performance is strong. Nobody will flag this during the process — you will simply receive a generic rejection with a different reason. To the hiring team: if contract terms, salary, and onboarding details are shared with a candidate during a screening call, that candidate will reasonably assume they are progressing. Either align internally before making those commitments, or stop making them.

      Questions d'entretien [1]

      Question 1

      Timed take-home coding challenge: build a full-stack workation management application in 2.5 hours using Java, Spring Boot, Angular, and SQL. Submitted via private GitHub repo. Evaluated on completeness, architecture, code quality, and testing.
      1 réponse