What challenges are you facing offshoring development to India?

Working with a team in India just plain sucks. Here are the top reasons why; - Timezone diff is brutal. I either have to take meetings late at night, or else I’m waiting up 24-hours for a response to any requests. The documentation requirements suck. The team would only do what is in the docs and nothing else. I’d end up with wonky solutions and shot code. The inability to deliver bad news. The team would never say no or would not deliver bad news. Issued deadlines were a common occurrence.

What I learned is that you get what you pay for. So, I could get smart developers in India if I’m willing to pay more. However, a good dev in India costs the same as a good dev in LATAM. at that point why would I deal with the TZ BS?

I am from Australia - a country with very high labour costs. Some years back, I trialed outsourcing programming tasks to developers based in India, only to consistently receive shockingly bad quality work. Over the years, I have also helped clients fix up shoddy work written by such developers.

I will never forgot the moment I encountered this MySQL query from hell that brought a customer-facing webapp to its knees:

    select oldurl, newurl, id, dateadd from  jos_sh404sef_urls where newurl <> ""  AND oldurl not like '%vmchk%' AND newurl not like '%format=feed%' AND newurl not like '%format=pdf%' AND newurl not like '%print=1%' AND oldurl not like '%__404__%' AND (  soundex(oldurl) = soundex('not_found') OR  oldurl like '%not%' OR  oldurl like '%found%') GROUP BY oldurl limit 500;

Other developers I have engaged from other places, especially ex-Soviet countries, were far more competent and seemed to care about a job well done.

In my view, the Indian government needs to encourage its industry and educational institutions to study the teachings of W. Edwards Deming to instill a culture of quality. Back in the 1950s, Japan was ridiculed for the quality of its manufactured goods and within a decade after embracing Deming's advice, they became known for their excellence. Perhaps India can also experience such a renaissance.

The timezones are brutal, particularly in summer.

And the cultural aspect that rather than deliver bad news, they prefer to just not deliver news at all (thinking that that's somehow less of a problem or gets them in to less trouble?).

Legislation relating to data leaks and software security are quickly killing all of our outsourcing contracts. We have some operational stuff still happening, but actual development and access to production systems is no longer an issue.

Now, some consultancies get around this by flying over Indian people who stay for the maximum amount of time their visa will allow them, living out of a hotel - but it's clear the quality of work these people are doing is so hit or miss, as often they staff the wrong people, with the wrong competencies, we basically tell them to fuck off on arrival and have to have arguments with our contacts on the ground here.

Overall, our dependency on India, and any other country that doesn't have similar laws in place regarding data breaches, privacy or liability is quickly becoming too risky.

Let's face it, if you earn $15-25K USD a year and you're given prod access to a retail database for a Fortune 500, finance, retail, customer-facing, tech services or platform company - you can turn your access into 10 years of salary in less than a week. There are recruiters for this on LinkedIn now, actively reaching out to people with offers for ransomware, data extortion or business-email-compromise profit-sharing arrangements.

And the risk is real.

Time zones, saying yes to one thing but doing something different, very high attrition rates.

The quality of the work has been abysmal, and the timezones make it hard to improve the situation

For the last 3 years or so, they have been having a much more difficult time finding quality programmers for us. This used to be no problem. I don’t think it’s unique to the company we are working with, rather that quality developers in India in general are able to earn better salaries. Our interest in India was due to the cost savings and with that gone, we’re looking at Viet Nam and Colombia now and letting things wind down with our Indian partner.

problems i faced working with consulting company in india

1. high turnover , you never know who exactly is working on feature at any given point. They even had just one git userid that they all shared ( consultincompany@mycompany.com), which was bit ridiculous.

2. I saw some of their employees be on-call in meetings with multiple clients .

3. Super slow responses via email. You finally just give up and resign to your fate.

4. Developers just dont care about quality, not because they not competent but because of apathy. They just don't give shit.

5. language and cultural barriers. I got pretty good at indian accents but once in a while someone would totally throw me off. I would feel embarrassed to ask them to repeat themselves repeatedly.

One of the first things to realize is that Indian developers, like in other countries, vary in skill levels experiences and there's no prototypical Indian developer.

There are many people in India who have found their way onto the software industry without adequate education (did a bunch of Java/Spring/Android/C# courses and YouTube videos vs. building and operating production systems) or passion for software engineering. With these people you can be sure to get shoddy work and spending lots of time micro-managing them.

At the same time, there are experienced developers and engineering managers who have worked at multi-national companies, built and operated large systems, perhaps even worked abroad, and have passion for the craft of software engineering. You need to find such people to form the core of the development organization. They are going to be more expensive than the rule-of-thumb "India salaries are 40% of US salaries". You will also need to ensure that they have sufficient autonomy and a seat at the leadership table so that they can independently move work forward and set the culture in India. Otherwise, they will lose interest and move on.

People have already mentioned the time zone challenges but those are mitigated by having strong/autonomous leaders in India. Don't assume that you can build an effective scrum team cross US-India time zones. Instead you need to be thinking of India org and US org with significant independent ownership of systems, and some dependencies between the orgs which will need periodic management.

Another factor to consider is the attrition rates of early-to-mid-level engineers in India which have historically been higher than the US. You need to manage this, through the leadership team in India, giving engineers appropriate growth paths and exposure to different responsibilities.

When I was at Allstate around 10 years ago most of the devs were in India (through Infosys I believe). They were actually worse than intern devs still in college. Most of my time was spent fixing bugs they introduced into the codebase (the SDLC process was ass and we didn’t do PRs so anything and everything got through, usually all the way to production).

I remember once looking at some code one of them had committed while I was sleeping… it still had the comments mentioning “Bank of America”. The thing is, I doubt BoA would have done anything had I tipped them off that their code was leaked to another company. These shit companies get what they pay for, and they get what they deserve.

Timezone offset from the US is difficult. Many lost days because of unanswered blocker questions during their working day.

Very strict almost pedantic adherence to instructions. Much less creative problem solving.

We have a developer contracting in South Asia. It's going well the only tricky part is money transfers. A lot gets eaten up in the conversion and transfer fees.

Unfortunately, by far and away the biggest problem I've had with offshored work in India is the sheer poor quality of work and the lack of attention to details. I've been in IT for 23 years and worked with offshore teams all over the world. With India above all else, your best bet is to work with a team that you have direct references for, or past experiences; otherwise you can expect disappointment. I've lost count of all the times, there were fake resumes, people suddenly ghosting, and COUNTLESS quality issues. It seems like the culture of, "Acceptable is what you don't get caught with" is quite rampant there above anywhere else. I never ever would select to offshore anything to India if I had a choice!

My experience was that I hired a developer who silently was replaced with a group of lesser capable staff. After the first few meetings, they were unable to take video calls and after 3 months the quality of the work went drastically down hill. I eventually had to let them go, and only found out because one person on the team felt bad about the situation and contacted me to say as much.

So my experience is not great.

Generally speaking, I don't think India is a go to country. For US firms, hiring workers in the UK is usually a much better bet because salaries are depressed there. Ghanian, Nigerian, Kenyan and South African firms are just as good as Indian IC and have noticeably better TZ difference to the US.

I have 3 members of my team in India, and they have been great.

If anything, I would say the cultural aspect of always changing jobs for a salary bump is a challenge.

But this same issue has started rearing its head in the US now.

A bit tangential.

Offshoring to India is being done in engineering fields as well. Many international Refinery / Petrochemical/ Offshore platform engineering companies have huge design office here.

Indian product designer here. I’ve worked closely with engineers and product managers, and recently was at a job that required me to collaborate with US teams almost every day. Ask me anything.

Timeones. Some firms offer a near shore PM, but that still didn’t help as it’s a big delay.

The language barrier can be tough too, but manageable.

+1 on timezone. Much easier to work with South America.