The first stage is a discussion with the manager, covering three main areas: solid coding principles, unit and integration testing, and cloud/DevOps.
This is more of a two-way discussion.
The second stage involves a pair programming task with a senior engineer, focusing on a basic ASP.NET Web API. You will be given the task to implement a new endpoint.
I failed this round but received no feedback on why. I justified all my decisions, wrote modular code with proper separation of concerns, and answered all questions asked. However, I did not complete the actual task due to time constraints.
My advice is that this is not a discussion or a pair programming session; spend as little time as possible discussing, as it wastes time. Your number one priority should be completing the task. I also advise completing the tasks before the interview so you can do them faster. This is not a two-way discussion; don't believe it if they say it is.
Your process in testing.
Your workflow on how you'd complete a new task.
Knowledge of SOLID principles.
How you do observability, logging, and monitoring on environments.
How you handle deployments.
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.