Hi there, Thanks for your feedback, we’re sorry to hear you were disappointed with the process. I’ve taken your feedback on board. We will work on making sure it’s clear from the outset that there are multiple stages to our recruitment process. The first interview as you correctly noted, is a non-technical interview, where you speak with a non-technical person as standard to see if there is a good fit with the company. This is very important to us culture-wise. We are a smallish company and we are currently hiring for just one iOS developer with the specific skill set that we need on the team. Employees at Teamwork are central to our culture and we spend a lot of time making it a great place to work. This is reflected in our hiring process where we have a non-technical interview at the outset, to avoid any frustration for our technical team - who want to code and not be caught up in first-round interviews. In this case our Head of Mobile reviewed your code immediately following submission and followed up directly with feedback on request. We appreciate the time that is invested in the process by all applicants. Yes we do expect a good standard of knowledge of the company, products, and for some roles, completion of a test before hiring someone, and this does take time. Though it may be hard to see from a different perspective, we do invest a lot of time from our side, in reviewing and discussing your application. With this role in particular, it’s necessary to use the coding test to gauge whether there is a good skill level match. The test works for us as it reflects the working style we need from someone at this level - the ability to take a brief spec and create something beautiful. We respect the time commitment you made and we’re sorry it didn’t work out this time around. Orla