Read on Twitter
1/ Woke up and timeline is full of negative tweets (particularly from Spain) complaining about remote work. Location based comp and complexity of managing timezones are the main arguments. Imho most are excuses based on fear.
2/ Looking back, going remote was a huge advantage and very clearly the right call for @RevenueCat. I’ve always been a library/office person (hey, I moved to the US to work). But I want to share our experience so far.
3/ For context: we currently have 6 timezones, and do equal pay based on SF rates. Comp is a controversial topic, but we believe if you are the right person, you’ll do the same job in SF, Montevideo, Taipei or Seville. Otherwise, you are not. @basecamp has done this for years.
4/ On the employer side, operationally it is tough. You need to figure out regulations and how to pay. Onbording new timezones is hard. But it gets so much better and easier as you add new timezones, and overlap gets better. Like everything in life, you learn a lot with practice.
5/ It is proven, clearly doable for software. Big open source projects have been developed asynchronously for decades. It is great for critical infrastructure too! People oncall feel great knowing somebody else will be working while they sleep. Machinery is always running.
6/ Access to talent. Silicon Valley works because the best talent comes here. But there are still people who don’t come here, can’t, or go back home. Find them, you can build a world class team. Trust me, much better in the long run than hiring entitled SF based engineers.
7/ You need to adapt. Constantly reevalute the process. You need to listen to feedback. You will screw up. You need to trust the team 100%. But ultimately, you will build a more solid company. And whether you want it or not, it is forced or not, it’s already happening in tech.
