Thread regarding Optum layoffs

Getting burnt out due to offshore

Over the past year, my team has steadily replaced onshore staff with contractors and offshore hires. Our previous manager was replaced by someone based in India. While the overall headcount has nearly doubled, output has dropped. Technical debt is piling up, and my workload keeps growing because I spend every morning untangling the mess left behind overnight by new team members.

Some of the most capable people on the team, especially the women, are being routinely talked over and dismissed during meetings. We’ve raised the issue with the new manager, but nothing has changed. I’ve worked with people from all kinds of backgrounds and know how to navigate cultural differences. But when those differences show up as outright s-xism that hurts the team, it crosses a line. What makes it worse is how this behavior is slowly becoming accepted as normal.

Work used to be something I enjoyed. Now it’s constant supervision and damage control. I spend more time fixing the output of so-called “senior” offshore developers from Cognizant than doing my own job. I explain the same requirements two or three times, only to receive something completely wrong. Then I’m left responsible for cleaning it up and covering the unfinished work of several people, all during standard onshore hours, in addition to my actual responsibilities. It’s draining.

I seriously have no idea what senior leadership is thinking. Are higher-ups just getting fed illusions about how bad it's getting at the individual team level? This business, especially the tech side, has only been chugging along due to the massive inertia of UHG's size. Sooner rather than later, the consequences of subtracting by adding offshore and contractor resources are not going to be able to be tucked away or covered up by the efforts of the remaining viable onshore workers.

by
| 2541 views | | 17 replies (last August 9) | Reply
Post ID: @OP+1k1xw2jsm

17 replies (most recent on top)

Can’t understand a word they say , the New ROC . They probable state there bilingual on there resume but it’s apparent no one has ever speaken with them in there interview. You have to guess at what there saying , if they would send emails like there supposed to prior to calling you could figure something out out . But apparently that first step in the process was skipped in training , and it doesn’t matter what you tell them they don’t know what you’re saying . If you tell them no I don’t work that city . They still say I can assign ticket to you ? Repeatedly get told outage in g4 because the letter J is pronounced gee (g) instead of of jay (J) , a different worker kept saying E !! It’s so bad some sentences I can’t understand any words . The Roc is a communication department and if this how companies communicate how anyone going do anything . It’s so stressful , no emails , no voice , you have to have your boss contact there boss to get a written email to figure out what’s off and where . Hows this saving money .

by
| | Reply
Post ID: @rh+1k1xw2jsm

Suggestion - document it. Date, task or issue, who was involved. That's the only way things change, when there is enough receipts to show how bad it is. Don't fix them and leave them for the next shift like they did to you. They will only learn if they have to fix it. If it is blocking you, report blocked by defect. Then send the defect list to your boss, have them do their job.
Its ok to take back the conversation when interrupted. A simple way is to wait until they run out of air because you can't really tell when they are done talking so quickly jump in before anyone else and say, thank you and name the person if you even can and the "I LISTENED to what you said but maybe you couldn't hear what I was saying when you interrupted me or talked over me." Then finish your thought. Do it enough times and they will stop. Embarrassment is the only thing that remotely works.

by
| | Reply
Post ID: @fr+1k1xw2jsm

@OP I'm on the ESRO team and we experienced the same behavior described where competent women were always talked over and their knowledge and skills ignored. In some cases there were reported to management to cover up lies by the teams in India and some of the same people here in the states.

Even when provided the security standards and laws for security, the men would lie about controls and also some are finding information on the internet and then claiming they wrote it.

by
| | Reply
Post ID: @eq+1k1xw2jsm

When you said Americans are stupid you hit the nail on the head. Specifically the MN leadership that is largely comprised of promoted cronies and are not experienced IT managers! There inexperience is in your face since the rest of the industry learned 20yrs ago that offshoring to India had many shortcomings and hidden costs. Doubt me go find multiple industry analysts such as Gartner dated early 2000’s stating the same. But of course when healthcare insurance becomes a cash cow under Obama then health insurance companies with weak management like UHG can afford to throw money at all their mistakes and failed initiatives, until they can’t! So they offshore to control costs and slowly degrade delivery and service to all the company’s customers, still disagree with me? Look at the stock price dum--ss!!

by
| | Reply
Post ID: @dz+1k1xw2jsm

The time zone difference su-ks too. The burnout from early morning and late night calls su-ks

by
| | Reply
Post ID: @dy+1k1xw2jsm

@d6 From OP: "Our previous manager was replaced by someone based in India," they're probably not doing it willingly or under pressure from their manager

by
| | Reply
Post ID: @dv+1k1xw2jsm

So not sure why you save them. Seems like if your doing their work, and covering up their incompetence you have no one to blame but yourselves and management will continue to not care because they know American employees are stupid.

by
| | Reply
Post ID: @d6+1k1xw2jsm

@ch Wipro supplies bodies as contractors. Cognizant takes the whole project, no employee involvement. Guess who is more threat.

by
| | Reply
Post ID: @d3+1k1xw2jsm

We still get cognizant devs? You think they're bad, wait until you see what the Wipro devs are like.

by
| | Reply
Post ID: @ch+1k1xw2jsm

This is my exact observation as well. I have seen it get worse and worse.

Senior leaders are non-technical. They truly believe contractors come in with specialized skills and teach us how to do things. I have never seen that be the case. The amount of hand holding required for the offshore teams and especially contractors is enormous. They want to replace US engineers with an army of offshore labor but the truth is, most of the people they hire offshore are incompetent. You could do the same work with 1/3 the employees. Obviously not all US employees are great either but there is a disproportionate amount of incompetence in the offshore teams.

by
| | Reply
Post ID: @bx+1k1xw2jsm

Stop cleaning up! Nothing will change if you continue to fix others mistakes!

by
| | Reply
Post ID: @bc+1k1xw2jsm

This is just a start, 2026 every project, migration, enhancement is being sent to Accenture and Cognizant.

by
| | Reply
Post ID: @ac+1k1xw2jsm

I've been letting them fail, leaders need to see it. I know that affects your work, but if they believe it's just the status quo and we aren't working 12 hour days, they will never know. Work your 8 hours only, do your work, let it fall apart. We don't have a choice at this point.

by
| | Reply
Post ID: @aa+1k1xw2jsm

get used to it. India and the Philippines runs your healthace while the rich drive bigger Yachts up the intercoastal Su-kers!

by
| | Reply
Post ID: @a8+1k1xw2jsm

And some of them are dishonest about their work. It’s frustrating. A simple task that should take 1 hr ends up taking them a week. Plus, I have to follow up with them every single day just to make sure it gets done.

by
| | Reply
Post ID: @a4+1k1xw2jsm

Im pretty sure there are multiple teams now that would be causing critical org wide outages if the 1 or 2 onshore people left who are holding everything together quit. And the offshore are either wholly incapable of taking over the ops, or not allowed to because PHI.

by
| | Reply
Post ID: @a3+1k1xw2jsm

Exact same thing happening on our team. You are not alone. All day is spent either cleaning up their mess or meticulously planning step by step their next task because they cant work otherwise. Arent contractors supposed to be able to produce?

by
| | Reply
Post ID: @a2+1k1xw2jsm

Post a reply

: