Glassdoor users rated their interview experience at ZenRows as 20% positive with a difficulty rating score of 2.4 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Technical Writer and Fullstack Engineer rated their interviews as the hardest, whereas interviews for Software Engineer and Marketing Manager roles were rated as the easiest.
The hiring process at ZenRows takes an average of 30 days when considering 5 user submitted interviews across all job titles. To compare, the average duration of hiring at similar companies like BlackRock, Inc. is 14 days, Fabricated Software, Inc. is 2 days, and Apple Inc. is 21 days. Candidates applying for Technical Writer had the quickest hiring process (on average 30 days), whereas Technical Writer roles had the slowest hiring process (on average 30 days).
I applied through a recruiter. I interviewed at ZenRows (Madrid) in Nov 2025
Interview
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!
Interview questions [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!
I applied through an employee referral. The process took 3 weeks. I interviewed at ZenRows (Barcelona) in Aug 2025
Interview
The interviews felt very natural, super engaging and laid back in the best way. It was refreshing to have such nice, smooth conversations and it gave me a clear sense of ZenRows’ culture and values.
I felt there was a great balance between learning more about the role and having the space to share my own perspective.
Interview questions [1]
Question 1
How do you bring structure to your role whilst working for a start up with no clear structure for day-to-day activities
I applied through a recruiter. The process took 3 weeks. I interviewed at ZenRows (Madrid) in Aug 2025
Interview
The interview process consisted of 4 interviews. The first with their Talent Team the typical "get-to-know" you stuff. Followed by a more in-depth discussion with one of the hiring managers in my case the first interview was with a fellow AE and the following with the COO. Both were deeper discussions about how my experience and skills fit the role etc. The conversation with COO was more high-level regarding sales processes etc.
Then, the final interview was with the CEO - a genuine conversation regarding company culture, vision, values and long-term alignment. Don't even try to prepare for the last one, just go with the flow and don't BS your way through it, he can tell.
Interview questions [1]
Question 1
If your team had to describe you or you were the "go-to" person for something what would it be.
Tell me something that frustrates you.