This was probably by far the worst interviewing experience I've ever had, and judging from their other Glassdoor reviews, it seems to be a cultural problem they have.
A recruiter contacted me to ask whether I would be interested in a position at Checkout.com. We scheduled an initial call, and on the day of the call... nothing. About twenty minutes later, I managed to find his work phone number and sent him a quick text message asking if the call got canceled. He then showed up, half an hour late.
He asked three or four very easy questions, all of which I answered. I distinctly remember him asking me why someone would use an interface instead of an abstract class. I answered that it depends on the programming language, but that an interface represents a contract that each class implementing it has to follow. I also mentioned that an example of using one would be if your team has to assume the existence of an object but is not responsible for implementing it. He answered that that's wrong and that the answer sheet he was provided with states that "it's used because multiple inheritances are not allowed in abstract classes," never mind that the majority of languages except C# do allow this.
Anyway, they gave me a take-home problem which was fairly easy to implement. Above all, they seemed to value documentation and the dependency injection pattern. I handed in my solution and was invited for the next round, with the negative point mentioned that I should have used dependency injection – so make sure you use it, and you should be fine, lol.
The actual last stage interview was very easy. One of the questions was why I was applying for the associate position given I had 1.5 years of experience. I answered that I wasn't considered an associate at my current job and asked whether I could be considered for the mid-level position since he was mentioning it.
The rejection email basically had two negative points: my salary expectations were unrealistic, and I would probably be difficult to manage since I asked for the mid-level position last minute. Never mind that he mentioned the mid-level position, and all I said about salary was my current salary, which was in the range provided here on Glassdoor. It can't be too unrealistic if I'm actually getting paid that much, huh?
Overall, it seems they have some serious cultural problems, which can also be seen from the other Glassdoor reviews. If you look past their fake reviews, that is.
Built a payment gateway system.
The following metrics were computed from 33 interview experiences for the Checkout.com Software Engineer role in United Kingdom.
Checkout.com's interview process for their Software Engineer roles in the United Kingdom is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having good feelings for Checkout.com's Software Engineer interview process in United Kingdom.