According to one popular-remote-company, that is a 30% downward adjustment. If you were making 200k in SF (for many, that is low), that is a 60k pay cut. If we assume 30k was a "real" adjustment, that is a 30k difference in spendable income. That feels like a demotion.
We also know that many large-ticket items in life do not adjust for "cost of living" in the area that you live. College tuition, medical expenses, etc.
Over just a couple years that 30k/year difference is an entire college education for a child.
From personal experience speaking with larger companies (not FAANG, but larger "start-up"), I was always seeing an even larger difference. Think "~150-170 in Austin, 225-250 in SF". You may want to knock my negotiation skills, and perhaps you have a point there that I could have pushed their initial non-SF numbers up, but these were at earlier-stage discussions and sharing those numbers seemed "reasonable" to them. And this was Austin, a city which the aforementioned salary calculator only gives a -20% "adjustment".
Note that even that 30% is for a "large" AR city. Anyone else in that state is given a 37(!)% reduction.
In my opinion, which I've been trying to wrangle into a coherent blog post over the last couple of days, any adjustments like this should be an absolute-dollar-number figure. Percentages don't make sense at _either_ extreme. A 60k/year position with a 20% "move to SF" upward adjustment? That is unlikely to even cover the change in rent. 400k/year with a 20% adjustment? Calling that "cost of living" is bonkers.
@nrmitchi is probably talking about GitLab and their “Compensation Calculator” [1].
[1] https://about.gitlab.com/handbook/total-rewards/compensation...
Clearly companies are willing to pay $200k+ for top talent. "Cost of living" or however you want to break down that salary is irrelevant to what companies think employees are worth.
Unless the company is getting less value, they can stand to pay the same no matter where you are physically. Calling it a cost of living decrease is just kabuki for paying less.
If WFH continues, salaries should normalize across all regions but its yet to be seen what the value of top talent vs average employee is at a global scale.
In a market where the market equilibrium for that top talent is $200K+. There is no inherent virtue in a '$200k+' number.
> "Cost of living" or however you want to break down that salary is irrelevant to what companies think employees are worth.
Exactly. Companies care about the cost of labor, not the cost living. And if you are in a different geography with a lower cost of living, it is believable that the cost of your labor is less. Why is it surprising then?
>There is no inherent virtue in a '$200k+' number.
Indeed there is. It shows that the value gained by the employer is at least that of $200k+. It is not arbitrary and it is not wholly derived by supply. The cost of labor is set by the labor supply as well as the labor demand.
Not only does a an employee's location not change the employers' demand, the moving also does not change the supply available to employer. Moving or not, the employer could always find a new employee abroad if supply was indeed plentiful.
A less abstract way to look at things is this. The cost of living boost is just a bait to work somewhere. There's no magic to it. Just because you took one deal doesn't mean you should so easily take the opposite deal.
The company tolerating remote workers changes the supply to the company.
The people moving immediately are seeing the first effect here, but if it becomes permanent, the people who don't move will inevitably get the same paycut. Why pay $200K for someone in SF when someone in Des Moines will take $140K, but wasn't willing to relocate five years ago?
The crux is that the supply curve is not fully known. For argument's sake, you can imagine both that talent is distributed uniformly as well as imagine top talent was already pulled towards urban centers.
We don't know exactly what the answer is but one thing that does not make sense is that the supply is somehow linked to local cost of living.
You admit yourself that this current offer to relocate is artificial and not a product of the market reaching equilibrium, so why accept it?
There's a potential scenario of now "company in cheap city X is willing to pay for SF talent, but couldn't convince them to relocate before, but can now hire them remote" that would also push up demand for top talent, but it seems much more likely to me that demand for top talent stays about the same while supply increases at least a small amount, which would push down wages.
I think I am understanding it, but you are merely repeating your points without addressing the economics that I am pointing out.
> Indeed there is. It shows that the value gained by the employer is at least that of $200k+.
Yes and so the value you generate for the employee puts an upper bar on what salary you can command, not a lower bar, which is what you seem to be implying.
> Not only does a an employee's location not change the employers' demand, the moving also does not change the supply available to employer.
It increases the supply available, because today, given the investments Google has made in setting up offices for ~30000 employees in the bay area, they have to fill that demand using employees located in the bay area. They don't have to do that if they can hire from anywhere, so the supply increases.
> Moving or not, the employer could always find a new employee abroad if supply was indeed plentiful.
And they do! Google has employees around the world, and surprise, they do not get paid as much as they would have gotten paid in the Bay Area. Why is a Google engineer in Bengaluru who is hired by the same hiring process paid 1/3rd of what they'd get paid in MTV? And to preempt the usual HN racism against the quality of Indian engineer, the same Google engineer would be paid the MTV salary if they moved to MTV. This is not a hypothetical, this is literally what happens to the countless Google engineers who transfer from BLR to MTV.
Based on your logic, why is that engineer NOT paid the MTV salary today in BLR?
————
I mean I am not even making a far-fetched claim. Bay area salaries are the highest in the world. They have to move down towards the average if some other salaries are going to rise because the engineer who lives in Randomville Alabama didn't have a Google office he could commute to and hence wasn't in the supply pool, but now is, can now compete for the Google job.
Indeed, perhaps that will be the case if there really is so much supply; if that's what the supply curve turns out to be.
But it makes zero sense to pin salaries to local cost of living other than to bait a candidate to live somewhere you want them to. Its not based on demand, its not based on supply.
Sure, they can "stand" to pay the same. But why would they. As you yourself said:
> Rates will be set by market forces, not any concept of "fairness."
Ie, companies are going to pay you as little as they can get away with. If the market-price for a good SF developer is $200k, and the market-price for an equally good Las Vegas developer is $100k, then your pay will trend towards $100k as soon as you move from SF to LV. Maybe inertia and your manager's largess will prevent it from being an overnight change, but that's the long-term trajectory you can expect.
The distinction is important when you end up in markets with high COL but low software engineer market rates (e.g., London), or how dealing with the expensive Bay Area can still make sense compared to midwestern metros--depending on the type of lifestyle you can live with, that is.
Of course some SE's in London don't have a visa to work in the USA, and others wouldn't want to even for a huge pay boost. But it's still quite fascinating that a location-dependent "market rate" materializes from this dynamic. In some cases it seems like location is used as a proxy for skill -- as though an engineer who opts to drive three hours south from Vancouver, BC to Seattle, WA is now a higher-skilled "Seattle dev" than they were three hours before.
If that assumption is taken away, then the fascinating thing is not that companies would pay less in areas like Vancouver or London, but rather that they are willing to pay such a high premium to engineers who live in Seattle and the Bay area.
It's hard to think of any explanation other than that very profitable companies (like Google and Netflix in the Bay area, and Microsoft and Amazon in Seattle) started there, and paid a lot for engineers to move in and join them in an era where remote work was rare; then, when remote work became common, the legacy of a location-dependent market rate created a self-sustaining expectation (Schelling point) that engineers in that area wouldn't work for less to compete with talent elsewhere, sometimes using high COL as an excuse. That might gradually be reversed as companies seek to reduce their payroll expenses, or it might not.
Very well put.