Checkout.com interview, and the gateway you'll build.

Checkout.com's candidate pack lists four stages: the application and a recruiter screen, a first-round interview, a task or challenge, and a final interview. It says the task can come before the interview, or be skipped, for some roles, and that every candidate is measured against the same criteria. Its jobs page says all technical interviews involve a take-home task, while the GitHub challenge offers live pairing as well, so ask your recruiter which applies to you. The rounds below add what candidates report.

The challenge is a small payment gateway: an API that accepts a card payment from a merchant, validates it, forwards it to a simulated acquiring bank and returns the result, plus an endpoint that returns a past payment's details. Checkout.com publishes the requirements, starter code in four languages and the bank simulator, so you can prepare on the real task. What it asks for is plain: code that compiles, automated tests, and a simple design without over-engineering.

• Choose live or take-home on purpose: Live pairing tests how you think aloud with a senior engineer; the take-home tests your code and how you defend it in the review. If you go quiet when you code, take it home. Either way, you tell the talent team your choice in advance.
• Run the simulator before the day: Cards ending in an odd digit are authorised, even digits are declined, and a zero returns 503 Service Unavailable. Know these by heart and test each path, including a missing field, which the simulator answers with 400.
• Make Rejected its own path: An invalid request never reaches the bank and returns Rejected. Validate first, return every failure clearly, and keep that logic separate from the call to the bank so it is easy to test.
• Never return the full card number: The README calls it a serious compliance risk: responses carry the last four digits only. Store and log nothing you would not want to show a reviewer.
• Decide what a 503 means for the merchant: The simulator fails on purpose. Choose what the merchant receives when the bank is down and be ready to explain why. A candidate reported a design question on exactly this: resilience when calling external services.
• Write the tests, keep the design small: Checkout.com asks for automated tests and says it does not want to encourage over-engineering. A handful of tests on validation, each simulator outcome and retrieval beats a layered architecture.
• Write down your assumptions: For the take-home, the README asks you to document your key design decisions and assumptions. Note the ones a reviewer will ask about: the payment ID format, money in minor units, which three currencies, and what you left out.
• Prepare the next step: Our suggestion: in the review, expect to be asked how the design changes for duplicate requests, refunds or real storage. Have one sentence ready for each.

The README gives no time limit for the take-home and one candidate reported five to six hours, so ask your recruiter how long you have. Front-end, mobile and AI candidates get different challenges in the same GitHub organisation.

Checkout.com publishes three values on its careers page and twelve operating principles on its Life at Checkout page. Its candidate pack also says how to answer: lead with the most important thing, include success metrics, and say what you achieved as part of a team.

• Aspire: big dreams and a long-term focus
• Excel: pushing yourself and each other to do your best work
• Unite: coming together as one team
• The operating principles, among them Customer First, Run Lean, Better Every Day, Never Give Up, Be The Owner, No Room For Approximation, Pace Matters, Talk Straight and One Team
• In answers: the most important thing first, success metrics, and your part in the team's result

Candidates report few exact behavioural questions. The ones below follow what Checkout.com says it measures, its three values and the answer advice in its candidate pack; the technical themes come from the published challenge and candidate reports.

Your Checkout.com interview

Don’t walk into Checkout.com hoping. Walk in rehearsed.

Reading about the loop is the easy part. Calibrd predicts the questions Checkout.com is likely to ask for your role, interviews you out loud, and tells you what a hiring manager would hear, before the real one does.

Built by Xiaochen Guo, 500+ interviews on the hiring side

 Search pass · 90 days · no subscription3 months for the price of 2

• Unlimited graded answers, reports and tailored CVs
• 45 mock interviews · about 7 full loops
• 6 questions answered by Xiaochen himself

Unlimited graded answers · 45 mock interviews · 6 questions to Xiaochen

Or start free: predict my Checkout.com questions →Compare all passes

The US ranges are from Checkout.com's own job ads, read on 31 October 2026. Its UK and Paris engineering ads publish no pay, so the UK row is the median total pay that engineers report to Levels.fyi (page updated 19 October 2026), not a figure from Checkout.com.

Applying to Checkout.com? Paste the posting and see whether they’d shortlist you →

1. Read the payment gateway README end to end and run the bank simulator before your interview.
2. Choose live pairing or the take-home by how you work best, and tell the talent team early.
3. For the live version, have your IDE, language and dependencies ready, as Checkout.com asks.
4. Build the gateway once on your own, with tests, in the language you will use.
5. Prepare to explain one design decision and one thing you left out on purpose.
6. Prepare a payments design: the authorisation flow, timeouts and retries to the bank, duplicate requests, and how card data is stored.
7. Write one story for each value, Aspire, Excel and Unite, each with a number and your part in the team's result.
8. Lead every answer with the result, as Checkout.com's candidate pack advises.
9. Paris roles: check the ad's French requirement; the Senior Software Engineer I ads ask for B2 or better.
10. Apply for no more than three roles at a time.

This guide covers Checkout.com's engineering hiring, mainly backend, with the front-end, mobile, AI and data variants it publishes or candidates report. It does not cover sales or account management interviews. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Monzo, Tabby or N26? Their guides follow the same format, from the first screen to the offer.

• 01Checkout.com, cko-recruitment on GitHubthe payment gateway challenge (README last updated 17 September 2025; .NET, Go, Java and Python starters February 2025), the React payment list (October 2025), the mobile payout app (June 2026) and the Fraud Success Manager assistant (March 2026)
• 02Checkout.com Engineering Assessment (README)the live and take-home variants, the requirements, the bank simulator's rules and what reviewers expect (read 31 October 2026)
• 03Checkout.com, Jobsfour to six weeks from application to offer, written feedback after the recruiter screen, no more than three applications, take-home tasks in technical interviews, office days Tuesday to Thursday (no date shown; read 31 October 2026)
• 04Checkout.com, Our hiring process FAQs (candidate pack)the four stages, the task that can move or be skipped, the same criteria for everyone, and the answer advice (undated; the file name says 2022; read 31 October 2026)
• 05Checkout.com, Careersthe three values, Aspire, Excel and Unite (no date shown; read 31 October 2026)
• 06Checkout.com, Life at Checkoutthe twelve operating principles (no date shown; read 31 October 2026)
• 07Checkout.com job board169 open roles by location and the US pay ranges, read 31 October 2026
• 08Checkout.com, Senior Software Engineer I, ParisFrench at B2 level or better (posted 23 October 2026)
• 09Checkout.com, Solutions Engineer, Payments, New Yorkthe $154K–$200K range (posted 30 October 2026)
• 10Taro, Checkout.com Senior Software Engineer I, UK (2 March 2025)the technical screen, a five-to-six-hour take-home with a live discussion, the payment gateway design and resilience question, the behavioural round
• 11Taro, Checkout.com Data Analytics Engineer, London (1 May 2025)the SQL tasks, the pipeline design and a process of more than three months
• 12Glassdoor, Checkout.com interview, London (March 2026)an engineering manager call, the task, systems design and an engineering director interview
• 13Glassdoor, Checkout.com interview, Tallinn (February 2026)a domain take-home with a live explanation, then system design and values interviews in person
• 14Levels.fyi, Checkout.com software engineerself-reported UK pay; Senior Software Engineer I median total £98,156 (updated 19 October 2026)

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.