Their interns are steered away from programming, towards career paths that are perceived as adding value: e.g. consulting.
I suppose in theory this makes sense: have the smart locals figure out what is needed, write up some specs and then get the guys in Bangalore to bang (sic) it out for you.
In practice, it is an absolute dogs bollocks.
(1) The local IBMers have forgotten how to do anything in the real world. No, seriously. They can't even install a server to use for their own use as a test machine in less than 4-6 weeks.
(2) The Bangalore IBMers cannot code for shit. They are the second worst programmers I ever worked with (and the worst was a consultant Thoughtworker who was actively sabotaging the project). The ones who did the least got promoted. twitch
(3) They can't even maintain the software they wrote 5-10 years ago, they just don't make any effort to retain that knowledge.
(4) It might be different for US IBMers, but outside of the US the programmers got the shaft big time when the GFC hit. Stupid little things like (even if your business unit was profitable) you had to bring your own coffee and milk in to work because they stopped supplying them free.
Other than the above, IBM is just like any other large organization.
To more about the state of affairs here, read my comment on another thread - http://news.ycombinator.com/item?id=2480368
IBM is the company that keeps a nearly-five-decade-old architecture and ISA around for its business customers, correct? (zSeries (or whatever its name is this week) is derived from s390, is derived from s370, is derived from s360, was created in the early 1960s.) z/OS and z/VM are modern versions of MVS and CP-40, which date to 1974 and 1967, respectively.
It seems odd that the company that does that would have problems with decade-old software in any of its business units.
That said, I have enormous respect for their mainframe division and operating system programmers. Their server hardware (z, i, and x), z/OS/, z/VM, AIX and their contributions to the Linux kernel are all very good.
IBM is certainly big enough and old enough that different divisions can behave like completely different companies. It's a bit unfair, in fact, to see one division tarnishing the image of a company so full with groundbreaking accomplishments and such a rich history as IBM. The consulting division has to compete for huge contracts, that are managed by pointy-haired lifeforms who can't see beyond hourly rates, with equally incompetent organizations like EDS/HP, Accenture and Tata.
You put an evolutionary pression on the market driving it to provide low prices. The marker responds optimizing for price and price alone.
When you have to compete in price with incompetent-but-cheap organizations, you either become incompetent-but-cheap or get out of business.
Tough choice.
The units in IBM that work on Mainframes and Supercomputers et al, are totally different than the ones that execute maintenance and service projects. The people, the culture everything is different.
I agree with the not letting smart people be smart... but it's not even that. If a project has caught fire and is burning down, they don't let the people with the firefighting skills come in and save it.
Partly it is an incentivization problem. That is, there isn't any incentive to be efficient and good at what you do. Especially if you're billing your people out as consultants by the hour and somebody else is paying for it. This is a two level problem. The individuals have no incentive to make themselves genuinely better at what they do (there are personal development programs in IBM which people are encouraged to take, but that just pushes them even faster towards positions where they don't actually do anything useful - e.g. management), and the organization as a whole actually loses money if it becomes more efficient.
During 90's and early 2000's most people got rapidly promoted regardless of whether they deserve it or not. They have hardly coded, spent most of the times at on site locations made good money and are now just relaxing and pushing time. Managers have no frigging clue how projects need to run, architects don't even have basic technical skills.
The assumption is that you can just give orders to juniors and get the job done. That is how most of the so called seniors work here. Good hackers/programmers are never rewarded due to many reasons. The horrible ones hop jobs to get good hikes and ultimately end up earning more than the good guys.
The general attitude of the guys joining the industry is not be technically good, never code, just get promoted quickly, go to onsite, earn money in USD, purchanse a flat, car, marry and settle down. And these sort of guys were actually rewarded during 90's and 2000's. So now everybody wants to be like that.
The actual good guys are there, but are lost in the crowd.