Live data from Hacker News

Don't become an engineering manager

newsletter.manager.dev

71–80 of 281 posts

Re: Don't become an engineering manager

#71
I'm a former EM who would never go back in an AI age.

EMs deal with friction and from my experience more output is more friction.

You have org leaders and businessy people putting their foot on the gas because AI is so productive and then programmers shipping 2-3x more code.

These two forces collide and you're stuck dealing with the friction so 10x the amount of initiatives you did before.

The friction is like sandpaper on sandpaper.

Re: Don't become an engineering manager

#72

There is a major gap in this analysis by not controlling for industry or companies. Engineering Manager is a very generic title, so this is going to get Start Ups, Big Tech, Little Tech, Enterprise, Contract Shops, etc. Staff Engineer is very uncommon in Enterprise or Contract shops, there you typically see SWE 1/2/3 -> Tech Lead -> Architect. Most Tech companies I think have more of a SWE 1/2/3 -> Staff Engineer ->…

> Engineering Manager positions often have more of an upside with bonuses / incentives than Engineers get Not really. Staff Eng and above will end up making similar to an EM including bonuses and has much more job mobility. You have to remember that most EM roles only open up once you hit Staff, so you are basically taking much more responsibility and longer hours for a marginal salary impact. Engineering Manager job…

> Staff Eng .... has much more job mobility

Not really.

Above Staff and Staff+ companies are usually looking for expertise in domain, in addition to cross org leadership. Unless you want to get hired with Sr title.

Management is different though, you have highly transferrable skillset, managing people, up and down.

Re: Don't become an engineering manager

#73
post #61

Earlier quoted context omitted.

As others have said, levels and titles are generally for compensation and performance reviews. Each company has their own bespoke ladder but it generally maps to: - L1: Intern with undergrad degree - L2: Intern with graduate degree - L3: Junior - L4: Intermediate - L5: Senior - L6: Staff - L7: Senior Staff - L8: Principal - L9: Distinguished - L10: Fellow Each company has their own numbers and names but it generally…

You're describing a very small number of companies that all copied each other's systems. The idea of a terminal role, for example, is pure Facebook. These do not apply in general across the industry except where managers from those small number of companies came in and shoved them in before they were fired.

Amazon had the concept of terminal role (SDE2, but I’ve heard it has changed) long before facebook existed.

Re: Don't become an engineering manager

#74
post #61

Earlier quoted context omitted.

As others have said, levels and titles are generally for compensation and performance reviews. Each company has their own bespoke ladder but it generally maps to: - L1: Intern with undergrad degree - L2: Intern with graduate degree - L3: Junior - L4: Intermediate - L5: Senior - L6: Staff - L7: Senior Staff - L8: Principal - L9: Distinguished - L10: Fellow Each company has their own numbers and names but it generally…

You're describing a very small number of companies that all copied each other's systems. The idea of a terminal role, for example, is pure Facebook. These do not apply in general across the industry except where managers from those small number of companies came in and shoved them in before they were fired.

In my experience a lot of tech companies, at least in the Bay Area, have all copied this system.

Re: Don't become an engineering manager

#75

Earlier quoted context omitted.

> There's this idea that there's a "dual ladder", and the IC ladder offers just as much respect and compensation as the management one It is not a lie. It is true IF you live and work in the Bay Area, Seattle, and TLV - which represent the bulk of tech industry employment. Companies where the underlying stack is a revenue generator and not a cost center are companies where these kinds of dual tracks exist, but these…

Sorry, I guess we'll have to agree to disagree. The ladders are simply not comparable, even in the Bay Area. Sure, at the entry point where one transfers from the IC ladder to management compensation can even drop. However, that's the bottom rung - and one typically can't get straight into management as a new grad. The management ladder goes higher.

Best to remember this isn't a ladder but rather a tree. Yes, it goes much higher, but you chances of ever getting there is minimal because it narrows so quickly.

Re: Don't become an engineering manager

#77
post #4

I cannot be alone in feeling that titles (within "tech" in particular) are almost completely arbitrary? What constitutes a "senior", "lead", "principal" and "staff" X, respectively, has so much overlap that it really depends on the organisation. I myself have been called all of those things, but have honestly not been able to tell the difference: in some cases, I have had much more responsibility as a "senior backend…

This is exactly why we built https://www.levels.fyi

Too often people were getting down-leveled because they didn't know any better. The level comparisons we show on the homepage compare scope and responsibilities. People frequently think levels are based on compensation but compensation is the byproduct of it.

Re: Don't become an engineering manager

#78
post #4

I cannot be alone in feeling that titles (within "tech" in particular) are almost completely arbitrary? What constitutes a "senior", "lead", "principal" and "staff" X, respectively, has so much overlap that it really depends on the organisation. I myself have been called all of those things, but have honestly not been able to tell the difference: in some cases, I have had much more responsibility as a "senior backend…

> that it really depends on the organisation. This is entirely it. Titles should be consistently ordered within an organization, but they are not portable from one organization to another. This is a lesson I’ve had to explain over and over to people at the beginning of their careers. I’ve been asked for advice about which offer to take from people thinking about leaving 10s of thousands of dollars on the table becaus…

100%

This is complicated during acquisitions… you have a new company coming in and leveling them is hard because it’s a mass title migration exercise, and nobody wants to be down-titled.

In the 2 examples I’ve seen gone wrong:

-the people at the parent company look at the acquisition’s team and think, “there’s no way this idiot should be a director.”

-the people at the startup think they’re geniuses because they got acquired but their tech is crap and they’re actually just 28 year olds running around without adult supervision

-the startup guys will all leave once they vest or be pushed out for being lousy

-the tech gets even more unstable because no one left knows how the code works

Re: Don't become an engineering manager

#79
There will always be a place for EMs and ICs. This goes back generations, there have always been labourers and managers of labourers.

Perhaps the balance may tip one way or the others due to AI but something else will come along and tip it back again.

Do what you enjoy and are the most effective at.

Re: Don't become an engineering manager

#80
post #61

Earlier quoted context omitted.

As others have said, levels and titles are generally for compensation and performance reviews. Each company has their own bespoke ladder but it generally maps to: - L1: Intern with undergrad degree - L2: Intern with graduate degree - L3: Junior - L4: Intermediate - L5: Senior - L6: Staff - L7: Senior Staff - L8: Principal - L9: Distinguished - L10: Fellow Each company has their own numbers and names but it generally…

You're describing a very small number of companies that all copied each other's systems. The idea of a terminal role, for example, is pure Facebook. These do not apply in general across the industry except where managers from those small number of companies came in and shoved them in before they were fired.

In all fairness, a LOT of this was copied over from the military. From ranks to "High Year Tenure" (aka "Up or Out") nothing here is particularly innovative.
Post reply on HN