Resume fraud weighs on Indian IT industry, one in five CVs contain fake information

These viruses and trojans get imbedded in hidden files. It is quicker to reinstall windows with a formatted hard drive. then to trouble shoot.
I do it, all techs do it.

Hatred of Indian IT is par for the course on DU. No amount of explanation will change that. All the negative and incendiary stories are cherry-picked and posted.

is filled with a bunch of Indian haters.

and American Execs could care less if these fake Indian IT workers actually know their stuff. They're cheaper than American workers.

As long as they do the work for half the price, they don't care if the employee has no integrity.

Besides, it's not as if integrity is a requirement for working for an American corporation.

and the corporations took over has been the ethics & morals they radiate in every dealing with the world & the American people.
People see what the those at the top do to get ahead and emulate it. Rinse, lather, repeat.
We've had thirty years of it. Long enough for an entire generation to grow up to be prosperous MBA's and day traders. Using every dirty & underhanded scheme made possible by the restructuring of our laws to turn our country into an unbridled free for all and leaving her as we see her today. Like the last buffalo stripped of its valuable hide and left to rot in the hot sun.

Or on job applications. I've never lied on one, except for leaving out negative stuff. That could be considered lying I guess.

The initial decision to send a job to India often only considers the wage implications. How much you have to pay the person.

But that focus is too narrow because out-sourcing a job to India generates other indirect costs, many of which can become substantial.

The first issue is training. You have to train these new employees, just like you do any new employee, but with the language and time zone issues, it takes longer.

Then, you have project management issues. Again, time zone issues are big here. If you are using a development approach similar to AGILE, you need daily scrums in which all team members are available. The time zone differences are so great, these are very hard to schedule. Schedule slips increase. Whatever buffer you might use with your US team needs to be expanded if you ship that same work to India or China.

Past this, you have quality issues. In some analysis, defect rates increase significantly as work moves to India or China. Basically, you are paying some one in India LESS then you paid their US counter part, but they often aren't as qualified.

And then there is the increased turn-over rate. Because IT jobs are "hot" in India and China right now, employees go to one company, get some experience, and then JUMP to a new company, or even start their own IT company.

That last item is important because when they JUMP, they often take critical Intellectual Property with them. So what happens is that the level of innovation in your company decreases, the people who now know how your products work LEAVE. So they take your best stuff with them, and then use it to lure your competitors into hiring them.

Some companies think that out sourcing their Support team helps them. But this too is short sited. The Support team talks directly to your customers can when leveraged appropriately, can become an engine for innovation and new requirements and features for your products. But when you out source this, the new knowledge that support gains may not make it back to you, but end up in the hands of some other entity. Basically, you've distanced your self from an important feedback loop regarding your product.

Out sourcing is no panacea ... and in most cases, its a drain on a company.

I headed a project which was outsourced. I was basically the lead on this side, while much of the work was done overseas.

I saw a lot of the same issues. We'd train people, they'd gain a couple months of experience and they'd bolt. I'd ask my lead counterpart there and he'd say "oh yeah he left the other day". And of course, there would be little if any notice. It would be difficult to get consistent work this way. Some of these problems are inherent when the work is being done over 8,000 miles away. Sometimes, we'd also find communication issues. Most had pretty decent English skills, but even with powerpoint slides, screenshots, and web ex conferences, there would still be gaps.

And of course, due to all these issues there would be rework involved. Often times it came down to specs and tribal knowledge within the company they weren't familiar with - or methodology issues. Ultimately, as a coworker said, "it's tough enough outsourcing a project outside of the company to a third party firm in the same city, what do you expect when the work is sent a couple thousand miles away?"

I think outsourcing works in limited cases, but often times I think the savings are overblown and finally companies are realizing that.

IT people here on DU have often stated that they have to straighten out what foreign IT people screw up. Silly, naive me -- I just thought those foreign IT people were just not trained well, not that they would outright lie about their qualifications. I guess it's true what I once heard: not matter how cynical you get, it's hard to keep up.

When I started my current job during the night we would call over to India and have them work on any problems that came up. But that wasn't working as well. One time we had to call for a problem and the response was literally "I don't know call someone else." My coworker persisted and eventually got him to call another analyst for help. That guy got his ass chewed as soon as our manager found out but still it didn't leave a good taste about the off-shore operation. Eventually they went to a local support model where we would just call a local on-site support person. They found that model works so much better, even when you're waking someone up at insane o'clock in the morning. The managers were much happier with the quality provided by local support.

The Indian students I knew in grad school were excellent at theoretical computer science but lousy when it came to coding and working in teams. Gosh, that wouldn't have any effect on their usefulness in the workplace, now would it?

Please consider reposting in GD. Thanks!