Climbing No More

Engineers have been reaching a common ceiling in their careers for decades. The pattern goes like this: an individual contributor gets promoted to a senior software engineer, and their career trajectory levels off. Likewise, an IC who transitions to an Engineering Manager often hits a similar wall, wondering if they’ll ever advance to a senior manager or director. In the tech industry, these are often referred to as terminal levels. These are the roles where you can build a meaningful career without having to climb further up the corporate ladder. That’s the theory, anyway. But what happens when the reality doesn’t match the promise?

In this piece, we’ll explore why staying at these levels can be a smart and deeply fulfilling career choice and why, for some, it might not be. We’ll dive into the trade-offs: what you gain by becoming a master of your craft in these roles and what you might miss by not pursuing a promotion.

What’s a Terminal Level

Most big tech companies and scale‑ups have two parallel career ladders: an individual contributor track and a management track. Each ladder has a series of levels. At junior and mid‑levels you’re expected to progress if you’re doing a good job; some companies even slap timelines on them to bring some consistency. Beyond a certain point, however, the expectation to keep climbing disappears. We call that the terminal level. This is where the organisation believes you can make a significant impact indefinitely and where promotions above become optional rather than expected. It’s the equivalent of realising you can actually live in your current house instead of constantly upgrading to a bigger one. And, that’s not a bad feeling.

For ICs, that terminal level is typically senior software engineer. For managers, it’s the line manager role leading a single team. These levels are designed so that most people can stay there for a long time, improve their craft and contribute without worrying that they’re not moving up fast enough. But here’s the concern or rather uncomfortable truth. The pay bands at these terminal levels are often narrow. Sure, compensation bands widen as you climb the ladder but if the terminal level is truly terminal, shouldn’t its band be the widest of all? In plain terms, people hit the top of their band eventually. Once you’ve hit the top of your band you may even see a zero‑percent raise. That means your salary stalls unless you change levels or switch roles. It’s not that a Senior or EM lacks impact; pay growth relies on promotion, not continued excellence. We’ll dig into this later, but keep this in mind: the ‘sweet spot’ feels less sweet once your paycheck flat-lines.

Why Are These Roles Terminal?

Here are some of the key reasons or rather some of my observations why these terminal levels exist and why they can be a positive career destination:

1. Organisational shape. Above the senior/EM level the org chart narrows dramatically. There are far fewer Staff+ Engineers, Senior Managers, Directors, or Principals. You simply can’t have ten directors for every ten teams.
2. No pressure. Companies intentionally stop nudging you after a certain point. They want you to develop expertise rather than chase titles. At most companies, for example, people can stay there indefinitely without negative stigma.
3. Different skills. Moving beyond Senior/EM isn’t just doing more of the same. It’s a role change that emphasises cross‑team influence, organisational design and long‑term vision. Not everyone wants that.
4. Personal choice. Life happens. Maybe you value coding or mentoring more than attending planning meetings. Maybe you have family commitments that make a higher‑stress role unappealing. The terminal level exists so you can keep doing great work without sacrificing your well‑being.
   

If that list reads like corporate pragmatism, that’s because it is. Going beyond is not about a lack of ambition. It is generally about geometry and sanity. The pyramid simply can’t support everyone at the top, and frankly, not everyone wants to stand up there bracing against the wind. The terminal levels give you permission to stay at the part of the pyramid where there’s space to breathe and you can still do the work you love.

The Senior Software Engineer

On paper a senior engineer is just someone with more years under their belt, but in reality you’re the one who can walk through a system like you built the beast yourself. You know why the caching layer uses Redis instead of Memcached, you remember the midnight incident when a database migration went sideways, and you’ve coached juniors through their first oncall. You own problem spaces end-to-end: designing systems, mentoring juniors, leading projects and knowing when to rip out a bad design before it costs millions.

You’re the go‑to person when something breaks in production, the one who can talk to product managers in the morning and debug a performance issue in the afternoon. You know your team’s dependencies and how to navigate them.

Scope and Influence

At this level your influence is deep rather than wide. You set technical standards, drive architecture decisions for your team and sometimes act as the technical lead for a project. You might lead a system migration, choose the caching strategy or decide how to handle scaling. What you don’t do is dictate how three other teams should coordinate their roadmaps. That’s staff territory. Many engineers find this focus satisfying: you can dive deep, still see your code ship, and avoid drowning in endless alignment documents.

Why Stay Here?

• Craftsmanship over politics. At senior level you still write plenty of code, design systems and see the direct impact of your work. If you love the craft, this is the sweet spot. You get to be the artisan, not the meeting scheduler, and you don’t need permission slips to refactor that twisted module.
• Deep expertise. You can become the resident expert in a domain. The person who knows the payment pipeline inside out. You know which engineering health issues you have and which ones need to be addressed soon. That kind of mastery is valuable and satisfying and, frankly, more fun than writing yet another quarterly planning doc.
• Balance. The scope is large enough to be challenging but small enough that you’re not drowning in meetings. Lying a bit… It’s easier to keep a 40‑hour week without sacrificing impact. You still have time to brew tea, play with the kids and maybe pick up a hobby.
• Lateral growth. You can switch teams or tech stacks to learn new skills without changing levels. You can reinvent yourself without resetting the clock.

What You Might Miss

• Broader impact. If you have big ideas that cut across teams, you might feel limited. Staff and Principal roles give you the mandate to drive organisation‑wide change.
• Recognition. Higher titles carry prestige and can open doors in the future. Staying at Senior may mean your accomplishments are less visible outside your team.
• Comp ceiling. Because pay bands at the senior level aren’t wide enough, you eventually hit the top of the band and shrink to the low single digits; in some cases they drop to zero. Once you’re maxed out in your band, it becomes difficult to get meaningful increases without changing levels.
• Misaligned rewards. Your mastery of a system is not always rewarded. At times you’ll watch an engineer who shipped fewer features but managed a cross‑team OKR leapfrog you simply because their scope fit the promotion narrative. 
• Stagnation. Without consciously seeking new challenges, you risk solving similar problems over and over. Growth doesn’t have to come from a promotion, but it does require intention.

The Engineering Manager

If senior engineers own technical depth, engineering managers own the team. They lead a group of 5–10 engineers, hire and coach people, plan projects and ensure the team delivers. An EM coordinates with product and design, sets priorities and removes roadblocks. Many EMs still write code in startups, but in large organisations their time is mostly spent on people management and execution.

Scope and Influence

A first‑line EM’s influence is also team‑bounded. You’re accountable for your team’s results and your engineers’ growth, not for defining the engineering strategy for a whole department. You’ll collaborate with peer managers and cross‑functional leads, but you’re rarely shaping the company‑wide technical direction.

Why Stay Here?

• Impact through people. Many managers love watching their team grow, facilitating collaboration and celebrating wins together. It’s rewarding to see others thrive because of your support. You become a multiplier, not a lone hero.
• Closer to product. As an EM you’re often the glue between engineering and business. You can influence roadmaps and ensure engineering work aligns with customer needs. You have a seat at the table and bring empathy for engineers into business conversations.
• Stability. Running a well‑functioning team can be deeply satisfying. You’re creating a culture and process that scales. You get to build your own mini‑kingdom rather than constantly applying to rule the next province.

What You Might Miss

• Ownership beyond one team. Some managers aspire to run multiple teams or entire departments. That’s the Director track. Making that leap means managing other managers, thinking about budgeting and long‑term org design. It’s not a badge of honour; it’s a choice to trade day‑to‑day coaching for higher‑altitude planning.
• Hands‑on work. You’ll write almost no code and may miss being in the weeds.
• Scarcity of roles. Director slots are limited and often tied to organisational growth. You can be an excellent EM and still not get the nod to manage managers because there simply isn’t room. That’s not about you; that’s about math.
• Different skill set. Managing managers requires different muscles. Strategic planning. Executive communication. Navigating even bigger politics. 

A Word on Compensation

If there’s one thing that really grinds my gears about most career ladders, it’s how money becomes the reason that forces people into roles they don’t want. I’ve always believed that a senior engineer who loves building should be able to make as much as a staff engineer who loves dancing around three teams. The same goes for an engineering manager. These are different jobs, not a hierarchy of worth. Your salary shouldn’t be the thing that drives you to give up what you enjoy.

Here’s the reality. The band structure itself encourages you to jump levels to keep your salary moving. When you’re at the top of your band, raises flatten out. It almost becomes zero, no matter how well you perform. Narrow bands push people to chase titles they don’t want, just to keep their salary growing. In other words, the compensation system treats your career like an RPG that forces you to switch classes to keep leveling. But if you’re a rogue, you don’t want to turn into a mage just to stay viable. Most people just want to keep getting better at the class they already love.

This sets up a frustrating dynamic. The only way to grow your pay is to take a job with a very different focus. A staff engineer spends much more time aligning multiple teams and writing design docs than hands‑on coding. A director deals with budgeting, hiring managers and organisational politics, not mentoring individual engineers. These roles aren’t better than the former. Yet the ladder treats them like a prize you must win to afford a nicer house. If you enjoy being a senior IC or EM, you shouldn’t have to make a career pivot just to pay your kids’ college tuition. Widen the salary bands. Let people stay where they thrive and still build wealth. No one should have to choose between work they love and their financial future. Honestly, companies shouldn’t accept the value loss that comes from incentivizing people to chase the wrong roles.

I don’t see why an EM can’t make more than a director given the realities of how work gets done. A first‑line manager can be the person shepherding a core product through its darkest nights, mentoring six engineers and owning a codebase that powers an entire business line. By contrast, a director might be three layers removed from any product heat, juggling budgets and head‑count quotas. So why should the director automatically out‑earn the person in the trenches? If an EM delivers more value and shoulders greater risk than a director, there’s no reason they shouldn’t be rewarded accordingly. My two cents!

Closing Thoughts

When I wrote about brewing Turkish tea, I emphasised the ritual over the rush. Let the leaves steep. Savor the process. The same applies to your career. The senior engineer and engineering manager roles are not dead ends. They are anchor points where you can find mastery, impact and joy. If you’re content there, embrace it. You’re not stuck; you’re serving your team and your customers in a way that only you can. Don’t let a pay band or an org chart tell you your worth.

If, on the other hand, you feel the itch to broaden your impact, recognise that moving up means learning a new craft. When you step into these roles, you need to be a strategist, facilitator and architect. The path up is narrower and steeper, but for some it’s the right climb. Climb only if you want the view, not because someone told you climbing is the only measure of success.