J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Checkout.com (Londres, Angleterre) en déc. 2021
Entretien
- Started with an HR call to talk about the position, product and the company.
- Moved then to a call with the responsible manager.
- Interview with two team members to have my technical skills assessed.
- After that a code challenge to be delivered up to a week.
- Another call with the role manager and team members that proposed a software architecture/design challenge
- A final call with the HR recruiter to check soft skills.
The whole process took a month and a half due to the end of year holidays, but it was challenging and fun. All question made sense and the interviewers were fair and helpful along the journey.
* Each step described above requires the candidate to receive a good feedback by its interviewer before moving to the next stage.
Questions d'entretien [1]
Question 1
General questions about:
- Decision making;
- Software Architecture;
- Software Engineering;
- Programming Language specifics;
- Personal goals, achievements, challenges;
- Mentoring skills;
J'ai postulé via un recruteur. J'ai passé un entretien chez Checkout.com (Tallinn) en févr. 2026
Entretien
The best interview process that I had so far . Starts with a survey after the recruiter screening which is very detailed for the candidates to align with the company culture, with a clear feedback on the end. The challenge at home with a task that makes sense for the domain of the company was the next one, followed by a live explanation of the project I liked much more than the traditional pair programming rounds, as it removes a bit the pressure of live coding which eventually brings problems totally disconnected of the position that we are applying and gives you the time to discuss your solution with the interviewers afterwards. The final stages, system design and values interview in person are much more enjoyable and feels more like a workday at the office with a colleagues than live interviewers made on-line.
Up until the system design it was really friendly. Then it became the most embarrassing interview I’ve ever had.
The guy visually facepalmed and laughed if I said something he didn’t like. Asking a lot of trick questions and said hashing the API Key when storing in the database doesn’t make any sense. 😆
Questions d'entretien [1]
Question 1
Why would you hash an API key when storing in the DB?
J'ai postulé via un recruteur. J'ai passé un entretien chez Checkout.com (Londres, Angleterre) en août 2025
Entretien
I had a first-round interview with talent acquisition, followed by a take-home test, and finally an in-person interview focused on system design.
During all three steps, I received positive feedback. However, after a call from the HR team informing me that I had successfully passed all the steps, they suddenly told me I was not successful due to some gaps in system design and the coding challenge from the second-round interview. This felt quite strange; it seemed like they didn't know what they were doing.
It is possible to successfully pass all interview stages and still not progress with your application, which I find unprofessional.
Questions d'entretien [1]
Question 1
Design a system that processes payments and communicates with two third-party providers, such as a bank and an inventory system.