← Affirm
High-stakes day at Affirm

Uncover why eligible purchases go unfunded

You’re the software engineer. Your team is in the room. Printed Sep 14, 2026.

Uneven customer behavior can signal a product gap, a timing problem, or an incomplete view of the evidence.

Teams must learn quickly without treating a plausible explanation as a settled fact.

Who you’d be doing this for

“I don’t know if I missed the option or if that purchase just didn’t qualify.”

Dwi Win · Dental office receptionist

Uses the card for occasional larger expenses and needs clear options after purchases settle.

What is at stake

Eligible purchase conversion differs by as much as 19 points across inferred merchant categories. You must weigh quick experiments against the risk of optimizing for a pattern the evidence does not yet explain.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • learning speed vs causal confidence
  • conversion lift vs eligibility clarity
  • broad patterns vs individual customer intent
  • instrumentation depth vs experiment velocity

Why Affirm

Cardholders use installment financing after purchases across merchants, making eligibility understanding and timing central to plan uptake.

Written with these in mind

product-minded backend engineerexperiment-oriented builderambiguous-problem solver

Not your kind of problem? 17 more at Affirm, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.