Salary negotiations will be a bit different since you're also competing with all local jobs. So you can take on multiple devs and pay them differently if they have similar skills (hard to measure anyway), or you can pay everyone the same and limit what markets you pull from. The former could get ugly if anyone found out.
This is why I have a burner phone and an SF address for salary negotiations. Then my W2 goes to Austin, TX to avoid all state taxes. #winning
I hope you actually live in texas...
Re:Work for a remote culture
by bjelkeman-again on Wednesday July 15, 2015 @01:42PM
(#9892828)
It is an advantage. But it isn't without disadvantages. Not everyone thrives in a distributed environment and it is hard to do certain type of work (brainstorming, very interactive requirements and design work, for example) in a remote only setting. It is also harder to build good team spirit, when you don't hang out together. It is possible, but it isn't a no-brainer even when you look at all the advantages. We have a hybrid model with a lot of us focused in hubs, but working remotely part of the time now.
I'd say that's a substantial advantage.