Engineering Manager to Senior EM: Breaking the Ceiling

Nia: You know, Jackson, I was talking to a friend who’s been an Engineering Manager for about three years now. She’s hit all the milestones—hiring, delivery, great one-on-ones—but she told me she feels like she’s hitting a ceiling. It’s that "what now?" moment.

Jackson: That’s so relatable. It’s a common trap to think the Senior EM role is just doing your current job but… more of it. But the real shift is actually counterintuitive. It’s not about being a "super-manager" for your team; it’s about moving from team-centric execution to organizational leverage.

Nia: Right, like instead of just making your eight engineers effective, you’re looking at how the whole department handles incidents or how the entire hiring process works. It’s a huge jump in ambiguity.

Jackson: Exactly. You’re moving away from a clear playbook into a space where you have to identify the problems yourself. Let’s explore how to start building that broader influence and navigating that shift in scope.

Jackson: It really is a shift in how you see your own value, Nia. Most Engineering Managers—even the great ones—measure success by their team’s output. Are the tickets moving? Is the sprint on track? But for a Senior EM, the metric changes to organizational leverage. You aren’t just a manager anymore; you’re becoming a multiplier for the entire engineering department.

Nia: That word "multiplier" is so powerful, but it’s also a little intimidating, right? I mean—if I’m not just focusing on my team’s daily standups—what am I actually doing? It feels like you’re stepping away from the "safety" of concrete tasks into this vast, blurry space of "initiatives."

Jackson: You’ve hit the nail on the head. It’s that jump from execution to strategy. Think of it this way—a regular EM makes their team effective. A Senior EM makes the company better at engineering. That might mean you’re the one designing a new incident response standard that every team will use—or maybe you’re building a formal mentoring program for new managers across the whole org.

Nia: Oh—so it’s about solving problems that don't just stop at your team's virtual front door. It’s like—if my team is struggling with a clunky deployment process—instead of just fixing it for us—I’m looking at whether every team is hitting that same wall and how I can fix it for everyone.

Jackson: Exactly. And that requires a massive increase in your comfort with ambiguity. As an EM—your director usually gives you a fairly clear direction. But as a Senior EM—you’re expected to find the problems yourself—propose the solutions—and drive the execution with very little guidance. You’re essentially writing the playbook while you’re playing the game.

Nia: Which is why it feels like such a growth spurt—right? You’re moving from being a "delivery owner" to being an "organizational architect." It’s less about the "how" of the code and more about the "how" of the people and the systems they work in.

Jackson: And speaking of systems—the complexity of the teams you manage usually scales up significantly at the senior level. We aren't just talking about more engineers—it's often about managing teams with much more difficult organizational dynamics or high-stakes strategic importance.

Nia: I was reading about how Senior EMs are often the ones called in when a team is going through a rough transition—like rebuilding after a lot of people left—or taking on a project where the technical requirements are totally up in the air. It’s almost like being a "special ops" manager for the toughest situations.

Jackson: That’s a great way to put it. To get ready for that—you actually have to seek out that messiness now. If there’s a cross-functional initiative with an ambiguous scope—volunteer for it. If a team is struggling—offer to help. You have to resist that very human urge to immediately escalate a problem to your boss. Instead—practice developing a point of view—making a recommendation—and then communicating your reasoning.

Nia: It sounds like you’re building a muscle for "informed decisiveness." But I wonder—how do you do that without losing touch with the ground truth? If you’re managing managers—or a massive team—you’re naturally further away from the code.

Jackson: That is the ultimate balancing act. One of the sources I saw mentioned that you have to shift your assessment style. You can’t just look at a pull request anymore to see how an engineer is doing. You have to look at indirect signals—team health metrics—delivery patterns—and the quality of the decisions your team is making.

Nia: Right—it’s like you’re looking at the weather patterns instead of just checking a single thermometer. And if you’re managing other managers—your job is to coach them—not to solve their problems for them. If you jump in and fix everything—you’re actually undermining their authority and stopping them from growing.

Jackson: Precisely. You have to provide frameworks—not prescriptions. Ask them—"What have you considered?" or "What are the trade-offs here?" instead of saying—"Here is what I would do." It’s about building a self-sustaining leadership team that can operate without you as the bottleneck.

Nia: So—if we’re pulling back from the day-to-day execution—where is all that extra time and energy going? It feels like a lot of it has to go toward building relationships—and not just with other engineers—right?

Jackson: Absolutely. This is where your "cross-functional diplomacy" comes in. At the Senior EM and Director levels—your most important relationships shift. They move from your direct reports to your peers in Product—Design—and even Finance or Operations. You have to start speaking their language.

Nia: I love that idea of being a "translator." A VP of Product doesn’t need a deep dive into your CI/CD pipeline architecture—they need to know how that pipeline affects the speed of feature delivery and the reliability of the product for the customers.

Jackson: You’ve got it. It’s about connecting the technical work to the business objectives. You have to be able to tell a compelling story about why a technical investment—like paying down tech debt—actually drives long-term business value. If you can’t articulate that—you’re going to struggle to get the resources your team needs.

Nia: And that visibility with leadership is so key for the promotion—isn’t it? But it’s not just about "self-promotion" in a cheesy way—it’s about demonstrating value where they can see it. Presenting at all-hands—contributing to long-term planning—showing that you understand where the company needs to be in two years—not just two weeks.

Jackson: Right. And don't forget the importance of your own manager’s advocacy. You need to have a relationship that goes way beyond status updates. You should be sharing your career aspirations—asking for honest feedback on your gaps—and proving you can handle the "real talk" about your development.

Nia: It’s also about building bridges with leaders outside your direct chain of command. If a Director of Product has seen you navigate a high-pressure trade-off—they become a powerful advocate for you when the promotion cycle comes around. They’ve experienced your impact firsthand as a reliable partner.

Jackson: One of the biggest hurdles I see for aspiring Senior EMs is the "single-threaded processor" trap. If every decision—every architectural review—every escalation has to flow through you—you’ve become a bottleneck. You aren't just slowing the team down—you're actually preventing your own promotion because you're "too essential" in the weeds to move up.

Nia: Oh—that’s a tough pill to swallow! So—delegation isn't just about clearing your calendar—it's about building team resilience. If I’m doing everything—nobody else is learning how to do anything.

Jackson: Exactly. You have to be ruthless about categorizing your work. There’s work only you can do—like performance reviews or sensitive personnel matters. But then there’s work someone else could do just as well—or even better. You have to give away the "interesting" work—not just the administrative tasks.

Nia: That’s a mistake I see a lot. Managers delegate the boring stuff—like scheduling or documentation—and keep the cool technical strategy for themselves. But it’s the strategy work that actually helps your senior engineers grow into leaders!

Jackson: Spot on. When you delegate—you have to be incredibly clear about the outcome—the constraints—and the level of autonomy. Don't just say—"Handle this." Say—"I need this outcome by this date—the approach is yours—but here are the three things we cannot compromise on."

Nia: And then—the hardest part—you have to let them do it their way! Even if it’s different from how you’d do it. Unless there’s a genuine risk—like a security flaw or a massive technical debt issue—you have to let them exercise their own judgment.

Jackson: It’s the "trust but verify" model. You set up check-in points that are proportional to the risk. If it’s a high-stakes project for a junior person—you check in more often. If it’s a senior lead—you pull back. But if you swoop in the moment things get difficult—you teach the team that you don't actually trust them. You have to be the coach—not the player-coach.

Nia: We’ve talked a lot about the high-level strategy—but I keep coming back to the people. Even as a Senior EM—or a Director—the "human" part of the job doesn't go away—it just scales. I was looking at the GitLab handbook—and they say Engineering Managers should see their team as their "product."

Jackson: I love that framing. Your "product" is the health—hiring—and success of the humans in your care. And a huge part of that is mentorship. But at the senior level—you can’t be the only mentor. You have to build a "mentorship culture" where everyone is teaching everyone else.

Nia: Right—because one-on-one mentorship doesn't scale as you grow. You have to create the conditions for peer mentorship—like brown bag sessions—tech talks—or even just pairing a backend engineer with a frontend lead so they gain that "system-wide" perspective.

Jackson: And you have to be intentional about it. Mentorship often gets crowded out by delivery pressure—especially in remote environments where you don't just "bump into" people. As a leader—you have to protect that time. You have to show that growth is just as important as shipping.

Nia: It also helps with retention—doesn't it? When people feel like they’re actually learning and being sponsored for new opportunities—they’re way less likely to burn out or look for the exit.

Jackson: Absolutely. And when you’re managing managers—your mentorship shifts toward coaching them on their "soft skills." How to give tough feedback—how to handle team conflict—how to stay calm during an incident. You’re essentially mentoring the next generation of leaders.

Nia: It’s a beautiful cycle—really. You grow by helping others grow. And that’s what creates a healthy engineering culture. It’s not about the perks or the snacks—it’s about psychological safety—transparency—and a shared sense of mission.

Jackson: So—to everyone listening who’s feeling like they’re at that "EM ceiling"—let’s get practical. What can you do starting tomorrow to show you’re operating at that senior level?

Nia: First—I’d say—look for the "gaps" in your organization. Is there a process that everyone complains about but nobody has fixed? A hiring bottleneck? A lack of clarity around on-call? Pick one of those "department-wide" problems and start building a proposal. That’s your organizational leverage right there.

Jackson: Great one. My second piece of advice—start tracking your time. If you’re spending 80 percent of your day in the weeds of your team’s specific tickets—you’re over-functioning as an EM. Practice delegating one meaningful technical decision or project lead role to someone on your team this week. Clear that space for strategic thinking.

Nia: Third—set up a skip-level meeting—but do it right. Don't go in to make decisions or undermine your tech leads. Go in to listen. Ask the engineers what’s frustrating them—what they’re proud of—and what they need from leadership. It keeps you connected to the "ground truth" without micromanaging.

Jackson: And fourth—initiate that direct conversation with your manager. Don't wait for them to notice you're ready. Bring the evidence. Show them where you’ve had an impact beyond your team. Ask—"What gaps do you still see between where I am and the Senior EM role?" and then—create a plan together to bridge those gaps.

Nia: I think it’s also important to remember that this transition takes time. The typical timeline is two to four years as an EM before moving to Senior. It’s a marathon—not a sprint. Focus on the impact—not just the clock.

Jackson: Exactly. And if the level doesn't exist at your current company—you have a choice. You can advocate for creating it—which is a great exercise in organizational design—or you can look externally for a company that offers the scope you’re craving. Both are valid paths to growth.

Nia: You know—Jackson—talking through all of this—it makes me realize that the move to Senior EM is really an invitation to be more fully human as a leader. You’re letting go of the control over the code—and instead—you’re leaning into the complexity—the empathy—and the vision required to lead people through ambiguity.

Jackson: That’s a beautiful way to frame it. It’s a shift from being a "fixer" to being a "facilitator." It’s about creating the environment where other people can do the best work of their lives. And that’s a pretty incredible mission to have.

Nia: It really is. I’d love for our listeners to take a moment today and reflect—where are you still holding on to "execution" because it feels safe? And what’s one area where you could step out into that "ambiguous" space and try to solve a problem for the broader team or the whole company?

Jackson: That’s the perfect starting point. The growth happens right at the edge of that discomfort. Thank you so much for joining us for this deep dive into the evolution of an engineering leader.

Nia: Yes—thanks everyone for listening! It’s been so great to explore this shift with you. We hope you feel a little more empowered to start writing your own playbook for that next level. Take care of yourselves—and your teams—and we'll see you in the next one!

Jackson: Absolutely. Take those small steps—and remember—leadership is a practice—not a destination. Reflect on what you’ve heard today—and maybe try applying just one of those ideas this week. Thanks again for spending this time with us.