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

      ZenRows

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur ZenRows | Offres d’emploi chez ZenRows | Salaires chez ZenRows | Avantages sociaux chez ZenRows
      Entretiens chez ZenRowsEntretiens d’embauche pour Fullstack Engineer chez ZenRowsEntretien chez ZenRows


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

      5 nov. 2025
      Candidat à l'entretien anonyme
      Madrid
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez ZenRows (Madrid) en nov. 2025

      Entretien

      1. HR filter talk (45min) 2. Talk with the CTO (1h), technical questions, typical stuff 3. Technicall challenge. You can find it if you search for zenrows-technical-assessment in github, I made it public. This technicall challenge requires a pixel perfect design based on a Figma After the technicall challenge, you get an email feedback with: "lack of documentation and automated database setup, which made it difficult to run your project and led to several errors. The UI, though responsive, did not match the Figma design closely, and the backend was simplified to the point of relying only on basic models and Laravel/ORM features. However: 1. it was clearly stated to "Focus on delivering a clear, maintainable MVP" 2. there's a README that indicates how to spin up everything and seed the DB. The task tells you to use docker lol (if the don't know how to do it.. I wouldn't be surprised) I had a decision log markdown file indicating the reasons of why some steps were made, one of them was not focusing on the pixel perfect side (although it was 95% identical) because it was a waste of time for an exercise that was quite long already. "Backend was simplified to the point of relying only on basic models and Laravel/ORM features.", that's literally a good thing. What do you want me to do? Over engineer it? The exercise stated it to KISS!

      Questions d'entretien [1]

      Question 1

      The gave me feedback that my solution was: "lack of documentation and automated database setup, which made it difficult to run your project and led to several errors. The UI, though responsive, did not match the Figma design closely, and the backend was simplified to the point of relying only on basic models and Laravel/ORM features. However: 1. it was clearly stated to "Focus on delivering a clear, maintainable MVP" 2. there's a README that indicates how to spin up everything and seed the DB. The task tells you to use docker lol (if the don't know how to do it.. I wouldn't be surprised) I had a decision log markdown file indicating the reasons of why some steps were made, one of them was not focusing on the pixel perfect side (although it was 95% identical) because it was a waste of time for an exercise that was quite long already. "Backend was simplified to the point of relying only on basic models and Laravel/ORM features.", that's literally a good thing. What do you want me to do? Over engineer it? The exercise stated it to KISS!
      Répondre à cette question
      1

      Meilleures entreprises pour « Rémunération et avantages » près de chez vous

      avatar
      Cisco
      4.0★Rémunération et avantages
      avatar
      SAP
      3.9★Rémunération et avantages
      avatar
      Capgemini
      3.7★Rémunération et avantages
      avatar
      Salesforce
      4.4★Rémunération et avantages