The three key CTO skills

I’ve been CTO of HappyFunCorp since last year, and it has been a deeply edifying experience. Everything people told me was largely true: I write less code; I go to more meetings, and turn out in more conference calls; I suppose more strategically, and less tactically; my day is spent in a more fragmented and kaleidoscopic manner.

Oh, yeah — and I’m a lot more involved in bizdev and sales. I’m, uhhhh , not always in perfect consonant arrangements with Sam Altman, but he pretty much nailed this one 😛 TAGEND

There are, however, a few things that amazed me.

HFC is more a services company than a product one — i.e. we construct products for our clients — so CTOdom is a little more ill-defined than it is at other places. I don’t identify and decide how to evolve the tech stack which is our competitive advantage, because, well, we have so many of them.( We build web services, smartphone apps, blockchain ecosystems, etc ., and we’re a “right tool for the right job” company .) I do try to foster excellence and a coherent team spirit across our very distributed team. I do a lot of assessment and estimation. And I talk about tech to clients, and prospective clients, a whole lot.

In doing so I have found there are really three key transferable skills here, all of which I used fairly extensively when I was more of a coder, but which just maintain getting more and more important the more senior you become. And they are 😛 TAGEND

Reading . I’ve always read like the wind; good thing, too, because nowadays I need to. Machine-learning papers and Github READMEs and API documentation and technical tutorials. Aspirational design documents and Statements of Require from clients. Emails and Slack backlogs. Oh, and the read just required to keep up with the state of the art in general, when “the art” covers nearly every facet of software engineering. That is, I assure you, a lot of words.

Writing . The they are able to crank out thoughtful, coherent, and concise prose on demand and on short notice — explaining problems to clients, explaining projects to engineers, breaking down projected solutions into their granular constituent parts, summarizing technologies for the non-technical, summarizing business requirements for the technological, all utilizing the written word so that there is a tangible record that can be referred to later on — is well past “valuable.” You might believe I overstate the great importance because it comes so easily to me thanks to my weird background. But frankly I guess I probably understate it for that same reason.

Empathy . Easily the most important of the three. Communication is often futile if you don’t understand the person you’re communicating with. Whether I’m talking to a curious client, a frustrated project director, a questioning engineer, or a speculating designer, I need to be able to identify with them, put myself in their shoes, and see the costs and benefits from their own personal point of view. If you can’t do that, it’s very hard to help them, or yourself.

Obviously I’m stacking the deck a bit here. Plainly a deep and broad technological background, and a track record in the furrows writing a panoply of software myself, are crucially important too. But the most striking thing about growing more senior in the tech industry is how, more and more , non-technical skills — dare I say it, liberal-arts abilities — begin to dictate your success and/ or failing. Food for thought.

Make sure to visit:


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s