Engineering Leadership

You know how to build software.  
Nobody taught you how to lead people.

Practical guidance for Senior Engineers, Tech Leads, and first-time Engineering Managers 
transitioning from writing code to leading people.

Is this for you?

This site is for you if:

  • You were recently promoted from Senior / Staff / Principal Engineer
  • You are stepping into your first Engineering Manager role
  • You are a Tech Lead now responsible for people, not just code
  • You feel stronger in engineering than in leadership conversations
  • Delegation feels unnatural or risky
  • Giving feedback feels uncomfortable
  • Your calendar is full, but your impact feels unclear
  • You manage former peers and are still redefining relationships
  • You are learning management through trial and error

If that sounds familiar - you’re in the right place.

The problem nobody explains

You didn’t fail into management. You were promoted because you kept growing as an engineer and became good at building software.

But now the rules have changed:

  • You are no longer measured by what you build.
  • You are measured by what your team builds without you.

And almost nothing in your engineering experience prepares you for that shift:

  • Meetings replace coding time
  • Delegation feels slower than doing it yourself
  • 1:1s feel awkward or repetitive
  • Feedback feels risky
  • You become a bottleneck without noticing it
  • Former peers see you differently
  • You’re constantly firefighting

And eventually a quiet question appears:

“Am I actually good at this?”

This is where most engineers quietly start underperforming as managers.

This is not a personal failure. It is a transition problem.

What changes when it clicks

A different kind of week:

  • You start with clarity instead of chaos.
  • Work moves without you in every detail. You trust your team with ownership.
  • 1:1s become real conversations. Feedback becomes normal, not stressful.
  • Former peers respect you — not because of title, but because of how you lead.
  • You still think like an engineer — but you apply that thinking to people systems.

That is the shift: From IC → Engineering Manager.

What you will learn here

Building Trust

Create the psychological safety that makes feedback land, risks surface early, and teams move faster.

Prioritization

Decide what matters when everything is urgent and your team is waiting.

Delegation

Hand off work with clarity so it gets done well — without you doing it yourself.

Effective Feedback

Give direct, useful feedback without damaging relationships.

1:1 Meetings

Run 1:1s that build trust and surface real issues — not status updates.

Developing People

Grow engineers beyond the next task — career conversations, ownership, and helping people reach their potential.

Start here

If you’re new, start with these four articles:

1. From IC to Engineering Leader
The mental shift that changes everything. What to let go of, what to lean into, and why your old definition of a good week will hold you back.
2. Your First 90 Days as an EM
A practical survival roadmap. Week by week: listen first, build relationships, then start shaping how the team works.
3. Building Trust in Engineering Leadership
Trust is the operating system of strong teams. Learn the practical habits that make feedback, ownership, and delivery easier.
4. What Is Engineering Leadership?
The 3Ps framework — Product, Process, People — and why balancing all three is the real job of an engineering leader.

About the author

I’m Bartosz.

I spent over a decade building software before becoming an Engineering Manager. Like many engineers, I assumed strong technical skills would automatically translate into leadership skills. They don’t.

I struggled with:

  • Delegation
  • Difficult conversations
  • Trying to stay the strongest engineer while managing people

It didn’t work.

So I started collecting what actually works:

  • Giving feedback without friction
  • Delegating without losing control
  • Running 1:1s that matter
  • Leading people instead of tasks
  • Developing People and Teams

This site is everything I wish I had at the beginning of that transition.

Engineering Leadership Weekly

Every Friday you’ll receive one practical engineering leadership idea you can apply immediately—a conversation technique, management insight, proven framework, or tool from real-world experience.

No spam. You can unsubscribe anytime.

Engineering Management isn’t a harder version of software engineering.

It’s a different discipline.

Instead of writing better code, you create the environment where other people can do their best work.

Your focus shifts:

  • From code to people
  • From implementation to influence
  • From output to outcomes

You won’t become a great Engineering Manager overnight.  
It happens one conversation, one decision, and one lesson at a time.  
Start small. Apply one idea. Improve one interaction.

That’s how great Engineering Managers are built.