Forgot your password?
typodupeerror
Databases Python

Job Postings For Python, NoSQL, Apache Hadoop Way Up This Year 52

Posted by Soulskill
from the year-of-the-accidental-dba dept.
Nerval's Lobster writes: "Dice [note: our corporate overlord] collects a ton of data from job postings. Its latest findings? The number of jobs posted for NoSQL experts has risen 54 percent year-over-year, ahead of postings for professionals skilled in so-called 'Big Data' (up 46 percent), Apache Hadoop (43 percent), and Python (16 percent). Employers are also seeking those with expertise in Software-as-a-Service platforms, to the tune of 20 percent more job postings over the past twelve months; in a similar vein, postings for tech professionals with some cloud experience have leapt 27 percent in the same period. Nothing earth-shattering here, but it's perhaps interesting to note that, for all the hype surrounding some of these things, there's actually significant demand behind them."
This discussion has been archived. No new comments can be posted.

Job Postings For Python, NoSQL, Apache Hadoop Way Up This Year

Comments Filter:
  • by Anonymous Coward on Wednesday May 07, 2014 @01:15AM (#46936911)

    It seems strange to specifically ask for experts that know no SQL.

    • by Tablizer (95088)

      It seems strange to specifically ask for experts that know no SQL.

      It shows one can pass HR's buzz-word filters without lying and STILL be a dumbshit.

      • It shows one can pass HR's buzz-word filters without lying and STILL be a dumbshit.

        right???

        holy crap you guys...

        seriously...

        I used to do db admin w/ a 800K contact database for a magazine publishing and tradeshow company including a call center...it was actually a fun job! we did all kinds of data 'pulls' for all departments...we were 'data services'...we used all kinds of programs, Oracle, the M$ products, even some programs we patched together

        That was many years ago...

        I'm wondering how you guys take it? W

        • by ArhcAngel (247594)

          I used to do db admin w/ a 800K contact database...it was actually a fun job!

          You poor kid. Would the other kids not play with you as a child?

          • You poor kid. Would the other kids not play with you as a child?

            yes! since age 5 I was kept in a burlap sack and only allowed out to code and poop...my only human contact until after college was a dog groomer my keepers paid to shave my head every 6 months

            but for real...it was the people that made it actually fun...I had two great supervisors and...well the company was in downtown Boulder, CO on the main walking mall area...so lunch breaks were fantastic

            • by ArhcAngel (247594)
              I might even be tempted to take a db admin job in Boulder, Co...
              • I'd suggest it...if you're the kind that likes good weather, beautiful scenery (of geological and human kind), being accepted as 'weird' w/o question by your neighbors, awesome restaurants, legal weed, and a big metro area just over the hill and across a federal wetland area 35 miles away...

                The misconception some have is that since Boulder is in Colorado that its somehow very 'wintery'...nothing could be further from the truth...it has a wet warm winter...but snow will stay on the ground...300+ days of sun

    • by DeBaas (470886)

      I'm sure there are a lot of DBA's that would be happy if less people in the company knew SQL...

    • by Chrisq (894406)

      It seems strange to specifically ask for experts that know no SQL.

      Maybe they want to employ happy programmers!

    • by DoofusOfDeath (636671) on Wednesday May 07, 2014 @04:57AM (#46937559)

      It seems strange to specifically ask for experts that know no SQL.

      It's a ploy to get more H1B's into the country. "We can't find any database experts in the U.S. who know no SQL!"

    • SQL is a bad thing, but not because RDBMSs are a bad idea. Quite the opposite. but all those people leaving RDBMS databases do it because RDBMSs are screwed up both by forcing people to use SQL (which is atrocious in itself) and because most RDBMS vendors have the same attitude now that Lisp machine companies had in the 1980s - they want outrageous money for bloated crap. Then they wonder why people go somewhere else for stuff that should have been commonplace fifteen years ago.

      • by ArhcAngel (247594)
        I would dance a jig if I could get the BU I support to switch to SQL. They are currently building a database of vendor and partner well data. They get the data from a UniData sourced db...upload it to a server that converts it to SQL (Using the corporate licensed Oracle db) just so the Microsoft ACCESS db can pull in the data. Of course for smaller projects why bother with anything but an Excel spreadsheet with thirty or so user generated add-ins that require your credentials which are parsed in plain text.
        • Well, yeah, there are people still stuck with mainframe(not the good parts)/IMS-level technology. :-) I get that.
    • Is SQL really such a bad thing?

      Off course not, but you must combine it with XML, and XSLT. What purpose does it serve to only write a program in SQL at run-time, and have it interpreted at run-time if you do not let the database server wrap the results in a human-hostile text format at run-time and parse it at run-time with the client? Especially if all the object-oriented techniques now make it possible to have enough separation to request the person details at index locations 3, 17 and 173?

      If you program blind-panic-style, I can imagin

      • And yet the NoSQL vendors are generally finding that SQL describes what they want to do without a problem...
  • by Anonymous Coward

    Sure, they'll post the job. Like posting a job for folks who have four years experience driving Chevy pickups. As if you can't learn the skills they want in two weeks.

    But it lets them pretend there's a "skills shortage" while leaving millions of qualified workers begging for hire.

    • If you think you can learn no-sql, python and the cloud in 2 weeks, you're deeply mistaking. It took me months to get up to speed with OpenStack, and I still learn every day after years doing its Debian packaging. Sure, as it's something new, companies should take into account that their future employee will have to learn and wont know all of this. However, it isn't a reason why not posting needed skills for the job.
      • If a competent programmer who knows SQL and C/C++, and a few other languages, maybe Java and LISP, can't learn enough NoSQL and Python in two weeks to start being productive, then NoSQL and Python are bad platforms and languages. A newcomer will not learn all the quirks, tricks, and libraries in 2 weeks, but doesn't have to. Don't have to know half of the typical bloated language to do useful work in it. As for the cloud, someone experienced with system administration ought to be able to pick up enough

        • If a competent programmer who knows SQL and C/C++, and a few other languages, maybe Java and LISP, can't learn enough NoSQL and Python in two weeks to start being productive, then NoSQL and Python are bad platforms and languages. A newcomer will not learn all the quirks, tricks, and libraries in 2 weeks, but doesn't have to. Don't have to know half of the typical bloated language to do useful work in it. As for the cloud, someone experienced with system administration ought to be able to pick up enough to make some good use of it in less than a week.

          In his example the issue is not necessary NoSQL or Python, it's how they are used by the other stuff (e.g OpenStack). Learning Python is the easy part; figuring out how everything inter-relates in OpenStack is the hard part.

  • Percentages? (Score:5, Insightful)

    by Anonymous Coward on Wednesday May 07, 2014 @01:37AM (#46936995)

    Percentages can be very misleading, do they have raw numbers?

    If there was only one python posting last year but 10 this year, that's 1000%!!!

    • Re:Percentages? (Score:5, Insightful)

      by antifoidulus (807088) on Wednesday May 07, 2014 @01:41AM (#46937009) Homepage Journal
      Not just raw numbers, some sort of weighting system would be useful too. A lot of postings I've seen throw in a lot of these technologies as sort of a "nice to have", but don't really require them nor will they most likely be used on the job. However the search engine will still hit upon them, influencing the numbers. TFA has no mention of their methodology or what they define the various positions to be, so I'm guessing their methodology is "search every job posting we have had for certain words and count them".... Wonder if they used map-reduce to do so :P
    • Re:Percentages? (Score:5, Informative)

      by Sarusa (104047) on Wednesday May 07, 2014 @01:51AM (#46937041)

      TFA is kind of dumb for not giving the numbers, but a quick search on Dice turns up 4800 python listings.

      Compare to 1770 Hadoop listings, 1490 NoSQL, and 3250 for 'Big Data' and you can see that it's kind of the opposite of what you were suggesting. The reason Python is only up 16% is because it had so many listings last year already.

      2700 Ruby listings for comparison, regarding another post.

      • Re:Percentages? (Score:4, Informative)

        by Anonymous Coward on Wednesday May 07, 2014 @06:59AM (#46938119)

        16599 for Java
        15924 for C,
        3359 for PHP
        4327 for Perl
        0 for fortran (heh)
        0 for COBOL (heh)
        2657 for iOS
        2522 for Android
        27 for Lisp
        11055 for Linux
        36 for Haskell
        373 for Scala
        425 for Groovy

        etc. etc..

        These numbers mean hardly anything at all. Dice has serious selection bias too.

    • by umghhh (965931)
      TFA speaks about increase so I assume you too. For 1000% increase you would have to have 11 times as many postings this year as you had last year i.e. 1 posting last year and 11 postings this year meaning there are 10 more i.e. this 1000% increase. That is what you get when you use percents and wrong example.
    • Re: (Score:3, Informative)

      by Anonymous Coward

      Anecdotal, but I've basically got all the skills listed in this article. I started job hunting a few weeks ago (mid April). The last time I went job hunting, about 6 years ago, my rule of thumb was that roughly 1 out of every 5 recruiters I spoke to would translate to an interview. This time around, every one of them seems to land multiple opportunities. I've done at least 3 phone interviews each week. This week alone I've had one face-to-face on Monday, and 4 more phone screens. I've never seen anyth

  • LPNAH just isn't the same.
  • for all the hype surrounding some of these things, there's actually significant demand behind them

    It could be the typical PHB gets sucked into the hype and tosses those buzzwords into the job ad to make sure he's getting the "freshest talent". The ad is already stuffed with gazillion buzzwords, so why not gazillion + 1

  • by Anonymous Coward on Wednesday May 07, 2014 @05:59AM (#46937811)

    Sure, the job may say "Python" or "PHP" in the title, but .... they usually want niche skills with some CMS you've never heard of written in these languages, and if you read the whole job writeup, it's not a "Python" job other than you need to know Python to write extensions for the CMS. So if you know Python programming, you still won't get the job.

    The reason why there's a "shortage" of skills at the same time there's a glut of developers available is the insanely narrow specialization that companies want. There aren't many people who have even heard of the CMS-of-the-week the company uses, let alone knows its internals well enough to do what the company wants done. Companies seem very good at picking losers in the technology race, and get stuck with things that are evolutionary dead ends, further limiting their talent pool.

    Big data is probably the same thing, but I don't know anything about it.

  • work performed by people relying on these folks to do their jobs falls dramatically. IT support staff frazzled at having to constantly find solutions to problems created by people who are supposedly wizards at what they do.

    IT management oblivious to problems so long as products get shoved at door and they can make their bonuses.

  • by tomhath (637240) on Wednesday May 07, 2014 @08:06AM (#46938665)

    Those were all niche markets a couple of years ago so big percentage increases don't mean all that much.

    IMHO...most companies won't ever have a use for Hadoop. "Big Data" is a buzz word that doesn't mean anything. "Cloud" doesn't require a specially trained expert. NoSQL is another word for caching, which most enterprisy applications don't do well, so that's worth knowing (especially if the app is trying to use Java/Hibernate for persistence, yuck). Python will continue increasing in popularity because there isn't a better alternative for quick scripting and small applications, Java is too cumbersome for small tasks.

    • How is NoSQL another word for caching? You can use NoSQL databases to implement cache systems, but that in no way is the extent of it (the term itself is very, very vague and means a multitude of different approaches to handle data).

      • by tomhath (637240)

        (the term itself is very, very vague and means a multitude of different approaches to handle data)

        Yes, that's a big part of the problem. But when you listen to the reasons to use NoSql they all come down to having the data stored in a manner the application can get to it quickly, with less consideration given to the usual RDB concerns like data integrity and normalization. To me, that's a cache (although "cache" is also a vague term).

        • Actually to me NoSQL means firstly schema-less data and not ACID operations. But then there are NoSQL DBs that allow defining schames and have ACID operations.

          But try to explain that to your average recruiter.

  • I wonder how many of those jobs for "big data" involve data sets that will sit on a USB drive?

    PHB: "But it's a TERABYTE, at least!"

The biggest mistake you can make is to believe that you are working for someone else.

Working...