[curryst]

I would avoid it for most roles. And not just India, but really anywhere that's more than a 6 hour time difference from where I work (and even then, I would prefer less than a 4 hour time difference).

I work on a globally distributed team currently. It is exceptionally difficult to maintain cohesiveness as a team given that there are 0 hours per day that we are all online. What has ended up happening is that we have virtually fragmented into 3 separate teams with our own products. For instance, my team members in Asia are working on a product that I can't effectively support because my shift doesn't overlap. If someone asks me a question about that app, which my team is supposed to support, I have to go start reading source code. Lacking documentation is also an issue there, but that's nearly a universal problem.

Remote working tools are the hot new thing, but nothing effectively solves the timezone issue. Sure, we have async communication, but unless someone is logging in after hours (which I would heavily discourage), you only get one exchange (i.e. an email or Slack message) per day. That's a painfully slow way to collaborate.

That being said, there are roles where the time difference doesn't matter, and is advantageous. NOC and helpdesk (if helpdesk is 24 hours) are well suited to a "follow the sun" model. The team communication seems largely limited to passing off info about incidents, with very occasional full group meetings to give new policy info. They just aren't the prestigious roles typically associated with SV.