[dpritchett]

Article fails to explain why a dev would desire to become a PM. My best guess is an entry point to a management career in shops run by non-devs.

Edit: I imagine that's perfectly natural - when I was in backoffice IT I strongly desired to transition into project management so that I could transition into people management so that I could make meaningful decisions and get credit for them. It's probably the same in product companies except low-level devs will want to manage products so they can manage divisions so they can run big-name tech companies. Currently I'm working as a consulting dev in a small dev consultancy and I don't feel the same pull in that direction that I used to. I think maybe all we really need is to be taken seriously and to have some meaningful work.

[plinkplonk]

"Article fails to explain why a dev would desire to become a PM."

(in most companies) more money, power, autonomy. Except in very early stage startups, it is the rare developer who has more of any of this than even the lowliest PM. e.g: I think Vic Gundotra makes more money, and has more power at Google than most (all?) engineers there.

[hifier]

This is not my experience. Companies with strong engineering organizations that are parallel with and equal to the product/business org structure would not have a product management bias. I would only work at a company where engineers are managed by other Engineers who are partners with the product and other business teams, not reporting to them. (I'm a Software Engineer).

I also think that engineers would be paid much better than product managers in such an organization, given the higher demand for engineering skills (there should be more engineers than product managers on any given team) and a smaller pool of potential hires.

[sbc4590]

I'm not sure this is true, at least in the current climate. At our (Series B) startup, PMs make about half what engineers do.

[ivanplenty]

Not to discount your experience, but at the large enterprises (Amazon, Microsoft, Google, etc.), Program Managers make the same money as Software Developers at equivalent titles. Program Managers are not JIRA monkeys (I love JIRA, by the way), but generally have coded in the past and have a better grip on reality than some MBA candidates.

The tradeoff is this:

1) PMs get broader visibility across the org, which tends to result in faster promotions into management for "good" PMs.

2) PMs atrophy technical skills and become more dependent on the larger organization (they acquire more firm-specific skills in econ talk) than do equivalent developers.

So, sometimes if you like your company and want to advance quicker, you will be willing to trade away some industry or general skills for firm-specific skills to get faster promotions or more power.

[dpritchett]

I've never worked at a product company per se, but that is exactly why I aspired to transition into project management back when I worked in corporate IT. Can't blame folks for wanting the money and the power after they see how things are for the Vics in their companies.

[RougeFemme]

In all but small companies, I think devs have little to no contact with the other product/project stakeholders. For those devs who would like to be in a position to influence/interact with the stakeholders, being a PM would eliminate some of the constraints/WTFs devs often feel. Well, not always eliminate necessarily, but minimize them, or at least provide some transparency into the part(s) of decision-making process(es) outside the devs' sphere of influence.

[nerfhammer]

I think because it trains you in skills that are relevant for a CEO or founder, whereas being a dev very often doesn't