ITU
Back to Blog
Engineering Leadership · [2026-11-05] · 2 min read

From founder-engineer to technical lead: what changes

Review, scope, and ownership when you stop being the only person who can ship.


// Article
447
Words
2
Tags
2 min
Read Time

// Content

I spent more than a decade as co-founder and CTO of Zitux. The job was to make the product exist: architecture, delivery, and operations, usually in the same week. That habit does not survive contact with a remote team you do not sit next to.

The useful change is not “I stopped writing code.” I still write and review it. The change is what I am allowed to be the bottleneck for.

What used to work

When you are the founder-engineer, context lives in your head. A Saturday patch is cheaper than a design doc. Production is a machine you know by sound. Hiring is optional; throughput is personal.

That mode built a company. It also trains you to treat every ambiguity as something you should absorb.

What has to change

Review. On a distributed team the pull request is the conversation. If I skip it because I could merge faster myself, I steal the only shared artifact the next timezone has. I review for the boundary, the test, and the rollback, not for taste.

Scope. A founder can change the week’s plan in Slack. A lead who does that to people eight hours away creates thrash that looks like “they are slow.” I would rather cut scope in writing than expand it in a huddle they cannot attend.

Ownership. If every incident still pages me first, I have not built a system. I have built a dependency. Ownership means a named engineer, a documented path, and a review that would catch the same bug if I were offline.

Time zones. GitHub is the office. Specs, checklists, and recorded decisions are not ceremony. They are how Quito, Phoenix, and a contractor in another country share a trunk. I lead AvenFort that way now: delivery through review, not through being online at the same hour.

What should not change

You still have to read the code. A lead who only manages process cannot tell a harness leak from a product leak. You still have to ship something yourself often enough that your review comments are specific.

You still have to say no. Founder-engineer no was “we cannot afford it.” Technical-lead no is “that crosses a boundary we will pay for later.” Same muscle, different evidence.

The uncomfortable part

The identity hit is real. Being the person who can fix it at 1 a.m. felt like the job. Being the person who makes sure someone else can fix it at 1 a.m. feels like stepping back. It is not. It is the only way the work survives you.

If a system only works when you are in the loop, you do not have a platform. You have a shift.

// Work With Me

Hiring a technical lead who still reads the code?

I went from founding and running the stack to leading remote engineers through GitHub. Open to US and global lead roles.

Contact

// Share

Share this article with your network


Ecosystem