First Time Start-up CTO

David Umoh
Sep 17, 2019 · 4 min read

As a first-time CTO, it is important to realise you are primarily responsible for everything technology in your company and your number one responsibility is to enable your company win, using technology.

Your job will be very different at different times, dependent on the stage that your company is at. It has helped me to outline what the possible roles are and it is by no means exhaustive. I like to see it as generally divided into 2: Individual Contributor — IC and Management.

Individual Contributor

Tech Lead

Engineering Manager

Project /Product Management (Dependent on if you have a dedicated product Manager) and some of what you'd would be doing are:

  • Requirement Elicitation/Customer Development
  • Aspects of Software Architecture in collaboration with Tech leads.
  • Acting as Scrum Master

Performance Management: Defining Career Ladders, Carrying out performance reviews.

Mentorship — Holding 1-on-1s, Career Improvement plans.

Recruitment

Communication — Communicate up, Down and Across.

And an Individual Contributor, E.g Devops/QA dependent on if you have a dedicated resource.

As with most things in this role, you are to provide guidance without micromanaging. And as a manager, you should be aware of your management style. I favour Task-Relevant Maturity(TRM) or what some people call situational leadership where you either show and tell; play a more communicative or delegative role dependent on how mature your report is with respect to the task at hand. It is important to realise that TRM varies with task. So it has nothing to do with how great the person is. Your goal with TRM is to get to the point where you are able to delegate. That’s where you get the greatest leverage. And it’s important to always know the line between Delegation and Abdication. A book I found really helpful is High Output Management by the legendary Andy Grove.

As an Engineering Manager you need to be looking for areas of greatest leverage and hire or delegate out less-leverage areas as much as possible.

You will not start out being great at all these areas. So you need to go out of your way to read, take courses, learn and get feedback on your progress as these are typically different from what is required of a Software Engineer who is an individual contributor. But I think, if you are a great software engineer and you are interested in people management, you will be great at this too. Why do I think so? Because a lot of the Software Engineering skills are transferrable; the greatest of which is your ability to continuously learn. In this role, you realise what you don’t know and go out of your way to deliberately learn. If you were able to really learn and become great at Software Engineering, then I believe you could be great this too.

One thing I find could be painful, is when for any reason you want to contribute individually as an Engineer in a project, and you realise that your Engineering skills may have become somewhat 'rusty'. That may not be a problem, depending on what your career plans are. But if you are looking to be able to start up a company not too long in the future as a CTO, then you may need to stay relevant there as well. And one way I have found to stay relevant is to have a side project. Your side project at the minimum, should be relevant to the technology stack your company uses if you do not have hands-on experience in it, or one you think your company may benefit from in the not-so-distant future.

Other Roles

Other responsibilities of a CTO that may not look urgent, but are extremely important are Business Continuity Planning, IT Security and Compliance.

In conclusion, I find that a lot of books not necessarily related to any technology have been very helpful. Some of the most impactful ones include:

There are several other books too, especially if you will play an IT Ops role or have an IT Ops staff report to you as part of your core CTO Responsibilities.

I’ll like to learn about the technical management/management books that have helped you, so I could also learn from them.

Yours in the business of creating and capturing value using technology :)

Engineering Leadership Network

A Community for Engineering Leaders

David Umoh

Written by

CTO @ Gloopro.com. A full-stack developer with 9+ years experience architecting, developing and deploying web applications of various sizes and complexity.

Engineering Leadership Network

The Engineering Leadership Network is a community for Engineering Leaders. A safe place to share ideas, thinking, seek advice and to network.

David Umoh

Written by

CTO @ Gloopro.com. A full-stack developer with 9+ years experience architecting, developing and deploying web applications of various sizes and complexity.

Engineering Leadership Network

The Engineering Leadership Network is a community for Engineering Leaders. A safe place to share ideas, thinking, seek advice and to network.

Medium is an open platform where 170 million readers come to find insightful and dynamic thinking. Here, expert and undiscovered voices alike dive into the heart of any topic and bring new ideas to the surface. Learn more

Follow the writers, publications, and topics that matter to you, and you’ll see them on your homepage and in your inbox. Explore

If you have a story to tell, knowledge to share, or a perspective to offer — welcome home. It’s easy and free to post your thinking on any topic. Write on Medium

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store