3 ms·
The rational way to do this would be for Facebook to take into account COL when setting salary for non-remote work, and to not take it into account when setting
by tzs 6y ago
The rational way to do this would be for Facebook to take into account COL when setting salary for non-remote work, and to not take it into account when setting salary for remote work.
Why? Because if they are specifically trying to fill a spot in Menlo Park they are going to have to pay enough to attract people who live within commuting distance of Menlo Park. If they are trying to fill a Seattle spot they need to pay enough to attract Seattle workers. And so on.
If they are trying to fill a remote spot then they should be largely indifferent to where that person lives. For remote work they only need to set pay high enough to get the number of people they want from the entire country.
If they set remote pay at a level that makes them attractive to people in Georgia but not to people in Connecticut, and at that level they can find all the remote workers they want, why should they care that Connecticut engineers aren't applying for remote Facebook jobs?
- rayiner 6y agoYes this makes total sense to me. The pay bump in SF is to get sufficient good people in SF, which the company cares about because it has an office there and needs local people. That rationale evaporates for remote work.
- hedora 6y agoIt would be interesting if they also figured in the cost of providing office space, food, etc when recomputing remote workers’ pay. The rule of thumb I’ve heard is that workers cost about 2x their salaries, with the additional money going to HR, taxes, IT, morale budgets and facilities. Facilities is the biggest of those costs. (This completely ignores stock based compensation.)
- esoterica 6y ago> If they set remote pay at a level that makes them attractive to people in Georgia but not to people in Connecticut, and at that level they can find all the remote workers they want, why should they care that Connecticut engineers aren't applying for remote Facebook jobs? Presumably because there are not enough people in Georgia alone who meet their hiring bar to fulfill their staffing needs. So they also need to hire people in HCOL areas with better competing offers and more leverage to demand more money from them.
- Xcelerate 6y ago> Presumably because there are not enough people in Georgia alone who meet their hiring bar to fulfill their staffing needs I kind of doubt this. Many of the people I went to Georgia Tech with immediately moved to the Bay Area for CS jobs. I'm pretty sure that school alone can supply quite a bit.
- joshuamorton 6y agoQuite a bit, yes. Maybe enough to supply facebok with junior engineers, but not that's one (and the smallest!) major tech company.
- dkersten 6y agoThen they need to raise the amount enough to attract more people. They can pay different people different amounts, but the amount should be based on what they need to attract them and not take location into account. Eg if the higher amount raises the number of applicants in the lower cost of living area too, then they shouldn’t go “oh, but you’re in the lower cost area so your offer is lower” Ie raising the offer raises the applicants, where those applicants are should not matter.
- deleted 6y ago[deleted]
- joshuamorton 6y ago> They can pay different people different amounts, but the amount should be based on what they need to attract them and not take location into account. But what if you need to pay someone in topeka less to attract them than someone in NYC? Specifically, if we think about the idea of a market, and assume some jobs won't be remote, the dev in NYC will have a larger market (remote jobs + onsite jobs in NYC) than the topeka dev (remote jobs + onsite jobs in topeka). This is actually the same way things are now. What is so unethical about a company choosing to pay you (in the case of facebook, well above) market rate in the market you choose to reside in?