The setting
runs a global network between users and Internet applications. is its service that routes requests to AI models from different providers, for developers who build applications that use AI.
Application-level control is pulling against the customer’s need to keep model clients unchanged.
The platform group needs a shared access boundary, while application teams need their existing provider calls to keep working.
Who you’d be doing this for
“A provider contract changed last week, and I spent half a day asking who still had the key.”
Rocio Perez · AI Platform Engineer · a character in this brief
Owns the customer platform that must govern several application teams using different AI model providers.
What is at stake
Provider credentials are scattered across application deployments, so access cannot be withdrawn consistently. You have to weigh a reusable control boundary against the integration changes application teams will accept.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- central control vs unchanged application clients
- fast pilot proof vs durable operating handover
- provider flexibility vs application-level access boundaries
- security review vs release-window pressure
Why Cloudflare
AI Gateway and Cloudflare One meet at the point where multi-provider inference needs both routing continuity and enforceable access control.
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 Customer Engineer, Hong Kong (Pre-sales) (opens in a new tab)
- Leverage AI agents and internal platforms to automate routine tasks such as RFP/Security Questionnaire responses, sandbox provisioning, and basic telemetry monitoring, reclaiming your time for strategic customer advisory.
- Strategic Alignment: Own the long-term technical relationship across the entire customer lifecycle, ensuring continuous alignment between the customer’s evolving business goals and our product roadmap.
- Senior Customer Engineer, Named - LA (opens in a new tab)
- You will bridge the gap between technical strategy and business value—guiding enterprise clients from initial pre-sales technical validation through onboarding, deployment architecture, and full lifecycle expansion.
- Design structured migration and onboarding blueprints tailored to the customer’s environment (e.g.
- Partner Engineer, Spain (opens in a new tab)
- The Partner Engineer (PE) is a high-impact, strategic technical sales leader responsible for end-to-end technical lifecycle and enablement of the assigned partners, managing both pre-sales and post-sales engineering activities.
- Principal Partner Engineer, APAC (opens in a new tab)
- Partner Solutions Architect- Service Providers Location New York/ New Jersey, Dallas, Denver or Seattle. (opens in a new tab)
- Global Service Monetization: Enable GSIs and SPs to embed CF1 and Workers AI capabilities deeply into their own global managed security portfolios and core enterprise offerings to shorten time-to-market, protect complex client AI pipelines, and maximize global profitability.
- In this elite role, you will act as the principal architect and single point of technical alignment, collaborating at the executive and enterprise architect level to drive joint global GTM strategy and design repeatable reference architectures.
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.
Three pilot repositories need scan results in merge requests within 10 weeks.
You have to weigh developer feedback against the customer’s approved data boundary.
Approved clinical requests are failing after a new access policy, despite the model working in notebooks.
You have to restore the application path while keeping the governed catalog locked down.
The same setting, from another role
Each is set around Cloudflare’s AI Gateway, written for a different role. They’re separate briefs, not the same scenario.
Discovery records are leaving sellers unsure which AI Gateway concern the buyer actually raised.
You have to decide where the extraction stops and the seller starts when a record's cost, access or routing concern is unclear, and who settles it before a next step goes out.
Prospects are hearing separate proposals for AI routing, security, and cost control.
You must decide what a partner can credibly lead and what stays in the direct technical conversation.
A $2 million platform agreement is stalled because the buyer cannot reconcile production AI traffic with its residency requirements.
You must weigh a credible multi-product commitment against terms that will survive technical and risk review.