From IC to Tech Lead: What Nobody Tells You

When I was promoted to Technical Software Lead at The Knot Worldwide, I thought I knew what the job would be. I had been a Senior Engineer for years. How different could it be? The answer: very. Here are the things nobody warned me about.

Your Calendar Becomes Your Primary Tool

As an IC, my calendar had a few standups and the occasional design review. As a Tech Lead, my calendar filled up within the first week. Cross-team syncs, stakeholder updates, one-on-ones, architecture reviews, hiring panels. These are not interruptions — they are the job.

The adjustment was painful at first. I felt unproductive because I was not writing code. It took me months to internalize that my impact was now multiplied through the team, not through my individual output.

You Stop Being the Best at Everything

As a senior IC, I was the person who knew every corner of the codebase. As a Tech Lead, my team members started writing code I had never seen, in patterns I had not approved, solving problems I had not scoped. This is a good thing. It means the team is scaling. But it is uncomfortable.

The skill shifts from "I know the answer" to "I know how to help you find the answer." Your value becomes enabling others to make good decisions, not making every decision yourself.

Communication Is More Than Half the Job

This was the biggest surprise. Writing clear project proposals, communicating timelines to stakeholders, documenting architectural decisions, giving feedback that lands well — these are not soft skills. They are the primary skills of the role. A technically brilliant Tech Lead who cannot communicate is a bottleneck.

I started spending deliberate time on communication: writing better RFCs, clarifying ambiguity in tickets, and over-communicating during incidents. The team's velocity improved measurably.

Mentorship Is the Best Part

If I had to pick one thing that gives me the most satisfaction, it is mentorship. Watching a junior engineer gain confidence, ship their first big feature, or handle an incident calmly under pressure — these moments are genuinely better than any code I have written.

Good mentorship is not about giving answers. It is about creating space for people to figure things out, providing guardrails, and being there when they get stuck. The hardest part is knowing when to step in and when to let them struggle productively.

Decision Fatigue Is Real

As a Tech Lead, you make dozens of small decisions every day: which approach to take, what to prioritize, how to handle a production issue. By the end of the day, your decision-making capacity is depleted. I learned to batch non-urgent decisions to mornings, defer reversible decisions quickly, and trust my team to make calls on their own.

If You Are Considering the Switch

The IC to Tech Lead transition is not a promotion in the traditional sense — it is a career change. You trade depth for breadth, code for coordination, and personal productivity for team productivity. It is not for everyone, and that is fine. Great ICs are invaluable, and staying on that path is a perfectly valid choice.

But if you enjoy mentoring, thrive on ambiguity, and want to multiply your impact beyond what you can build alone, the transition is worth every uncomfortable moment.