OpenAI's GTM organization, decoded.

If you search LinkedIn for "Member of GTM Staff at OpenAI," you get hundreds of profiles back (607 as of May 15). The title tells you nothing. It doesn't say whether they sell, deploy, manage, or strategize. It doesn't say which industry they cover. It doesn't say how senior they are.

Of those 607, roughly 184 are GTM-adjacent but don't actually sell. Most are in GTM recruiting or corporate communications. We removed those from this analysis. A further 33 profiles were empty. What's left is a 390-person GTM machine.

We read each one carefully (their summaries, their prior roles, their tenures, their employment patterns) and built a classification system. Here's what five different "Members of GTM Staff" actually do:

The composite "Member of GTM Staff" doesn't exist. There are at least nine distinct functions hiding behind that label, and the people doing each job have radically different backgrounds, compensation, and career arcs.

The prevailing wisdom is that AI labs are different. That they sell themselves, that they don't need traditional sales orgs, that GTM at a frontier lab is mostly partnerships and developer relations.

The data says otherwise. 169 of 390 profiles (43%) are individual contributor Account Executives. Add in front-line sales leadership, Solutions Engineering, and Deployment, and over three-quarters of the GTM workforce is in direct revenue generation or technical pre/post-sales.

The shape of this org tells you what OpenAI is optimizing for: direct enterprise revenue. Partnerships (3.6%) and CS (3.1%) are remarkably thin compared to typical B2B SaaS orgs at this scale, where post-sale teams typically run 15-25%. OpenAI is leaning on AEs and Deployment Engineers to handle the entire customer lifecycle, with Solutions Engineering as the technical wedge.

Across all 390 profiles, the most common path into OpenAI's GTM org starts at one of ten companies. They account for 30% of all hires.

What's surprising isn't who's on this list. It's who isn't. HubSpot, Zoom, Atlassian, Workday, ServiceNow, SAP, Oracle: none crack the top 30. OpenAI is not hiring from the legacy enterprise sales bench.

OpenAI is not hiring from the conventional MEDDIC mafia companies (Snowflake, MongoDB, Splunk, Smartsheet, Confluent, etc). While MEDDIC mafia companies are frequently targeted as places to hire GTM talent from, their alumni only represent 2.8% of the OpenAI GTM workforce. By comparison, AWS, Stripe, Twilio, Slack, Salesforce, and Statsig combined account for 27%.

A note on Statsig: it ranks #3 by volume, but it's an artifact of OpenAI's $1.1B acquisition in September 2025. The other 20 OpenAI acquisitions to date haven't moved GTM headcount in any meaningful way. Statsig is the exception, not the rule.

Across the dataset, 18 people who joined OpenAI's GTM team were previously founders or co-founders of their own companies. That includes founders of acquired startups (Adam Michalski sold Partnered to Crossbeam; Brij Dhanda sold Ezra Digital; Omri Nevat sold Data Leaders), founders who joined post-acquisition (Vikram Soma, ex-Insight, YC 2014), and founders who never sold but joined OpenAI's GTM bench anyway.

Six of them are now in leadership. The other twelve are not. Six are quota-carrying AEs. The rest are in SE, Deployment, Partnerships, and Customer Success. OpenAI is hiring ex-founders into individual contributor seats, not just executive ones.

This is unusual. Most senior hiring managers screen founder-types out of IC roles, on the assumption they'll churn the moment something else interesting comes along. OpenAI apparently doesn't, or has decided the trade-off is worth it.

The Strategy & Operations function rarely gets attention in market reports. It's invisible from the outside, has no quota, and doesn't show up on customer org charts. But at OpenAI it's the third-largest GTM function: 44 people, 11.3% of the GTM workforce. That's larger than Partnerships, Customer Success, and Enablement combined.

This is the function people often confuse with Enablement, so the distinction is worth making clearly.

It's easy to confuse the two here. Strategy & RevOps is what's building the planning cadence, pricing rigor, systems architecture, and growth experiments at OpenAI. It's the layer underneath the AE motion. Enablement is downstream of it.

For B2B SaaS founders trying to understand how OpenAI is scaling: they're investing heavily in non-customer-facing infrastructure roles, and they're hiring senior people to do it. This is not a hero-AE sales motion with minimal systems. It's an operationally disciplined motion with serious people behind the scenes.

Sixteen people in our dataset have current OpenAI-adjacent titles like "GTM Consultant (OpenAI)" or "GTM @ OpenAI | Accenture." They're not OpenAI employees. They're Accenture consultants placed full-time on the OpenAI account.

Most of them are based in Atlanta (Accenture's hub), not San Francisco or New York. Atlanta is effectively OpenAI's third GTM hub, but the workforce there is augmented, not employed. Their titles vary from "Sales Manager" to "GTM AI Consultant" to "Member of GTM Staff." On LinkedIn, the distinction is invisible: they look like OpenAI employees to most readers.

The Forward Deployed Engineer (FDE) function is a relatively new role in B2B software, born at Palantir, popularized by Anduril, and now showing up at OpenAI in force. 37 people in the dataset are doing this work, 9.5% of the GTM headcount.

What's striking is the title soup. The phrase "Forward Deployed Engineer" doesn't appear in a single current title at OpenAI. Instead, the same role is being called:

The remaining 17 are labelled "GTM Staff," "Customer Engineer," "Technical Success," "Integration Team," or some other variation. If you searched LinkedIn for "Forward Deployed Engineer at OpenAI," you'd get zero results. Yet the function is real and substantial.

The bench is senior: median 12 years of experience, zero VPs, but 11 of 37 (30%) are at Director or Manager level.

While Palantir is where the term FDE was created, only 2 people in the entire 37-person OpenAI team came directly from there. Another 2 came from McKinsey's QuantumBlack AI consulting practice. The rest come from a long tail of modern SaaS Customer Engineer and Solutions roles (Slack, Google, AWS, Outreach, Amplitude, Postscript, Pocus). The pattern: engineering background plus customer-facing experience, with a bias toward people who've done either AI consulting or technical pre-sales.

For B2B SaaS hiring managers building their own AI deployment function, the talent pool is real but narrow. The role doesn't need to be called "FDE" to be the same job.

Two cities house 68% of OpenAI's GTM workforce. Outside SF and NYC, the only meaningful clusters are Atlanta (12 people, mostly Accenture consultants) and Seattle (13 people, mostly ex-AWS, ex-Microsoft, and ex-Statsig).

The workforce is senior. Median total work experience is 13 years; for AEs specifically, median sales-role tenure is 10 years. There is no entry-level GTM at OpenAI. Every seat is a senior hire, even those with vague "Member of GTM Staff" titles.

The bachelors pipeline runs heavily through California public universities: UC Berkeley (19), Cal Poly San Luis Obispo (9), USC (8), UCLA (6), Santa Clara (6), UC Davis (6), UC San Diego (6). The top East Coast schools (Penn, Harvard) each appear five times.