Interview consisted of five parts: 1: To get to interview you had to pass a Codility challenge. The coding challenge consisted of two tasks: 1. Find an error in a piece of code and fix it by changing just two lines of code. 2. Write a program which does X. There are other Codility challenges on the web which can give you practice doing coding challenges. One thing I would stress is that the company is focused on the accuracy of your solution and not its efficiency. Another good website for preparing for coding challenges is Codewars. If you pass the interview you will be invited for an interview, they like to call it an assessment centre. The interview is four parts, the order of which you do each of these parts can vary: 1) Whiteboard challenge. You will be asked to diagram the architecture of a web application based on a brief. You will given thirty minutes total to do this. Ten minutes to diagram it and a further twenty minutes to explain your reasoning. For me this was the hardest part of the interview. I wish they had have gave more insight going into it what they expected, maybe some samples or practice exercises to get you prepared for the interview. 2) A group exercise: You are given a simple exercise to test how you work as a group. In our case we had to work as a team to select and justify which items we would take to help us survive on a desert island. 3) Another group exercise this time it involved finding errors in a piece of code. You are given thirty minutes, approx ten minutes to discover errors in a short program written in Java. There are lots of obvious errors, and they do give you an indication of what type of program it will be. In our case it was a Fizz, buzz, woof program. My advice would be to make sure you are heard. The interviewer asked us who would like to go first, I spoke up, and a fraction of a second later, another member of my group did. Out of politeness I let them speak first, only for them to proceed to identify most of the key errors, then another person spoke and identified the majority of the rest, by the time the third person had offered their opinion almost all the errors were identified. It's a tricky one to balance, you don't want to be seen to be too forceful or aggressive, but if you are too meek, your voice won't be heard. 4) An actual interview. Typical job interview questions asking you to tell you about a time you did X

After applying for the role, I waited about one month before receiving an invitation to do a Codility programming question. I completed both questions, however one was not an optimal solution. I was then rejected without receiving any feedback.