← Back to Directory

Affirm

Large Enterprises

Screna has 17 Affirm interview write-ups. The most reported round is the technical phone screen (7).

17 interview notes · updated Jun 2026

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 question about building an A/B testing platform from scratch, which sounds manageable until you realize how many moving pieces they actually want you to cover.
  • 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 handle deterministic, low-latency user bucketing that stays consistent across sessions and remains mutually exclusive across overlapping experiments?
  • What guardrails would you put in place to catch sample ratio mismatch or peeking problems in your analysis engine?
  • How would you design the exposure logging system to handle billions of events per day with minimal overhead on the request path?

“This is a beast of a question and I underestimated the scope going in.”

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 big deep-dive into designing a Venmo-like payment system, covering data modeling, ledger logic, and the social layer. Dense question, took up the full session.
  • Design the data model for a peer-to-peer payment system similar to Venmo. Walk through the core entities, how money movement is tracked, the social feed schema, indexing strategy, and how you'd handle consistency, auditability, and reversals.

“This was a single question that ate the entire interview.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Jun 2026
Part two of a software engineering interview at Affirm where I had to implement logic to match a Fraud Event against a transaction. Pretty focused coding session, no fluff.
  • Implement a function that matches a Fraud Event to a corresponding transaction.

“The problem sounds straightforward until you start thinking about what 'match' actually means.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Jun 2026
Affirm software engineer interview with a meaty coding problem centered on offer redemption logic. The problem was scoped for about an hour and required careful thought on data modeling and parsing before writing a single line of code.
  • Design and implement a system that reads offer redemption events from a CSV on stdin, processes them chronologically, and outputs which offers each user can still redeem on a given processing date, taking into account per-offer validity windows and per-user redemption limits.

“This one took me a few minutes just to parse what was actually being asked.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Jun 2026
Went through a technical phone screen for a software engineering role at Affirm. The coding problem was finance-flavored which made sense given the company, and the follow-ups pushed pretty hard into distributed systems territory.
  • Given a list of transactions for a single day where each entry has a timestamp, user ID, and amount (positive for credits, negative for debits), compute the end-of-day net balance for every user and return a map of user ID to balance.

“Pretty approachable once you see it as a groupby-sum problem.”

View Post

Affirm·Software Engineer·Recruiter / HR Screen

Jun 2026
HR screen at Affirm for a software engineer role. Pretty standard stuff, background questions and one behavioral prompt about juggling competing priorities.
  • When you have multiple tasks competing for your attention, how do you decide what to work on first?

“I had an answer ready but fumbled a bit trying to come up with a concrete example on the spot.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Jun 2026
Affirm SWE coding round with a two-part problem around loan and transaction processing. Nothing flashy, but the devil was in the details of the spec.
  • Given a list of loan records with fields like loan ID, borrower, principal, rate, and term, aggregate them by a specified key and produce summary outputs including totals, counts, and weighted averages.
  • Given a list of transactions and the aggregated loans from the first part, match each transaction to the correct loan using provided rules based on borrower ID, date window, and amount. Output per-loan transaction history and flag unmatched records.

“The aggregation itself wasn't hard.”

View Post

Affirm·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Affirm for a software engineer role. The whole session was basically one big question about building an A/B testing platform from scratch, and it went deeper than I expected.
  • Design an A/B testing platform that allows product teams to run controlled experiments at scale, covering experiment configuration, user assignment, metrics collection, and statistical analysis.
  • How would you handle the assignment service hot path to keep latency under 10ms at the 99th percentile?
  • Walk me through how you'd handle the high volume of exposure and conversion events flowing into the platform.
  • How would you deal with late-arriving events in your metrics pipeline, and what impact does that have on your analysis?
  • How would you evolve this platform to support ML-driven multi-armed bandits instead of traditional fixed-allocation A/B tests?
  • How would you detect and handle a sample ratio mismatch in a running experiment?

“This one sprawled fast.”

View Post

Affirm·Software Engineer·Hiring Manager Screen

May 2026
Hiring manager round at Affirm for a software engineer role. The whole thing was hypothetical scenarios, not 'tell me about a time' stuff, so you can't just pull a war story from memory and coast on it.
  • How would you handle a hypothetical situation involving competing stakeholder priorities or a difficult technical trade-off?

“The format threw me a bit.”

View Post

Affirm·Software Engineer·Hiring Manager Screen

May 2026
Affirm software engineer screen that was basically a deep dive into one project you've owned, plus some background questions. Come ready to defend every technical decision you made because they will push on it.
  • Walk me through the highest-impact project you've driven. What decisions did you personally own, what did you build end-to-end, and what were the measurable results?
  • What were the key technical trade-offs in that project and why did you land where you did?
  • How did you work with stakeholders on that project, and what would you do differently looking back?
  • Tell me about your background and what draws you to this kind of role.

“This is the whole interview basically.”

View Post