I find them usually often inaccurate, though.
For companies that don't pay at the top of the scale, the people in the high-cost areas are comparatively screwed (software engineers having to resort to living with roommates!?), whereas for the companies paying more, sometimes it tips the other way (like failing to account for how most costs don't scale with area the way housing does, so you could end up with a $500+ disadvantage in disposable income in one of the cheaper areas).
For instance, the only person who can classify income as disposable or not is me. No one else is allowed to make that decision, or is even deserving of knowing the information at all.
If your hiring manager is giving you the song and dance about calculations on your cost of housing and milk, you need to turn around and go elsewhere.
If you think you’re a cog in a machine, yes, you can determine your value this way.
If you feel you have inherent value in and of yourself, your attitude will change about work and employment.
The value I provide to a company has absolutely nothing to do with where I live. If I’m a good hire, I’m a good hire.
It's a view on negotiation, not on employment.
But I think feelings like yours get in the way, regardless.
"Determining your value" is internalizing things way too much. Failing to convince the opposite side in a negotiation is very different from "your value".[0]
Being a cog in a machine - or, more directly in this situation, being seen as replaceable by the next candidate who would accept the offer you don't like - isn't about how you feel or think of yourself, it's about what you can do and what you demonstrate. That holds true for far more than just the initial interview and offer negotiation, too.
[0] I'm tempted to suggest the person who's happy to be a "cog" - show up, do some work, get paid, and define their life and their value in non-work terms - may value themselves more than us maximizers!
If you want to get paid the big salary, move to the big city. Don't complain about higher rent and cost of food. Or live frugally.
I dictate my value, not my zipcode or employer.
That could be totally fine and rational since there are other utility-maximizing considerations for you like how much you want to work, the kind of work you do, the kind of clients you're willing to take on, etc., but that doesn't change the fact that you can't arbitrarily set your price and not expect a change in the amount of business you can conduct.
You may not be profit-maximizing, but companies certainly are, and as a result, they'll pay whatever rates the market allows them to.
It's obvious we're not comparing humans to rice here since we're not buying and selling humans. It's so obvious that I can only conclude you're acting in bad faith intentionally.
I don't think companies that want to attract upper-tier engineering talent will be able to get away with it either.
Good engineers:
A) Are outnumbered by job openings non-trivially
B) Return many multiples in value of their total compensation cost
C) Are well aware of A and B from a negotiating standpoint
If I'm operating in the same market orbitals as Facebook, I see this as an instant hiring advantage. Simply tell candidates:
"Not only have we shifted towards remote-focused teams, we won't arbitrarily grade your salary based on where you or your family choose to live"
The increased costs will be a pittance compared to the potential 8-9 figure market advantage gained in 18-36 months by having consistently won hiring battles.
For example, for engineers in many big tech companies, pay vs COL in London is not very attractive.
I get why management wants to do this, but I doubt it will stick with remote workers.
EDIT: And odds are, the employer won't notice enough to fire me.
1) You're upfront about it and tell your manager, they update workday, HR schedules a meeting with you to explain the multiplier effect and how your salary is being reduced.
2) You're kind of sneaky, you update your state tax withholding, it updates workday and put you into the appropriate COL bucket for next year's performance review, your salary slowly falls in line with people in your COL area.
3) You keep it secret, allow the company to keep paying taxes to your original state, maybe pay estimated taxes or something to your new state? Don't develop any relationships with coworkers that'll eventually leak your true situation, get away with it?
But if you reduce my pay, you're gonna make me take stock of what I'm giving you and shift the balance in my favor if I can easily get away with it.
Where this development fascinates me is that it vastly increases the pipeline into the FAANG BigCos. I'm sure that, not to be outdone by FB, other members of FAANG will be having serious conversations that are along the same lines as this. Even if your career at a certain company plateaus because of satellite syndrome, you at least have the door open to moving to where the action is if that's what you prioritize.
But for me, so long as the real world reflects the asymmetry of capital allocation at central nodes, so too will salaries reflect that. I don't see any point in protesting that. I feel like it's more valuable to try and figure out a way to speed up the diffusion from central nodes outwards which already appears to be happening, and which this story is part and parcel of.
Tech companies have always paid less to staff in cheaper cities like Pittsburgh, but the ratio usually still favors the employee (i.e. they make 90% of the Bay Area base salary and their cost of living is 20% as high). Workers can also hack the system by getting irrevocable, long-term RSU grants and then getting transferred to cheaper markets.
Salaries WILL be the same everywhere in the world. They will just be a lot lower than you are used to.
Are they paying "Bay Area" salaries, or "Skills With The Most Obvious Correlating Signal Of Living In The Bay Area" salaries?
> Salaries WILL be the same everywhere in the world.
Does a Mercedes and a Honda Civic cost the same?
No?
Well why not? They're both cars.
They're paying for the skillsets, and for salaries to be the "same everywhere in the world", the skillsets would have to be the same, and we're not at the point where they've been commoditized to that level(which is a different discussion versus geography anyways).
This is THE reason driving all these companies to announce the shift to remote: it’ll be a massive cost saving. Access to talent that can’t live in a center where they have offices is nice, but hardly justifies the overhead of remote work
However, if the choice is between working for a local company and working for a high end bay area firm, then absolutely the best financial move is to move to SF/Seattle/NYC. Local companies here top out at $150,000 for a senior engineer, so if I can make $400,000 in a big city, then even with the higher cost of living, I still would come out way ahead living in SF.
I could go on, but you get the point I'm trying to make here right?
Because people living in those other markets will be more than happy to take a "reduced pay" for SF standards, since that's way higher than any other local wage.
If a company suddenly allows working remotely full time, they've suddenly increased their supply of talent, as moving to another city will no longer be a roadblock when they consider Facebook.
At the same time, if more and more companies go with a remote friendly approach, the supply of job openings that applicants have access to will also increase.
Theoretically, this will lead to some sort of equilibrium where compensation is actually based more on the value/output of your work than other factors.
To make an analogy, an apartment building in SF serves the same purpose as an apartment building in Ohio, yet they charge vastly different rents. You're paying less in Ohio for something that provides the same utility (shelter), because of factors outside of the direct utility of the apartment.
Facebook pays Bay Area salary only because they have to, to get the talents they want.
In fact, developers everywhere benefit from the high salaries of the Bay Area, as it sets the general expectation for the profession.
Competition -> high pay
high pay + zoning rules -> high COL
The variation won’t be as dramatic within a region but it’ll be there.
Personally, this is a deal breaker for me. I don't want to get paid less for doing the same amount of work. In a remote world, deciding where to live should be a personal decision of how one spends their income. Facebook doesn't pay employees less because they decided to drive an expensive car to work.
Facebook, along with all other tech companies, make crazy amounts of revenue per employee. The pay reductions will be a rounding error on the company's budget. Why not keep salaries the same and get the absolute best talent in every market across the world?