Applied online via CWJobs and Lucy at Elastic Recruitment (who was awesome through the whole process) The process took around a week from start from finish, it consisted of 3 stages: 1) Telephone call with Dan @ Dotfive - this was a very relaxed, non technical telephone call talking about the company, how they work and the sort of work they do. Dan was professional yet relaxed throughout the call. At the end of the call Dan explained the technical test, how it was created and explained the two parts of the test and what was expected. 2) Technical test - After completing the call, Lucy sent over the technical test which was a PDF consisting of 2 parts; a 25 questionnaire which covered a wide range of topics from PHP to MySQL. It was one of the most diverse question sets I have come across while interviewing, and it tested your experience in various subjects rather than your ability to read the PHP documentation which was great. Like the other reviewer on Glassdoor I also showed colleagues the test as I was impressed, and I received positive feedback from them all (they all particularly liked the describe yourself in JSON question!) The requirements for the code test were as follows: "Create an application which will allow at least two users to log in simultaneously and manage items in categories. The categories should be in a hierarchy of potentially infinite depth. The items only require a label. The users should be able to perform standard CRUD (including moving items and categories around in the hierarchy), plus if one user makes a change, the other user should see the change (if appropriate) without manually refreshing their page. Your solution should follow best practice and be robust and scalable." There was also a separate list of "Bonus points" which you could implement if you wished. It was advised that the test should take 2-3 hours (which has been around the same as all of the other technical tests I've been asked to do recently), but you could spend as long/ as little as you liked on the test. I spent around 4 hours on the test, which was over the span of a weekend. I fulfilled all of the requirements, and a couple of the "Bonus Points" in that time. 3) Technical Interview - This was a Slack screensharing call with Dan and a Senior Developer named Rhys. They were both very friendly and personable guys which kept the conversation casual while remaining on-topic. The call started by talking about my technical test, things I would have done differently if I had more time, and what things I wasn't happy with etc. After that the call progressed to some very "out-of-the-box" thought provoking questions asking you to explain (at a high level) how you would go about developing certain scenarios explained to you (one was about detecting collisions within a grid). The call then progressed on to some live coding. Dan and Rhys asked how I would implement a couple of new features into the test I produced for them, they weren't after perfect code, was more pseudo code seeing how you would approach the task and where you would put the logic etc. The call was very relaxed, we had a laugh, we got on well and the whole experience was very enjoyable from start to finish. ----------------------------------------------------------------------------- Shortly after the call Lucy got in touch saying that Dotfive would like to make me an offer. I won't go into details of the offer but I will say it was above the market average for remote roles. From start to finish, it was one of the most enjoyable interview processes I have experienced in 13 years, and I think a lot of development companies would benefit a lot from adopting a similar approach. The end result was, I was very happy with the offer, the company and the people. However, due to a sudden change in personal circumstances I decided to abort my job hunt completely. That said, as soon as I sort out my personal life - the first thing I do will be to get back in touch with Dotfive!