TLM role has always sounded like a trap to me, I would never say yes to it personally. I’m sure it’s sold as an expected 50% code, 50% management but everyone I’ve talked to who has been near it says the expectation is more like 80% code 80% management.

TLM roles are a trap, but not in that sense. There's no expectation that you do two jobs at once.

It's just a way to ease unsuspecting engineers into management. If you don't suck at management, your team inevitably grows (or you're handed over other teams), and before long, you're managing full-time.

Which means that there are three type of people who remain TLMs in the long haul: those who suck at management; those managing dead-end projects on dead-end teams; or those who desperately cling on to the engineering past and actively refuse to take on more people. From a corporate point of view, none of these situations are great, hence the recent pushback against TLM roles in the industry.

Usually it means you have to manage people but you have no real input on their career trajectory, and in the worst case, if they need to be fired you do not have the power to do so.

This was my experience in a TLM role - you have to manage down to your ICs but you have little lateral or upward power. You're basically just conveying whatever your manager decides to do with your team, but with all the additional responsibilities of a staff engineer.

In big FAANG-style workplaces, I don't think that middle managers without the TL- prefix have the kind of influence or leverage you're talking about here. It changes at VP level, but ultimately, most of the corporate management hierarchy is just spreadsheet misery.

its called the straw boss.

as in "and the strawboss said well a-bless my soul, you load 16 tons.."

I mostly found TLM a disservice to people who reported to TLMs. They didn't have to earn a promotion as both an engineer and a manager at the same time, so many optimized for their own engineering promotion and any managing they did was out of the goodness of their hearts.

People that selfish shouldn't be managing people.

As a devil's advocate (I don't work in Google or in a similar role) but if the requirements for engineering promotion are similar for technical managers and engineers, while the first have to manage people then this is just how the system is set up. In this case I think blaming the system more than people is justified, and Google decided to dismantle the role for some reason.

> If you don't suck at management, your team inevitably grows

Inevitably because why?

> those who suck at management

If higher management can figure out not to put more people under them, why can't it figure out to remove the existing people under them?

> those managing dead-end projects on dead-end teams

If "dead-end" just means "not growing" then that sounds fine. When a company does thousands of things only a small fraction of them need to be growing.

> those who desperately cling on to the engineering past and actively refuse to take on more people

"Desperately cling" is a wild way to refer to someone sticking with a job they like. And if they're a TLM it's not the past, it's the present. Wanting to keep your present job is very normal.

And is the end goal to have zero TLMs in this expanded team? If you're going to pick new TLMs to go under the one you push into higher management, what's bad about leaving them in place and putting someone else above them?

Look, I'm trying to describe reality; you seem to be expecting me to defend it. But briefly:

> Inevitably because why?

Because proven, effective managers are always in short supply, so when you hire new people, or if any of the existing managers leaves, it's the default pick.

Plus, most people want to make more money over time. And on the management track, this means angling for that director / VP role down the line, even if it wasn't your childhood dream.

> If higher management can figure out not to put more people under them, why can't it figure out to remove the existing people under them?

They can, but in big and / or growing companies, performance problems are addressed less vigorously than they probably should. This cuts both ways: neglecting problems is wrong, but cutthroat performance management makes people cranky too.

> There's no expectation that you do two jobs at once.

I laughed out loud when I read this. I've never seen anyone at any company in a hybrid tech/manager role that wasn't expected to do two jobs at once. Or at least they felt like they were, which is still the same problem.

80% coding & 80% management for that role sounds about right.

80 / 80 is sure close to reality.

As alternative explanation, even if there's no pressure to do so, the thing is these people came to do dev, and probably enjoyed their job enough to get recognized for their work.

So when asked to split between dev and management, outside of a few exceptions they'll want to do 80% of tech by choice. But the management part doesn't go away of course, so it will still be at least 50% (and 80% if they want money, because that's the part they're actually evaluated on)

I've been a TLM at two big companies and in my experience there was no expectation to do two jobs at once - I did majority of management with very very little hands on coding. More like frequent pair programming with more junior staff, code reviews etc. My last manager told me explicitly when I started - there is zero expectation on you to do any hands on work, you need to make sure your team performs and keeps going in the right direction first and foremost.

Most work 40 to 50 hrs per week. Some places even a more extreme 60.

For this to be accurate, you're saying 160% aka 1.6 or 64 to 80 hrs per week, with 96hrs as the extreme?

I mean, 64 - 80 hours a week can be the expectation, and then it's just that almost nobody is living up to the expectation.

Anecdotally, a hybrid technical manager I had in the past worked 60 hours a week pretty much minimum. Which sucks.

Management requires a birds-eye view of the project in all its breadth, and quickly responding to issues, as well as reporting up (proactive stakeholder management). The job of the manager is to keep the CXOs happy (inform/manage expectations) whilst protecting their own team so they can focus on getting their work done with minimal disruption (isolate).

Coding requires the opposite, zooming deeply into the code and retaining focus. The job of the IC coder is to deliver (design and implement) beautiful and pragmatic architectures that do what is expected.

I recommend anyone to reject to fill roles where these two are combined into one. Note that this is not a comment about workload, but about irreconcileable differences. (The perfect candidates for each even match different personality profiles...)

I've been in engineering, TLM, and management roles in multiple companies. In terms of output, TLMs are not held to the same standard as full-time engineers at the same level, period. Their engineering contributions are dissected only if their performance as a manager is in serious doubt.

In any role, there are some folks who push themselves too hard, and there is no one to tell them "stop", but that's their choice.

This is true for EMs at my company. They are pretty heavily technical, with full manager responsibilities. I honestly always assumed that's what EMs were.

This has largely been my experience in TLM roles. You’re a staff/principal level engineer so people still expect outputs from you. However, you now have the job of managing your teams’ impact and outcomes as well.

Impact and outcomes are far more important than outputs, so it makes sense to for you to spend a lot of time on that. But, when performing review time comes around, you’re still bounded by hard metrics around outputs.

But were all the other managers in the team in a TLM role?

The problem I foresee here is, there would be escalation meetings and all the non-technical managers would sit back and point fingers at the TLMs until they leave.

TLM is fine. TPM is the awkward one. I don't understand what hierarchy (if any) there is to TPMs, they kinda float around and ask people to do stuff. Some projects get passed around to different TPMs like hot potato. The skilled TPMs stick around and make things happen, but even then idk how that works because they lead people without having any actual reports.

That is the point of a TPM. They're supposed to be the neutral third party that makes sure you're doing the work, and can explain to upper management why the work is not getting done. As such, they don't have any decision-making power on what the work is or how long it's going to take. Generally the manager and IC negotiate back and forth on what needs doing and on what schedule, they set their own deadlines based on the realities of the project, and then the TPM holds them to what they committed to.

Much of the reason the TPM job exists is simply so your manager can be an advocate rather than a nag. The nag job is offloaded to the TPM, but the TPM has no decision-making power, so you don't get perverse incentives where the manager burns all their relationship capital making you do your work, or sandbags the deadlines so they don't have to.

In many orgs TPMs are also in charge of goodies like fun events or device/swag distribution, as a way to offset the negative emotions that come from them basically being nags.

A few thoughts:

(1) As an engineer, I prefer to be managed and guided by someone who actually knows what I work on, preferably better than I know it.

(2) A manager who actually understands the tech is often better at unblocking the team.

(3) Since senior IC openings tend to grow very thin as you become older, TLM path might be a viable career path for at least some.

Can this role work if we don't expect IC output from the TLM beyond what they themselves take on for their own satisfaction and growth?

When you become a good enough IC, “ As an engineer, I prefer to be managed and guided by someone who actually knows what I work on, preferably better than I know it.” is no longer reasonable. Then your managers role is to maximize your ability to make an impact by putting you in the right place/project.

As a manager of people who know far more about the things they do than I do, my goal is to assist and ensure in the right place (for them and the org). It’d be foolish for me to hire peons who know less than me.

Control issues prevent experienced IC from just roaming the halls looking for trouble.

Not sure why you'd take the leap from the idea of technical people managing technical people to "hiring peons who know less than me", that wasn't my intention. Also "as an engineer" was rhetorical -- I'm a manager myself and it's been over 15 years since I've been an engineer. So I do see the point you're trying to make. I still feel the immediate management layer above mid-level ICs should have some level of hands-on knowledge of the system they're developing. At the next level up, I think engineering fundamentals and past technical experience would suffice.

GP made the point that early in your career, your boss should absolutely know more than you do about your technical work, but at some point (fairly early), that inverts and your leader unavoidably knows less than you do about your technical work, because you’re the expert on the team at it and they can’t know more than all 5-8 of their reports like you can when leading 3-5 junior/new devs.

In post 1, you want your lead to preferably know more, someone says that’s not realistic, and in post 2, you profess to not understand their point while changing the goal post to now be “some level of hands-on knowledge”, which sounds like you do understand their point.

What you're asking for is more of a TL.

At the risk of oversimplifying, the role of a manager is to find you that TL.

GOOG has made a systemic push to eliminate the role starting ~3 years ago. At that time my M was a staff level IC TLM with 4 reports who was forcibly converted to EM.

In those last 3 years I've only seen TLMs used to assist an overloaded EM.

The pattern I've seen is something like:

Principal EM |- Staff EM (7 reports, project A) |- Staff EM (8 reports, project B) |- Staff IC (projects A, B, C) |- Senior IC (projects A, B) |- Senior IC (project C) |- Mid level IC (project C) |- Mid level IC (project C)

Maybe project C was just reorged under the Principal EM or maybe it's a speculative side project. But those last three are clearly clustered, but there's no good EM fit and the principal EM feels disconnected from the 2 mid level ICs. Project C is a bit of an island and projects A and B are taking up most of the EM's time.

So the Principal EM deputizes Senior IC on project C as a TLM until things have changed enough that there can be a dedicated EM. Eventually the TLM converts to EM, a new EM is brought in, or there's a reorg, etc.

Of the two times I saw saw it happen locally, both converted back to ICs after a year or two and noted that the role felt like being 70% IC and 70% EM.

Nowadays the TLM role doesn't exist so the principal would delegate most of the technical responsibilities of the M role, giving them nearly full control of project C, but would not give them a formal role. (I've been that senior IC for project C.)

Can someone explain the various acronyms?

IC -- individual contributor, EM -- enginering manager, TLM -- technical lead manager

EM = Engineering Manager IC = Individual Contributor

Do you have a mapping to roles/levels[1], for example:

Principal EM - USD$1.3m/yr per https://www.levels.fyi/companies/google/salaries/software-en...

Staff EM - USD$664k/yr per https://www.levels.fyi/companies/google/salaries/software-en...

Staff IC - USD$557k/yr per https://www.levels.fyi/companies/google/salaries/software-en...

Senior IC - USD$410k/yr per https://www.levels.fyi/companies/google/salaries/software-en...

Mid IC - USD$290k/yr per https://www.levels.fyi/companies/google/salaries/software-en...

levels.fyi doesn't appear to use the term "Technical Lead". There is "Technical Program Manager" and "Technical Account Manager" that sound like they'd be similar (someone technical transitioning into a full-time non-technical role). And then roles such as "Product Manager" and "Program Manager" seemingly for those who are currently 100% non-technical in their work.

Does the change mean the most competent solution architect who has successfully designed and implemented many complex systems from scratch is capped in salary package because they're not doing the important job of demanding those around them fill out TPS reports all day?

[1] https://www.levels.fyi/companies/google/salaries/software-en...

TPM and TAM are completely different roles. TPMs are essentially project or program managers across wider parts of the org, and the "technical" means they have something beyond a surface understanding of the technical aspects, but are likely not writing any code. TAMs are account managers in the sales org with a focus on giving clients more technical support or planning integrations etc.

"Technical lead" is not a role profile or ladder, it's what you're doing. You could be a TL at L4 on a small project, and you could not be TL at L7 if it's a big enough project. All very subjective.

The point of this thread is that there are teams with a manager who is the defacto TL for the projects the team is doing, so they have IC responsibilities, and then there are teams where the manager does manager things and there's one or more separate TLs.

I've worked on teams in both structures, both in and out of Google, and whether TLMs vs EMs work well depends on so many factors: who the manager is, their management style, the org's priorities, the projects, etc.

Hell, I’d happily be Lundberg for $1.3M/year. Shoot, I’d probably even do it for just $1.0M — and the Bobs would be pleased!

It also sounds like the 10x developers are underpaid by a factor of 100!

It's been a few years, but from what I recall, a Principal is a Director-equivalent (L8) level.

The prior poster is missing the L7 tier, which is Senior Staff Engineering Manager for the Engineering Manager Ladder.

L8 is a Director on the Engineering Manager Ladder L8 is a Principal on the Software Engineer (SWE) Ladder.

Tech-Lead Managers (TL/M or TLMs) were on the SWE Ladder.

For reference:

Software Engineer Ladder

L8 - Principal Software Engineer

L7 - Senior Staff Software Engineer

L6 - Staff Software Engineer

L5 - Senior Software Engineer

L4 - Software Engineer II

L3 - Software Engineer (new graduates would start here)

----------------------

L2 and below exists in rare occasions.

Engineering Manager Ladder

L8 - Director

L7 - Staff Engineering Manager

L6 - Engineering Manager (M1)

L5 - Engineering Manager (M0 - normally this level does not exist for external hires and is for the rare situation when a SWE is converting to the Engineering Manager ladder)

What's the difference between Staff and Senior engineer?

Senior engineer is usually focused on a single project, and knows it deeply. Usually directing and mentoring more junior engineers in the process.

Staff engineer typically is overseeing multiple projects, providing deep technical oversight and guidance on those projects, and mentoring Senior engineers. They start to influence technical culture. They are actively involved in ensuring business needs get met by the technical solutions their group is building.

Senior Staff Engineers will be overseeing a product function, and multiple Staff engineers. They build the correct technical culture. They ensure larger architectural issues get resolved. They are actively involved in ensuring the technical work being done is meeting business needs, and identifying business needs their technical org can be meeting - and working to make that happen.

Principal engineers are setting the tone for an entire large product (typically), and ensuring the Senior Staff engineers are doing the right things - and also often involved in driving strategic product direction.

Senior Staff and Principal tend to be increasingly political, but even Staff will get pulled into that type of thing somewhat regularly.

One of the problems is that large corporations have such complicated role structures, and another problem is that they are also different from all other large corporations. A third problem is that the compensation models are again vastly different. A fourth problem is that they change over time.

All of this means as an individual you suffer from extreme information asymmetry.

Even if you got two offers from two different FAANGs, it would perhaps be hard to figure out which one is better.

Has anyone defined any mapping tables between role names across Amazon, Meta, Alphabet etc. and figured out salary ranges for them in a public spreadsheet?

BTW, has anyone got a leaked (anonymized) copy of FAANG employment contracts so one can compare the various clauses across employers, and track changes of their standard templates over time? (I haven't seen this topic discussed much on here in the systematic way that it deserves.)

Given the developer community invented open source it is surprising that corporations have so far succeeded in keeping such obvious things relatively secret (compared to, say, the emails of Sarah Palin and Ehud Barak ;-).

levels.fyi has this

Google and Meta/Facebook have generally aligned and numerically equivalent levels for the main Software Engineer and Engineering Manager ladders.

This is not really an accurate representation of FAANG hiring and job searching. In reality, there is a very very high amount of job hopping and also connections to people at other FAANGs (and there's also levels.fyi and blind) so we're well aware of comp structures, what employment agreements, levels, etc are across companies and how to compare then. There's very little information asymmetry in fact people go into negotiations with recruiters very well equipped, far better than at small companies.

> BTW, has anyone got a leaked (anonymized) copy of FAANG employment contracts so one can compare the various clauses across employers, and track changes of their standard templates over time

If this doesn't exist it's only because it's incredibly uninteresting. levels.fyi will tell you all you need to know. (also they aren't employment contracts, in the US we do agreements because we're at-will)

I've hopped multiple FAANG+s now across my career.

Adding a correction on above ->

L7 is Senior Staff Engineering Manager (M2)

L6 is Staff Engineering Manager (M1)

they are of equal level to the SWE ladder L6 and L7 titles

TPM, TAM, and PM have nothing to do with this. A technical lead is usually a semi-formal role for an IC or a TLM that implies that they are leading a project with other folks working on it. There are situations where the Mid, Senior, or Staff IC could all be a technical lead of various sized projects.

> Does the change mean the most competent solution architect who has successfully designed and implemented many complex systems from scratch is capped in salary package because they're not doing the important job of demanding those around them fill out TPS reports all day?

No.

I believe a TLM is an IC on this scale.

> Does the change mean the most competent solution architect who has successfully designed and implemented many complex systems from scratch is capped in salary package because they're not doing the important job of demanding those around them fill out TPS reports all day?

In house solutions architects are not really a thing at FAANG. Designing and implementing systems is what mid+ level SWEs are expected to do. The solutions architects I have seen were all in the sales org helping external customers better use the cloud. My experience isn't exhaustive of course.

I suspect they’re talking about Senior Staff IC’s - aka TL’s of TL’s.

> At that time my M was a staff level IC TLM with 4 reports who was forcibly converted to EM.

I am obviously not disputing your experience, but wanted to mention that this was not the standard pattern. The standard pattern for forced conversion at L6 (Staff) was either 6 or 7 reports (I don't remember exactly).

> Principal EM

I don't want to be overly pedantic, but there's no Principal EM on Google eng ladders and so it's not entirely clear which level you're referring to.

The IC ladder runs Staff SWE (L6) - Senior Staff SWE (L7) - Principal SWE (L8) - Distinguished SWE (L9)

The Eng Manager ladder runs EM II (L6) - EM III (L7) - Director (L8) - Senior Director (L9)

P.S. I hope I got the EM II/III designations right. I think EM I is L5, though almost never seen in practice.

P.P.S. Confusingly, the IC ladder allows a limited number of reports (the limit increases with level).

Yeah principal EM is confusing here. Wouldn't EM I report to EM II? At Meta it's typically M1 -> M2

I think L5 Manager at Google is EM1 which is what Facebook calls M zero. So L6 manager (vast majority of line managers) would be EM II at Google.

>> At that time my M was a staff level IC TLM with 4 reports who was forcibly converted to EM.

>I am obviously not disputing your experience, but wanted to mention that this was not the standard pattern. The standard pattern for forced conversion at L6 (Staff) was either 6 or 7 reports (I don't remember exactly).

I think you're both saying the same thing. By "forcibly converted to EM", I think B-Con was saying the person was given more reports.

> I am obviously not disputing your experience, but wanted to mention that this was not the standard pattern. The standard pattern for forced conversion at L6 (Staff) was either 6 or 7 reports (I don't remember exactly).

Given more reports and forced to be on the EM track.

I think 4 is still OK for L6 (L7 can have up to 19!).

> I don't want to be overly pedantic, but there's no Principal EM on Google eng ladders and so it's not entirely clear which level you're referring to.

I meant L7 EM - I have no idea why I wrote Principal (probably because I was moving too fast), and now it's too late to edit.

Wait, so you have ICs who work on multiple projects, and report to a different manager depending on the project? That sounds like a nightmare. Having one manager to manage is usually enough work...

It’s generally just fine if they all boil up to the same manager and that manager has a direct line to that IC.

In the company i work at this is the standard. Its all pure waterfall and its dreadfull

It's chaos. This is standard corporate management in 2025 though.

It's actually quite common and it's called "matrix management". Multiple people to give you orders and no one to take accountability. You'd be surprised how wide spread it is.

Everytime I see such charts and explanations it helps me understand how Musk could fire 80% of Twitter with no visible effect on product.

Except extreme outages? Their reliability went to shit for a while. Fortunately half their users and advertisers quit too so the load downscaled a lot

In addition they reduced API by a lot, some backend and advertiser focussed things are gone and the big thing: we can't know what would have come.

I've always been perplexed when I see 100s-1000+ people work on software product development and very little happen with the product for YEARS while there are tons of obvious (to me) improvements possible. Only tiny bug fixes released on a pretty slow release cycle. Then I also just think of the twitter/X example.

Occasionally one reads stories of how people get paid pretty hefty salaries to mostly just work very casually. Contrast with the usual software engineering types I know that work insanely hard solving difficult problems day-in and day-out.

When I was younger I remember a lot of project managers (almost exclusively ladies in my environment back then) that mostly just ran around interrupting the programmers and relaying feedback and status and a lot of chitchatting and busy work. Often there can be tons of support roles, wellness officers and who knows what that can probably be slashed. What shocks me is when a lot of these really low value-add positions are given high seniority with crazy paychecks and very little real skill required and fairly low responsibility or accountability for anything vaguely tangible. I suspect in tech companies generating huge cashflows that almost seem decoupled from headcount in comparison to non-tech businesses, this stuff just get covered up. A big machine that is very profitable due to massive competitive advantage/network effects, can hide a ton of HR waste.

> I see 100s-1000+ people work on software product development and very little happen with the product for YEARS while there are tons of obvious (to me) improvements possible

I worked in an org with about 60 engineers all working on the same product and I have to actively _not_ fix small issues to keep my sanity. Whenever I see a small issue I would have:

0) If it changes anything visible to the user discuss it with UX or PM (very annoying)

1) Fix it (easy part, usually)

2) Create PR and explain issue

3) Get someone from the other overworked team to look at it (not as bad if it is from my own team)

4) Get comments for often trivial things (depends a lot on the changes)

5) Get asked to refactor some related functionality because the fix is a bit messy without it (workaround) or to address the root cause of the issue (this is usually a big deal)

6) Possibly several rounds of reviews

7) Someone break my fix next time anyone makes a change to that part of the code

All to get something done that wasn't asked of me, that my manager will probably not see or know about unless I bring it up, that if I do bring it up my manager will probably tell me to not waste time on it since "it is the other team's problem".

So I would either ignore the issue or create a ticket that will probably be ignored. Only if it is a really trivial uncontroversial change would I bother to actually proactively do it.

Thanks. This explains Android. Because the only other explanation would be no dev at Google actually uses it day to day as their phone because it has so many dumb little infuriating things.

Example: Why does my kitchen bluetooth, that I connect to the most, and that I am located nearest to, always go to the bottom of my bluetooth list, meaning I can't select from the quick screen and have to unlock and pull up another screen (when my hands are kitchen dirty)? I consume media on bluetooth the most showering and in the kitchen. The devices used should be 1 and 2, but they never are. EVERYTHING on Android is this 'devs must not actually use this' unfriendly. I still can't use the timer function using voice because if I don't wait for my phone to repeat back all the timer info and I touch something it just blanks out my timer, so I've learned I can't trust it after ruining too much food. These are my two most common use cases for my phone and where it ads value to my life, and both are needlessly annoying on Android causing me to hate the platform because in 2025 these little details should work. Someone at Google must cook things that need timers. Someone at Google must listen to music/audiobooks and have enough devices they spill over to the secondary screen. If feels like Android has zero actual world love/care from the devs or these daily annoyances would bubble up instantly.

I see your Android, I raise you a google home speaker. Please someone help me understand, why is it a freaking pain to use these speakers with bluetooth? Why can I not use them as output for the tv? Is the audio lag just an artificial limitation? I got them assuming they were bluetooth speakers with the Assistant and streaming stuff. But apparently not. Which sick product manager came up with that?

> Contrast with the usual software engineering types I know that work insanely hard solving difficult problems day-in and day-out.

Well you just know some... not effective or smart folks then, unless they literally enjoy living such life. There is time for some hard work, but if that's one's default modus operandi long term, rest of their lives suck pretty badly, no realistic way to avoid that.

That's failure to manage one of most critical aspects of life. Especially bad fail if employed at some heartless mega corporation, or just usual often amoral FAANGs of these days (unless the goal is to earn enough money in few years and move to saner place in life, but few achieve that even if they plan for it, ie mortgages and kids happen).

Some of us live to work, and the rest work to get some good actual life.

Many large organisations inadvertently, with reasonable intentions create a structure with a powerful bias towards inaction.

It's reasonable, when a company is looking into buying a new SaaS product, that the legal team review the contract.

It's reasonable for legal to ask for variations in the contract, if there's something in it they can't approve.

It's reasonable for the product to be reviewed for compliance with our privacy laws, before we order employees to start using it.

It's reasonable that the information security team get to be consulted before a new product is adopted, we don't want insecure products sneaking in.

It's reasonable that we want single-sign-on from our vendors, that's good for security. And we want SOC2 compliance if possible, as we're trying to be SOC2 compliant ourselves.

It's reasonable that a vendor have a record in our finance database, so we can pay them and know who we've paid what.

It's reasonable that, before approving a vendor, we get a statement from them that they do not use slave labour in their supply chain.

It's reasonable that every expense be attributed to a project or department within the business.

It's reasonable that the project or department's budget have an owner, who has to approve major expenditures.

It's reasonable that the work above is split across quite a few teams, and that each team have a queue of work where non-emergency requests can take a week or two.

But take those reasonable policies together, and it takes 3-6 months to adopt a new SaaS product - so it's a heck of a lot easier to stick with an under-performing, over-priced vendor than it is to get a new vendor approved.

Except few companies can do what musk did on an ongoing basis without losing all experienced staff and system knowledge. It's short term gains at the expense of long term gains. People only put up with it if they think they can capitalize on the prestige.

How was there no effect on product? What has 'X' even been able to launch since the acquisition?

All he showed was you can an existing thing running with 20% of staff.

Furthermore, a bunch of functionality was entirely deleted, and the effect on the quality of discourse has been... Profoundly negative.

Yea but hey 80% of people lost their job. No wonder all SV CEOs are so eager to copy Elon

we had this in my company it was pretty hit miss. Almost always the 'TLM' was someone who was in the role for a really long time and it warranted a second person, so it ended up being a 1-2 junior reporting in absorbing the knowledge that the tlm had.

If you were in a growing domain, and the TLM stayed engaged with the code it worked really well, but as soon as one of those failed it was a bad roi for the company and a pretty terrible experience for everyone. the juniors were never getting promoted since there was only room for 1 expert on the small domain. The TLM was just chilling getting 5-10% raises a year without going outside of their little kingdom, but making sure their domain worked well.

As their junior got better they coded less but their juniors couldn't grow as long as they were there because the niche didn't need that many people.

I don't think its a coincidence that all these companies eliminated these rolls after 2022. When you have unlimited money and massive headcount growth these roles can exist and give your good but not exceptional people room for career growth. At static headcount, you basically need to do what banks do -- yearly cuts or no one can be promoted or hired.

I wouldn't actually say that, but I would say that the TLM role works at a very specific stage in a company's lifecycle, and many companies that use it (including Google itself from around 2010 onwards) have long since past that point.

IMHO, the conditions where a TLM role is appropriate are:

1.) You need to be in the company growth phase where you are still trying to capture share of a competitive market, i.e. it matters that you can execute quickly and correctly.

2.) There needs to be significant ambiguity in the technical projects you take on. TLMs should be determining software architecture, not fitting their teams' work into an existing architecture.

3.) No more than 3 levels of management between engineer and person who has ultimate responsibility for business goals, and no more than 6 reports per manager. The mathematically inclined will note that this caps org size at 6^3 = 216, which perhaps not coincidentally, is not much larger than Dunbar's number.

4.) TLMs need to be carefully chosen for teamwork. They need to think of themselves as servant-leaders that clarify engineering goals for the teammates who work with themselves, not as ladder-climbers who tell others what to do.

Without these, there is a.) not enough scope for the feedback advantages of the TLM structure to matter and b.) too much interference from managers outside the team for the TLM to keep up with their managerial duties. But if these conditions are met, IMHO teams of TLMs are the only way to effectively develop software quickly.

Perhaps not coincidentally, these conditions usually coincide with the growth phase of most startups where much of the value is actually created.

If you don't mind me asking, why did your team get bigger? Did your scope increase?

I assume you're referring to my other comment, since I didn't mention my team size in this one.

I'd love to say that the answer is "because I'm a good manager", but I think that the real answer is "because there was money=headcount available, the layers of management above me successfully presented our value and inflated our needs enough to convince a VP to give it to us, and my own manager physically did not have enough hours in the day to have 1:1s with all the new incoming headcount without introducing some layers of management under us". If it weren't me, it would've been some other manager. For that matter, I wasn't a manager when I joined the team, but I was interested in managing and of sufficient level that I could pass department policies, so I ended up more than doubling my team size within 6 months of becoming a manager. The team was pretty busy for the first year or two after that - we'd gotten all that headcount by arguing that we were critical to some big strategic initiative, after all - but there were long periods after where we were oversized by a factor of about 2, so I just let everyone work 20 hour weeks and phone it in until the next big project came.

The more time I spend in the corporate world, the more I become convinced that success is a matter of meeting the minimum qualifications, bullshitting, saying yes to opportunities created by people who are themselves bullshitting, and doing the minimum amount of work needed to avoid being called on your bullshit. Businesses don't hire because they actually have work to do. They hire because they have money and money=headcount and headcount is the only way for a manager to get promoted or pad their resume.

I passed on a similar opportunity, kept the team small. This was back in the pandemic when headcount flowed freely. What you describe sounds about right. My experience is that having a capable team goes a long way creating those expansion opportunities.

This kinda brings up a question I've often thought about. Why is it that we structure growth in a company to be so biased towards moving into management roles?

I mean there is the obvious part of the answer in that managers are the ones that are given the power to define that growth ladder, but I'm not sure this fully explains things. If people are transferring from technical positions to managerial positions then should they also not be aware that there is a lot of advantages to allowing people to keep climbing the ladder through technical positions? That institutional knowledge can be incredibly valuable. It's often what leads to those people being such wizards. They've been with the code for so long that they know where things will fail and what are the best parts to jump in to make modifications (and where not to!). But every time you transfer one of these people to a non-technical role that knowledge "rots". More in that code just keeps evolving while their knowledge of it remains mostly frozen.

Which what you say sounds like maybe the worse end of that. Taking that person with institutionalized knowledge and hyper focusing their capabilities on one aspect. That doesn't sound like an efficient use of that person. Though the knowledge transfer part sounds important for a company's long term success, but also not helpful if it's narrowly applied.

This hasn't been true in a lot of companies for like my entire career. You can move up as an ic. Titles like Staff, senior staff principal. A Staff and Sr manager would be paid the same

What do those roles do? Where I work there's a managerial track and a technical track, but if you actually read the job descriptions the technical track is basically either the same as management track, or a devrel role (effectively managing people outside the company).

Ic role has bigger scope of projects. Makes technical decisions. They're not writing performance reports or doing any people management tasks.

> A Staff and Sr manager would be paid the same

do they report to the same level? every place I've seen a "technical track" and "management track" it seems the higher level technical people report to someone on the same or even lower level in management. I.E. a manager can have technical reports that are equal level or higher. that obviously doesn't happen in the management track.

not that these are first level managers but if a principal engineer not reporting to a VP, the it doesnt seem like the tracks are equal.

Why does the reporting chain matter? They're separate roles and jobs so the manager is leveled differently.

If I'm a jr engineer reporting to a director does that give me more authority then a staff engineer reporting to a manger?

Management is a different job, it would be leveled differently.

Maybe a high level IC needs to work closely with a team for a bit so they just report to the manager of the team.

> This hasn't been true in a lot of companies for like my entire career. You can move up as an ic.

You can, but it's a dead end ultimately. I've been a distinguished engineer which is about as far as one can go (some companies have Fellows, but it's just a few people so basically impossible). If you have any desire to grow beyond that, management track is the only possibility.

Also, moving to management from a DE level is harder because you're basically around a Sr.Director level (give or take, depending on company) but have no management experience.

If you care about career growth (and I'm not saying you have to, geeking out on the IC ladder is way more fun), I suggest as soon as you are at the equivalent level of a manager on the numeric ladder, switch to management.

Your making 7 figures? What is left in career growth. You beat the corporate game at that point.

This reads like "get rid of the old experienced people so I can get promoted".

only if you're cynical, google found a much better solution though, make them IC's again and redistribute the junior talent to places they can grow and offer buyouts for anyone who feels like they're not into it anymore.

I am cynical. Better for what? I can only interpret moves made by large companies across the board as ways to move the stock price and consolidate control.

The U.S. military actually uses precisely that system for officer promotions. And in practice most of the U.S. military branches do essentially the same thing for their enlisted force too, deliberately allowing high attrition for the sake of frequent promotions.

Given a fixed headcount, you can't have frequent promotions without either personnel turnover or allowing for employees to be routinely demoted.

If your position has no upward mobility juniors will change jobs, likely change companies, once they have the experience and all the effort you spent training them will be wasted.

If your position has no authority seniors will change jobs, likely change companies, and all the effort you spent on them will be wasted.

I don't know why you think this is an either or situation. Not being a junior doesn't stop you from having a manger.

Statistically you should charge companies. Even if you get promoted, you’ll make less than someone hired in at the same level. Even if you like the company, it’s best to “boomerang”

Its tricky to use statistics for personal decisions. In general something might be correct but not for your specific subgroup. I know many people who changed for worse.

If you are in a bad position then change, but if you like the company and role, don’t take it for granted and think carefully.

This advice is consistent with the broad statistic if more than half of the sample is currently in “bad position”.

Since we are talking about BigTech, I can’t imagine to a first approximation any IC up to and including senior or a low level manager being at any BigTech company for a reason besides wanting to maximize their income via cash and RSUs.

Does anyone stay in the same position/team for more than two or three years even at the same company?

It sounds to me like Google is moving to a more typical "technical lead" model where leads have substantial authority and some mentorship responsibilities, but they're essentially an IC and someone else up the chain actually handles proper management. Informally, tech leads can gently chew out less senior devs, but if someone actually needs to be disciplined then the lead needs to talk to the manager.

TLM is an odd role. I understand big tech companies have their own culture but it does seem like a poor management strategy regardless of efficiency.

The original ethos was that you didn't want the company ran by MBAs, so you wanted to build your management team by tapping into talented engineers.

Of course, this can backfire in many ways. You end up wasting engineering talent, and as the organization grows, managers spend more time on paper-pushing than on creative work. And there's no shortage of engineers who are just bad at reading, talking to, and managing people.

But the huge perk of management is leverage. If you're technically competent and credible, and want something to happen, your team will see it your way. If you're a random "ideas guy" in an IC role, that's not a given.

> But the huge perk of management is leverage. If you're technically competent and credible, and want something to happen, your team will see it your way. If you're a random "ideas guy" in an IC role, that's not a given.

There are three levers of power in an organization - relationship, expertise and role. Role power is by far the least effective. If you can’t get team buy in for your ideas or they believe you’re an idiot, you won’t get anything done.

A high level trusted IC who builds relationships inside and outside of the team and who is strong technically can work miracles.

At my current 700 person company, I’m pushing through a major initiative that management up to the CTO was at first skeptical about because I convinced them of my vision and I built relationships to get buy in.

I’m a staff engineer.

Even at BigTech I saw L6s and L7s ICs push through major initiatives the same way.

And wielding all three at once is the most effective.

> Role power is by far the least effective.

To be frank: it sounds nice, but I don't think that's really true. It's the power of "who's going to decide my promotions", "who is going to advocate for my team and get us more resources", "who approves my expenses", "who is going to protect me if something goes wrong", etc.

This doesn't give the manager a pass if their ideas are objectionable, but if they're credible, it's a huge advantage. Small disagreements disappear and people fall in line behind your vision, get excited about it, and make things happen.

In contrast, in an IC role, you can successfully push for initiatives, but you're always working against that dynamic. The merit of your idea aside, folks might simply feel that you're pushing them in a direction that's less likely to get them rewarded or recognized within their reporting chain. That takes extra effort to overcome.

Being very visibly anointed by some VP helps, but that's tapping into the exec's leverage, not yours. And that approach has downsides; I worked with more than one architect / uber-TL person who were universally disliked and feared. The perception was that they showed up to make your life worse by putting extra work on your plate, without having much skin in the game.

> Being very visibly anointed by some VP helps, but that's essentially tapping into the exec's leverage - an illusion of IC influence.

Of course that’s the play. Even a lind manager can’t get major initiatives through without getting the buy in from their manager. When I was working for startups, the director (1st company I had influence at) and the CTO at the second had been convinced of my idea and gave me the authority to pull who I needed to get it done.

Fast forward past BigTech to where I work now - a third party AWS consulting company, after convincing the powers that be of the market, I had it escalated to be one of the companies initiatives for the year.

But more so in BigTech, promotions aren’t completely on your manager. At least at AWS you had to have recommendations by I believe two or three people one level ahead of you and it had to go through a committee.

From talking to a couple of L4s that I mentored when they were interns and when they came back, they were both complaining about the promotion process even though their manager supported them.

> the CTO at the second had been convinced of my idea and gave me the authority to pull who I needed to get it done.

But that mean those people have the power, not you. Without that formal power structure you wouldn't do so much work trying to convince these people, the formal power structure forces everyone to try to manipulate and work with it, even you.

So it makes it so much easier to do anything if you are that high up person, imagine that was you, now instead of having to convince these people to do it now you just do it.

Power structures exist in any group of size. Companies can choose how formal to make them, but they can’t avoid them.

Imagine instead of having to convince the Director, VP, or CTO to support your good idea, that instead you had to convince 100 out of 700 people to support it, while at the same time, those 100 people are hearing good-sounding ideas from 99 people who aren’t you.

I’d way rather work in the former than the latter.

> Role power is by far the least effective.

Eh, maybe at faangs or at the executive level but at non faangs you might not notice a role having power because most roles with the Manager title are no longer actual managers but supervisors.

I had more agency over where capital was deployed as a teenager deciding how many people were going to be on the shift for closing, then I have making over 200k/yr as a Senior Manager.

Any role that has decision making power over where money goes automatically has a massive amount more power than a role that does not

The article is mostly about first level managers. I’ve never had any “manager” that really has any power over raises more than 3-4% or any real control over budgets.

When I was being hired as a strategic hire for startups - and was being interviewed by the director or CTO - I specifically asked would I be reporting directly to them or another manager. I actually refused one job because I saw that the expectations they had from me and how far I was down in reporting structure was incongruous.

>The article is mostly about first level managers

Maybe for faangs. At every company I have worked at with a manger title from 2019 to present, this was expected of people with "director" in their title and below.

You are not a manager if you do not get to decide where capital is deployed, without your boss's approval.

For anyone reading this comment, if you think you are a manager, ask yourself this question

"If I decided tomorrow that the company would be better off if I hired someone to do role {X}, can I open a new req for that role without permission?"

If the answer is no, you are a supervisor with less agency than the a Walmart deli leader circa 2010

I think the common vernacular for that cutoff is “director” rather than “manager”.

Directors direct (including opening hiring reqs without higher-level approval).

Managers manage (which doesn’t include unreviewed role openings).

Both do useful work in a well-functioning company.

You do not manage if you do not have agency. Modern day “managers” are supervisors making sure their directors or executives management plans are going according to plan, and if anything requiring money or headcount is needed to get the plan back on track, once again the director or executive needs to make that decision.

I was not joking about the roles having less agency than a Walmart deli supervisor. I had more say in how the work was done in that role, than I have at any software company while I had the word “managers” in my title

I've worked at places where the "senior executives" couldn't do any of these things without CEO approval. Even if they claimed to "have budget" for something, it still needed sign off.

There's tons of title inflation out there, especially at smaller firms.

> I had more agency over where capital was deployed as a teenager deciding how many people were going to be on the shift for closing, then I have making over 200k/yr as a Senior Manager.

But the value of the capital you had sway over as a 200k manager is significantly higher. You have to accept that you won't ever have total agency over 7+ digits worth of both human and non-human capital if you're not a VP/CEO (or a fintech bro I guess).

By make-up I think most TLs at Google had no reports even before this change. The idea of ICs in leadership has always been a common occurrence at Google. If anything I don't really see it as commonly outside of Google.

Yeah, that helps put this in perspective. At first the headline sounded like a somewhat jarring and sudden staff cut, but if we're essentially just seeing Google migrate TLMs to TLs, that actually makes sense.

Do you have any opinion on the success/value of the TLM role?

Not OP, but I think TLM works best when it's a transitional role. You have someone you want to groom into a full-time manager, and you have a team that you plan to grow over time. TLM itself is not that efficient, but can lead to strong full-time managers who understand the team really well and had time to grow into the role.

I was thinking this too. Tech lead/developer and manager are two completely different jobs. I can see TLM as a useful transitional thing, while the person is being trained or mentored at being a manager (and hopefully not just thrown into the deep end). But 6 months, max 12, I think. Otherwise it just becomes a role where someone has two jobs and ends up overworked.

It's a rather awkward role as you have to carve out a maker's schedule within a manager's schedule [1]. As others have mentioned, it only makes sense as the person ramps up for full management or decides against that career path.

[1] https://paulgraham.com/makersschedule.html

This is a funny question to me, because my entire career (mostly small companies/small tech depts) I've never reported to an EM. It's only when I moved to big tech that EM-who-doesn't-code became a thing, and it took some adjustment for me. All prior roles had TLs (aka TLM) which led the team while being the expert - aka the "surgeon model" from Fred Brooks' book.

As far as I can tell, the main function of an EM is to enforce the company policy. I'm not sure there really is a need at a smaller place.

As someone who has worked in companies from <30 to >100k, I would say that what an EM does is more about communication. Think of a company with m employees as a m by m matrix, with a 1 where there regular communication and a 0 where there is no communication and a 0.5 for those hallway meetings which our CEO's assure us are why RTO is so important.

In a small company (let's say anything under Dunbar's Number), you have a very dense network organically, and EM's aren't necessary. As the company grows larger, the matrix becomes sparser and sparser- until you get to something like Google (180k employees plus maybe that many again contractors) and you have almost all 0's. So an EM's job is to solve the communication problem, because information still needs to flow around the company, in and out, whether it's "do this project" or "another team already solved this problem" or "this project is a never-ending world of pain and should be ended" to "employee 24601 is awesome and should be given more responsibility."

That's a large part of it.

Probably the best description I've heard of the EM role is that "It's a large collection of part-time roles, all with disparate skillsets, that together are responsible for ensuring the success of the project."

Communication is a huge part of that - downwards (telling reports the information they need to be successful), sideway (getting information from cross-functional partners and managerial peers so you align your projects with theirs), and upwards (managing expectations and asking for direction at the appropriate point so upper management doesn't freak out).

But other skillsets involved are: playing therapist (managing anxiety, morale issues, resentment, and misconduct); coaching (both technical and interpersonal); splitting up vague exec mandates into subgoals; prioritizing; hiring; managing performance; serving as a point of contact for whatever random problems your reports bring you; negotiating; setting team structure; developing expertise among your reports; managing their careers so they get promoted; ensuring that they're recognized for their accomplishments; helping people have fun in the office; modeling a culture of respect; selling new product initiatives; and yes, enforcing company policy.

Thanks for this message, this is actually helpful :). I have been a TLM/EM for the last 4 years, and I still struggle at times to define what my role is about...and in downtime moments (which are rare, most of the time, you are overloaded), what the fuck should I spend my time on.

I can't say for Google, but at work it's more or less how it works at the office (mostly software dev, half a team does some firmware/hardware), but it's more ad-hoc than as a rule. Like all the teams are small, all the TLM equivalents started as devs before being promoted to their management position, so they have time to do some technical work; how much and what technical work depends on the team, some are still directly contributing to the team's products, others are more on (technical) ancillary tasks, which can be interrupted by management questions with less impact on the development.

I find that it works well, the TLM keep a foot in the action, so to speak and has a better idea of what's happening with the product being developed, what issues we're facing (also in terms of tools, environments...) and it keeps their knowledge of the product more up to date. Of course with their background, I wouldn't say they are all the greatest at managing, but I don't think they've ever done big mistake on that side of their role. So in short in our case it works, but it could just be a consequence of the local organisation and people working there.

Former TLM that was involuntarily reclassified as an EM because I had too many reports. I'm from old-line (pre-2011) Google, so was an engineer back when the TLM role was one of our unique competitive advantages.

I have a lot of thoughts on this. IMHO, it's appropriate for the state that Google is in now, where it is a large mature conglomerate, basically finance & managerially driven, built around optimizing 10-K reports and exec headcount & control. It's not a particularly good move from the perspective of shipping great software, but Google doesn't really do that anymore.

The reason is because software construction and management is unintuitive, and concrete details of implementation very often bubble up into the architecture, team structure, and project assignments required to build the software. TLM-led teams have a very tight feedback loop between engineering realities and managerial decisions. Your manager is sitting beside you in the trenches, they are writing code, and when something goes wrong, they know exactly what and why and can adopt the plan appropriately. Most importantly, they can feed that knowledge of the codebase into the new plan. So you end up with a team structure that actually reflects how the codebase works, engineers with deep expertise in their area that can quickly make changes, and management that is nimble enough to adopt the organization to engineering realities rather than trying to shoehorn engineering realities into the existing org structure.

Now, as an EM with 10+ reports, I'm too far removed from the technical details to do anything other than rely on what my reports tell me. My job is to take a slide deck from a PM with 10 gripes about our current product, parcel it out into 10 projects for 10 engineers, and then keep them happy and productive while they go implement the mock. It will take them forever because our codebase is complex, and they will heroically reproduce the mock (but only the mock, because there is little room for judgment calls in say resize behavior or interactivity or interactions with other features and nobody's holding them accountable for things that management didn't have time or bandwidth to ask for) with some hideously contorted code that make the codebase even more complex but is the best they can do because the person who actually needed to rewrite their code to make it simple reports up through a different VP. But that's okay, because the level of management above me doesn't have time to check the technical details either, and likewise for the level of management above them, and if it takes forever we can just request more headcount to deal with the lack of velocity. Not our money, and it's really our only means of professional advancement now that product quality is impossible and doesn't matter anyway.

Ultimately the value of the TLM role was in that tight bidirectional feedback between code, engineers, and management. As a TLM, you can make org-structure decisions based on what the code tells you. As an EM, you make org-structure decisions based on what your manager tells you. But at some point in a company's lifetime, the code becomes irrelevant - nobody reads it all anyway - and the only thing that matters is your manager's opinion, and by transitivity, your VP's opinion. A flattened org structure with as many reports per manager as possible is a way for the VP to exert maximal control over the largest possible organization, mathematically, and so once that is all that matters, that is the structure you get.

Brutal

As a current IC, +1. I don’t know if it’s the case globally at Google, but I certainly know it’s also this way in my org.

+1, L5 IC in google. Your words resonate a lot with what I feel about current org, and it’s great to have this validation besides corporate gaslighting

I'm essentially in a TLM position currently. We're a small company, with a small codebase. I oversee three junior to mid-level developers, and I represent the team in our product/roadmap planning process. I also write a lot of code, review a lot of code, and make a lot of architectural decisions. At our current scale, and with our current resources, I think it works pretty well. Moving fast is one of our biggest priorities, and having a TLM definitely reduces overhead versus a more traditional separation of responsibilities.

I really never intended to have a management position, but this has been an incredible opportunity to experience a portion of it without fully committing. Other replies have described this as a transitional role, and I don't think they're wrong. In the long term, especially if the company grows, I can probably be more valuable by committing to one path or the other. However, for the right person and situation, I could see us minting a TLM again, regardless of size.

(personal opinion)

I thought it was a nice stepping stone for people to learn management without having 10 people dumped on them. But it looked bad on paper.

10 is a lot for a first time manager, but too few reports is also bad for a new manager. 4-5 direct reports is probably the sweet spot where you actually get some experience and the team is big enough that interpersonal stuff averages out.

I think the idea of a leader on the line makes alot of sense. Someone should represent the work and be able to navigate the hierarchy. These types of roles always exist informally anyway.

There’s always a downside to anything, and the merits/demerits are all about the politics of the org.

speaking from personal experience, it's not that good to have TLM as your manager because in some ways you're competing with your manager on technical scope, and you'll lose

The is funny to read because it captures my feelings on this exactly: when you're a company of passionate people driven by a mission from the top down (very important this alignment is genuinely top down), the drawbacks of the TLM-like position are totally workable: the org gives some grace and flexibility to everyone involved knowing that the TLM is sacrificing some effectiveness as an IC, those under them are losing some room for direct impact. It all works out as long you're able to "grow the pie" and make up for the smaller slices by executing.

Once you're late stage though, that's done. TLMs are probably being held to 100% of IC standards and manager standards, people under them are jockeying for "impact" and don't want to compete with their manager, etc.

I totally see why it wouldn't work at today's Google. Honestly maybe it's a positive sign they recognized that.

Doesn’t work when headcount stagnates because the teams never grow to full teams and the junior reporting engineers eventually become peers in a too small team.

Simple as that. It’s fine during times of growth but that’s not happening right now.

The value of that kind of role is that the person interfacing with the bureaucracy and the business hierarchy and its many demands also actually does the technical work and knows things about what they are working on.

Without it, nobody on the management side of things actually writes any code, or has first-hand experience with working on the product. The line managers just end up as a go-between between the workers and their directors, because they only know what their reports tell them. They don't know much for themselves.

You can't quantify this sort of loss on an earnings report, but among many other things, it does a great job of diluting ownership of the product away from the teams working on it.

I never worked with a TLM who actually wrote code regularly.

Not at Google but I'm in such a role right now and I really dislike it. Can't really get much focused coding in because you constantly have to jump in to review something or help fix something or handle a live site juniors cannot handle, or update some TPS report on what everyone is doing, or some PowerPoint or whatever. I dislike all of these to start with, but getting my own (expected) features in is an exercise in frustration. And when I ignore people and try to have uninterrupted time it feels like I'm neglecting all this other stuff. I wonder who thrives in such a mixed role...

I just structure my time Monday-Wed-Fri meetings, Tue-Thu no meetings coding. Yes, sometimes non-urgent things have to wait a day.

TLM role was both the best and worst role in tech.

Best in that the TLM generally has complete control over the product execution (and can commonly bulldoze the PM). It's amazing if you have a solid vision of what you want and you want to get it done.

Worst in that the workload can be intense as the team grows.

We did something like this but called it a different name. It was absolute garbage. Its really no surprise to see those roles move back to a more traditional alignment.

Why was it bad?

Managing skills and techlead and IC skills are pretty different disciplines.

Being 50/50 makes it hard to advance/develop in either one of them significantly.

The biggest issue is that management requires a lot of "wasted time" paying attention to whats going on around you and IC skills require a lot of "heads down time". It's a big fight between those two modes.

I've done it at a startup but it required doing most of my IC work after hours. Which isn't that sustainable.

It was terrible because the "managers" had very little training which made them mostly useless and a legal liability to the company in regards to employment law cases. In many instances they weren't even on the same direct team but an adjacent team, so rhey hahd very little interaction. This completely invalidated the premise that a technical/coding manager would be a better mentor since there was never any time for it. Of course the company paid them the same rate as the senior devs that weren't managers. I'd say at least 50% of the first year cadre left the company or reverted to a regular senior dev after one year or less. Most divisions of the company don't use this model now. The only real reason they did it was because Google did it.

It’s the only point in one’s career where you’re expected to do both programming and managing and it’s hard to do both at the same time and at a good level.

I remember TLMs being considered a bad idea in 2010. Looks like the pendulum took a full swing in the mean time.

A TLM reduction isn’t any middle management reduction. It’s an IC role still.

> This was called the TLM role at google. Technical Lead/Manager. You were expected to code and manage a couple of more junior engineers.

Ohhhh this explains so much. My career is pretty much entirely at b tier companies who try to implement what faangs/mag7 type companies do but always fuck it up because they don’t understand the fundamentals or are unwilling to part with any of amount of power or money even if they got more after all was said and done.

Anyways post covid all of a sudden every company was expecting me as part of the Software Engineering Manager roles I was getting, to have 7-10 direct reports, do 30 hours of project management per week, _and_ simultaneously be better versed in every single project my direct reports were working on or at least be the initial architect for the project.

I just ignored it and kept my people productive since that was an impossible ask of me, and for 5ish years that was good enough for companies but I guess if the faangs are wiping that role clean I better switch career niche again

> It’s part of an effort to have dedicated managers and dedicated engineers instead of hybrid roles.

The hybrid role idea has always been ridiculous. It's two different jobs, like being a mechanic and an accountant. Do you need a mechanic? Cool, hire a mechanic. Do you only need a mechanic part-time? Cool, hire a part-time mechanic. But I don't want my mechanic stopping and starting the work on my engine 3 times a day because somebody has tax questions.

The whole point behind the division of labor is to specialize, and get really good at your specialization. Picking up multiple very different jobs and trying to do both is the opposite of efficiency. People knew this 250 years ago.

I was a TL and then a TLM in my org, and am now an EM. I'm actually pretty happy about it, personally. I am organizing an eng summit tomorrow between my team and a sibling team (which is onsite and visiting from elsewhere) in my org, and I noticed that about 18 months ago, I would have been the person to give 4 out of the 5 main talks at the summit (as the expert / TL on that system). Now it's five different eng. This tells me I've been able to nurture / elevate the other engineers on the team, get them all into technical leadership roles, and then have them reach out and be ready to talk about their work to other teams.

Overall: this is a good thing. By taking up less room on the technical side, I've replaced one of me with four strong engineers. Previously, I was split between TL work and EM work and as a result, did a half job of each, leaving too much un-done.

The other thing I'll note is that engineers are basically the only role with this distinction. Product Managers, Program Managers, Sales, Marketing, all those roles seem to combine management with seniority. Only on the engineering side do we have both a TL and Manager hierarchy (while typically the TLs for a team report to the same manager that the line manager for the team does, they exert authority differently). This works out okay on the eng side when there is a strong alliance between the TLs and the EMs, but that doesn't always happen.

A recruiter in India was talking to me about some roles for some time and then disappeared. After a few weeks, when I was ready for interviews, I reached back. I was informed that those roles didn't exist anymore. I enquired further asking wahether those roles were filled, and the reply was something on the lines that no, they didn't exist anymore. Bit of a bummer because Google was one of the very few companies here that actually interviewed you pretty fairly even after a considerable employment gap. Those were L7 roles (not sure whether those are around TLM).

I think this is a good thing. Every time I've seen people in dual tech/management roles at any company, they've always been incredibly stressed about their job, and always have way too much to do.

I've also never really liked the idea of engineering managers who are technical enough to approve/veto tech decisions that team members make, since there's a power imbalance there. Even if your TLM is pushing a bad technology choice, you might not want to push back too hard because they're also responsible for your performance review and comp changes and whatnot.

>always been incredibly stressed about their job, and always have way too much to do.

So, no different from any other dedicate IC or manager at these companies?

>I've also never really liked the idea of engineering managers who are technical enough to approve/veto tech decisions that team members make, since there's a power imbalance there.

How is this different from any other manager or higher up making decisions? If your boss or boss's boss really wants something and you're not in a good market, it's never a good time to poke your head out.

>How is this different from any other manager or higher up making decisions?

Non-technical managers usually don't have strong opinions about which framework or database to use. Among engineers these decisions are usually made in a meritocratic way (weighted by who is the loudest sadly), but if your manager says "let's use X" it has a different weight than if your peer does.

I was in such a role and am now being pushed out of it (promoted to PE).

What I really love about it is the leverage. In a technical domain with a good core team it is almost like running your small company.

Some TLMs have been moved into people manager roles, it is not a move that brings the most joy vs just getting to be a TL without M again.