This is how you keep poor countries / states poor. Instead of paying people the same which would result in larger taxes paid and more spent in those locations you are keeping status quo.
It has nothing to do with your value and everything to do with what the company has to pay to get the talent it wants.
If lots of people are applying from a low-cost country, the employer is free to choose and thus, would be able to offer a lower salary. But from my understanding, employers want the same level of quality as they would get from the bay area, but insists on paying 3rd world wages if the remote is at a low cost of living location, even though there are very few other candidates suitable!
This is only true as long as remote jobs are so rare that the candidate is unlikely to find an employer who will pay non-location-adjusted compensation (even if that comp is midway between Bay Area-adjusted and Asia-adjusted comp), or more directly, to pay based on value added.
And… that statement is already not true for great (top 20th percentile?) candidates, and trending towards not true for candidates in the middle of the Bell curve. That is, a person with known skills and a good network can obtain offers from multiple remote-first/remote-friendly companies today. There's already a location-ignorant market for their skills.
As more remote jobs are available, more people will get multiple remote offers, that is, they'll find a location-ignorant market for their skills. The clearing price for their skills will trend towards the value they're perceived to add, even if it takes 5 or 10 years to get there. That perceived value isn't location-adjusted, particularly for remote-first companies trying to hire the best candidates or to hire as many great candidates as they can find (rather than to save compensation expense).
There will be the "location independent" companies that pay top dollar, and then everyone else who pays a "global market average". Top candidates will get the top pay, and everyone else, even if they live in the Bay Area, will have to fight for the "global market" rate jobs, meaning it won't be feasible to be a programmer in the Bay Area anymore (barring a solution to the California housing crisis).
Hmmm... this sounds very strange.
Getting a job is dependent on you proving how much value you'll bring to the company, but your pay has nothing to do with "your value".
Sounds like someone wants their cake and to eat it, too.
California taxes aren't higher because the average pay is higher... Someone making minimum wage pays the same for fuel as anyone else there. The taxes are higher because there are more social programs and generally it all costs more. the real estate in large parts of california are higher based on market desire. That creates side effects of people asking for and getting more money to work there, and it circles around.
Taxation as a percent of income is entirely down to effective spending. And often corruption. Maybe start charging Nestle fair value for all the water they remove from the state.
Colocated employees at the same skill level performing the same job aren't paid the same - employers and employees negotiate compensation individually.
In the UK it's particularly comical because a good number of people commute that far; I've had colleagues (Central London) living in places that according to GitLab should earn half as much.
The train takes 35 minutes to get into Waterloo... Commuting sucks, but it doesn't suck that much.
Interesting. This is roughly the amount they're offering contractors in Poland.
Everywhere in Poland on top of that, because it's considered a single region, so you could possibly live in a small town where rent is ~£250 and other expenses proportional to that.
If not a PO Box, some other proxy by which you aren't genuinely living there. Maybe just a short-term roommate lease situation?
It's almost a no brainer to me. If I can charge 3-4x more for the same skills that I have, why not. I'm not gonna take a huge pay cut just because my location changed. And there's almost no explaining involved.
At times when you can't go somewhere physically, sometimes you can tell your clients you're traveling this month. If something is important, you can take a flight. The amount that you're saving, the flight costs are negligible.
Also, what happens to a full-time remote worker who decides to move? If they tell their employer that they moved from SF to somewhere far cheaper, should that employer dock their pay? What if they're just temporarily moving (e.g. living abroad for a year, but returning afterward)? If you're going to work remote, it may make sense to rent for a month or so in SF to be present for interviews and then move back to wherever you want to live, which would essentially mean you "live" in SF for that period, so it wouldn't be lying.
I know that shit works because rich people do it for taxes all the time.
The middle ground is irrelevant. The market price will be determined by supply, demand, and the differences in productivity and other factors of remote programmers. They’ll meet somewhere in the middle between the current local labour market model and one where collaboration software and practices are so perfect that there’s only one market for programmers, the global one. But we don’t know where yet.
If that's too expensive, adjust your recruiting or hiring strategy. Maybe recruit bay area programmers that realize their current salary isn't sustainable since they need to plan for illness, retirement, saving up to launch an idea, etc.
[0] https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/dat...
You should always pay me for what I can do not where I live.
I think, the idea, is that in SF he'll have no problems finding jobs. They are looking remote because of shortage in SF. I mean according to them.
As long as it's within US?
The only fair way to adjust is based on value to the company, and what the potential employee is willing to accept. It isn't reasonable to use pay to remove the financial advantages of a candidate's choice of location, and then claim "you can now hire the best people on the planet in any particular function" as the original link does. If someone is among the best people on the planet, they'll likely be paid considerably more than the San Francisco average without regard to what their costs are.
One of the touted benefits of working remotely, for those who can, is exactly the ability to trade off the advantages and disadvantages of living in places with varying characteristics, and it's unsettling to have a company which claims to support and encourage remote work also be upfront about actively working against remote workers' ability to make these choices.
AFAICT, the flipside is that "flat global pay" is that then the company can't offer as compelling an offer to those in expensive areas. (i.e. if everyone paid a flat fee and you were stuck in an expensive city, then you would be penalised when looking for remote work).
How does that explain the large number of Bay Area, on-site-only startups?
None of these are perfect, you're never going to get two truly comparable locations when accounting for mortage/rent, groceries, cost of transport, cost of consumer products etc., but it's a whole lot better than mainly looking at one variable (rent).
Not for work where the employer isn't specifying a location constraint. For on-site work, while one can debate the exact ideal formula, location adjustments within a firm based on comprehensive cost-of-living makes quite a lot of sense.
For example in the UK if you live in London and earned £60k, according to GitLab's 'Move Calculator' in Bristol you would earn £42k, or in Brighton £38k. Yes there is a difference between the living costs, but there is not that much difference. A 1br apartment close to the center of Bristol is around £900/mo, and in London zone 2 around £1200/mo.
I've seen a lot of remote startups offering salaries around $100k USD, independent of location. For most of the US (outside hot areas like SF or NYC) and Europe that's a good salary, but what if the person you want to hire likes living in the middle of SF and doesn't want to move? For them that salary is going to be too low. I'm not really sure what is the middle ground here.
[0] https://about.gitlab.com/handbook/people-operations/global-c...