The setting
runs a global network that developers and businesses use to build and protect applications. is a runtime that gives applications routing and storage and keeps their state, for uses such as real-time chat and multiplayer games.
A fixed workshop price depends on activity that participant counts do not explain.
The launch needs a defensible margin estimate, while the customer needs room to change how workshops behave.
Who you’d be doing this for
“Our founder asked what a hundred workshops would cost, and two versions of my spreadsheet gave completely different answers.”
Ximena Torres · Founding application developer · a character in this brief
Builds the customer's workshop application and must explain its infrastructure forecast before the paid launch.
What is at stake
A workshop app needs fixed pricing, but 24 observed sessions support conflicting forecasts of its operating costs. You have to weigh a reusable evaluation integration against a narrower trial that answers the launch question sooner.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- launch-specific answers vs reusable integration
- representative activity vs content minimization
- simple room estimates vs shared infrastructure costs
- conservative headroom vs competitive subscription pricing
Why Cloudflare
Workers and R2 sit inside a customer evaluation that must connect interactive session behavior to a price the customer can sustain.
Written with these in mind
Not your kind of problem? 103 more at Cloudflare, 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 Cloudflare. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Solutions Architect, APJC (Developer Platform) - India Market (opens in a new tab)
- Stay Hands-On: Build, review, and troubleshoot representative applications and integrations.
- A background in public speaking, technical writing, open-source contribution, or community building.
- Principal Solutions Architect, APJC (Developer Platform) - Mandarin Speaking (opens in a new tab)
- Become a trusted technical advisor and collaborative partner to strategic customers, partners, and internal leaders.
- Senior Customer Engineer- (AI & Start-Ups). Los Angeles (opens in a new tab)
- The role requires up to 25-30% travel to attend meetings with prospects or customers, attend conferences and other industry events, and to collaborate with your Cloudflare teammates.
- Customer Engineer AI/ Start Up's (opens in a new tab)
- Cloudflare offers a complete package of benefits and programs to support you and your family.
Reporting read before this brief was written
The pieces closest to the situation in this brief.
On October 2, 2026, celld, a runtime for running Cloudflare Workers and Durable Objects applications on one's own machines, described using deterministic simulation testing and found an alarm bug where a delayed cleanup removed a wake entry a new alarm still needed.
Deterministic simulation testing in celld: exploring execution orders and reproducing bugs · celld (opens in a new tab) · celld.dev · Oct 2, 2026
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.
The same setting, from another role
Each is set around Cloudflare’s Durable Objects, written for a different role. They’re separate briefs, not the same scenario.
Busy Durable Objects can slow down or reject turns while adjacent objects remain healthy.
You must decide what evidence AI can assemble and what an engineer must verify before a fix moves forward.
Developers are replaying uncertain events after disconnects, which can duplicate or lose session state.
You have to weigh a simple recovery API against the runtime guarantees needed to make it trustworthy.
Overload errors are disconnecting players and leaving some match turns uncertain.
You must weigh immediate queue relief against the evidence needed to trust state recovery.