4 ms·
And I worked for a company where it worked beautifully; the remote folks (who were very carefully picked) meshed perfectly with the team (and better than many o
by vanusa 5y ago
And I worked for a company where it worked beautifully; the remote folks (who were very carefully picked) meshed perfectly with the team (and better than many of the native folks).
It's an eternal topic on HN of course. Whether it works or not seems to depend on multiple factors (not simply language issues, or remote versus local), in my view.
- ironmagma 5y agoYeah, several things my (former) company did that made it worse: - Not consult with existing employees before making this decision to see if we were on board. - Not hire individually, instead acquire an entire company. - Said company was struggling financially (which made it a "good deal").
- hn_throwaway_99 5y agoI can hardly imagine that situation working out if the company you acquired were in the US.
- Daishiman 5y agoNewsflash: competent senior engineers in LatAm with 10+ years of experience are not dramatically cheaper than US engineers outside of NY/SF. A good engineer in Latam might work below market rate for a couple of years, then they realize their market value and stop working at a discount.
- oblio 5y agoThat's the case for any good dev, anywhere in the world. If they're not chained to their job for various non-work reasons, they <<will>> move on to competitive salaries.
- KptMarchewa 5y agoSo this is very, very different and incomparable situation than presented in the article or discussed in the comments. The same issues could present if you bought incompetent company in the US.
- ironmagma 5y agoThe language barrier was 80% of the problem. Everything else could have worked out if we had been on board and the management handled it correctly. The engineers were good enough.
- KptMarchewa 5y agoLanguage barrier would be something that you could filter on within 15 minutes of recruiter screen talking with the candidate.