News for hackers. Stuff that matters.
Re:Stripe's remote engineering hub, one year in by rajman187 on Sunday May 31, 2020 @05:45AM (#23368384)
There are two issues at least. First is working in a country whose government could demand or seize your company-issued equipment, jeopardizing privacy and corporate secrets. Second is tax regulation. If you are an working in a country where your company doesn’t have a presence, suddenly the government can make the case that now there is a reason to tax the company because your working there can constitute presence. So not only would you be potentially liable for taxed earnings but so too your employer. Also some companies have announced that they would adjust compensation in accordance with cost of living, so moving from the Bay Area to Idaho or Belize would no longer be as favorable (I’m sure it would still afford a very comfortable standard of living regardless).

Note that I am not a tax attorney nor an expert on international affairs. These are some things I’ve gathered for why I can’t sit on a beachfront property in Thailand or South America and work.

Re:Stripe's remote engineering hub, one year in by abalos on Sunday May 31, 2020 @09:28AM (#23369459)
Another challenge is time zone differences.
Re:Stripe's remote engineering hub, one year in by GordonS on Sunday May 31, 2020 @10:11AM (#23369697)
This is definitely true for most orgs, but in some case it can actually be a benefit, with work following the sun".
Re:Stripe's remote engineering hub, one year in by jdxcode on Sunday May 31, 2020 @01:05PM (#23370851)
I worked at a mostly remote company for 5 years. It works very well with on-call rotations but it's a big problem for product work.