Great place to work. Fast-paced and fantastic engineering standards
Great place to work. Fast-paced and fantastic engineering standards
Emphasis on maintaining code, removing legacy, and keeping up to date.
Great standard of engineering, shared libraries, and collaboration.
Mandatory 2 days in the office per week.
Remove mandatory in-person office days to allow flexibility for employees.
Additional Ratings
Was this helpful?
Checkout.com Interview Experiences
Software Engineer II
The interview process was very unique. It wasn't like asking just one random LeetCode question, resulting in a binary fail/pass situation based on that single question, which happens at many other companies. Here, it started with an online assessmen
Software Engineer II
Here's the process: * Recruiter screen * Take-home task * 1-hour interview with engineers * 1-hour interview with engineering managers * 30-minute interview with in-house recruiter on culture fit I had plenty of time to ask the questions I needed.
Software Engineer II
The first round was a screening by a recruiter, who was helpful and nice. After that, I was sent a HackerRank challenge. It was mostly related to microservices architecture and problem-solving. The next step was a technical interview, where we disc
Software Engineer II
United KingdomAugust 5, 2022The interview process was very unique. It wasn't like asking just one random LeetCode question, resulting in a binary fail/pass situation based on that single question, which happens at many other companies. Here, it started with an online assessmen
Software Engineer II
United StatesMay 1, 2022Here's the process: * Recruiter screen * Take-home task * 1-hour interview with engineers * 1-hour interview with engineering managers * 30-minute interview with in-house recruiter on culture fit I had plenty of time to ask the questions I needed.
Software Engineer II
Tallinn, EstoniaOctober 1, 2021The first round was a screening by a recruiter, who was helpful and nice. After that, I was sent a HackerRank challenge. It was mostly related to microservices architecture and problem-solving. The next step was a technical interview, where we disc
