This hardly comes as a surprise. How many companies, especially startups, really need to tackle tough technical challenges? On the other hand, how many companies desperately need product talents to figure out what is valuable to produce? In addition, engineers have commoditized many technical solutions that used to be challenging in the past 15 years. Scaling used to be a tough challenge, not any more for many compan…
Waves hand, "We can always throw some more engineers at that part of the problem, what's really hard is figuring out what to do", said the project manager, and the product manager, and the QA manager, and the manager-manager. Meanwhile, talking heads in also ran companies in Silicon Valley continued to sell off stock in the mantra, "Innovation is 1% inspiration and 99% perspiration".
The highest paid workers in Silicon Valley are product managers (2016)
201–210 of 365 posts
Re: The highest paid workers in Silicon Valley are product managers (2016)
#202Re: The highest paid workers in Silicon Valley are product managers (2016)
#203This hardly comes as a surprise. How many companies, especially startups, really need to tackle tough technical challenges? On the other hand, how many companies desperately need product talents to figure out what is valuable to produce? In addition, engineers have commoditized many technical solutions that used to be challenging in the past 15 years. Scaling used to be a tough challenge, not any more for many compan…
What's up with this usage of the word "talent"? Tech is in such acute need of humble pie I don't even know where to begin. I'm becoming disillusioned. Why is a programmer etc. a "talent", but a carpenter just an employee, hire or whatever? But maybe it's actually an appropriate term, now when our interview processes so clearly have ceased to be job interviews, and have become auditions - because nothing less satisfie…
Re: The highest paid workers in Silicon Valley are product managers (2016)
#204Earlier quoted context omitted.
It is a job where your goal is to try disappoint people most slowly. You are pretty much rigged to disappoint everyone. Gotta spread that around though. Marketing, sales, and the business end all have expectation of perfect execution, on-time delivery, bug free, and the development, testing, support teams all just want realistic requirements and timelines. Somewhere in the middle is the island of slight disappointmen…
This was very well put. And one of the hardest topics to navigate in an interview process: "how would you handle a case when peron X is failing to meet requirement Y or delivery date Z? I freaking hate this question as there is no magic answer aside from "whatever it takes to minimize the overall negative impact of the outcome for the company/project/product"
Re: The highest paid workers in Silicon Valley are product managers (2016)
#205I swear, every time I read an article on HN about salary it gives me anxiety. I'm perpetually worried that I'm not earning as much as I should be earning. I don't think it is healthy but I can't look away.
Re: The highest paid workers in Silicon Valley are product managers (2016)
#206In my view, they can have it. I was a project manager (granted, a slightly different title and role) for a couple years. I went back to the bench. Fortunately I took a pay hike in both directions. Those middle management jobs seem to be super high stress, long hours, and low reward. Literally everybody I've known who went into one of those jobs did so upon the birth of their first kid, when they felt the financial pr…
Middle management -- this hits home hard. Switched to People Manager / Product Manager / Many Other Hats role around the birth of my child. I find it quite rewarding, but yes, endless hours and high stress. It's also an adjustment from programmer life when you had very short feedback loops, but now as a manager no one ever tells you "Hey, you're doing a good/bad job here!" and instead, you have to just read every sit…
Re: The highest paid workers in Silicon Valley are product managers (2016)
#207Boy, do I hate PMs. It’s as if almost every PM I’ve had to deal with isn’t particularly proficient in business, programming, or design management but knows exactly enough of all 3 silos to be dangerous at once to the other two. More often than not, I’ve found a PM will try to steer a project with some compromise to dev and design and bias toward business — in my selfish opinion as a single-silo employee, it’s mostly…
Trust me, I’d love to dig into the code (and most of the engineering team doesn’t realize I read their PRs + code every day still so I’m well aware when they’re sane-bagging) but the goal of a well run team is push/pull.
I can weigh the benefits of a product feature from the business and engineering tech debt, retention, etc angles and I do from time to time when the team doesn’t step up but I’m going to be biased towards shipping business value because I’m the umbrella that catches all the praise and the shit-storm when things go wrong.
You need a ton more victories to survive in PM world then you do in Eng world. It’s easier to be mediocre in Engineering then product b/c you’re gone after the 2nd or third bad launch.
Re: The highest paid workers in Silicon Valley are product managers (2016)
#208I swear, every time I read an article on HN about salary it gives me anxiety. I'm perpetually worried that I'm not earning as much as I should be earning. I don't think it is healthy but I can't look away.
I find them endlessly fascinating as well. My feelings are 1. Stop using the word "earning". We get paid, we don't necessarily earn our pay. Detach your pay from your perception about the work you do, and detach both from the value in the rest of your life. That may help you to take more money as well, if it turns out that that's what you really want. 2. As sibling comment says, it may be worth taking a pay cut in or…
Beautifully put. I kind of want to frame this, because it captures the brutal honesty of compensation.
Re: The highest paid workers in Silicon Valley are product managers (2016)
#209Earlier quoted context omitted.
What's up with this usage of the word "talent"? Tech is in such acute need of humble pie I don't even know where to begin. I'm becoming disillusioned. Why is a programmer etc. a "talent", but a carpenter just an employee, hire or whatever? But maybe it's actually an appropriate term, now when our interview processes so clearly have ceased to be job interviews, and have become auditions - because nothing less satisfie…
...because the skill gap between “ok”, “good”, and “great” is so much bigger for some jobs (software development) than it is for other jobs (carpentry).
Re: The highest paid workers in Silicon Valley are product managers (2016)
#210Earlier quoted context omitted.
What's up with this usage of the word "talent"? Tech is in such acute need of humble pie I don't even know where to begin. I'm becoming disillusioned. Why is a programmer etc. a "talent", but a carpenter just an employee, hire or whatever? But maybe it's actually an appropriate term, now when our interview processes so clearly have ceased to be job interviews, and have become auditions - because nothing less satisfie…
...because the skill gap between “ok”, “good”, and “great” is so much bigger for some jobs (software development) than it is for other jobs (carpentry).
It's really not. Most of the software you use every day was developed by very average software developers. The vast majority of the work software developers do isn't terribly novel or particularly difficult. And you know what? They do just fine. Things work well. Systems stay on line. Companies make money.
I've seen too many "bad" teams produce perfectly functional software over the years to think that this gap exists anywhere but in Joel Spolsky essays.
I think comparing carpenters to software engineers does a disservice to carpenters. Software developers to me are more like dry-wallers. A really good one can do it faster, but the end result mostly always looks the same.
The difference between an average and a great carpenter, however, is immediately obvious. There is real craftsmanship there, and you can clearly see the difference.
It isn't until you get to the edges of software development that those same differences become clear. When you're dealing with very high scale, very aggressive performance metrics, or very difficult mathematical concepts you see the difference between average and great developers. But those are less than a fraction of 1% of software projects I'd wager.
* I should note: I'm a software developer.