Complex day at Affirm

Choose between in-place upgrade and evacuation for checkout in 4 hours

Published Nov 1, 2026

You’re the devops engineer. Your team is in the room.

The setting

is a financial technology company that lets people buy now and pay later at checkout, and gives merchants payment tools. Its let shoppers split a purchase into scheduled payments.

Checkout's security deadline arrives before its upgrade evidence is complete.

Keeping the current control plane protects known runtime behavior, while advancing it ends an exception with no supported downgrade.

Who you’d be doing this for

“I've got the cart ready for tonight, and I need to know the payment option will actually work.”

Camille Bos · Retail shopper · a character in this brief

Plans to use an interest-free option during the merchant promotion affected by the cluster's capacity.

What is at stake

A checkout cluster carries 28% of available capacity, and its security exception expires in four hours. You must weigh an irreversible upgrade against moving traffic onto capacity reserved for tonight's promotion.

Why it isn’t already fixed

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

  • security deadline vs checkout capacity
  • compatibility coverage vs time to test
  • irreversible upgrade vs reduced peak headroom
  • node automation vs bounded disruption

Why Affirm

Interest-free checkout shares an EKS foundation whose capacity must remain available as merchant promotions bring more shoppers.

Written with these in mind

Kubernetes platform engineersReliability-minded DevOps engineersInfrastructure automation specialists

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

Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.

The organization context comes from public information. The situation and characters are written for the brief.

Job postings it was written from

Public descriptions of the work at Affirm. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.

Reporting read before this brief was written

The pieces closest to the situation in this brief.

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.

Other live briefs connected to this one, and what connects them.

Similar problems at other organizations

Like this one, each of these turns on moving faster inside a system others depend on.

The same setting, from another role

Each is set around Affirm’s Interest-free payment plans (Pay in 4, Pay in 2, Pay in 30), written for a different role. They’re separate briefs, not the same scenario.

Other problems with a similar purpose

In each of these, as in this one, the aim is to build high-assurance systems where a consequential change's correctness can be demonstrated, not merely hoped for.