Dear Tech Lead: The Impostor Syndrome Trap

Dear Allison,

I was recently promoted to tech lead at our fintech startup in Denver, and I feel completely like an impostor. Every morning, I wake up second-guessing my technical direction, and I find myself secretly fixing my team's code at night because I don't trust their pull requests. I am working sixty hours a week, and my span of control feels totally out of hand. I'm exhausted, I've lost touch with my own hobbies, and I'm terrified that someone will expose me as a fraud. How do I survive this steep learning curve?

Sincerely, Panicked in Denver.

Dear Panicked,

First of all, take a deep breath. You are experiencing the classic growing pains of someone who has just stepped up to tech lead. When you try to wear many hats while refusing to let go of your old habits as a senior developer, you burnout fast. You cannot be a player-coach forever without trusting your team. An ownership mentality means letting others fail and learn, rather than sneaking in at midnight to rewrite their functions behind their backs.

Stop holding back your team's autonomy. You need to set the bar for quality through clear architecture discussions, not by pulling rank or fixing their bugs in secret. Leadership style is not about knowing everything; it is about becoming a force multiplier for the brilliant engineers around you. When you give them a bird's-eye view of the product goals, you empower them to rise to the challenge.

Now, let me share a little secret with you that might make you feel better about your current situation. When I took my first lead role in Manchester years ago, I was so overwhelmed by the sudden change in responsibilities that I actually quit after just two weeks. I walked out of the office, handed in my laptop, and swore I would never manage people again. It felt like an absolute disaster at the time.

However, after spending a year working purely as an architect and observing other leaders, I realised my mistake wasn't the role itself—it was my inability to delegate and transition into servant leadership. I took the helm of another team a year later with a completely different mindset, and it was the best career move I ever made. You don't need to quit, but you do need to stop treating your team like junior interns who need your nightly supervision. Trust them, step back, and watch how they grow into their roles while you finally get some sleep.

Warmly, Jason.

Read again and choose the right answer

What is the main problem Panicked in Denver is facing?

• They hate programming and want to switch to marketing.
• They feel like an impostor, work sixty hours a week, and fix code at night.
• Their manager forced them to relocate to London.

What advice does Jason give about fixing team code at night?

• Do it only on weekends.
• Stop doing it and let the team learn through autonomy.
• Ask the CEO to help with midnight reviews.

What surprising detail does Jason reveal about his own past?

• He once quit a lead role after two weeks and took it again a year later.
• He has never written a single line of code in his life.
• He was fired from three different companies for poor performance.

According to Jason, what should leadership style focus on?

• Being the smartest coder in the room.
• Becoming a force multiplier for the team.
• Writing all documentation alone.

Sources: photo by https://kaboompics.com/ on Pexels