←back to thread

574 points frays | 1 comments | | HN request time: 0s | 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 #
1. SkyPuncher ◴[] No.45046770[source]
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.