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.
Keeping build caches warm is consuming the disk checkout tests need.
Cache eviction protects worker capacity, while retained artifacts protect developer feedback time.
Who you’d be doing this for
“I've rerun the same commit three times, and now the release cutoff is an hour closer.”
Roberta Vazquez · Checkout Backend Engineer · a character in this brief
Waits for passing automated tests before a checkout change can enter today's release.
What is at stake
Checkout developers lost 18 of 60 builds to full disks. You must weigh automatic cache eviction against larger disks in the only maintenance window left today.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- disk headroom vs warm caches
- fast feedback vs complete test coverage
- storage allocation vs artifact downloads
- bounded cleanup vs predictable capacity
Why Affirm
Checkout changes depend on Buildkite workers running on Kubernetes before they reach shoppers choosing interest-free plans.
Written with these in mind
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.
- Senior Software Engineer, Backend (Workload Safety) (opens in a new tab)
- Proficiency in Go or Python, including building production infrastructure software such as Kubernetes controllers, operators, or admission webhooks
- Senior Staff Software Engineer, Backend (Compute Platform) (opens in a new tab)
- Staff Software Engineer (Continuous Integration) (opens in a new tab)
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.
Where similar work appears
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.
Checkout p95 latency is 690 ms after origin eligibility reads rose from 3% to 19%.
You must weigh a reversible Worker-side pattern against a rollback that protects today’s change window.
Authentication callbacks reach 2.8 seconds during the morning peak.
You must weigh a fast Workers KV cache against the access risk of stale entitlements.
Large repositories are timing out on fetches when agent activity and CI work arrive together.
You must weigh immediate repository protection against keeping ordinary pipeline work moving.
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.
A referral test must win 2,000 first-time plan selections while first scheduled-payment completion stays at 95% or higher.
You have to weigh low-cost acquisition against the clarity shoppers need before they commit.
A major home merchant may move its support toward a competitor as shoppers question fixed payment schedules.
You must weigh an immediate checkout lift against the trust signal the campaign leaves behind.
Campaign-referred shoppers select interest-free plans 11% of the time after reaching checkout.
You must weigh a stronger acquisition message against an expectation the fixed schedule cannot meet.