We try and make our interview process as smooth as possible for our candidates and provide useful feedback, but on this occasion, we’ve fallen short, and we can only offer our sincere apologies for your experience. To explain a little further about our interview process, our initial technical tests are meant to pose a simple problem. What we are keen to discover is how candidates approach their work. We look for unnecessary complexity, evidence of TDD in the commit history, cleanliness of code and so on. It never ceases to surprise us the number of ways that people approach and solve these simple problems, and we feel they offer us valuable insight into our candidates. Face to face interviews seek to carry on this process of discovery about how candidates approach problems, and how deeply they understand and care about the things we believe in as a software development organisation. As such we try and foster a conversation that will help us explore topics such as development practice, on what it means to be agile in software delivery, and what our candidates truly value when developing software. There are occasions where we will interview otherwise strong candidates, but who we end up not making offers to due to a difference in our values. We can only offer an apology in this instance that we did not adequately communicate our feedback