Affirm Product Manager Interview Questions

1.Tell me about a product feature or workflow you owned that was genuinely confusing to users or stakeholders. How did you figure out it was confusing, and what did you do about it?

2.Walk me through a time when a product metric dropped unexpectedly and you had to figure out why. Where did the investigation take you, and what did you find?

3.Tell me about a time you shipped a feature and later discovered a risk you hadn't anticipated — something that could hurt users, create compliance exposure, or damage trust. How did you handle it once you found out?

4.Describe a time you disagreed with a director or VP on a product direction and decided to push back. What was the disagreement, how did you make your case, and how did it end?

5.Tell me about a time you owned a product area where the underlying rules — pricing logic, eligibility criteria, or state transitions — had become so complex that even your own team couldn't fully explain what it did. How did you tackle that?

6.Walk me through a time when you discovered that a problem in your product was actually caused by something happening much earlier — or later — in the user journey than you expected. How did you diagnose it, and what did fixing it require?

7.When you're working with engineers on a feature that touches our underwriting or loan servicing logic, how do you know when you understand the system well enough to write a good spec?

8.Affirm uses Kafka for event streaming across several core flows. As a PM, how would you think about the difference between designing a feature that's event-driven versus one that's synchronous, and when would that distinction actually matter to you?

9.Adaptive Checkout personalizes loan terms at the point of sale using real-time ML underwriting. If you're tasked with improving its approval rate without increasing loss rate, how do you structure that problem — what's your north star metric, and what experiments would you actually run?

10.Affirm runs a financial ledger at scale — every loan disbursement, payment, and interest accrual has to be recorded accurately and durably. How would you think about speccing a new payment feature in a way that accounts for ledger correctness, not just happy-path UX?

11.The Affirm Card lets users split a purchase into installments after the fact — that's a fundamentally different underwriting moment than point-of-sale BNPL. If approval rates for post-purchase splits started declining and you needed to diagnose why, how would you structure the investigation?

12.Affirm is considering building a real-time fraud signal that would reject transactions at the point of sale within 200ms — it would require a new low-latency path through the underwriting stack that bypasses several existing compliance checks. How do you decide whether to build it, and what would your 6-pager or design doc need to cover?

13.Walk me through how you'd design a repayment reminder system for Affirm Pay-Over-Time — one that nudges users before a payment is due without feeling like a collections agency. What does the system actually need to do?

14.You're designing the merchant onboarding flow for Adaptive Checkout — the part where a new merchant configures which loan terms to offer their shoppers. What does that product need to do, and what are the hardest parts to get right?

15.The Affirm Card needs to let users set a monthly spending limit that also accounts for their outstanding BNPL balances. How would you design the system that tracks available credit across both real-time card spend and existing installment loans?

16.Design the system that powers the Affirm Money Account's high-yield savings rate display — the APY needs to update when the Fed changes rates and be accurate across the app, website, and marketing emails simultaneously. What could go wrong, and how do you design around it?

17.Affirm is expanding into a new country where installment lending requires regulatory approval for each individual loan term we offer. Design a system that lets Affirm's compliance team configure which loan products are available in each market, and that guarantees those constraints are enforced at checkout with zero margin for error.

18.Design a system that detects and resolves split-brain scenarios in Affirm's loan repayment flow — specifically where a user's payment is confirmed by their bank but our system failed to record it, leading the user to see a past-due balance they already paid. How do you design the reconciliation loop, and how does it interact with the consumer experience?

19.Tell me about a time you had to represent your product area to a cross-functional partner — like a risk, legal, or finance team — who had a legitimate veto on your roadmap. How did you earn their trust?

20.Describe a time you had to sunset or significantly cut back a feature your team had built and was proud of. How did you make the call, and how did you communicate it?

21.Tell me about a time you had to align multiple engineering teams on a shared technical dependency that your product needed but none of them fully owned. How did you get it built?

22.Tell me about a time you had to make a product decision with incomplete information — where waiting for more data would have cost you something real. How did you decide, and what happened?

23.Imagine you're six months into a role at Affirm and you discover that a metric your team has been optimizing for is actually pointing in the wrong direction — it's going up, but user outcomes are getting worse. How do you handle that internally and externally?

24.Tell me about a time you had to make the case for investing in something unglamorous — infrastructure, observability, reliability, or tech debt — against competing feature work. How did you frame the argument and what happened?

25.Estimate how many Affirm Pay-Over-Time transactions happen on a typical Black Friday. Walk me through your assumptions.

26.Affirm's checkout approval rate for a major retail partner dropped 4 points last week. No model changes shipped, no incidents were flagged. How do you start diagnosing it?

27.Estimate the annual revenue impact to Affirm if average loan term length increased by one month across all Pay-Over-Time transactions. What assumptions does that hinge on?

28.The activation rate for the Affirm Card — users who get approved but make their first transaction — has been declining for two quarters. How do you build a framework for diagnosing and fixing it?

29.Affirm is thinking about offering a 'Pay in 2' product — split any purchase into just two equal payments, no interest. Estimate the unit economics of this product and tell me whether you'd build it.

30.Affirm wants to expand Pay-Over-Time into a new vertical — say, healthcare or home services — where the average transaction is $3,000 and repayment periods could be 12–24 months. What's your framework for deciding whether to enter, and what are the hardest product bets you'd have to make?