3 ms·
Does anybody at Microsoft know whether "PM" refers to "Product" or "Program/Project" manager? In either case, that sounded like a tough decision, although hopef
by otoburb 12y ago
Does anybody at Microsoft know whether "PM" refers to "Product" or "Program/Project" manager? In either case, that sounded like a tough decision, although hopefully he built up a large enough personal runway that helped make the decision to strike out on his own easier.
- adamvalve 12y agoFrom when I went to interview with MS, the PM role was Program Manager.
- santaragolabs 12y agoNot at Microsoft but know the company well (did contracting work for some teams). PM refers to Project Manager as far as I know. But there are different levels of PM's within Microsoft. You can be a completely junior PM managing two really junior devs developing a simple feature. Or you can be a principal level PM and earn that amount of money. Just the term PM doesn't mean much.
- vtbassmatt 12y agoThis isn't correct for product development groups; things may be different in IT and MCS. In product groups, PM always means program manager and the role really isn't much about project management. PMs at Microsoft are engineers and subject to the same "I", II, Senior, Principal, Partner title hierarchy.
- santaragolabs 12y agoThanks for clarifying that. And I indeed meant the title hierarchy you mentioned.
- halestock 12y agoprogram manager.
- kelukelugames 12y agoPM means program manager at Microsoft for anyone in engineering. I honestly don't if Microsoft's product managers call themselves PMs or not behind closed doors.
- ethomson 12y agoA "PM" at Microsoft is a "Program Manager". This is a relatively vague term when it comes to responsibilities and deliverables and tends to vary from team to team. Generally, though, they will tend to be more customer facing than engineers - collecting information from the customers and creating a plan for the Engineers to execute. While this might sound like the old Office Space gag that they "take the specs from the customers and bring them to the engineers", a good PM brings a lot of value to the team and - in the classical PM role - frees up the engineers to worry about implementation and less about what this message should say when this error happens. But a great PM will come up with product strategy and just do whatever needs to be done to get the software out the door. Sometimes this means working closely with lawyers. Sometimes this means working closely with the security team. Sometimes this means writing code. Or making sure the marketing team is on the same page as the product team. Or that the sales team knows how to pitch this and has all the materials they need to present. Or presenting to customers at conferences. Sometimes this means baking cupcakes for the team, just because. It's a time consuming, unenviable position in a lot of ways. But it's also probably the position at Microsoft with the most ability to impact products that ship to customers. (Disclaimer: Microsoftie.)
- FireBeyond 12y agoGreat description, very spot on. I started to describe, then figured that this sums it up just right. - Ex MSFT PM