← Back to Directory

Affirm interview notes, page 1 of 4

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

Apr 2026
Coding round at Affirm for a software engineer role. The problem was about aggregating records from a stream across different dimension combinations, basically a hashmap exercise dressed up with a systems angle at the end.
  • Given a stream of records with fields like user_id, country, product, amount, and timestamp, write code to build aggregate maps (count and sum of amount) grouped by individual dimensions and combinations of dimensions, and also return the top-K users by total amount.

“The grouping part was fine, nested maps are pretty mechanical once you stop overthinking the key structure.”

View Post

Affirm·Software Engineer·Hiring Manager Screen

Apr 2026
Hiring manager round at Affirm for a software engineer role. The whole thing was hypothetical scenario-based, not the usual 'tell me about a time' stuff, so you're reasoning through situations live without a past example to anchor on.
  • How would you handle a hypothetical situation where you need to navigate trade-offs, align stakeholders, and decide on a course of action, without drawing on a specific past experience?

“The format threw me a bit.”

View Post

Affirm·Software Engineer·Hiring Manager Screen

Apr 2026
Affirm software engineer screen that was basically one long deep-dive into your most impactful project, plus some background questions at the end. They really do mean it when they say 'go deep', so don't bring a project you can't defend from every angle.
  • Walk me through the project you've driven that had the biggest impact. What was your specific role, what decisions did you personally own, and what was the measurable business outcome?
  • For that same project, what were the key technical design choices and trade-offs you made? Walk through what you built end-to-end.
  • How did you collaborate with stakeholders on that project, and what would you do differently if you ran it again?
  • Tell me about your background, what motivates you, and how you like to work.

“This is the whole interview, basically.”

View Post

Affirm·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Affirm for a software engineer role, focused entirely on past projects. They go deep, so if you're planning to coast on a vague story about some old feature you shipped, think again.
  • Walk me through a past project in depth, including the context, your role, the design decisions you made, and the outcome.
  • What technical challenges came up during the project, and how did you work through them?
  • What did you learn from that project, and what would you do differently if you had to do it again?

“This is the core of the whole round.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Apr 2026
Interviewed for a software engineering role at Affirm and got a transaction processing problem that felt deceptively simple at first glance. The follow-ups are where it gets real.
  • 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 balance for every user and return a map of user ID to net balance.

“Pretty much a hash-map accumulation problem.”

View Post

Affirm·Software Engineer·Online Assessment (OA)

Apr 2026
Affirm software engineer OA on HackerRank. The problem was more business-logic flavored than pure algo grinding, which I wasn't expecting. Took me longer than it should have to even parse the problem statement.
  • Given a list of user redeem events (each with a timestamp, operation type of redeem or unredeem, and an offer ID), and a set of pre-defined promotion offers (each with an ID, start/end time, and max redemption count per user), output for each user the offers they are eligible to have redeemed before a given cutoff date.

“The problem itself isn't algorithmically hard.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Apr 2026
Affirm software engineer interview, coding round, one question the whole time: implement an LRU cache with O(1) get and put. Pretty standard if you've seen it before, brutal if you haven't.
  • Design and implement an LRU cache supporting get and put operations, both in O(1) average time, with eviction of the least recently used entry when capacity is exceeded.

“The classic combo of a hashmap and a doubly linked list.”

View Post

Affirm·Software Engineer·Technical Phone Screen

Apr 2026
Coding round at Affirm for a software engineer role, two-part problem centered on loan and transaction data processing. The emphasis was on reading the spec carefully and implementing exactly what was given rather than building something clever and general.
  • 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 fields including totals, counts, and weighted averages.
  • Given a list of transactions and the aggregated loan data from the previous part, match each transaction to the correct loan using rules based on borrower ID, a date window, and amount. Produce per-loan transaction history and flag unmatched records.

“My first instinct was to write something flexible that could handle any grouping key, which was the wrong move.”

View Post

Affirm·Data Scientist·Technical Phone Screen

May 2026
Affirm data scientist interview with a fraud risk scenario question. Pretty technical, focused on how you'd actually debug a real production issue rather than anything theoretical.
  • Credit card approval rates have been stable for months and then suddenly drop in a single day. Walk through how you'd diagnose what happened, what data you'd pull, and what your leading hypotheses would be.

“This one took me a second to get organized.”

View Post

Affirm·Software Engineer·Onsite - System Design / Architecture

May 2026
Interviewed for a SWE role at Affirm and got a system design question about building an AB test platform. Pretty open-ended, which I wasn't fully prepared for.
  • Design an A/B testing system from scratch.

“I started with the assignment layer and worked outward, but I think I underweighted the metrics collection side.”

View Post