Affirm

Large Enterprises

Most of these Affirm write-ups come from Software Engineers (25), then Data Scientists (4) and Product Managers (3). The most reported rounds are the technical phone screen (15), the hiring manager screen (5), the system design round (4) and the product sense round (3).

32 interview notes · updated Jul 2026

Affirm·Software Engineer·Technical Phone Screen

Jul 2026

Interviewed for a Data Engineer role at Affirm. Just one question from what I can tell, basically a structured self-intro prompt with a project highlight baked in at the end.

Give a 1-2 minute self-introduction covering your background, key achievements, SQL and analytics experience, and why you're a good fit. Wrap up with a project you're proud of and the impact it had.

“Classic opener but the project-at-the-end part tripped me up a bit.”

View Post

Affirm·Software Engineer·Hiring Manager Screen

Jun 2026

30-minute hiring manager screen for a software engineer role at Affirm. Pretty standard format, nothing shocking, but the cross-team conflict question tripped me up more than I expected.

Why are you interested in this team and role specifically, and how does your background line up with what they're actually trying to get done?
Walk me through a recent project where you can point to real, measurable results. What were the goals, what constraints did you work under, and what decisions did you make along the way?
Tell me about a time you had to work through a difficult collaboration or conflict with another team. What tradeoffs did you make and how did it turn out?
How do you deal with unclear or shifting requirements? Walk me through how you prioritize your work and keep people informed when things get uncertain.
What do you actually want from a manager and what kind of team environment helps you do your best work?

“I had a decent answer but it felt a little rehearsed.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Jun 2026

Affirm software engineer interview with a classic game theory DP problem. The follow-up asking for an actual move sequence on top of the score was the part that tripped me up a bit.

Given a row of N integers, two players take turns picking either the leftmost or rightmost card, both playing optimally. Implement a function that returns the maximum score difference (first player minus second player). Then explain your time and space complexity, and modify the solution to also return one optimal sequence of picks as a list of indices.

“The core DP wasn't too bad once I recognized it as a minimax problem with memoization.”

View Post

Affirm·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

Got a product design question at Affirm that was more open-ended than I expected. One question, accessibility angle, and I felt underprepared for how far the conversation could go.

Design a vending machine specifically for people with disabilities.

“I jumped straight into physical UI stuff, lower buttons, braille labels, and the interviewer just kind of waited.”

View Post

Affirm·Product Manager·Onsite - Product Sense / Strategy

Jun 2026

Interviewed for a PM role at Affirm and got a product strategy question that had nothing to do with Affirm's core business, which threw me off a bit.

How would Uber go about expanding into the bicycle market?

“Spent the first minute just trying to figure out why Uber specifically.”

View Post

Affirm·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026

Behavioral round at Affirm for a software engineer role, focused pretty heavily on impact and ownership. Just one big question but they really dig into it.

Walk me through a project where you had the most significant impact. Cover the problem, why it mattered, your role, the technical and organizational challenges, the decisions you made, how you measured success, and what you'd do differently.

“This is one of those questions that sounds easy until you're actually in it trying to remember concrete numbers on the spot.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Jun 2026

Affirm coding screen, one meaty string problem that took up the whole session. Felt like a decent challenge but I came in underprepared for the optimization discussion.

Given a list of strings, find the shortest substring for each string that doesn't appear as a substring in any other string in the list. Return None or empty if no such substring exists.

“I went straight to brute force: enumerate all substrings for each string, throw them into a global frequency map, then scan shortest-first for one that's unique.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Jun 2026

Affirm software engineering round, one meaty coding problem that was clearly designed to take the full hour if you let it. The problem looked like a data pipeline exercise but had enough edge cases baked in that you could easily sink 20 minutes on just the parsing.

Design and implement a system that reads offer redemption events from a CSV on stdin, tracks how many times each user has redeemed each offer within its valid time window, and outputs which offers each user can still redeem as of a given processing date.

“This one has more surface area than it first looks.”

View Post

Affirm·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Affirm for a software engineering role. The whole thing was basically one long question about building an A/B testing platform from scratch, and it went pretty deep into the weeds on bucketing, pipelines, and stats. Left feeling like I covered most of it but probably could've been sharper on the analysis layer.

Design an A/B testing platform for a large product organization, covering experiment definition, user assignment, exposure logging, metric collection, analysis, and experiment lifecycle management.
How would you ensure user assignment is deterministic and consistent across sessions, and how do you handle mutual exclusion between overlapping experiments?
Walk through the event pipeline for exposure logging at billions of events per day. What does the architecture look like from the client event to the data warehouse?
How would you approach the stats engine? Compare frequentist and Bayesian approaches and discuss guardrails like sample ratio mismatch and the peeking problem.
How would you integrate the experimentation platform with a feature flag service, and what are the tradeoffs involved?

“This is a beast of a question.”

View Post

Affirm·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Affirm for a software engineer role. The whole thing was one big deep dive into designing a Venmo-like payment system, which sounds scoped until you realize how many directions it can go.

Design the data model for a peer-to-peer payment system similar to Venmo, including core entities like users, accounts, transactions, payment methods, transfers, and social features.
How would you represent money movement using double-entry accounting, including ledger lines and idempotency keys?
What indexes would you add to support common queries like user transaction history, a friends activity feed, and balance lookups?
How would you handle reversals and disputes in your data model, and what does auditability look like?

“This question sprawled way more than I expected.”

View Post

Affirm interview FAQ

What rounds are in the Affirm interview?

Candidates most often report a technical phone screen (15 write-ups), a hiring manager screen (5), a system design round (4) and a product sense round (3).

What does the Affirm technical phone screen cover?

Across 15 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (16 questions), Technical Trade-offs (12) and Data Modeling (7).