technical leadership | engineering management | new manager training | first time manager | tech team lead | delegation
What You Will Learn:
- Decide what a technical leader owns and what stays with the engineers
- Delegate a task you could do faster yourself, and not take it back
- Run a one-to-one that produces something rather than filling a slot
- Choose and develop a deputy so the team survives your absence
- Handle the brilliant, difficult expert on your team
- Set goals with OKR and connect them to what the team actually does
- Ask a question instead of giving the answer, using GROW
- Set up a mentoring pair and close it properly when it has done its work
- Control quality without turning into the person everyone routes around
- Learn alongside Mike’s 1.6 million students from 185 countries
The “Expert to Leader” Transition: My Honest Take
Let’s be real for a second: most of us got into tech because we love solving puzzles, not because we wanted to spend six hours a day in meetings. But then it happens—you’re the top performer, you’re the one everyone goes to when the server melts down, and suddenly your reward is a promotion to tech team lead. You’re thrilled about the career growth, but within a week, you realize that your job-ready skills in Python or AWS architecture mean absolutely nothing when two developers are arguing over a pull request or a project is slipping.
I’ve seen plenty of “leadership” courses that feel like they were written by HR professionals who haven’t seen a terminal in a decade. Mike’s course, Leadership for Technical Experts: Expert to Leader, is a refreshing departure from that fluff. This isn’t just about “being nice” to people; it’s about the psychological pivot from being the smartest person in the room to being the person who ensures the smartest people are actually productive. It tackles the core anxiety of every new manager training: the fear that if you stop coding, you’re losing your edge. This course argues that your new “edge” is your team’s collective output, not your individual GitHub green squares.
What I appreciated most was the focus on the “Ego Death” required for engineering management. Mike breaks down the specific friction points where technical experts usually fail, like the “hero complex” where you jump in to fix a bug because it’s faster than explaining it. He gives you a framework to stop being a bottleneck and start being a multiplier, which is the most critical shift for any first time manager.
Prerequisites
- Senior-level technical experience: You should have a solid handle on your tech stack. This isn’t for juniors; it’s for those ready to move from beginner to advanced levels of organizational influence.
- Direct Reports (or a promotion in sight): You’ll get the most out of the real-world projects and scenarios if you have a team (or at least a mentee) to apply these frameworks to immediately.
- Humility: You have to be willing to accept that your technical brilliance is now a secondary skill.
Skills & Tools You’ll Master
- The GROW Model: A coaching framework that keeps you from just giving the answer (and therefore keeping your team dependent on you).
- OKR Frameworks: Using industry-standard tools like Objectives and Key Results to align your team’s daily tickets with the company’s actual business goals.
- Effective Delegation: Learning how to hand off hands-on labs and tasks without losing sleep over the quality of the deployment.
- Conflict Resolution: Specifically tailored to the “brilliant but difficult” personality type that exists in every high-performing dev shop.
- Mentoring Architecture: How to set up and successfully sunset a mentoring relationship.
Career Benefits & Job Roles
Completing a course like this is essentially certification prep for the “soft” side of high-level tech roles. It moves you out of the “replacable developer” bucket and into the “strategic leader” bucket. The career growth potential here is massive; we’re talking about moving from a Senior Dev salary ceiling to the compensation structures of an Engineering Manager, VP of Engineering, or CTO.
Companies are desperate for people who speak “Engineer” but can also speak “Business.” By mastering these skills, you become the bridge. You aren’t just managing Jira tickets; you’re managing the human capital that builds the product. This is how you secure roles in technical leadership at Tier-1 tech firms where the interview process focuses heavily on behavioral leadership scenarios.
Pros
- No Fluff, All Function: Mike skips the motivational posters and gets straight into the mechanics of 1-to-1s and delegation. It feels like a real-world project for your career.
- Addressing the “Brilliant Jerk”: Most courses ignore the fact that some experts are hard to work with. This course gives you actual tactics to manage the person who is technically gifted but socially destructive.
- Scalable Systems: The advice on creating a deputy is a lifesaver. It’s the difference between a vacation where you’re on Slack all day and a vacation where you actually unplug.
Cons
- Heavy on Theory: While the concepts are industry-standard, I would have liked to see more downloadable templates or specific software recommendations (like specific 1:1 tracking tools or OKR dashboards) to make it even more turn-key for busy leads.