4 ms·

Some already realized that. For USA companies, the problem with Asia, India, and even East Europe is timezones. I used to work at a US company that had offices

Some already realized that. For USA companies, the problem with Asia, India, and even East Europe is timezones. I used to work at a US company that had offices here in Mexico and had a GREAT QA team in India (despite the hatred they get here in HN, Indian techies are GOOD! ) . The TZ problem is what ended up fracturing the relationship between the teams . Us/Mexico teams synergy was just great, while Indians were generally disconnected. But yeah, US and Canada companies that turn to LatAm do get an "unfair advantage". I'm slowly but steadily trying to help this happen. Sorry?

re-thc 3y ago
> For USA companies, the problem with Asia, India, and even East Europe is timezones. I've seen more of a mentality and attitude problem than timezones. Often these other offices are just treated as 2nd class citizens without enough context to act.
gg-tyrael-hgh 3y ago
> that turn to LatAm do get an "unfair advantage" My company has been trying to do this (pay top percentile latam salaries) but it’s just been a larger grind to find decent devs than when we were advertising US salaries. “You get what you pay for” seems to be at play for us. I imagine remote work can give you some edge but we’re trying to get 2 devs for the price of one and it’s really hard. We’re probably losing money on all the time wasted (you get a ton of applicants at lower price points).
jmye 3y ago
I think the timezone issue is being mitigated - I’ve found Indian devs (only picking them out because of direct experience) were generally already working odd hours to at least give US overlap, but I think asynch tools will continue to get better and make it less of an issue. Probably doesn’t work in a five person startup where you need a lot of direct/constant communication, but especially in mature companies, I think the timing issues are very solvable (where they haven’t already been addressed). Agree on the quality - there were some devs we worked with who needed more hand-holding, but a majority were very capable.

re-thc 3y ago

> For USA companies, the problem with Asia, India, and even East Europe is timezones. I've seen more of a mentality and attitude problem than timezones. Often these other offices are just treated as 2nd class citizens without enough context to act.

gg-tyrael-hgh 3y ago

> that turn to LatAm do get an "unfair advantage" My company has been trying to do this (pay top percentile latam salaries) but it’s just been a larger grind to find decent devs than when we were advertising US salaries. “You get what you pay for” seems to be at play for us. I imagine remote work can give you some edge but we’re trying to get 2 devs for the price of one and it’s really hard. We’re probably losing money on all the time wasted (you get a ton of applicants at lower price points).

jmye 3y ago

I think the timezone issue is being mitigated - I’ve found Indian devs (only picking them out because of direct experience) were generally already working odd hours to at least give US overlap, but I think asynch tools will continue to get better and make it less of an issue. Probably doesn’t work in a five person startup where you need a lot of direct/constant communication, but especially in mature companies, I think the timing issues are very solvable (where they haven’t already been addressed). Agree on the quality - there were some devs we worked with who needed more hand-holding, but a majority were very capable.