This is my understanding. Please correct and answer: 1) TPM - These are technical folks work on mostly microservices, distributed systems with engineers. Take care of communication, coordination with tech partners or stakeholders. Paid well, Obviously less than engineers. 2) Program Manager - Nontech folks, working on stuff like vendor management, Paid less. 3) Engineering Program Manager - What the heck is this now? I have seen all these three titles exist on LinkedIn. Why I need this info: I am gathering data points to write a blog on TPM. Who am I: Staff TPM with LinkedIn. My TC ?: Very less comparison to my engineering friends at the same level. $360 all-inclusive.
Why are you writing a blog post about this if even you don’t know the answer?
Wat? I have had a program role in MSFT and in different teams it ranges from data engineering to product product. How are you supposed to generalize this??
Can you elaborate on qualifications needed for these roles? Do u need an MBA for any?
Nope, sorry, more closer to actual coding - more salary. Why - tpms have to understand both coding, user experience and project manager skills. PMs are pretty much marketing and user experience and little bit of data and sales, much easier to get skills. Def on higher levels salaries would be comparable as for directors preference would be for people who had their company before and pretty much L6 is a terminal level for all.
From your definition Google pgm also include product managers areas?
TPM and PgM at Google are on the same ladder. PdM is not. Both TPMs and PgMs are owners of programs (engineering or non-engineering) of varying size and complexity. Google TPMs are required to demonstrate technical judgment of a SWE at some level, often N-1. Technical judgment isn’t necessarily coding but involves understanding engineering: architectures, design, scalability, reliability, etc. if you don’t, you can lose the T at promo. T/PgMs do all kinds of things. Lots of external facing coordination. Helping drive decisions and making sure that data/process is in place so decisions can be easily made. Automating workflows, capacity, requirements gathering, user engagement. Eng leads can’t be everywhere at once so there’s sometimes making decisions (or marshaling decisions) on their behalf that require broad context. We tend to operate in multiple contexts, both high level and in the weeds. We can help prioritize. We keep an eye on the bottom line. We unblock engineers. At our best, we are a force multiplier—minimizing confusion and helping make good decisions so we don’t spin wheels later. We take ownership of the team’s outcomes and help team members get recognized for their work. We won’t tell you what to do, but when we’re good, you’ll know that listening will pay off.
Great explanation, what are best sources to prepare for Techical interview ? Is system design and basics of data structures enough ?
System design, highscalability, cracking the coding interview... sadly it’s kind of luck of the draw. You probably won’t be coding but I can’t guarantee it. I had to code.
Can someone post the link to the blog?
Yes please OP, can you post a link to the blog
What’s expected comp for L5 TPM at Google? And what’s the career path they take?
For tech Program manager do you need CS? Then how tech Product Manager credentials differ from that of Tech program manager? Just trying to understand the backgrounds for T product Mang and Tech program manger
At least from my experience in G for the past 5 years, they don't have material difference in terms of backgrounds. I've been in internal products (tools Googlers use) teams, and here, the line between PM and TPM is very blurry (e.g., PMs don't do market research or competitor analysis, etc.)
www.theTPMblog.com has a lot of information.
EPM is what some companies call their TPMs. In your blog post, you should (in my opinion) be candid about the generally negative perception toward TPMs, and to what extent you think it's justified.
I have seen all three title on LinkedIn for Google. Btw, I myself is a TPM, the blog is about diversity of role, research is needed