Lack of Exposure

For most of my early career, I thought the engineers who made it into leadership were simply better engineers. Sharper, faster, more technically fluent. It took me years to understand that was almost entirely wrong.

The ones who moved up weren't necessarily the best at the craft. They were the ones who had been in more rooms.

I joined EuroDNS in 2006 as a software architect. It was a small company — the kind where you wear many hats not because the org chart says so, but because there aren't enough people to do otherwise. That context forced something on me that I wouldn't have sought out on my own: I started attending meetings that weren't technically mine to attend. Two years later I was CTO. Not because I had suddenly become a better engineer, but because I had accumulated context nobody else had thought to collect.

It happened because the company was small and the walls between functions were thin. A sales call would happen near the dev room. A finance conversation would bleed into a lunch. A client complaint would land in the inbox of someone technical because there wasn't a dedicated customer success team to catch it.

Each of those moments is a data point about how the world works beyond your codebase. The client who canceled because the renewal process was confusing. The enterprise deal that stalled because nobody could explain the pricing in plain terms. The partnership that fell apart because two technical teams couldn't agree on an integration scope before the business relationship soured. I filed all of this away without knowing I was doing it.

By the time I became CTO, I had accumulated something that no amount of technical skill would have given me: a working model of how business decisions actually get made. Not the theory — the actual thing. The politics, the timing, the way a CFO thinks about risk differently from a CPO, the way a salesperson will promise something to close a deal that the engineering team will spend six months regretting.

That model is what separates those who aspire to lead from those who stay in the technical track — and to be clear, staying technical is a legitimate and valuable path. Not everyone wants or should move into leadership. But for those who do want to move up, the differentiator is rarely more skill. It's exposure to how the business actually works.

Most engineers don't get this exposure. Not because companies hide it from them, but because it doesn't naturally fall within the boundary of their role. If you're a backend engineer at a company with 200 people, there are entire layers of organizational reality that your job description will never surface. You could be brilliant for a decade and still not know why the product roadmap keeps shifting, what the board actually worries about at night, or why the company made an acquisition that seemed strategically strange from the outside.

The easiest way to get this exposure is to have a mentor — someone already in those rooms who pulls you in, explains the context, and helps you read what's actually happening. When you have that, it's a genuine blessing. Most people don't. When you don't, you have to get out of your comfort zone deliberately: ask to sit in on the sales call, offer to help with the customer escalation, read the board deck even though nobody told you to. The gap closes the same way either way — through accumulated context. A mentor just accelerates it.

The engineers who break through usually do one of these things. Some find companies early enough that the walls haven't been built yet. Some actively look for the seams — projects that require talking to finance, post-mortems involving stakeholders from three departments, client escalations where a technical person has to sit across from an unhappy executive. Some find a manager who treats them as a thinking partner and, through that relationship, absorbs context that would otherwise never reach them.

If you're an engineer frustrated by slow career progress, ask yourself what rooms you're actually in. Are you hearing how decisions get made about the product? Do you understand the commercial pressures that shape priorities? If not, your ceiling might not be skill. It might be exposure.

Nobody will usually tell you this directly. The performance review will mention communication, or strategic thinking. It won't say: you don't understand enough about how this business works to be trusted with bigger decisions. But that's often what it means.

This is, in a way, the opposite of the Peter Principle. That's about people rising beyond their competence. This is about capable people who never rise at all — not because they can't do the job, but because nobody ever gave them the view from the room where decisions are made.