I am an h1b working in US from past 3 years.Worked in India for 3 as well. I've always felt that all big companies should be doing their own IT. The only agenda outsourcing companies have is to increase the headcount.
Technically, 95% people working in them are so challenged. I've seen Java programmers who don;t know that Android is a Google owned OS and the apps are written in Java, even when they use Android phones themselves.
Culturally, 80% folks do not make an attempt to learn american way of life. They are high on nepotism.
The only basic diff is that they know basics of SDLC and some knowledge of coding. They are otherwise not technically inclined.
I feel more companies should be having homegrown IT. IT is not going to be a commodity any time soon, better tech will give an edge for some time to come. It will also improve the overall culture of companies in automobile, bank or other markets.
We often joke that with the turnover rate we are essentially a University for people offshore to learn from when they are doing IT. It takes so much hand-holding and rote instruction to get things done, once they learn and are proficient they want to move up.
Generally speaking, are the vast majority of folks offshore just doing their time before moving up? I sense this is culturally what people want to do - you know move into ever increasing status job titles. Trying to find senior technical people that want to continue that is hard.
Yep all off-shore people want is an opportunity at on-site. Not to learn new tech or experience a different culture or have better management skills. But to earn some $$$.
There are some good companies that do really quality work at off-shore(mostly India) - like ThoughtWorks, Nagaro etc.
Since I am one of those off-shore guys who's now at on-site. But not one day has been like when I feel I am in software business, its human resources business.
Also, I find American managers much better than Indians(I am Indian myself .. just speaking out honestly). Americans rewards talent better, are not racist and don't encourage nepotism.
I agree on principle. But I think that the future of IT will not be another IT department, but maybe a team of <5 DevOps engineers and IT architects who will are proficient in using cloud automation tools.
Unfortunately, it's not that simple. Have you ever tried posting a redirect for a story? Then another user posts the direct paywall link, which promptly rises to the front page while your submission gets buried. This is an issue that needs a solution.
What is with this? I thought Google announced in the past that sites serving different content to its crawlers than real members would have those results removed from their index. Is this some ridiculous loophole whereby it's ok if the link works with a google referrer but not directly? So stupid. If the link is not truly open, it should not appear in search results, simple as that.
Googling suggests that _Google_ employs approximately 18K software engineers, best as anyone can tell. And Microsoft maybe 40-60K. Amazon probably under 10K. (All of this is pretty much guesses and estimates, I googled around to see what people thought).
Google's most recent quarterly report has the following info:
" As of December 31, 2014, we had 53,600 full-time employees: 20,832 in research and development, 17,621 in sales and marketing, 7,510 in general and administrative functions, and 7,637 in operations. "
i'm not sure... google is certainly a company i would expect to have any number of software engineers in all of those departments, and also plenty of non-software people (biologists, economists, psychologists etc.) in core R&D.
At a local AWS group meeting an Amazon IT guy mentioned in presentation they support around 15 000 internal software development machines in the cloud. Also surprisingly all their dev machines have a commercial Lisp IDE licensed and installed.
That many :-) when I worked for BT the systems engineering division alone had over 50k that is not counting all the developers in other divisions Celnet, Syntegra plus contracted out staff at GCHQ
SE is/was the part of the company that is the heir to Tommy Flowers
It strikes me as terribly inefficient to house the software on dealerships' servers - not to mention a change management nightmare given the different competency levels amongst dealer IT personnel.
I'm also curious about the size and scale of all of this. 8,000 developers/engineers isn't that many when you measure that cost against a $3B/year HP deal. But, it seems like it's way more than it needs to be. And, the costs associated with this bloat is going to be absorbed by consumers.
That's how they started(and with a heavy lobbying effort from dealers), but it's lately been used to attack Tesla's business model, which does not use in independent dealers.
They're going to be the face of the lobbying because they're local to legislators being lobbied, but I wouldn't assume that means anything about who pays the bills.
It's more than selling cars, I know folks that got hired who are working on their mobile apps or car entertainment system, etc. And selling cars is what they do, how many programmers does google have so they can sell ads online?
Not at all ridiculous. The company I consult with currently has 5K programmers, another 10K information technology staff and 48K sales people in branches. Their site moves more product and brings more profit than the branch network. Actually the sales staff interaction with customer is 99% scripted. Those humans are just another interface, that is not much different from the Web.
It sounds like the ban on direct-to-consumer sales is in part why they need so many developers.
They'd have one group of programmers developing the core products, but then another (maybe much larger) group of programmers who are the tech assets on teams standing up partnerships with dealers. Since most dealers are independent businesses, there's probably a wide diversity of software stacks and levels of tech competence.
I don't think upper management knows much about computers, or programming? I sometimes wonder just why they are putting so many computers and sensors in their automobiles? I understand they need they to get their autos past emmission standards, but it's
gotten rediculous? When something goes wrong with these autos you can't just plug in and find the fault. It's an art to repair, and all too frequently, the mechanic just replaces a bunch of good sensors--praying he found the lazy one; even at the dealership.(Ask a dealership mechanic--it's a running joke.)
Personally, I wouldn't buy a new automobile until everyone has open access to these propriatiary automotive computer systems? I think that date is around 2018? If interested read this blog:
But then again, maybe no one cares? I know Saturn engineers tried to make a repair friendly car(you could get to failed components, but no one seemed to care?) This was before the Internet though? Times must have changed?
Are these in the Detroit area? That's great for the region. Michigan has great schools and a lot of talent, but the lack of top software jobs causes a brain drain.
Who knows, in a few years small groups of these engineers may be founding their own startups.
For example, I am part of this 8000, and I, along with many peers, were hired from HP to (at first) do the same job as before, but for GM. We had previously been contractors or part of HP Enterprise Services with GM as our customer. So, for a good number of these it wasn't a bunch of jobs being created but a simple insourcing shift.
It's been roughly two years since my transition over to a direct job and I've been happy with the choice to take the offer. There's nifty things happening here, way more flexibility and opportunity than before, and GM's a good company to work for.
ADDENDUM: I wouldn't consider myself a programmer; I'm more of a systems engineer / troubleshooter / sysadmin who writes small utility things as-needed.
With all of the recent layoffs that HP has had, I'm glad I'm no longer there. Working directly for GM feels considerably more secure than HP ever did. As others have said, I suspect it was an easy way to shed a bunch of employees without having to pay severance.
GE and GM have really warped the developer employement market in Atlanta. GE snapped up a crazy amount(thousands reportedly) of devs for their new integrated dev shop. This drove salaries up across the board.
I love to hear about companies insourcing development. There are still myriad ways that a project can fall to pieces, but paying for internal developers is a step in the right direction.
8000 seems like an awfully high number for whats effectively an e-commerce website. Be nice to know some more details of whats happening behind the scenes.
What's interesting is that GM essentially sold off their IT to EDS in the 80s. You have to be a very well run company to do your own IT well. I'm not convinced that GM is very well run. I do see some of the points that others have made regarding offshore work. Yes, these problems do exist, but they also exist in unmotived onshore workers.
Technically, 95% people working in them are so challenged. I've seen Java programmers who don;t know that Android is a Google owned OS and the apps are written in Java, even when they use Android phones themselves. Culturally, 80% folks do not make an attempt to learn american way of life. They are high on nepotism.
The only basic diff is that they know basics of SDLC and some knowledge of coding. They are otherwise not technically inclined.
I feel more companies should be having homegrown IT. IT is not going to be a commodity any time soon, better tech will give an edge for some time to come. It will also improve the overall culture of companies in automobile, bank or other markets.