(I work at one of the listed companies, and these views are my own.) Honestly, on-site just wouldn’t work well with the existing company culture at all. My cur

(I work at one of the listed companies, and these views are my own.) Honestly, on-site just wouldn’t work well with the existing company culture at all. My current team has members in at least 7 countries in North America and Europe. Some teams are more time-zone collocated, but many are not. The culture is built so that async communication — and in particular, publicly searchable written communication — is the default for nearly everything. So having a big time zone split isn’t a problem when you’re used to communicating via long-form written communication. Obviously, on-site is hugely different. If I went on-site, I would not be working with my specific team. I’m not even sure how the company could possibly reorganize to make that happen at all. It’s not like new hires in X geographic region are placed in Y division. So the best that could be done on-site is you get to make social connections. Can’t really have an on-site collaborative culture if none of your teammates live in the same city. And you can’t change that after the fact either, because people live in so many different places! And as a side note, having frequently worked in OSS projects, communication and work is very distributed anyways. So it’s important to be habitually in tune with that style of communication and work to be effective in a large OSS project with maintainers spread the world. So I would argue that even trying to have an on-site collaborative culture doesn’t make any sense if your company is truly globally distributed.