Re:Ask HN: On companies hiring remote developers and why don...
by mindcrime on Tuesday February 19, 2013 @05:43PM
(#5247614)
Well, we[1] don't hire remote workers, because we don't hire any workers yet, as a self-funded, bootstrapped startup. But, when we do get to a point where we can hire people, here's what I'm thinking:
1. If you limit yourself to "locals only" you stand to miss out on some good talent.
2. Distributed software development teams certainly can work in practice, just look at many F/OSS projects.
3. Guess what, all our stuff is OSS anyway.
4. But, there is extra coordination cost and overhead when it comes to dealing with remote workers.
5. And there are times you just want everybody in a big room together to hash things out. This is obviously harder with a distributed team.
6. All of that said, we'd almost certainly look into remote workers. Within that framework, I think there might be some slight preference for people in the US (less language barrier, fewer time zone issues, etc). The idea of "rural sourcing"[2] strikes me as interesting as well.
7. But we would definitely consider non-US as well. I've heard good things about working with folks from Eastern Europe (Latvia, Ukraine, Estonia, etc.), as well as the Philippines. I think South American countries like Brazil would be intriguing as well. But, at the end of the day, it's about a match between talent, skills and the needs, weighed against the tradeoffs of cultural barriers, timezone issues, language issues, etc.
8. Perhaps surprisingly, I see India as lower on the list of places to seek remote talent. Partly because the timezone, language and cultural mismatches seem more severe between India and the US, compared to some other choices. And also a perception (which might be flawed) that there are fewer individual developers in India looking for remote work. My perception is that it's all Infosys and their ilk when going to India, and that doesn't interest me so much. That said, I'm not saying we wouldn't work with folks in India, just that some other areas seem like they might be better options. But time will tell.
1. If you limit yourself to "locals only" you stand to miss out on some good talent.
2. Distributed software development teams certainly can work in practice, just look at many F/OSS projects.
3. Guess what, all our stuff is OSS anyway.
4. But, there is extra coordination cost and overhead when it comes to dealing with remote workers.
5. And there are times you just want everybody in a big room together to hash things out. This is obviously harder with a distributed team.
6. All of that said, we'd almost certainly look into remote workers. Within that framework, I think there might be some slight preference for people in the US (less language barrier, fewer time zone issues, etc). The idea of "rural sourcing"[2] strikes me as interesting as well.
7. But we would definitely consider non-US as well. I've heard good things about working with folks from Eastern Europe (Latvia, Ukraine, Estonia, etc.), as well as the Philippines. I think South American countries like Brazil would be intriguing as well. But, at the end of the day, it's about a match between talent, skills and the needs, weighed against the tradeoffs of cultural barriers, timezone issues, language issues, etc.
8. Perhaps surprisingly, I see India as lower on the list of places to seek remote talent. Partly because the timezone, language and cultural mismatches seem more severe between India and the US, compared to some other choices. And also a perception (which might be flawed) that there are fewer individual developers in India looking for remote work. My perception is that it's all Infosys and their ilk when going to India, and that doesn't interest me so much. That said, I'm not saying we wouldn't work with folks in India, just that some other areas seem like they might be better options. But time will tell.
[1]: http://www.fogbeam.com
[2]: https://www.google.com/search?q=%22rural%20sourcing%22