Not Technical*
, rewritten
In 2015 I was an engineering manager, with two teams, at a company I’d rather not mention. It lasted six weeks. Near the end of it I sat down with my manager for a 1:1 about a PIP for one of my reports. The PIP went sideways, then the meeting did, and somewhere in the wreckage he told me, to my face, that I was “not technical.”
I had been an engineer for the better part of two decades at that point. I’d built factory infrastructure at Apple and kept a DNS root server up. I had gone to work for this person because I thought I could learn from him. So I sat there and took it, and then he added the second half: I wasn’t strong enough as a leader to make up for it.
I left soon after. That part I have never regretted.
Here’s what still gets me, eleven years later. That he said it. That it was wrong. And that it was wrong and I half believed it anyway, for longer than I’d like to admit.
He was almost right about something else. I wasn’t “not technical.” I was inexperienced as a manager and in over my head. That part was true. It is also not the same thing.
Since then I’ve been an engineer again, more than once, and I’ve been a CTO. I’ve read the books, done the courses, collected the degrees, found the mentors. I’m a technical leader now, beyond any argument, and I’m still a work in progress. Along the way I learned three things. I’ll keep them short, because the longer version of this post was a listicle and I hated it.
Be humble. When you don’t know, say so, and then go find out. The higher you climb, the less feedback you get, so treat what you do get as a gift. And remember that however approachable you think you are, you’re still the person who can fire them.
Be honest. “Fake it till you make it” has its uses. Technical leadership isn’t one of them. Know what you can do, stretch within that, and ask for help when you need it. Watch how people react when you ask. It tells you a lot about where you work.
Be helpful. Your job is to make your team better. Give feedback and praise in the moment. Be generous with what you know, especially to the people who’ve been generous with you. You represent the company, sure, but you’re there because of the team. It’s depressing how many managers forget that.
I’m flawed on many levels. So very many. But of all the things that are wrong with me, “not technical” isn’t one.
* Or, “I got 99 problems but not being technical ain’t one.”
Rewritten in October 2026. The 2022 version was a language model’s draft of my notes. This one is mine, with a model holding the pen.