The setting
's is a platform for deploying and running application code, static sites, and full-stack applications around the world. Developers use it without managing servers.
Three healthy applications still depend on one departing champion.
Customer independence competes with the certainty of temporary specialist cover.
Who you’d be doing this for
“I asked who could handle tomorrow's release, and everyone pointed at the person going on holiday.”
Astrid Haugen · Application Engineering Manager · a character in this brief
Responsible for the developers accepting operational ownership of the three applications.
What is at stake
Three production applications have only one qualified operator, who leaves tomorrow. You must weigh customer independence against temporary specialist cover within today's single working session.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer independence vs. experienced temporary cover
- complete rehearsal vs. a single working session
- healthy production usage vs. demonstrated operational readiness
Why Cloudflare
Workers deployments and R2 access both sit inside the customer's acceptance criteria, so live traffic alone does not establish adoption.
Written with these in mind
Not your kind of problem? 100 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.
- Technical Support Engineer - Developer Platform (opens in a new tab)
- Technical Support Engineer, Developer Platform (opens in a new tab)
- As a Technical Support Engineer on our Developer Platform team, you’ll help developers build and run applications on Cloudflare Workers, Workers AI, Durable Objects, R2, D1, Workflows, Pages, Queues, and Workers KV.
- You’ll investigate platform behavior, replicate reported issues in a test account, guide customers on enabling logs and tracing, and turn findings into clear, practical guidance.
- Senior Customer Engineer, Digital Native - Vancouver BC (opens in a new tab)
- Deliver tailored technical presentations, architectural diagrams, and demonstrations that show how Cloudflare solves specific performance, security, and reliability challenges.
- Design structured migration and onboarding blueprints tailored to the customer’s environment (e.g.
- Technical Support Engineer, Application Services (opens in a new tab)
- Create and maintain knowledge base articles, technical guides, and troubleshooting documentation for internal and customer use.
- We are the eyes and ears of Cloudflare, acting as the real-time voice of the customer to help communicate their needs and real-world use cases back to the rest of the company - for better service and future product development.
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 Cloudflare Workers, written for a different role. They’re separate briefs, not the same scenario.
Resource-limit alerts are reaching responders without the same evidence, so severity calls diverge.
You must decide where the route stops gathering telemetry and proposing a severity, and where the on-call engineer takes over the severity call and the incident actions.
Discovery details are being reconstructed after calls, leaving technical buyers to repeat architecture and migration constraints.
You must decide where the system stops and the seller starts between the call record, the qualification fields, and the first message a buyer receives.
Recurring Worker failures leave responders with competing explanations and application developers without a clear path to recovery.
You must decide where the system's evidence gathering and cause ranking end and the on-call engineer's confirmation of the cause begins.