Get tailored insights about working at Yozu in one quick step.
Yozu interview questions
based on 4 ratings - Updated Jun 9, 2026
Averageinterview difficulty
Very negativeinterview experience
How others got an interview
67%
Staffing Agency
Staffing Agency
33%
Applied online
Applied online
Interview search
4 interviews
Yozu interviews FAQs
The hiring process at Yozu takes an average of 14 days when considering 1 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 Software Developer had the quickest hiring process (on average 14 days), whereas Software Developer roles had the slowest hiring process (on average 14 days).
I applied through a staffing agency. I interviewed at Yozu (Liverpool, England)
Interview
The process was going ok up until the on site visit. They offered to cover expenses to visit the office so spent my entire 09:00-17:00 on site but then ghosted me after. No response regarding my expenses.
Felt like an idiot that got scammed but my fault for not reading up on them and realising this is a pattern.
Interview questions [1]
Question 1
Do a technical challenge in a comfortable language
I applied online. The process took 2 weeks. I interviewed at Yozu
Interview
Initial video call to discuss experience and explain the role. 30 minutes.
Second technical interview carried out via video call. 1 hour.
Technical task in their office in Liverpool. Full day. (May as well have been remote as there wasn't a great deal of interaction throughout the day.)
After this full process zero feedback was provided other than they would not be progressing me any further in the process.
I have requested feedback several times and been completely ignored.
If you're wondering whether you should take a risk on investing so much time in this process. You shouldn't. There is no interest in making it worth your time.
There is also discussion amongst the developer community that they are repeatedly doing this to applicants.
An in person interview is valuable, but the way this company is running their process is exactly why people don't want to partake in them anymore.
I applied through a staffing agency. The process took 2 weeks. I interviewed at Yozu (Liverpool, England) in Oct 2022
Interview
An initial chat telephone interview followed by a slightly more in depth video interview with a technical guy who asked some good, sensible questions. 3rd stage is a full day evaluation at their city centre Liverpool offices, where you are to complete a technical task. The technical task is given in advance, and states that it is language / platform agnostic and you should use the platform you are most comfortable with. Despite being told my ruby on rails was very rusty in the interview, when I expressed that I would be completing the task using another platform I was more familiar with (PHP laravel) it was expressed that it would be to my disadvantage, they wanted it in rails. Irritated that I spent time heading into Liverpool to find that it wasn't what was expected and their advance information was misleading. Also slightly worried that despite describing themselves as 'remote first' the Liverpool office was very busy. It is an old fashioned large, open plan, rows of desks, noisy environment (they also had 2 dogs running around, whether that's a plus or minus is up to you!), and not what I expected from a business focused on software development ( but it could be that the office itself is more of a sales / admin focus ). The tech guy in the interview seemed like someone I would like to work with, but people should be warned, despite what you are told, they are looking for people focussed on rails, who can hit the ground running on rails. They are not looking to take on good brains and let them spend any time getting back up to speed.
Interview questions [1]
Question 1
Typical technical question, what is a polymorphic relationship?
Really sorry for any misunderstanding here - there was an assumption made on our behalf that given this specific role was for a Senior Rails Developer then the technical task was to be completed in Rails and the candidate would have that as their preferred framework, but we definitely should have made that clear in the task spec and have now altered the wording to reflect that.
As for the office being busy - that's because we ask anyone who's local if they're able and happy to, to come in and meet the candidate in person and have lunch with them. We like for you to meet a good selection of us so you get a better sense of the team you'd be working with and ensure we're the right team for you, as much as the other way around (we do also have candidates speak to members of the team working remotely on video calls throughout the day, too).
Apologies again for any miscommunication or misunderstanding on our behalf - obviously not how we want the team and tech day to go!
All the best.
Top companies for "Compensation and Benefits" near you