6 ms·
Tech salaries aren't risk premia: If tech salaries were risk premia, you would expect the expected value (weighted average over all foreseeable futures) of com
by rahimnathwani 7y ago
Tech salaries aren't risk premia:
If tech salaries were risk premia, you would expect the expected value (weighted average over all foreseeable futures) of compensation packages at startups to be higher than those at established tech giants. This might be true, but it doesn't seem obvious: there are often comments on HN doubting the claims of high packages at tech giants, suggesting the commenters aren't getting paid more at their more risky (p(fired | laid off | shutdown)) jobs.
Software engineering salaries are high because there's competition for the 'best' software engineers. In a competitive hiring market, the absolute upper cap on compensation is the marginal contribution of an additional engineer, less some percentage to account for uncertainties. That marginal contribution is high at the largest tech companies, so salaries are high. Other companies can either pay high, too or, if they can't use a software engineer as efficiently (e.g. because they don't get as much leverage from software, or if their engineering is poorly managed), they won't be willing to pay the market rate.
- allovernow 7y agoI'd like to add that tech salaries are somewhat unique compared to other industries because, given the nature of software development, the marginal contribution of a single developer can be substantially greater than an additional expert in most other industries. Software development in general lends to resource accumulation because useful code is written once and then potentially sold/downloaded indefinitely.
- rahimnathwani 7y agoSure, but this line of thinking applies to many non-tech jobs. For example: - developing a training curriculum or materials - designing operational processes - developing a brand identity The difference with software is that the software kind of runs itself, without much need for humans. The examples I gave above are also 'create once and execute many times' things, but they require humans to do the execution.
- chadash 7y agoTo add to this, I have friends who work in hedge funds and there, the salaries really are risk premiums. You can be very smart and capable, but have a bad year due to luck and get fired. In my career as a software engineer, I've yet to see a great engineer get fired due to bad luck alone (not saying it doesn't happen, but not with the same frequency).
- acslater00 7y agoCorrect, the author is describing the effect of a competitive, liquid talent market. The other dynamic he correctly identified was asymmetry in switching costs (cheap for me to quit my job and go work at Google, expensive for Google if I quit and leave some project in the lurch). But he didn't call it this, and it's not a risk premium per se.
- rahimnathwani 7y agoYes, there's a competitive, liquid talent market. I don't buy the part about asymmetry of switching costs. It's possible to argue that asymmetry exists in the opposite direction: each employee has one job, so switching jobs is time-consuming and risky; Google has thousands of engineers who have had the same training/experience on internal tools/standards, so it's easy to replace a single engineer when they leave a project. The other point I made is analogous to Baumol's cost disease except that, instead of applying to different types of job, it applies to different types of employer.
- withinboredom 7y agoI got fired once they realized I had an interview with a certain company. My wife was best friends with the CEO’s assistant’s hairdresser (true story of bad luck). They fired me because they knew they couldn’t afford to keep me and if I was courting these companies, they knew I would get an offer. Which was true.
- boring_twenties 7y agoI don't understand the logic in firing you though. Wouldn't it make sense to keep you for however little time longer they could? Knowing that you would be quitting soon they could try to get knowledge out of you or have you help train a replacement. And if they knew that you were going to get an offer they couldn't match, then obviously you were worth more than what they were paying you. In other words, a great deal for them. Why would they cut that any shorter than they had to? Was it just good old fashioned spite, cutting off their own nose?
- withinboredom 7y agoI didn't mention timelines. My wife and I put two and two together and realized they must have known at least a month before they fired me, and aligned with when they suddenly asked me to document a bunch of things I had built -- and focus on fixing even the smallest bugs in them. Once all that was done, I was fired. Exactly one week before I would have put in my notice.