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.
A working Pages site leaves customer file exchanges in developers' hands.
Guided adoption protects customer independence, while hands-on assistance competes for a limited advisory allowance.
Who you’d be doing this for
“I forwarded eleven attachments yesterday, then our operations lead asked why customers still couldn't upload them themselves.”
Yuna Gao · Application Developer · a character in this brief
Maintains a Pages site for a small business whose customers submit supporting files by email.
What is at stake
Six Pages customers still depend on developers to move customer files. You need to weigh guided production adoption against a service commitment small application teams cannot sustain.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- individual guidance vs reusable service economics
- production adoption vs customer operating capacity
- broad eligibility vs bounded support commitments
- technical milestones vs fewer manual exchanges
Why Cloudflare
Pages customers need an operating path into Workers and R2, not another demonstration of a static site.
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)
- You will focus on providing support on our Developer Platform products: Workers, Workers AI, Pages, KV, Stream, R2, D1, DO etc.
- You will work with our customers on a variety of technical support issues as well as the Technical Operations team that is responsible for running our global distributed network.
- 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.
- Cloudflare’s Customer Support team helps customers resolve complex technical problems and build a better Internet.
- Senior Customer Engineer, Digital Native - Vancouver BC (opens in a new tab)
- Define, document, and educate both internal teams and customers on deliverables such as Standard Operating Procedures (SOPs), architectural best practices, and technical guides to continuously raise the technical baseline across the organization.
- Technical Validation: Partner closely with Account Executives to lead technical deep-dive discovery, capture business requirements, and map complex customer infrastructure - DNS, CDN, Zero Trust, Network Security, Workers - to fit-for-purpose Cloudflare architectures and bespoke solutions. .
- Technical Support Engineer, Application Services (opens in a new tab)
- Serve as a trusted technical advisor for our Enterprise customers, responding to and resolving inquiries and incidents related to Application Services/Performance, while delivering timely, high-quality and personalized assistance.
- Whether it is a Wordpress blogger using our services for free or a global Enterprise business with petabytes of web traffic, we are always eager to assist.
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 is about people starting something and never quite finishing it.
Only 18 of 70 intended application teams are using signed images in production.
You must weigh faster adoption against keeping the platform security team’s evidence standard intact.
Sixty-two percent of newly activated workspaces do not return for a second production session within 21 days.
You must weigh a scalable configuration-and-enablement path against a simpler setup change that uses the same capacity.
Only two of nine subsidiary workloads reached accepted production use within 60 days.
You must weigh a repeatable customer programme against the local architecture and reporting decisions that need individual attention.
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.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn a person's earliest brush with a product into a habit they keep coming back to.
New enterprise accounts are starting tables but not returning to run a second workflow.
You have to weigh a fast activation path against a promise that still feels safe for RevOps.
New desktop users are skipping iOS setup and staying in a single-device inbox habit.
You need to decide how prominently mobile setup belongs before users reach their first inbox.
Three enterprise customers are rebuilding executive updates in slides even though their teams actively use projects.
You have to weigh a helpful guided service against a model that can scale beyond six pilots.
