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.
Two valid tenant identities send participants in one room to different state.
Compatibility with issued tokens pulls against keeping tenant routing simple and explicit.
Who you’d be doing this for
“I moved a card on my laptop and watched my phone sit there unchanged. Tomorrow I'm supposed to demo both together.”
Mai Santoso · Customer application developer · a character in this brief
Builds the shared planning experience and must demonstrate browser and mobile participants collaborating in one room.
What is at stake
A customer's shared-room pilot splits participants in 11 of 40 join cases. You must weigh compatibility in Workers against cleaner tokens that require the customer's authentication change.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- token compatibility vs canonical identity
- passing joins vs tenant isolation
- adapter ownership vs issuer change
- demonstration speed vs customer operability
Why Cloudflare
Workers is the customer's entry point for shared room state, so the pilot depends on translating existing authentication into stable object routing.
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.
- Senior Solutions Architect, APJC (Developer Platform) - India Market (opens in a new tab)
- Principal Solutions Architect, APJC (Developer Platform) - Mandarin Speaking (opens in a new tab)
- Senior Customer Engineer- (AI & Start-Ups). Los Angeles (opens in a new tab)
- Customer Engineer AI/ Start Up's (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.
Authorized responders cannot reliably find Microsoft 365 runbooks after seeing them in Slack.
You must weigh a fast pilot correction against evidence that permissions still hold for every test identity.
Tokens stay valid long after an employee is dropped from the roster, and a review tied several delayed removals to live sessions.
You weigh strict expiry against blocking a legitimate checkout.
Eighteen of 60 employees receiving transferred seats saw a purchase prompt despite having paid access.
You weigh a database read on authenticated access against forcing affected learners to sign in again.
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.