{"id":90,"date":"2026-08-04T08:05:46","date_gmt":"2026-08-04T08:05:46","guid":{"rendered":"https:\/\/www.dobryakov.net\/blog\/90\/"},"modified":"2026-08-04T08:05:46","modified_gmt":"2026-08-04T08:05:46","slug":"leadership-hiring-from-intels","status":"publish","type":"post","link":"https:\/\/www.dobryakov.net\/blog\/90\/","title":{"rendered":"Hiring Is Buying Delivery Leaders, Not Another AI Engineer"},"content":{"rendered":"

Hype counts how often \u201cAI\u201d appears in job descriptions. I count the mandate: who is being bought at the leadership layer, which pain the hire is meant to close, and where the feed inflates volume.<\/p>\n

<\/p>\n

I recently worked through a one-day vacancy-intel corpus \u2014 reads from open job posts: dozens of roles, many reposts of the same JD, some reports still stubs without web verification. After dedupe, roughly thirty unique company\u2013role pairs remain. The durable signal isn\u2019t a recruiter\u2019s polished line. It\u2019s the repeating mandate \u2014 why the seat exists at all.<\/p>\n

This is a different cut from AI job demand read through specialist clusters<\/a>. That piece looked at IC and specialist patterns in the org chart \u2014 agents, evals, Applied AI, partner delivery. This one asks who is being hired upstairs<\/strong>: how AI vocabulary masks uneven maturity, why \u201cplatform\u201d became the shared language of pain, and how not to confuse founding\/plant noise with the same market.<\/p>\n

The title is about leadership, not an IC seat<\/h2>\n

In this slice, Engineering Manager \/ Head \/ Director \/ CTO \/ founding roles dominate. IC roles (Applied AI, GenAI pipeline, QA, principal) are the minority.<\/p>\n

The market is buying someone who can assemble a capability and stitch the org, then turn strategy into a roadmap \u2014 not another headcount slot. That matches what EM\/Head\/Director JDs have said for years: people leadership + delivery operating model + platform thinking + data\/AI readiness + stakeholder management.<\/p>\n

AI amplifies uncertainty. The purchase core stays the same: predictable delivery of business value and lower risk for decision-makers. Where a typical EM starts with hiring rituals, the stronger JD signal starts with what is breaking delivery right now.<\/p>\n

AI is mandatory vocabulary at uneven maturity<\/h2>\n

AI \/ GenAI \/ LLM shows up across most substantive companies in the slice. The meaning isn\u2019t the same.<\/p>\n\n\n\n\n\n\n\n
Cluster<\/th>\nHow AI sounds in the JD<\/th>\nWhat it usually means<\/th>\n<\/tr>\n<\/thead>\n
Regulated enterprise (utilities, healthcare-adjacent)<\/td>\nevaluate, benefit assessment, GenAI + compliance<\/td>\nFOMO plus fear of production<\/td>\n<\/tr>\n
Industrial \/ motion \/ water tech<\/td>\n\u201cuse AI tools\u201d, intelligent solutions<\/td>\ncost\/productivity lever; often resistance from traditional engineering<\/td>\n<\/tr>\n
Product \/ scale-up<\/td>\nAI in the product, pipeline, orchestration<\/td>\nneeds governance and production readiness<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The hire isn\u2019t for \u201cAI research.\u201d What\u2019s on offer is the move from pilots to a system: ownership, evals, agent boundaries, observability, security. Without that, AI stays a set of parallel demos \u2014 impressive on demo day, expensive in operations.<\/p>\n

If you are a CTO and the JD says \u201cmust use AI tools\u201d while nobody owns production AI outcomes, you bought vocabulary, not capability.<\/p>\n

Platform engineering is the shared pain frame<\/h2>\n

Recurring phrases from the day:<\/p>\n