Is it a coincidence that as soon as Verizon partnered with these two Indian companies everything started getting much worse? Or am I being unfair?
5 replies (most recent on top)
There are a couple main issues with hiring overseas contractors:
Time differences not allowing those who are asking for the thing to be built to talk directly to those building it.
Cultural differences. Even merging two US based companies has been problematic due to corporate cultural differences.
We've tried to mitigate this by having on site Indian employees do the 'translation', but clearly that hasn't done it. By the way it's not just VZ - how many apps, websites gave you been to over the last 5 years that are cr-p?
As shared earler, a third issue tied to contractors in general is that they are not as bought in as full time employees. With HCL for example, there is a really high turnover rate. That is massively disruptive to a project team.
At some point the loss in business revenue more than outweighs the cost savings. Now might be the time to re-think the contractor strategy especially in light of recent contractor labor rate increases.
Then Sampath hires Executives back from this failed strategy? It’s impossible for Dan to get this deep into the weeds. It will take 2-5 yesrs to clean out this Director+ level of nepotism
No one is being racist. It’s just a fact they are not proactive in their work and really don’t care. It’s just a cultural thing. VZ need to bring it back to states.
The fact is that people over in India have no skin in the game so why work hard or communicate with customers in the US or Verizon US employees. They have no common sense on how to communicate or be PROACTIVE in their work. PERIOD.
It's not that they are Indian. The devs, mostly, are very bright and qualified. The problem is a lack of context, bad strategy, and alignment. You can't outsource 70% of your engineering staff, without any context, and expect them to build the right thing right.