The process is similar to other tech companies:
I did not pass the take-home test because my coding style did not match the reviewer's. The test was relatively straightforward, although it took a while to complete. You are given about a week, but it can easily be done in a day or two.
However, given what was asked in the take-home test, it seems the reviewer did not pay much attention to it, to put it lightly. On the feedback regarding improvements or missing parts, there were clear tests that covered many cases, and the feedback stated these tests were very good. Then, the comment on the implementation mentioned that I missed checking a few things and could have avoided repetitive calls. If the reviewer had examined and understood the tests, they could clearly see all those cases were covered.
Rejecting candidates on a take-home test for minor issues like that, which can be improved very easily or changed without requiring upskilling, seems to be solely based on the reviewer's preference. That's how it appears.
All stages are conducted via phone or Zoom.
Take-home test to create an API
The following metrics were computed from 19 interview experiences for the Checkout.com Senior Software Engineer role in London, United Kingdom.
Checkout.com's interview process for their Senior Software Engineer roles in London, the United Kingdom is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having negative feelings for Checkout.com's Senior Software Engineer interview process in London, United Kingdom.