The interview process wasn't bad, but it was very long. I applied for the role in February 2025, and there was an interval of about two weeks between each round. Consequently, my final interview took place at the beginning of May.
The process included:
Everything went well until the final behavioral interview. During that conversation, the manager mentioned that promotions are not available to individuals but only to the team as a whole. This was a huge red flag for me, especially since it was framed within a “team-as-family” narrative.
After that interview, I never received any further communication or notification from the company. While it wasn't a loss for me personally, it does highlight their overall approach to the interview process and communication.
The first two rounds focused on questions about my professional background and previous work experience.
Technical Round: This round included two SQL tasks, which I’d describe as medium-to-hard level, similar to those found on HackerRank.
Technical Round (System Design): I was given a near real-life scenario and asked to design a data pipeline based on it.
Behavioral Interview: This interview consisted of questions about my day-to-day work preferences, team communication, and what I consider most important in my role.
The following metrics were computed from 2 interview experiences for the Checkout.com Data Analytics Engineer role in London, United Kingdom.
Checkout.com's interview process for their Data Analytics Engineer roles in London, the United Kingdom is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having mixed feelings for Checkout.com's Data Analytics Engineer interview process in London, United Kingdom.