Slashdot Mirror


95% Engineers in India Unfit For Software Development Jobs: Report (gadgetsnow.com)

An anonymous reader shares a report: Talent shortage is acute in the IT and data science ecosystem in India with a survey claiming that 95 percent of engineers in the country are not fit to take up software development jobs. According to a study by employability assessment company Aspiring Minds, only 4.77 percent candidates can write the correct logic for a programme -- a minimum requirement for any programming job. Over 36,000 engineering students form IT related branches of over 500 colleges took Automata -- a Machine Learning based assessment of software development skills -- and over 2/3 could not even write code that compiles.

32 of 453 comments (clear)

  1. I have a dream by Anonymous Coward · · Score: 5, Funny

    ...that we can discuss the abysmal skills of your average Indian IT worker, without being branded a racist, or using excessive PC language.

    1. Re:I have a dream by Tukz · · Score: 4, Funny

      Racist.

      --
      - Don't do what I do, it's probably not healthy nor safe. -
    2. Re:I have a dream by DontBeAMoran · · Score: 5, Funny

      If you don't like using excessive PC language maybe you could try excessive Mac language?

      --
      #DeleteFacebook
    3. Re:I have a dream by segedunum · · Score: 4, Insightful

      I don't know why it has to be branded as racist and India is an irrelevance to the point. The fact is, when companies scrape the bottom of the barrel for least cost this is what they get.

    4. Re:I have a dream by ElRabbit · · Score: 3, Interesting

      I think we shall consider also the abysmal skills of IT workers all around the world ... India is just having more issues than others. India must have difficulties with initial training and there is not enough skilled engineers on the market to perform additional training later. Manager are very keen to recognize the existence of individual performance when it is related to their bonus but completely blind when it comes to replace a skilled worker with a cheaper one (to get a bigger bonus). You can get super discount when you buy single layer toilet paper compared to double layer but you have to use twice more to not end up in covered in sh... (this was our poetic intermission).

    5. Re:I have a dream by Billy+the+Mountain · · Score: 5, Funny

      Irony: Like Goldy or Silvery but made of iron.

      --
      That was the turning point of my life--I went from negative zero to positive zero.
    6. Re:I have a dream by Anonymous Coward · · Score: 5, Interesting

      I remember when I first worked with colleagues from India in the 90's.

      They were all IIT 1% ers, the very cream of the crop, and it was terrifying to me that a country with a billion people who were freakin geniuses would out-compete Americans in every job field.

      Since then I have learned that America was receiving their very, very, very best, and that India had pretty much gone down the path that the Japanese had with their pilots in WW2, which is to say, they expended their very best without cycling them back to train new pilots (or engineers in the case of India)

      This has resulted in a decidedly lower quality of engineers in recent generations.

      India should do with their Engineers, what the US did with their pilots in WW2, which is to pull the best pilots out of front-line positions and bring them back to the states to train the next generation of pilots to be at least as good as they are.

    7. Re: I have a dream by Anonymous Coward · · Score: 3, Insightful
      PC is fascism pretending to be manners.

      -- George Carlin

  2. My experience... by Anonymous Coward · · Score: 5, Interesting

    Completely validates that report. When my last employer decided to fire the American citizens (forcing them to train their "offshore" replacements in order to receive any severance) that built the products and systems that made the company a success, those of us that remained discovered that we had to rewrite everything they produced (with a much smaller staff, of course). The greed of executive management results in far worse products for the customer - but they got their bonuses, so they do not care.

    1. Re: My experience... by pchasco · · Score: 5, Interesting

      Similar to my experience as well. We hired offshore teams to help migrate away from some mainframe systems. Of course, the few guys they sent over to work on site were incredible: Professional, knowledgeable, and excellent communicators. On the other hand, the work churned out by the offshore team was abysmal. Inefficient, convoluted, and just plain dumb in many cases. For example: I was working for an insurance company. The company was developing the software to sell a new type of product. We had a database already with all the tables necessary to support the existing product. The offshore team, in some cases literally just added columns to existing tables for this new, unrelated product. I'm not talking just a few new columns. Entire tables' worth of columns. There were no shared keys or anything between the two data. It was like building a table for payroll, then adding more columns so that you could also store warehouse inventory.

    2. Re:My experience... by Anonymous Coward · · Score: 5, Insightful

      Not even remotely the same. C-Suite generally have parachutes and bonus in the six to seven figure range. Add to that a hefty salary and it's quite likely they have a decent nest egg.
      Today's engineer/cs is suffering flat wage inflation and are competing with throngs of indentured workers from around the world. Some, as I have experienced, having mortgage payments, family, retirement goals (no pensions), random layoffs, and a poor job market barely have enough left over to say that they have a disposable income. Many end-up having to use there 401k savings to get by.

      They have little choice in the matter. They don't get golden parachutes. They don't have pensions. They have families and payments to make. I can't blame them. And, I'm certain they don't like it either.

    3. Re: My experience... by AmiMoJo · · Score: 3, Insightful

      Doesn't sound like it's anything specific to India though, the same stuff happens in the west all the time. It's the standard case of they send the best people to meet you and write a spec, but the people implementing it have little knowledge of your systems or business and you want to pay the peanuts so they aren't interesting in doing more than the bare minimum.

      I've had products like that from western developers. Had some firmware written by a contractor where a CLI was specified. If you entered more than 64 characters it would overwrite the stack and crash in the best case, lock up in the worst. When asked about it he said the spec didn't say it needed to check buffer sizes or not crash if not used in the exact way that the manual specified, with no room for error.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    4. Re: My experience... by CODiNE · · Score: 4, Interesting

      That's part of why I'm moving over to security instead of continuing as a programmer. The rush to bring in new people means untrained guys writing horrible insecure code daily.

      --
      Cwm, fjord-bank glyphs vext quiz
    5. Re:My experience... by mysidia · · Score: 5, Insightful

      You only need guys with basic skills to nail 2x4s together every 14".

      "Framing a house" is a more static job than programming, because you can make plans, Your requirements for framing are Not likely to substantively change within a job or from one job to the next. Also, you can tell your guys with basic skills exactly what to do, And you can even make sure the nails and 2x4"s they are given to use are all the same and the exact right kind for the job, and rated appropriately.

      Programming does not fit that model, because every programmer needs to make strategic decisions about what kind of code to apply to the parts of the problem they're assigned to complete. In programming, the distance between metaphorical 2x4"s is dependent on the fine business requirements and can change from one iteration to the next, Also, each nail is different, the worker needs a bag of 1000 different kind of nails and the general knowledge of which one is the correct one to use on each board based on its type and location, and not all the boards are 2x4"s, and the programmer needs to work out what kind of board is a safe and best fit where. The boards and nails need to be put in an appropriate place that cannot be planned in advance, the Right nail has to go to the right kind of board, otherwise there will be an obscure problem that may causes random unexpected failures of boards on the opposite side of the building, with no definitive quick/easy way of tracing exactly which nail was hammered in of the wrong type or inserted incorrectly, or to a board not at the correct precise spacing or angle.

    6. Re:My experience... by Opportunist · · Score: 4, Funny

      But of course I'll train them! I'll go into every detail informing them about the Slebit and Nifdit adjustments that we do in the Sedurok Environment, so we can easily interface from there with the INKFUUL. That's the technology you're familiar with, right? I mean, you don't want me to tell my current and your future boss that you don't understand what I'm talking about here, do you?

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    7. Re: My experience... by Frosty+Piss · · Score: 4, Funny

      When asked about it he said the spec didn't say it needed to check buffer sizes or not crash if not used in the exact way that the manual specified, with no room for error.

      I don't see a problem with this. You want specific levels of error handling? Put it in the spec.

      --
      If you want news from today, you have to come back tomorrow.
    8. Re: My experience... by Orgasmatron · · Score: 4, Insightful

      That's a good way to get into specification-paralysis: assume that the programmers have absolutely no idea what is reasonable and specify everything down to the absolute smallest detail. Might as well just write it yourself if you are going to assume that your programmer is exactly as dumb as the compiler.

      --
      See that "Preview" button?
  3. I wonder... by Anonymous Coward · · Score: 5, Interesting

    What the numbers would look like in the US.

    1. Re:I wonder... by alvinrod · · Score: 4, Informative

      I was somewhat skeptical of the numbers as well, and found a previous year's version of the same survey: 2016 Report (PDF) It seems that part of the problem is that it looks at any type of engineer, whether computer, electrical, software, or mechanical. It also measures employability in fields such as civil engineering, chemical engineering, and other fields that have nothing to do with software development. The numbers for some of those fields are higher than the number quoted in the summary, which leads me to believe that a reasonably chunk of the engineers surveyed have no desire to program at all or pursue a career in it.

      There are some other interesting figures in the report, but it's quite large. Seems like this is another case of a reporter not understanding a study and making a bad headline.

    2. Re:I wonder... by bluefoxlucid · · Score: 3, Interesting

      We've got a lot of experienced programmers here, and a lot of good and intelligent people. They've managed to create a colossal fuck-up and still believe it's well-designed and functional and doesn't need any real architectural rework. The one guy who's a giant nerd and actually studies beyond the ok-plateu is correlating all the fires to real understanding of architectural flaws; and of course the non-programmer (me) who studied project management is looking at the spread of expert knowledge and coming to the conclusion that that guy's right.

      So probably 95% of programmers are idiots who found a chainsaw and think they know what they're doing because they can hit a tree with it.

    3. Re:I wonder... by arth1 · · Score: 4, Insightful

      Yes, the correct answer to a request for a recursive Fibonacci routine that returns the Nth element is "I refuse to do that on basis of it being immensely stupid, unless I can do it in assembly or a language that allows stack-free re-entry and short-circuiting".

      fib 3871934874 is what?

  4. It'll get better, maybe someday by conquistadorst · · Score: 3, Insightful

    Pretty sure my parent company still outsources to all of them. I hate making large broad statements, but I've never yet met one I was impressed by. Seems to whole business model for outsourcing revolves around everything being so cheap you can rebuild it 5x and still come out ahead on direct project costs. As for impacting the business with garbage software, that doesn't cost anything, right?

    1. Re:It'll get better, maybe someday by drinkypoo · · Score: 4, Insightful

      This is a direct result of the extreme overpaid status of the American tech workforce.

      Well, no. It's the direct result of us not closing down trade with countries which use slave labor. We talk a good game on the subject of slavery, but then we completely fall down when it comes time for the rubber to meet the road and make shit happen. Instead, the wheels spin and there's a lot of smoke and stink.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  5. Not that bad. by Gravis+Zero · · Score: 4, Funny

    I heard that 3/4 of the people working on Windows 10 couldn't write code that compiles, so I understand why they are hiring from India. ;)

    --
    Anons need not reply. Questions end with a question mark.
  6. I don't think it's just India... by adosch · · Score: 5, Insightful

    I would say in a whole, true software engineering has been completely watered down and very disappointing over the last 10-15 years. From all the way down in school systems with STEM and all they way up with these 3-4 day crash-course 'bootcamps' and seem to manufacture quick hot-on-resume-paper skills without experience is really the problem. And even on top of that, how many people just 'google' their way into a job or solution? No one thinks anymore, we are in an age of just-give-me-the-stuff mentality. Don't care how or why, just blindly take the answer and move on. You don't grow as a competent and efficient engineer that way.

    Coupled with the fact that any business, company or dev shop wants talent in our psychotic digital age, this reminds me nothing more than a massive amount of people doing nothing more than to try to get their foot into a hot job market and doing nothing more than trying to flip a huge salary for 6-12 months. And that's why I say it has very little to do with India.

  7. This is truly suprising! by Ihlosi · · Score: 4, Funny

    I am shocked! I cannot describe how shocked I am.

  8. Engineers? by Oswald+McWeany · · Score: 3, Insightful

    Why would Engineers write code? Shouldn't those Engineers get back to driving the trains and leave the programming for the programmers?

    / Call me a Software Developer. Call me a Programmer. Call me a Code Monkey even. I am not an Engineer. Calling programmers "Engineers" is stupid. It's like calling janitors "sanitation experts" or secretaries "office administrators". Call a rose a rose and stop all this silly flowery job titles.

    --
    "That's the way to do it" - Punch
    1. Re: Engineers? by HornWumpus · · Score: 3, Interesting

      Both mechanical, electrical and software systems are developed to higher standards to be 'man rated'. Not every bit of code needs to be that well tested.

      Engineers understand the difference, software developers might not.

      --
      John McAfee 'It was like that time I hired that Bangkok prostitute; to do my taxes, while I fucked my accountant'
  9. All that glitters is software. by achacha · · Score: 5, Interesting

    I think there are many talented and smart developers in India (as anywhere else). The biggest issue is that they mostly want to work for very large companies (prestige), they are in a hurry to be promoted to managers (many are not good at managing anything but it's all about the title) and thus good developers become weak managers. This depletes the software developer pool so they have to hire people less and less qualified to do the coding.

    Another is that there are a lot of "software consulting" companies that handle outsourced work, they tend to have some good developers and a lot of "junior" developers, so when they sell themselves to a customer they can say they have a staff of 100 developers ready to go. This is compounded with the problem of developers trying to get promoted into management (again, title and status are very important to people).

    I am not sure if 95% is an accurate number (seems a bit high), but the problem exists nevertheless.

    I have read that a lot has to do with sociological issue of being used to a caste system, and while it's not as prevalent as it used to be, rank and status are very important. While this is also true in many other countries (I have worked with many Eastern European and Far East companies), India remains as the place where every developer seems to be looking for a promotion. Some companies placate the developers by giving them over-inflated titles like chief architect or senior staff engineer; but in a company with dozens of chief architects the title no longer has a significant meaning.

    Anecdotal evidence: I worked with a developer who was young and his mom kept emailing him to get promoted to a manager so that when she went looking for a wife she could pick from a nicer "deck" because he was a manager ( a deck of pictures/bios is how moms and matchmakers and astrologists get together to determine who gets to marry whom, it's very complicated from what I have seen). I thought it was funny, but he was very serious that the "quality" of a wife his mom could get depended a lot on where he worked and what his title was. At one point he lobbied to get a temporary title and we put him on a short term support project where he was handling issues for one single customer and had a temporary title of a "Senior Customer Manager". He was married within 3 months.

  10. Doesn't seem unreasonable. by nedlohs · · Score: 3, Interesting

    It's a company trying to sell their assessment products that are more marketable the higher the number they manage to produce out of their "study". Extrapolating "36,000 engineering students from IT related branches of over 500 colleges" to " engineers in the country" seems a little generous as well. Most of the students in IT related branches I've met are also really crap at programming - because they aren't actually doing programming or because they are first years who haven't managed to learn anything yet.

    That said most of the people I have interviewed for programming positions I would put in the "can't program" category too. Not 95%, but probably 60%.

    And I would expect the Indian IT education system to have more than its fair share of really bad "colleges" compared with say the US (and note that the US has things like "ITT Technical Institute"). It's a bigger country population wise with worse infrastructure and government oversight. The good programmers seem far more likely to go and get a job overseas than they do to take up an academic career in an Indian college...

  11. Lies, damned lies, and statistics by Kenneth+Stephen · · Score: 3, Informative

    So there is probably a lot of truth in the reporting, but the shock value of the story comes from the numbers. 95% you say! Oh my! We cannot have any Indians write code! The details, in this case, matter a great deal, so lets take a look at some of the unanswered questions that may impact the accuracy of that number.

    * What does "...not write code that compiles" mean? Were the people being tested provided an IDE? I'm an expert Java programmer, but if I were to open up a text file and type Java code, odds are pretty good that my code won't compile on the first try. That's what IDE's are there for - to fix the inane syntax issues. But lets say that the IDE's were provided. What sort of languages were used in the test? Were the test takers familiar in the language being used? Was the measurement really meaning that they ran out of time to make the program compile or that they were incapable of making it compile because they really weren't a programmer? I note that the "cannot even compile" statistic is 2/3 - not 95% according to TFA. Still bad, but details are needed to see what was being measured.
    * What does the sample mean? TFA says that the sample size was 36000, but how does this compare to the universe out there, and who made up the sample? Were these graduates in computer science or first year students or people already working in the field? What was the level of quality for these universities? Where did the 5% who did good come from, and did those 5% come from the really good schools? Was the sample size structured to represent the real world distribution of quality in educational institutions?
    * Bias: who is aspiring minds, and what is their motivation? Are they tied to a particular agenda? Is there a competing country that wants their programmers to be hired over Indian programmers pushing these stats? I will point out that there were numerous doctors pushing the agenda of the tobacco industry, and numerous scientists pushing the agenda of the oil industry (global warming). So, yes, the affiliations need to be clear.

    I will also point out that in the silicon valley, Indian engineers are present in high numbers. And a lot of the clamor for getting Indians into the US comes from companies in that area. If 95% of them were useless, I can't help but think that there would be less demand.

    --

    There is no such thing as luck. Luck is nothing but an absence of bad luck.

  12. Re:In other words... by arth1 · · Score: 3, Insightful

    95% percent of Software Development employers unwilling to train people into the job.

    Programming isn't an assembly line, where you can train people in the steps and they just repeat it. You have to have an ability to think, and come up with new solutions to new challenges. And when faced with alternatives, be able to pick the one that's the best for the task at hand, and understand and be able to explain why.

    Training means very little. Someone who requires training is near worthless as a programmer.