You just became CTO. Nobody told you it would feel like this.
The technical problems are the easy part. The hard part is everything they didn't put in the job description.
Getting the CTO title is a milestone. What follows is a transition that most people underestimate — and most companies do nothing to prepare you for. You are still expected to know the architecture, hold the technical vision, and make the engineering team function. And now you are also expected to sit in a room with the board, the CEO, and investors and speak their language. Fluently. From day one.
Very few are born knowing how to do this. The ones who figure it out faster usually had someone in their corner who had already been there.
What we work on
The six challenges that define your first year as CTO.
Every first-time CTO hits these. The question is whether you navigate them or get navigated by them.
- The technical roadmap no one wants to fund Product owns the feature roadmap. You own the technical one — infrastructure, reliability, platform, debt. The hard part is making the business care about it. How to argue for the work that doesn't show up in the demo, and how to hold the line when every sprint gets raided for features.
- The rewrite temptation The legacy codebase looks like a dumpster fire. You have opinions. But "rewrite it all" is almost never the right answer, and the cost of getting it wrong falls entirely on you. How to make the rewrite-or-iterate decision without it defining your first year.
- Managing former peers Yesterday you were one of the team. Today you're their manager. That relationship shift is one of the most underestimated challenges in the transition — and mishandling it breaks trust in both directions.
- Your first board meeting Explaining technical strategy, debt, and risk to a room that thinks software is a cost centre. How to translate, when to push back, and how to earn credibility with people who have very little patience for technical nuance.
- Hiring your first senior head At some point you need a Head of Engineering, a Head of Platform, or a VP of something — someone who will own a domain you used to own yourself. That hire is different from anything you've done before. How to know when you're ready for it, how to assess someone that senior honestly, and how to set them up to actually lead rather than just execute.
- The identity shift You were promoted for being exceptional at the technical parts of the job. This role isn't about code anymore. That shift — from maker to multiplier — is harder than anyone warns you, and it's where most first-time CTOs stall. I learned it the hard way: when the team was failing, I had failed them. When they were succeeding, we had succeeded together. The day you internalise that is the day the role starts making sense.
I've been a first-time CTO. At Jolla, I built an R&D organisation from scratch while co-founding a company and raising $50M. I've hired and led over 200 engineers across six companies. I made every mistake on this list. Now I help first-time CTOs make fewer of them — faster.
Weekly or fortnightly 1:1 calls · 6-month engagement · One spot currently available
Book a free 30-minute call →Also relevant: VP of Engineering mentoring → · CPO and VP Product mentoring →