When They Hire A Chief Information Officer Who has Never Actually Coded
In the Runtime Regret episode, Joe talks about something that genuinely confounds him: the recurring pattern of companies hiring a Chief Information Officer who has never actually run engineering or technology systems in the trenches. To Joe, this is one of those organizational decisions that sounds reasonable on paper but breaks down immediately when you look at how technology work really happens. Companies will recruit someone with a polished executive résumé—someone who has managed budgets, sat in board meetings, or overseen “IT strategy”—but who has never personally lived through the chaos of running real systems. They’ve never been responsible for a failing deployment at 2 a.m., never had to debug a cascading outage, and never had to balance reliability, developer velocity, and operational risk at the same time.
What bothers Joe most is the disconnect between the expectations placed on the role and the experience the person actually brings. A CIO is often expected to guide architecture decisions, shape infrastructure strategy, and evaluate the tradeoffs between new platforms and legacy systems. But if the person has never operated production systems themselves—never been “in the weeds,” as Joe puts it—they lack the intuition that comes from experience. They may understand the vocabulary of technology leadership, but they don’t always understand the consequences of the decisions they’re making. That gap shows up in subtle but important ways: unrealistic timelines, overconfidence in vendor promises, or strategic initiatives that ignore the operational complexity engineers deal with every day.
Joe frames this as part of a broader cultural problem in how organizations think about technology leadership. In many companies, engineering experience is treated as something you grow out of rather than something foundational to leadership. The result is that executives sometimes come from backgrounds closer to finance, consulting, or general management than to software or infrastructure. From Joe’s perspective, that’s like hiring a hospital administrator to run surgery who has never stepped inside an operating room. The leadership might be excellent in terms of communication and organization, but without firsthand exposure to the work itself, it’s difficult to make grounded decisions.
Ultimately, Joe isn’t arguing that every CIO needs to be the best engineer in the room. Leadership, after all, involves far more than technical skill alone. What he is pushing back against is the idea that deep operational experience is optional. The most effective technology leaders tend to be people who have spent real time in the systems they’re now responsible for guiding. They understand the constraints engineers face because they’ve faced them themselves. That perspective builds trust with teams and leads to decisions that respect the messy, complicated reality of running modern software systems. Without that grounding, Joe suggests, organizations risk creating a leadership layer that talks about technology but doesn’t truly understand it.
This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit runtimeregret.substack.com [https://runtimeregret.substack.com?utm_medium=podcast&utm_campaign=CTA_1]
