Why Outsource When Workers are Willing to Telecommute?
An anonymous reader asks: "Corporations and management resisted telecommuting for years, now jobs flow to distant nations. Did telecommuting become acceptable because of the greater distance? Because some form of on-site management persists? Because labor laws are favorable? Because a well paid middle class is a political threat? Is it really as simple as money? I'll work cheaper if I can choose where I live and work. Must I leave my country to do so?"
Workers in India are cheaper.
Is it really as simple as money?
short answer is yes.
I'll work cheaper if I can choose where I live and work.
Not as cheap as someone oversees. What is considered good money in India wouldn't be a living wage in Silicon Valley, or in most of the United States.
Not only that, but even if you cut your rate to $10/hr, there will be a third-world person who will do it for less.
You will never be able to be cheaper than a third world person, because a third-world person pays third-world prices for rent and food.
First, I'm pretty sure it *is* all about the money. Having said that, I don't think the workers receiving the outsourced work are telecommuting. My understanding (and correct me if I'm wrong) is that they are employed by a company and report to work at a physical location. They have supervisors looking over their shoulders making sure they're not surfing the web, reading slashdot (*cough, cough*). I don't think they're hanging out at home in their underwear watching Spongebob, which is/was the fear managers had of telecommuting. Moot point now, eh?
Lower salaries are the main reason, but throw in fewer benefits to be paid, cheaper medical, lower taxes, simpler (and fewer) regulations, and so on.
You can look on it as exploited workers overseas, or spoiled workers at home.
I don't know what your experience is, but I've worked at several companies that relied on off-shore resources for some engineering. Sometimes it was collaborating on a project and in some cases entire mini projects were assigned to the off-shore engineers.
In every case, massive re-engineering needed to be done.
It sounds stupid to say this, but these guys just aren't as good as the seasoned tech people we have in the US. They can't see the big picture. They lack the comprehensive technical immersion that we in the US have. This immersion gives us a greater understanding of technology, how it works, how to architect it, etc. Most off-shore engineers were in non-technical jobs before they managed to go to college and learn how to program. They just don't have the background that we do. In 20, 50, 100 years I'm sure this technology gap will fade and perhaps even vanish, but certainly not in the short term.
To buying products made in the USA?? I can remember just a few short years ago when that made in the usa tag meant you got a better value for your dollar. The product might have still been made in a sweatshop, but it was a sweatshop in the USA!!.
I think that the way to convince middle and upper management to stop going overseas for tech workers is to convince them that although it might cost more to employ workers in the US, you get more value for your dollar if you stay at home, you get better code, better communication, and better management of the project.
Its time to stop whining about the jobs leaving, and find reasons to keep them here... and show IT managers why they should do things the RIGHT way, teach them about value, not just about bottom dollar.
But thats just my 2 cents...
Fire in the hands of the village idiot is no tool, but a weapon of mass destruction
To the boss, the fact that the fully clothed workers' hourly wage is 1/4 that of the unshaven half-naked ones is another big factor.
I get the feeling that most slashdotters, when they hear "outsourcing to India" picture some run down building with old computers and starving Indians in cheap work clothes who are happy to program for $2 an hour or less, working in sweatshop conditions.
This isn't necessarily the case. India does have almost 1 billion people; not all of them are poor, or uneducated, and not all of them work for nothing.
The fact is, a software house in india may produce work just as good as one in the US, at a fraction of the price, simply because the overall cost of living is so much less.
Educated, intelligent programmers who appreciate their jobs, which are good by their local standards, and these sofwtare firms are competing on a global scale with every other firm out there. And winning.
This isn't the garment industry.
Um, Linux is "out sourced" as in its developed by a mildly interconnected bunch of people and its a decent product. [so to speak].
The problem with computer sweat shops in India is greed. Anyone and their brother with two weeks of IT training can become a "highly trained MCSE engineer" and then get paid 10% of what a US worker would get paid.
It isn't that India folk are stupider. It is that they pick the bottom of the barrel [and many jump in to fill in].
Likewise there are many stupid people who live right there in the US who have the same MCSE diploma. The trick the CEOs realized is why hire a dozen MCSEs in the US for 55K when you can hire some MCSE overseas for 5K.
Someday, I'll have a real sig.
Sure, I agree about the money, but it's also about whining. Are you a political threat? You sure are. You make your $80K and whine that you're exploited, mis-treated, screwed-over, and your boss is Dilbert's boss. You want your employer to give you a lifetimne job, but you can quit any time on two week's notice. If you take an additional breath beyond the quota you've established, you want overtime.
And then we have to listen to you tell us how you're the universe's great gift to your employer because you know how to initilize a variable and by God you've forgotten more about programming than I will ever know.
At least the guys in India are thankful for the opportunity.
How about a moderation of -1 pedantic.
I don't believe you because as has been pointed out here at Slash many times, English *is* the language of tech, and *most * Indian developers speak it fluently. It is not a problem that they are Indian, it is a problem that because of their economy, they work cheaper. I think this discussion can do without the ubiquitous bad jokes, if the services where sub-par, we would not be out-sourcing there. Give it up, Indians are excellent coders. Problem is, the work for cheap.
Your salary is only about half of the expense you represent to your employer. You might be willing to work for half salary; would you be willing to work for half salary and pay for all your health care benefits? If you're not a telecommuter, your employer pays for the space you work in; are you willing to work in half a cubical? You need to have some administrative staff support; do you think the people who do those jobs are willing to cut their salaries in half? And work without benefits? (Yes, I know their jobs are at risk, too.)
... well, it might not be a coincidence.
I'm not saying outsourcing is a good idea. I'm saying, if you want to understand it well enough to deal with it, you should understand it well.
P.S.: Even if your employer cuts back, and makes you pay a bigger share, health care costs to employers in the U.S. are outrageously high. If you hear a story about a pharmaceutical company reporting record profits, and then a story about a company outsourcing its software development because programmers in the U.S. are too expensive
Stupid job ads, weird spam, occasional insight at
Telecommuting from my experience, is when one employee basically works from home. Outsourcing is quite different, in the sense that US countries are not hiring a bunch of individual Indians to work at their homes remotely. They have their own offices in India, employees commute to work just like everyone else, and there's surely a management team there overseeing the office.
So to make the original analogy more appropriate, commpare this to when Intel has a sattellite office in another state. Now, instead of Oregon, the satellite office is overseas. And it has everything to do with money.
maybe technical jobs over there don't have quite the prestige they do here in america, and therefore the industry doesn't get as bright of people as here in the US. maybe these firms offering cheap engineering resources aren't very selective in who they hire, since they are only looking to cut costs. whatever the reason for the discrepancy in quality of work, i'd like to think there's something more to it than just that americans are better engineers across the board. i know plenty of good engineers who immigrated from overseas and weren't "immersed in technology" their whole lives.
but if you outsource to India you don't have to pay benefits. Remember that big settlement that MS had to pay, which gave contractors benefits? It was because current law (IANAL) says that you can't just hire contractors to get out of paying benefits.
This all means that even if your area has 1/2 the salaries of The Valley, you'll still be paid significantly more than someone in India.
Cars, computers, TVs, and pretty much everything else except for housing and food will cost around the same as it does in the USA. It's NOT a good deal no matter how you slice it.
Your pizza just the way you ought to have it.
That's because your salary is only a fraction of your total cost of employment.
There's your payroll taxes (your company pays half your obligation).
There's workman's comp, which is all gray in the area of corporate liability should you electrocute yourself trying to telecommute from your laptop in the bathtub.
There's OSHA regulations and costs (see my point above about laptops and bathtubs).
etc.
Companies don't outsource to individuals in India. They outsource to COMPANIES in India.
Go ahead and form your own 1099 company and bid for some of those outsourcing contacts as your own company.
You can tell a great deal about the character of a man by observing those who hate him.
For example, you go to old navy and buy a ten dollar t-shirt that was sewn up in China. I can vouch for the fact that the quality is crappy and this shirt will get a hole, tear, break within a year or two. But who cares? It was ten bucks, and these things still sell like hotcakes. Heck they are so cheap when the shirt tears, you throw it in the trash and buy another one, and you're still spending less money than if you bought some cashmere T-shirt from Versace.
You may think this comparison is apples and oranges, and I kinda do to, but I bet the CEOs and execs outsoursing the tech jobs don't.
Telecommuting will not save your job.
;-).
Working longer hours will not save your job.
Working for less money will not save your job.
If you think it will, then you're looking at this problem in the wrong way. You will never be able to beat the cost of offshore labor. Even if you could, you wouldn't want to. There's a reason it's so cheap...everything here costs 10 times more (rent, food, clothing, etc...) than it does in India and China.
It's like trying to beat Tiger Woods at golf. Maybe...maybe...if you train really hard, sacrifice your family and friends, and everything you ever knew or loved, you might be able to beat him in a round of golf if you were having a good day and he was having his worst one ever.
But a much simpler way to be him would just be to school his ass at Tiger Woods PGA Tour 2003' for the PS2. The game is a lot easier if you change the rules a bit
The weakest point of outsourcing is the lack of communication. Developers in India can't communicate with customers here because:
1) English is not their native language
2) There's no face to face communication
3) They're 12 hours ahead
And if you can't talk to the customers, you can't solve new problems. Old problems are easy to solve. Those are the kinds of things that can be effectively outsourced. Building yet another e-business website with a shopping cart and inventory control; Creating one more payroll processing system based on an SQL database; It's the well understood problems, where the customers know exactly what they want, that can be outsourced. Everything else seems to fail.
And that is the IT Industry's saving grace. Using new technology to solve new problems that are not well understood will always have to be done here, because solving those problems requires constant and effective communication with the "customer" (the users of the sofware).
Software is slowly and painfully learning the lesson that manufacturing learned a long time ago: "Build where you sell". If engineers can't talk to the people who will be using thier products, they won't know what to build. Most problems in software are not well understood enough to be completely spec'd out by an intermediary party and passed onto the engineers for implementation. That is why lots of outsourcing ventures fail, and that is why the innovators here in the States will always have a job.
Slight misconception, what a H1B is used for...
Companies don't go through the hassle of sponsoring a H1B to get trainees. Any B-type visa / visa waiver would be good for that as long as they don't get payed more than a moderate daily expense and leave after 60 days.
At the company I work for, they only apply for H1B if they spot a promising foreign PhD who might fit into and benefit to the company research profile.
- He had a unique skill set that wasn't easily replaced
- He worked well with his boss, didn't need a lot of supervision, and met his deadlines
- He was respected by his peers - played well with others
If you sum it up, it was a better value to the company to keep him working, even remotely, than to find and train a replacement.****
"I'd never want to join a club that would have me as a member" - G. Marx
There's a number of ways to categorize what makes someone in the "working" class and what doesn't.
One is to observe that even someone on welfare in the US has a higher standard of living than many people who work 70 hours a week in much of the Third World - and that this is a consequence of the incredible difference in purchasing power and wage power between, say, the US and Indonesia. After all, we buy their labor to produce shoes and clothes that we buy at a tiny fraction of our own labor costs - that differential is a "privilege"/advantage that anyone in the US enjoys. Meanwhile, the cost for first-world-produced goods and services remains extremely high for much of the 3rd world (a Uruguayan friend of mine laments how a single GameCube game costs half the entire monthly salary of his wife, a biologist at a Uruguayan university.)
However, another way to look at it is alienation of labor - do you own the fruits of your own work? By this more classic Marxist description, even some 6-figure earning people are "working" class. Other metrics like this are whether one owns one's home, or how many paychecks away from homelessness one is. The capital-gains model is one of these ideas: when one's wealth and power comes from "ownership of the means of production," then one can be thought of as in the ruling/upper classes.
And another way is more cultural, dealing with type of work: a plumber making over 100K a year is considered by some more working-class than a low/mid-level manager making 60K a year in a small company, and both are considered "lower" than a college professor making 45K a year. There's an idea called "cultural capital" that expresses the idea that certain types of work have a cachet that isn't reflected in the amount of money they earn.
I agree with your opinion on outsourcing results, but not your conclusions. You get back crap from overseas, but if the Indians outsourced a project to the US, they would get crap back.
The problem is that you can't build a good system without access to the customer. I've been in software development going on 30 years, and I've never seen a spec that didn't have holes. And I've never seen a design that didn't have holes. If the coders are 12 time zones away from the designers/analysts/customers, then they are going to make things up to fill in the holes. Which means that 99 times in 100 the result is crap.
Alistair Cockburn has a very good book Agile Software Development that is about methodology, mostly. He says that he has never seen a methodology that works for outsourcing part of a project, like coding. He says that what will work is outsourcing whole projects, including architecture on down. This sheds some light on IBM's recent announcement that they will be moving high level jobs offshore in the coming years.
-- Some things are to be believed, though not susceptible to rational proof.
Here's a quote from the an article previously referenced on SlashDot:
IDC warns that Bangalore, India's primary IT hub, may no longer offer the world's best IT outsourcing value; that the infrastructure there is saturated; and wages for skilled workers are being bid up, with many new grads demanding annual salaries of $4,000 (USD) or more -- not only in Bangalore but all over India.
Oh my God. The nerve of those Indian developers demanding more than $4k/year. No wonder companies are turning to Romania and China. They're obviously less greedy in those countries.
Can you cut your salary demands from $75k to $4k, probably with no health, pension/401k benefits? If you can't, then the argument for telecommuting is moot because someone else will do your job for a hell of a lot less than you will.
I know a lot of Slashdot readers are in favor of globalism, but I don't think they're prepared for the effects of it. Unless you're a plumber or electrician, you better get used to a wildly lower salary and standard of living, because if your job can be sent overseas, it will be, due to this type of astromonical savings.
Not just IT -- engineers, benefits administrators, architects, analysts, animators, call centers, they're even shipping radiologist work overseas because someone in India can read X-rays just as well as someone in NYC.
We won't see the alleged benefits of globalism for decades, so there is probably a long stretch of very rough waters in our future, where entire industries will be eliminated almost overnight by offshoring, and the economic balance of many regions of the US will be ripped to shreds.
The problem is that the change is just too fast to react to. IT is still a relatively new field; when I attended RPI 10-12 years ago there were really no IT courses being taught, it was all CompSci -- data structures, etc. The IT industry as a career has ramped up and burned out in a span of about 10-15 years. That's about 1/5 the length of a person's working years.
How can someone completely retrain themselves every 10 years, when retraining means starting from the ground floor both salarywise and knowledgewise? I'm not talking about evolving, like moving from mainframes to PC's. I'm talking about moving from being a programmer to being a lawyer or an accountant.
How can anyone prepare for a career when there's a significant chance that the career could be totally obliterated in as short a period as 5 years.
Ralph
That's about 40k a year. For 40k a year i might consider living in India if i had zero job opporunities locally. Of course for 40k a year i'd also consider living in Maine or Colorado or someplace else with very low cost of living. (Okay, i don't know that Colorado and Maine are low cost of living, but i know such places exist in the US, and those seem like reasonable guesses)
Hell, i'm only making 60k a year and living in LA. I'd probably be better off at 40k and living in the woods someplace, and i'd get to work from home to boot! And the mangement of whichever company would have an American programmer who shared their language and culture for the same price as an Indian programmer. Sounds like a win-win situation to me!
This Space Intentionally Left Blank
Here is a reprint of the main part of the post I read:
- None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
I've had similar experiences. No one likes to admit it , but probably 90% of domestic 'software engineers' are mediocre to poor. 90% of Indian engineers may be mediocre as well , but the population of Indian developers that reach the US tend to represent an above average cohort.
/. actually provides a pretty good representation of the types of developers that I've worked with - they're convinced that they're smarter than everyone else , but are really only a smidge above average in intelligence. They tend to be immature and often vindictive. They're dogmatic in their views about software engineering , but don't really have the depth or breadth of knowledge necessary to form these opinions. And they tend to have a BIG chip on their shoulders.
The Indians I've worked with behave more professionally , they seem to have more respect for the engineering process and can interact with non-techs like normal people.
>
>Going to Nola's or Baha Fresh everyday for lunch? Not anymore dude. thats $300+ a month reduced to $100 by bringing my lunch from home. Now that I ride the train, I dont stop at Fry's twice a week to "just look around" like I used to tell my wife. An easy $150 a month saved just by staying out of the book/CD/game aisles. If I need something now, Ebay has it. Drinks after work with my team? Once a week instead of 3-4 times. Thats another $100 saved.
After-tax, he's saving $200+250+50+200+150+100 = $950/month.
Now dig this. With combined California + Federal taxes on $200K at around 43%, that after-tax savings is equivalent to a pre-tax salary raise of $20000 - about 10%.
> If you can give up some of the ego stuff, you can live just fine in the Valley.
Preach on, brother. You just got yourself a 10% raise, with zero change in your standard of living. (Well, apart from no longer "just looking around" at Fry's, but hey, we all gotta make sacrifices. I'd spend less time "just looking around" at Fry's too, if someone was giving me a $20000 raise for it :-)
Suggested summer read: The Millionaire Next Door: Surprising Secrets of America's Wealthy.
Yeah; I get the drift - you're one of those Einstiens who thinks that 250 million Americans can treat themselves as self-promoted companies, and we'll all be better off for it.
There's perhaps 1% of OUR industry that can do that; and other industries have even smaller percentages of self-promoters. The whole concept is ludicrous on its face; this is not a solution for the masses, even in IT.
I don't want to hear from somebody who makes 200K a year. Boo hoo, don't care.
try cutting back on 60K a year, thats a whole new ball game.
Its unbeleiveable that some who makes 200K a year doesn't understand that, and lies to his wife.
Last month I bought 1 latte, and felt guilty for it.
By ego stuff I assume you mean food, day card insurance and housing, cause buddy, thats all some of us have these days.
The Kruger Dunning explains most post on
I would be interested to see some projections on where this is leading in the longer term. I can see the following problems but I have yet to see a (rational) discussion on them:
I can't help feeling a little glum about this, kind of like the weavers must have felt when the mechanical loom came around first. Sure it's just another structural change, but I wonder whether we'll see some surprising consequences from structural changes in the knowledge economy; after all, that's what the dominance of the western countries has been based on in the past.
Of course the only difference is in cost of living. All you have said is that you can have a similar lifestyle to an engineer here in the US, but at a fraction of the cost.
... I'll move down next to you and eat what I consider better food than we have in the states for only 75 cents ... then we can go out and have some beers together.
... companies are sending jobs overseas without giving US employees an adequate chance to compete for those jobs.
As much as I hate to see US companies abandoning their own country, I think this is exactly what needs to happen. Economics demand that companies find ways to produce with minimal costs, and thats what they are trying to do.
However, the problem I have is that these same companies are not giving their US employess a chance to compete in that market. I am a huge fan of traveling and seeing other countries, and I would love to live in some other places, but the reality of making that happen is not so simple. If I was given a chance to work in another country, but at a small fraction of my current salary, I would definitely think about it. As long as I was capable of making a good living wherever I was.
I would totally sign up to work at an office for my company in another country where they could pay me less. We can just move my whole building and team down there for all I care.
Shit
The point being
The savings from telecommuting could rival savings from offshore outsourcing, if the telecommuting is done en masse.
1 _2.html. The result is that Indian programmers are 1/3 - 1/2 as expensive as an in-house US employee when counting total direct costs, not as low as 1/10 - 1/5.)
... and we know what happened with that. Now they are jumping on the offshore bandwagon in pursuit of dubious savings.
If they made the almost the entire IT department telecommute, they could reduce their real estate and other physical overhead costs drastically. They would just need a room for the servers, a few floating terminals lined up side by side like an Internet cafe (ie no space-hogging cubicles) for when people do come in to the office, and a set of meeting rooms so teams can meet once or twice a week.
It would also need a different approach to management and more strict rules regarding being at your home desk during office hours -- there is no good reason for not answering your phone for an hour, because you're not going to be away at somebody else's cubicle discussing anything.
Combine the reduced real estate costs with the reduced salaries that they can pay because people would accept less money in order to telecommute, and US employees wouldn't cost much more than Indian programmers when taking total costs into consideration. (Remember that although Indian salaries are only 10-20% of US salaries, their physical overheads are often the same or more than in the US - for example look at the office real estate costs in Bombay compared to Boston http://www.forbes.com/global/2002/0527/066sidebar
Then after you add in the undocumented and indirect costs associated with outsourcing that result from differences in language, time zone, and culture, and other factors like the relative lack of company-specific business knowledge, you're probably saving MORE by telecommuting than by outsourcing.
But outsourcing is popular now not because they are really interested in saving money; it is happening because it is the latest fad. If they were really interested in saving money, this big outsourcing wave should have been happening 5 years ago when American programmers were hard to find and expensive to keep, and Indian programmers were much less expensive than they are now. But no, the fad back then was to throw megabucks at anything that touched the Internet, and pay six figures for any semi-talented web programmer. They jumped on the dotcom bandwagon in pursuit of dubious profits
---------
There is inferior bacteria on the interior of your posterior.
Outsourcing means giving away the whole problem (and it sounds good in management circles too).
Engineering is the art of compromise.
I understand a companies need to show a profit, they are in business to make money. But I think certain rules should follow them if they are US based.
I have specific numbers for my wife, so I'll use her as an example. She works in a call center making about $14.55/hr. The company she works for has been using outsourcing in India and Costa Rica for some time now. They pay Indians $0.50/hr to transfer calls to her because they don't know how/don't want to do their job, this accounts for at least 10%-25% of her calls each day. They pay Costa Ricans $1.00/hr.
Now, of course the alleged cost per transferred call is $3. Supposedly management believes that this cost is worthwile. Even though many of the customers call to cancel their account because they can't understand what the outsourced people are saying on the phones.
My suggestion is this: If a company is US based, they must abide by US labor laws. Especially minimum wage laws, UNLESS the minimum wages laws in that country exceed that of the US. This helps the situation at least somewhat so that even our slightly lower paid US workers won't all show up on unemployment. Oh, and to be considered non-US based the execs need to move their a**es to India too, no point in saying your company is not US based when you get to live the high-life. They can see what it's like to live in a third world country.
I've heard such dumb comments from a COO that we are helping that countries economy! What the HELL about the US's economy, you know the country these shmucks live in?
There is my idea, take it or leave it.