Hacker News new | past | comments | ask | show | jobs | submit login

What's different here is presumably the scale the policy is being applied at, which creates the likelihood that significant groups of employees will be able to demonstrate disparate impact. For it to be a problem, there need to be enough remote employees in "favored" and "disfavored" {location,compensation} buckets to make a case. Gitlab is presumably not there yet.



You think the US government isn't "at the scale" of Facebook?


USG pays flat rate globally. They then plus up a COLA allowance based on high-cost areas, special circumstances, etc. But the base rate is a flat rate for a given position. You can pay 'less extra', but not 'less', generally. Which I'm sure is what FB and others will technically do.


Parent comment started:

>What's different here is presumably the scale the policy is being applied at

Suggesting that FB is somehow going to apply any policy to its employees that is at a larger scale than the US government is a bit ridiculous.

Yes, I agree that's what FB will do.


BAH is based on your duty location


For Active Duty - yes it is based on duty location zip code, because they assume you will move near the base that you work at.

For National Guard - it is based on Home of Record zip code. Many National Guard members travel >100 miles to their assigned Armory.


But that's an adjustment / extra, not a change to your pay as an O-3 or E-5 or GS-12 or whatever.


Does it really work on a company level like that? In the industry as a whole the scale should be enough.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: