s o c i a l s ☕
----------------------------------------
Discord: [ Ссылка ]
Instagram: [ Ссылка ]
Twitch: [ Ссылка ]
Twitter: [ Ссылка ]
business inquiries: michael@rainysun.day

s u p p o r t 👏
----------------------------------------
BuyMeACoffee: [ Ссылка ]
programmer merch: [ Ссылка ]
Join the club: [ Ссылка ]
my book list (affiliate): [ Ссылка ]

g e a r (affiliates) 🖥️
----------------------------------------
Keyboard: [ Ссылка ]
Mouse: [ Ссылка ]
Monitors: [ Ссылка ]
Chair: [ Ссылка ]
Desk: [ Ссылка ]
Mic: [ Ссылка ]
Camera: [ Ссылка ]
gear store: [ Ссылка ]

d e s c r i p t i o n 🔥
----------------------------------------
Chapters:
00:00 - intro
00:35 - my experience as a technical program manager
05:30 - my idea of a tpm
06:17 - career path
07:11 - recommendations
08:24 - outro

Becoming a software engineer is usually the most common path computer science students take after graduating college. And throughout my time studying math and computer science at ucsd, I definitely mostly looked into software engineer internships and software engineer new grad jobs.

Though I did hear about program manager positions a little bit in college, I never really understood what they were or what they did. It wasn't really until I joined Microsoft as a technical program manager that I finally understood the nuances between a non-technical program manager, a software engineer, and a technical program manager.

My original position at Microsoft was to be a software engineer. I was eventually transitioned to a software engineer program manager hybrid, which ultimately evolved into my technical program manager position.

On my first team at Microsoft, I did a lot of coding, which is very atypical for a "program manager." I mostly programmed in C#, but I was also responsible for some PM tasks like writing user stories, creating diagrams, hosting meetings, giving presentations, and editing demos.

Eventually I transitioned teams at Microsoft and my technical program manager position became a lot more program manager oriented. So a ton more meetings, planning, presentations, reporting, and ultimately less coding (but I still do code in Python!)

My experience at Microsoft so far has been that software engineers will build the product, but do not really engage with the user requirements or planning. The program managers will create the plans based on the customer requirements, but may not have the full technical perspective. Therefore the technical program managers act as the facilitators between the program managers and the software engineers, and provide support for both technical and non-technical work!

In essence, the responsibilities of a technical program manager can and will change based on the company and team (and some companies don't even have technical program managers), but overall I have really enjoyed my time as a tpm at Microsoft!

Comment down below any questions you have about becoming a technical program manager!

#softwareengineer
#programmanager
#tpm

c r e d i t s 🎵
----------------------------------------
Juan Rios - Libélula [ Ссылка ]
Juan Rios - Cabaña [ Ссылка ]

d i s c l a i m e r
----------------------------------------
I do not claim to own any or all of the pictures/footage that may be shown in this video.
All of my opinions are entirely my own and do not represent any company I work for or am affiliated with.
Any financial topics discussed are not financial advice.

свернуть