Honest and grounded
No grand leadership theories, just situations I face every week and what to do about them.
Browse
Make the move from engineer to manager: one on ones, feedback, delivery, hiring, performance and working with your own manager
Created by Samuel Mensah
Most engineering managers are promoted because they were good engineers. Then, almost overnight, the skills that made them successful matter less, and a new set of skills they were never taught matters a lot. This course is a practical guide for that transition, written for your first year in the role.
Each lesson focuses on a situation you will meet, with scripts, agendas and templates you can adapt. We follow a fictional new manager, Rui, who takes over a team of six engineers he used to work alongside. His mistakes and recoveries make the advice concrete.
New engineering managers, tech leads taking on people responsibilities and senior engineers considering the move. The examples come from software teams, but most of the advice applies to any technical team. If you are deciding whether management is for you, the first section will help you understand what the job really involves before you commit.
Engineering manager teaching practical leadership for engineers who now lead people
I was a backend engineer for years before moving into engineering management, and I still remember how unprepared I felt in my first month. Since then I have managed teams, managed other managers and helped many engineers make the same transition.
I teach leadership as a set of learnable habits: one on ones, feedback, delegation, hiring loops, technical decision records and running a team rhythm that protects focus. I try to be specific. Instead of abstract principles you get scripts, agendas and templates, plus the reasoning behind them.
My courses are for new managers, tech leads and senior engineers who want to grow their influence without losing touch with the work.
No grand leadership theories, just situations I face every week and what to do about them.
Every mistake Rui made in week one, I made too. The delegation lesson alone would have saved me months of stress.
Small, frequent feedback using the simple model made my one on ones far more useful.
I used the difficult conversation opener almost word for word. It went much better than I feared.
Tracking my time for a week was eye opening. I cut eight hours of meetings without anyone complaining.
I am a tech lead without direct reports. Most of the delivery and people sections still applied.
The structured interview and debrief lessons improved our hiring loop. I wanted more on remote teams.
Good principles, but promotion and performance processes vary a lot. The course acknowledges that, which helps.