For engineers becoming managers
You know how to build software.Now learn how to lead people.
Practical guides for Senior Engineers, Tech Leads, and new Engineering Managers. Plan your first 90 days, delegate with clarity, and give feedback your team can act on.
Free guides. Read without signing up.
Still deciding whether management is right for you?
Explore the move from engineer to manager
Where are you in your transition?
This is the mental shift
You used to move work forward by doing it yourself. Now you move it forward by making the work clear for someone else.
The Four W questions make that concrete before a handoff:
- Why: What problem does this work solve?
- What: What result do we need?
- Who: Who owns it, and do they have capacity?
- When: When is the result needed?
What do you need help with this week?
Build trust with your team
Build everyday habits that make it easier to raise concerns, ask for help, and work together.
Decide what matters first
Make trade-offs explicit when everything feels urgent and your team needs direction.
Delegate without taking the work back
Agree on outcomes, boundaries, and check-ins so someone else can own the work.
Give specific, useful feedback
Use the FUKO structure to connect facts, impact, and expectations in your next feedback conversation.
Clarify who can decide
Agree on which decisions engineers can make themselves, which need an update, and which need approval.
Help your team take ownership
Give engineers room to make decisions, solve problems, and grow beyond the next task.
Hi, I’m Bartosz Pater.
My background spans software engineering, architecture, and team leadership. Before becoming an Engineering Manager, I worked as a Senior Engineer, Software Architect, and Scrum Master.
I created Engineering Leadership to share what I wish I’d had during that transition: clear explanations, worked engineering examples, and tools you can adapt to your team.
More about my experience →