1) 10-hour time difference between West Coast US and, say, Kyiv is pretty big. It's easier on EST people, but on the US side you're going to have to plan on jamming your calendars full of meetings between 7:30-10:30am.
2) Because you have fewer "business hours" between two, you need product, project, and engineering management to operate in a fairly well-oiled manner with more stuff spelled-out up-front, otherwise your team across the pond is stuck until the next day for some answer. Also, if your org even attempts to adopt "agile" this communication breakdown will murder your velocity; you're better off doing Waterfall.
3) They cannot be on-call to troubleshoot product issues during US business hours. This makes the business-side uneasy
4) Higher churn-rate than domestic engineers. Mostly over salary; this falls squarely at the feet of the "middleman" who undercuts their engineers. We attempt to ameliorate this by giving them feedback on employees who they should focus on retaining but IME they just view their talent as widgets rather than craftsmen. I've seen several good devs leave over money we'd have gladly paid them but their contracting org refused.
5) Speaking of higher churn rate: Onboarding can be more painful, again because of the TZ difference as well as certain cultural issues.
None of these are deal-breakers. But it's easy to understand why a company might be willing to pay 50-100% more to avoid these concerns.
https://www.atlanticcouncil.org/blogs/ukrainealert/kyiv-not-...
2) Spot on - Agile does not work well in such environment, I have seen it first hand twice. I feel that with senior/staff level devs, you can expect and should get higher level of autonomy and less hand-holding, so in a solid project oriented company, I do feel that fewer "business hours overlap" would impact much. I do feel that at least 3, preferably more hours should be reserved for meetings / overlap.
3) I'd argue about that one, haha. I have been on-call troubleshooting production at 2-3am my time, not once, but multiple times. For a great employer, with proper compensation and benefits, you'd be surprised what devs from this area would do!
4) YES! Companies are greedy. However, they do have to pay pension/insurance on the hourly rate they give to the dev, think 50-60%, but they don't want to give away their cut at all, it seems to be non-negotiable flat fee, which is deal breaking. Another point is that Microsoft and other big brand outsourcing names are coming to EE and stealing away the workforce.
Disclaimer - I work as a senior/staff level dev with high base salary and equity, so my experience may be a bit skewed.
An example - in Serbia and Slovenia you arrange a net salary, and the company pays the taxes/insurance etc on top of net salary (usually around 50-60%). So for a senior salary in Serbia of around 4k euros. you're looking at the company paying around 6-7k euros. For a contractor (as a sole proprietor) you can make at most 50k euros a year and then you pay benefits that are minimum 300e. If you go above that you pay 10% tax on profit + 15% personal income tax. You can choose to still pay yourself salary and 50-60% on top of that, and you will most likely not pay yourself a big salary, but take the profit and pay the 15%.
What we would try to accomplish is:
- Not have developer as a contractor, but as an FTE
- Create a pipeline of US based companies
- Bump the salary for devs for 25%-30% -> pay the taxes/pension (30k+ more)
- Take a 15% of the annual salary (20-30k)
- Provide cheap senior/staff/principle devs that are cheaper than the same devs, but same or similar quality