Build backend systems on the critical path of every Affirm Card transaction

Affirm is hiring a Software Engineer II for its Card Management & Transaction Processing team, which owns the issuing/processing infrastructure behind authorization, transaction processing, and card lifecycle management for the fast-growing Affirm Card. The role wants 1.5+ years of backend experience in Python or Kotlin, comfort with AWS/MySQL/Kubernetes-style distributed systems building blocks, and strong ownership of code quality and on-call operations, fully remote from Canada.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Backend system design in Python or Kotlin
Distributed systems fundamentals: AWS, MySQL, Kubernetes
Correctness in transaction systems (idempotency, concurrency, failure handling)
Breaking ambiguous business problems into phased engineering delivery
Operational ownership: metrics, on-call, 'keep the lights on'
Code review practices and growth/feedback orientation

Common question themes

Design a backend service you built that spanned multiple components, and the tradeoffs you made

How would you ensure a payment/transaction isn't processed twice under retry or failure

Debugging a production issue in a system built on AWS/MySQL/Kubernetes

Breaking a vague business requirement into a phased engineering plan

A time you gave or received difficult feedback in a code review

Feedback that changed how you approach your own growth as an engineer

How candidates describe it

Real Software Engineer II interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Affirm Software Engineer interviews

All Affirm interviews