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...
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.
1) one coworker who moved from the bay area to the midwest
2) another coworker evaluating NYC vs other potential places to live in the US
it seems like what Mozilla pays doesn't differ that much across their different US geographic salary bands. Both coworkers found it would be more favorable for them to take the small pay cut in exchange for a dramatic cost and quality of living difference.
And yes, someone from Mozilla confirmed here some time ago that they do differentiate salaries based on the country/region - they won't pay "US salary" to someone in Ukraine for instance.
I work for a big US company in the UK in a senior role and I get $150k approx. I work just outside London but I regularly have to attend meetings right in the City.
I'm going to move to Mexico before Trump gets his wall!
Anyway, the sad reality is that salaries are currently location based, no matter how you put it. At least until the world becomes a single economy, if it ever happens.
If it were a “nobody wants to live there” comp, I would completely understand. Supply and demand. But is London really ~twice as bad as Brighton? My lungs agree, but surely that’s not what the market thinks?
Pay people double to live on the South Pole, not San Francisco.
* Perhaps it is a rational reaction from companies to an irrational behaviour of the labour market, where the majority of devs expect it and get offended if you don’t. Fine. Whatever it is, it’s “free money”.
It could also be fair if they were to offer relocation to any place the employee picks, but even writing that sentence is ridiculous, why would a business act fair when they can exploit people?
Which is extra annoying, because working remotely means that at least two expenses may be pushed on you: office and hardware.
If you're me, and you live with just cats and love your vintage 2013 MB Pro, that might not be that much. But I also would get 80% of the benefit from a job that's just close enough to my home, doesn't have an open office, and doesn't enforce strict working hours. People who benefit more, like folk with families, also need to spend on a home with an extra room.
Desk, monitor, computer, chair, etc. Alternatively, offer a budget for a coworking space.
These kind of expenses are nothing compared to a monthly salary.
It's considered vintage already? I only just bought it 18 months ago.
Another issue is related to the time zones; things tend to fall apart if teams work across more than 4-5 timezones. I should be possible to organise teams according to time zones, but that creates a similar (although less disruptive) differentiation as co-location.
I've been the employer. With any technology professional, I'm willing--and happy--to pay right up to the rough approximation of value I feel the team member brings. Most of the time, that rough approximation is, "Do I feel like the company is getting its money's worth out of this team member?" It's rare to find the same amount of quality among a number of team members, because everyone is unique and brings their own flavor of contribution to a team. Person A might bring a lot more to the planning, architecture, and direction of the project. Person B might be great at not only delivering code, but helping others do so, as well. Person C might be a royal pain to manage as part of the team. Person D might crank code out non-stop, but seems to create bugs/issues in proportion to the amount of code they're pushing out. Judging the quality of team member contribution winds up working out to some sort of curve--there are usually outliers on the high and low ends. You want the vast majority of the team to be roughly equivalent and trending toward the high end. The low-end outliers--those who clearly are not keeping up with the team, not providing enough value in their contribution, are difficult to manage, aren't good team players, etc--those are the people where the cost starts to become an issue.
An employer who prioritizes the exact dollar cost to be as low as possible isn't looking for quality--they're looking to fill seats as cheaply as possible, while hoping something passable comes out as a result. Nobody who knows what they're doing is going to want to stay in an environment like that.
>dollar amount an employer-employee relationship definitively has is the negotiated price at which the two actors are willing to play together
I agree with this. But don't forget, the employee living in lower cost of living area can afford to negotiate lower pay to undercut those who live in expensive area.
Let say I move to vietnam, I can now easily afford to demand for 1/2 of the pay compared someone who live in bay area. Then why don't a company choose me instead ? Again, assuming I can produce the same quality of work as bay area programmer.
The goal of a company is still to make money and managing expense is always important.
If think you are that really really special programmer who are better than most people worldwide in what you do, then yeah you can demand whatever you want.
I knew I'm not that special. By living let say in Vietnam, I'm still happy with the 1/2 amount I got and companies has incentive to hire me instead.
> I thanked him for his opportunity and advised him to contact some sweatshops instead of playing the "remote" game.
> asking me to go down 1/3rd of my price because of where I lived in seemed ridiculous to me.
I agree with the general principle that you shouldn't give massive discounts because you live in a lower cost of living area, but you're comparing it to a Bay Area salary as if that's the norm. It's a massive outlier. Going down 1/3rd of a Bay Area salary (I'm assuming a developer of some sort from context) still puts you in the top 1% or so of earners virtually anywhere in the world. Offering two thirds of a Bay Area salary certainly can't be described as a "sweatshop" salary.
Also it's worth considering that in this business your employees are hired to think. It is nice companies starting to realize that it's not needed to be present 100% in the time in an office to be able to deliver the thinking, but they also need to realize that my brain produces the same output no matter where I live.
This was part of my point: you're taking the Bay Area as the standard by which you're judging everything else. This is backwards. The Bay Area is an extreme outlier.
Yes, it's a personal preference. But if you choose to live in the Bay Area, your income requirements eclipse everybody else's. Everybody else can live extremely comfortably anywhere else on that kind of money. If you have the personal preference to live there, why should a business pay you more than everybody else everywhere else? It's your personal preference and it doesn't help the business in the slightest.
What's to stop me just moving somewhere cheaper after I get the remote job tired to location? Are they going to renegotiate with me? What if I just forward my mail and don't tell them.
Further still, there are always expensive areas in poorer places and cheaper areas in expensive places. Are these companies going to start auditing our finances before they discuss renumeration?
As an example, GitLab explicitly requires you to inform them and makes no guarantee about if and at what pay level they offer you a new contract.
> What if I just forward my mail and don't tell them.
Sounds like an interesting problem for the courts once they find out.
But at the end of the day, do we really think gitlab is going to dimiss or renegotiate with a performing employee rather than this being a loophole to get rid of someone they don't value?
Nothing, assuming I can find other people with the similar quality as you, but significantly cheaper because they live in lower cost of living area, why would I not replace you ?
I read "going down to 1/3" differently than "going down by 1/3". "going down to" leaves you with 1/3; "going down by" leaves you with 2/3.
They didn't; as the OP already mentioned, they went back and edited it.
A person did put in the same effort as the other one for learning something.
Since a person leaves in an area which isn't properly developed or cheaper, he/she is living in order to save money or due to some other personal reasons, shouldn't be discriminated and paid less for the same talent/value the company receives.
Obviously it always feels better to live in developed areas.
When a company is receiving same quality from different vendors, they should pay the same for different vendors irrespective of their origin of locations.
Your biggest mistake was mentioning the Philippines. The sad fact is that a lot of employers, including Filipino ones, associate this country with low-wage employees and cheap labour. That's why the PH is the capital of outsourcing and offshoring in order to cut costs. It shouldn't matter, and I feel sorry for Filipinos trying to get paid fairly in this business climate, but unfortunately this country is so corrupt that it's a case of poor economics and planning.
I would love a list of such companies, maybe people posting on the monthly who's hiring thread can clarify that.
Rent, food, taxes, transportation etc etc reflect on salary. Also competition has a major impact on salaries. Companies fight a lot over SF engineers, not so much for those in Asia. (unless they're super brilliant)
Edit: Google has ~ 85,000 employees. If they give each employee an extra $100K bonus it would cost them $8.5 Billion. They can afford it. Why they don't give it? Because they don't have to.
What would happen to salaries if 150,000 more engineers from middle America started to apply to jobs in SF?
He's right, you are wrong. Bay Area salaries are high because it's very expensive to live there. Even dev salaries in Europe are 20-30% of what they can be in the BA.
The brutal fact is most companies simply re-brand outsourcing as "Remote" employees. Case in point, a few years ago, a DIY website builder (a company with a name of a coniferous plant species which I won't name directly) contacted me for a "remote" position.
I passed all their tests and we eventually went to the salary negotiation stage. I agreed to this interview in the first place because I read online they paid really well for their employees, particularly in the US (Bay area).
So, when we were discussing the pay, I threw in a number that's common for the Bay area employees and what seemed very, very reasonable for me. In fact, my current salary was almost the same, just so to make it clear to you that I wasn't trying to take advantage of them or anything.
Immediately, the founder got offensive and told me, "What? Are you serious?? You live in Asia (I was living in Singapore at the time, which already had better pay as opposed to PH), for our employees in Philippines we pay 1/3rd of that and I can still get the job done. Why would I want to pay you that salary?" I told him, "Well, this is what you pay your Bay Area employees, don't you? Besides, my experience more than matches the job profile and requirements and my test results just proved to you I am more than capable for this position."
His answer? "But, you don't live in the Bay area". I thanked him for his opportunity and advised him to contact some sweatshops instead of playing the "remote" game. Since then, I very very carefully ask anyone who uses the word "remote" a LOT of questions, qualify them if they really know remote isn't the same as outsourcing before even going into the interview.
I would have happily agreed to a lower salary if it was fair enough. But, asking me to go down to 1/3rd of my price because of where I lived in seemed ridiculous to me. In the last 10 years, I've lived in 7+ different countries and 35+ different locations within them as I'm that sort of person who likes to travel and explore new cultures. Basing my salary or worth based on where I'm from, where I live in at present seems the most ridiculous thing to me about remote work.
Edit: Typos and clarifications