←back to thread

574 points frays | 1 comments | | HN request time: 0.354s | source
Show context
AnotherGoodName ◴[] No.45045883[source]
This was called the TLM role at google. Technical Lead/Manager. You were expected to code and manage a couple of more junior engineers.

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

This is being sold as an efficiency win for the sake of the stock price but it’s really just moved a few people around with the TLMs now 100% focused on programming.

replies(15): >>45045891 #>>45046165 #>>45046216 #>>45046446 #>>45046469 #>>45046545 #>>45046627 #>>45046811 #>>45047198 #>>45047268 #>>45048052 #>>45048255 #>>45048293 #>>45048558 #>>45049014 #
corytheboyd ◴[] No.45046446[source]
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.
replies(5): >>45046592 #>>45046770 #>>45046997 #>>45047867 #>>45048059 #
frollogaston ◴[] No.45047867[source]
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.
replies(1): >>45048021 #
1. nostrademons ◴[] No.45048021[source]
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.