Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      WorkFlex

      ¿Esta es tu empresa?

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de WorkFlex | Empleos en WorkFlex | Sueldos en WorkFlex | Prestaciones en WorkFlex
      Entrevistas en WorkFlexEntrevistas para el cargo de Senior Software Engineer en WorkFlexEntrevista en WorkFlex


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Senior Software Engineer

      20 de mar de 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé en línea. Acudí a una entrevista en WorkFlex en feb 2026

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 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 respuesta