3 ms·
> But when they go remote, aren't you competing with them? Not really. There aren't many companies who are considering both American and Indian remote develope
by learc83 9y ago
> But when they go remote, aren't you competing with them?
Not really. There aren't many companies who are considering both American and Indian remote developers for the same positions.
Well paying remote jobs tend to have time zone constraints, and require better English communication skills than the average Indian developer has (there definitely are Indian developers with excellent communications skills, but they aren't average).
People think that because they are out of the office that politics doesn't affect them and they don't need soft skills. But communicating effectively is even more important in remote work because of the inherently lower communications bandwidth.
- logicallee 9y agofair enough.
- petra 9y agoAssuming an Indian coder is a good English communicator, would working the night shift be such a big barrier ,compared to the salary potential ?
- peteretep 9y agoMany hiring managers will be carrying around at least some latent racism from previous interactions with offshored developers that worked out as well as a car crash.
- hluska 9y agoIn some projects, having a night shift can be a tremendous advantage. It works particular well in extremely agile environments with fast assignment->deployment turnarounds. For example, if the night shift does daily deployments, then the parent does QA during the day and sends fixes/new requests before the start of the night shift. Other times, particularly if the project has complicated architectural requirements, it's too hard to get the night shift on the same page a super the parent.