The setting
runs a global network between people and Internet applications. is the platform that gives customers network connectivity, security, speed, and developer services from that network.
Production resilience tests move faster than their remediation decisions.
Safe test cadence depends on clear dispositions, while engineering capacity limits how much new reporting it will carry.
Who you’d be doing this for
“My leadership asks what happens when a change fails, and I need a straight answer.”
Hani Dabiri · Network Security Administrator · a character in this brief
Runs access and connectivity policies for a distributed organization evaluating whether its critical applications can rely on the platform.
What is at stake
Open chaos engineering findings are reaching readiness reviews without a clear disposition or linked change. You must weigh a faster test cadence against a remediation record engineering can trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- test cadence vs remediation certainty
- engineering focus vs reporting discipline
- change-control rigor vs review speed
- capacity commitments vs safe deferral
Why Cloudflare
Chaos engineering protects the global network that carries secure application and network connectivity for distributed organizations.
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.
- Senior Technical Program Manager (opens in a new tab)
- Execution & Readiness: Coordinate readiness reviews, go/no-go decisions, and safe execution of production resilience tests.
- Program Ownership: Lead end-to-end chaos engineering, from test planning and execution to results publication.
- Developer GTM Strategy Manager, Technical Programs (opens in a new tab)
- This person will help Solutions Architects, Forward Deployed Engineers, Professional Services, and Developer GTM leadership identify the right customer opportunities, organize technical GTM work, and turn high-value customer engagement into repeatable programs and operating rhythms.
- Supply Chain Program Manager - Rack Integration (opens in a new tab)
- By working closely with external manufacturing partners and cross-functional teams, we ensure the infrastructure powering the internet is built, tested, and deployed efficiently, securely, and resiliently.
- Senior Project Manager, Professional Services · no longer posted
- Proactively identify project risks, including zero- or low-downtime migrations, multi-vendor dependencies, resource constraints, scope changes, and customer operational impact, and implement mitigation strategies to protect customer outcomes.
- Program Lead Strategic CDN Accounts GTM (opens in a new tab)
- Establish a planning and review rhythm for a portfolio of strategic accounts, with clear owners, milestones, decisions, risks, and measures of progress.
- Orchestrate account execution: Create the operating rhythm for strategic accounts, including account reviews, action plans, executive alignment, stakeholder mapping, opportunity tracking, decision logs, and follow-through.
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.
Readiness records stay stale even after owners discuss changes in Slack and email.
You choose what the agent writes into a readiness record from a thread, and what waits for the owner and program manager to confirm.
Homeowners are receiving conflicting follow-up after readiness changes fail to reach the service handoff.
You must decide where the system stops after spotting a dependency change and where a program manager takes over before the readiness record and the service handoff are updated.
Refund-policy changes are approaching review while Jira, Salesforce, and Slack disagree about unresolved work.
You must decide what AI can reconcile and what Program Managers must verify before acting.
The same setting, from another role
Each is set around Cloudflare’s Cloudflare Connectivity Cloud, written for a different role. They’re separate briefs, not the same scenario.
Incomplete facilities and deployment requests sit unassigned while physical changes wait for context.
You must decide which parts of the intake, from reading a request and filling its fields from Nlyte and Jira to naming an owner, the AI carries and which the handlers keep.
Two regions reserved different rack footprints for the same incoming hardware model.
You must weigh faster deployment intake against a reusable record that capacity and finance can trust.
Installed hardware is ready for a regional traffic ramp, but its physical records do not agree across systems.
You must weigh available capacity against an irreversible capital and change-control decision.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn confusing, fragmented technical systems into something the people relying on them can understand and trust.
Growth sellers are revisiting call records because key qualification details are thin or unsupported in Salesforce.
You decide where the draft stops and the seller starts: who fills a qualification field from a call record, who confirms its source link, and who writes the proposed next step.
Health-system opportunities stall after first meetings, even when the discovery notes are complete.
You must decide where the AI's work on those notes ends and where the seller takes over what a care-management leader reads in the proposal.
Eleven producers appear complete in the dashboard, but only seven pass migration checks.
You must weigh a timely wave against publishing a readiness view people cannot trust.
