Unofficial. A job application for OpenAI’s Applied AI Delivery Lead role, built from public pages. Not affiliated with OpenAI.

The evidence.

Everything on this site comes from pages any visitor can open, read on November 22, 2026. I created no account, submitted no form and tested no system.

Where OpenAI already leads

OpenAI beside six other providers

What a customer’s delivery lead can establish from each provider’s own public pages. Each name links to the page that provider’s row starts from.

ProviderRollout guideBaseline stepAdoption analyticsDelivery peoplePartner listRetirement noticeReserved capacityPublic uptime figure
OpenAIEight-step guide, and a nine-item quickstartIn the value guide, not in the rollout guidesUsage, task insights, outcomes, surveys, an APIForward Deployed Engineers; AI advisorsPublic, 73 named6 months for generally available modelsReserved Tier; Scale Tier99.9% on Scale Tier
AnthropicFour-phase admin guide with a checklistNot foundDashboard and two analytics APIsApplied AI engineersPublic directoryAt least 60 daysThrough sales; the older tier is closed to new buyersNot found
GoogleThree-phase guide with named roles, for WorkspaceYes, a baseline survey in phase 1Gemini reports; a value tabCloud Consulting; engineers placed with integratorsPartner network; list not readable12 months of availability, or at least 45 daysProvisioned Throughput99.5% for the Gemini API
MicrosoftFive-step admin guide; a success kitNot foundCopilot Dashboard; usage reportForward-deployed engineers; FastTrackPublic directories60 days; 30 for previewProvisioned throughput units99.9% on the product page
Amazon BedrockA maturity model; no rollout checklist foundNot foundUsage telemetry; no per-user view foundForward Deployed EngineeringPartner network; list not readable6 months, or 45 daysProvisioned Throughput99.9%
CohereNot foundNot foundNot foundForward-deployed engineers; architectsPartner page; no list seenPolicy with no period statedNot foundNot found
MistralNot foundNot foundUsage dashboardA named deployment teamPartner page; no list seen6 months; 1 month for othersDedicated capacity mentionedNot found

“Not found” means not found on public pages, not that the provider lacks it. An AI research agent gathered the rival rows from each provider’s own pages. I checked the OpenAI row against saved page text. Eight rival facts were spot-checked. The rest were not checked line by line, and Cohere and Mistral got a short look only.

What a delivery lead should know about this market

Four things that shape a plan, whichever provider it is built on.

  • Every large provider now names forward-deployed engineers.OpenAI, Google, Microsoft and Amazon all describe them on public pages, and Anthropic funds training for them. The engineers are no longer the difference. How their work is planned and joined to the customer’s is.
  • The model can retire during the program.For generally available models, stated notice runs from 45 days to six months across the providers I read. A launch date and a retirement date belong on the same page.
  • Measurement has moved from seats to outcomes.OpenAI, Google and Microsoft all publish ways to connect usage to results. Of the rollout guides I read, only Google’s makes a baseline survey a named step.
  • Capacity is bought ahead.OpenAI, Google, Microsoft and Amazon all document reserved capacity per model. It has to be sized before launch, from a test and not a guess.

What is not on this page

While reading, I found seven places where OpenAI’s public pages disagree with each other, and a few smaller inconsistencies. Most touch things a customer plans around: capacity, retirement dates and reporting.

Those are in a findings report I will send to OpenAI directly. A public page is the wrong place for them.