[cebert]

You don’t think not even progressing to a senior engineering role or lead engineer role after two decades in the profession would be a red flag? These are still IC roles, just more senior. I would sure have a lot of questions at least.

[piva00]

That's your personal bias showing, I'd never be questioning anyone who decided they found a good role where they feel competent and secure about their job and craft, much the contrary as Peter's Principle usually apply very quickly to the careerists.

Senior engineer is usually where a lot of competent folks stop, the role of Staff/Principal starts to become quite different, some people just want to be good at helping the business to build things. A good senior will be the necessary glue between team and the larger org (including the Staff/Principal layer), facilitating a lot of stuff that isn't immediately visible but is definitely felt when you miss it.

On top of that, there's not even close to enough positions to promote every single senior engineer to a higher level in most companies. Not everyone wants to play the career game.

[coffeebeqn]

Sr Engineer is a terminal role for most people. If you can build quality software and are a somewhat pleasant human being then I don’t see anything wrong with it. If everyone’s a director then who’s getting the work done? There aren’t that many leadership roles compared to IC roles.

[theduder99]

not a red flag at all..as long as they are competent at dev work. Many devs just want to dev and have no interest in taking on lead responsibilities, architecture, negotiating with product owners, attending lots of unproductive meetings, etc.