The Job Vacancy Nobody Named

The AI Inflection Point (TAIIP) Essay | 920 words | Reading time: ~4 minutes

As Y Combinator outlined in its 2026 playbook for AI-native companies (see YC’s video here, summarized in this article), the future belongs to organizations that ‘keep humans only for corner cases — high-stakes decisions, ethics, sales, brand-new situations where the loops haven’t been built yet.’

Although meant as a vision of leaner, more automated companies, if read differently, it was describing a job.

Not a hypothetical one. An unfilled one — sitting, right now, inside almost every organization far enough into agentic AI deployment to have a governance gap and not yet know it.

Last month, this series named one version of this gap directly: a single owner, accountable for the intersection where AI agent capability meets vendor risk, contract review, and cross-functional accountability — a role no existing title quite covers. That essay used the vendor-contract review process as its example. But the amendment back door is one instance of a broader pattern, not the whole of it.

Organizations adopting agentic AI are discovering, function by function, that they need roles that sit between their existing boxes. Legal knows contracts. IT knows access and infrastructure. Operations knows what normal looks like and notices when it drifts. Procurement knows vendor relationships. HR knows where accountability lands on people. None of them, on their own, owns the intersection where all of those things meet an autonomous system making a decision nobody explicitly authorized.

That intersection is where the “novel situations, ethical considerations, high-stakes moments” category actually lives. It’s not a leftover bucket for whatever AI can’t yet do. It’s a role — and right now, in most organizations, it’s vacant.

Here’s the structural reason that vacancy tends to get filled by an outside hire, when it gets filled at all: organizations search by title, and this role doesn’t have one yet.

A board that recognizes a gap reaches for the nearest existing job category — often a senior title in whichever function feels most implicated — and posts an external search for someone who’s “done this before.” That’s a reasonable instinct. It’s also, structurally, the wrong search, because the role isn’t defined by which function it sits in. It’s defined by a composite of judgment — contract literacy, cross-functional standing, systems thinking, the nerve to hold a “no” — that doesn’t correspond to any single existing title, inside or outside the company.

Searching externally for a title that doesn’t exist internally isn’t a solution. It’s a workaround for not knowing how to search internally for a pattern instead.

That’s not a claim that external hires are wrong. It’s a structural observation: the search criteria most boards are using — years in a specific title, prior experience “doing this” at another company — screens out exactly the internal candidates most likely to actually have the composite judgment the role requires, because that judgment rarely lives under a title that matches the search.

This is the part of the current moment that’s getting less attention than it deserves.

No shortage of reports exist documenting the deep anxiety among tech workers—record industry profits alongside genuine fear among the people building the systems generating those profits—describes an economy where output is climbing while headcount holds flat or falls. That’s real, and it’s not limited to engineering roles. But it’s not the whole story.

Every one of those “novel situations, ethical considerations, high-stakes moments” is a place where human judgment is still required, still valuable, and critically — still unowned in most organizations. That’s not a consolation prize. It’s a genuinely new category of demand, created by the same transformation that’s generating the anxiety.

The people best positioned for it aren’t necessarily the ones with the most AI credentials. They’re the ones who’ve spent years operating at the intersection of two functions without a clean title for it — the Ops person who’s spent a decade translating for Legal, the Program Manager who’s run cross-functional escalations that never had an owner, the HR generalist who’s watched accountability diffuse and had no formal authority to stop it. Career paths that felt hybrid, hard to categorize, or slightly unfocused on a resume are turning out to be exactly the composite experience this moment is creating demand for.

For boards considering on whether to default to an external search for whatever this role gets called at your organization, map the internal bench against composite experience, not title. The person best positioned to own this intersection may already be inside the building, in a function nobody would have thought to look at.

For workers watching this transformation with the kind of unease that’s been well documented this year: the anxious framing is “what happens to my job when this system gets better.” There’s a second framing available, less discussed and just as real: “who is going to own the judgment this system still can’t make and is there a version of my experience that already qualifies me to propose myself for that.”

Nobody’s posted that job yet. That’s not evidence it doesn’t exist. It’s evidence that naming it first is still available to whoever moves.

This month’s Deep Dive: the practitioner mechanics — how to source an un-named role within your organization, how to justify funding, and scope the first 120 days, whether you're standing it up as a board member or proposing yourself for it as a candidate.