I work at a big co on the west coast and we have had developers in India, hired by the company's India arm, on some projects.
There are coordination issues because it's exactly halfway around the world, especially if a project requires collaboration with another department. Projects sent overseas need to be well-defined and self-contained to get a good result. This alone could cause you to shy away from hiring in other time zones.
Expectations and the engineering culture are different in the two countries. I have worked with India developers who produced work that was worse in terms of depth, quality, and maintainability than the same project later taken up in the US. I do not have an anthropological explanation, and the developers from India I've worked with stateside didn't have the same issues. /fireproof
More experience and tech muscle is concentrated in the US team. How about this: if you were highly skilled and experienced, as a rule you would have moved to the US for the greater opportunity and the big bucks. There's a positive feedback loop here, because banging together lots of skilled workers creates more opportunity and attractive companies, creating more motivation to come, and so on.
Thanks for you answer :), yeah, I know time zones is one of the main problems companies faced.
How about this: if you were highly skilled and experienced, as a rule you would have moved to the US for the greater opportunity and the big bucks
Makes sense, though there are a couple of things to consider one of them is visa issues. Also, not everyone wants to live in the U.S or Europe or leaving their hometown.
I dont really consider 'outsourcing' to be remote working, and as for the 'anthropological explanation' its pretty simply explained that outsourcing projects (to anywhere) are typically a self fulfilling prophecy of failure.
I work at a big co on the west coast and we have had developers in India, hired by the company's India arm, on some projects.
There are coordination issues because it's exactly halfway around the world, especially if a project requires collaboration with another department. Projects sent overseas need to be well-defined and self-contained to get a good result. This alone could cause you to shy away from hiring in other time zones.
Expectations and the engineering culture are different in the two countries. I have worked with India developers who produced work that was worse in terms of depth, quality, and maintainability than the same project later taken up in the US. I do not have an anthropological explanation, and the developers from India I've worked with stateside didn't have the same issues. /fireproof
More experience and tech muscle is concentrated in the US team. How about this: if you were highly skilled and experienced, as a rule you would have moved to the US for the greater opportunity and the big bucks. There's a positive feedback loop here, because banging together lots of skilled workers creates more opportunity and attractive companies, creating more motivation to come, and so on.