Loading
Back to BlogBusiness

From Engineer to CTO - What Changes When You Lead

6 min read

The Identity Crisis

The first month as CTO, I reviewed every pull request, rewrote code I did not like, and stayed up late fixing bugs myself. I was the best individual contributor on the team and the worst leader. The hardest part of becoming a CTO is accepting that your job is no longer writing the best code - it is building the team that writes the best code.

What I Had to Unlearn

As an engineer, I optimized for code quality. As a CTO, I had to optimize for shipping velocity, team morale, and business alignment - sometimes at the expense of technical perfection. That was painful. I remember approving a Next.js frontend that I would have written differently, because the team owned it, it worked, and rewriting it would have cost us a product launch.

Your job as CTO is not to be the smartest engineer in the room. It is to make sure the room full of engineers is pointed at the right problem.

The Three Hats

Every day I switch between three roles:

  • Architect - Setting technical direction, choosing technologies, defining system boundaries
  • Manager - Hiring, mentoring, removing blockers, running sprint planning
  • Business partner - Translating technical constraints into business language for stakeholders and investors

The balance shifts depending on the company stage. At Loomora's early days, I was 70% architect. Now it is closer to 40% manager, 30% business, 30% architect.

Decisions That Compound

The CTO decisions that matter most are the boring ones: hiring standards, code review culture, deployment processes, and on-call rotations. These compound over months. At Karcis ID, investing two weeks in a proper CI/CD pipeline with automated testing saved us hundreds of hours of manual QA over the next year. But in the moment, it felt like I was slowing us down.

Advice I Wish I Had Earlier

Write less code, read more code. Talk to customers directly - do not rely on secondhand requirements. Hire people who are better than you at specific things and get out of their way. And most importantly, measure your success by your team's output, not your own commits. The day I stopped tracking my own GitHub contributions was the day I actually started leading.

Have a project in mind?

Tell me what you want to build. I reply within one working day.