Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
IT Technology

The Great IT Hiring He-Said / She-Said 574

Nemo the Magnificent writes: Is there an IT talent shortage? Or is there a clue shortage on the hiring side? Hiring managers put on their perfection goggles and write elaborate job descriptions laying out mandatory experience and know-how that the "purple squirrel" candidate must have. They define job openings to be entry-level, automatically excluding those in mid-career. Candidates suspect that the only real shortage is one of willingness to pay what they are worth. Job seekers bend over backwards to make it through HR's keyword filters, only to be frustrated by phone screens seemingly administered by those who know only buzzwords.

Meanwhile, hiring managers feel the pressure to fill openings instantly with exactly the right person, and when they can't, the team and the company suffer. InformationWeek lays out a number of ways the two sides can start listening to each other. For example, some of the most successful companies find their talent through engagement with the technical community, participating in hackathons or offering seminars on hot topics such as Scala and Hadoop. These companies play a long game in order to lodge in the consciousness of the candidates they hope will apply next time they're ready to make a move.
This discussion has been archived. No new comments can be posted.

The Great IT Hiring He-Said / She-Said

Comments Filter:
  • by msobkow ( 48369 ) on Monday November 03, 2014 @10:17PM (#48306883) Homepage Journal

    The biggest clue shortage on the hiring side is requiring x years of experience with a tool or product that has only been out for less time than they're demanding. I've lost count of the numbers of times I've seen such asinine job posting requirements.

    Another good clue shortage is expecting x years with one product, y years with another product, and z years with a third, while specifying that it's an intermediate position. Make up your mind -- either you want someone with only 5 years of experience or you want someone who's spent time with the tools you're requesting -- the two are mutually exclusive!

    • by lucabrasi999 ( 585141 ) on Monday November 03, 2014 @10:24PM (#48306935) Journal

      expecting x years with one product, y years with another product, and z years with a third, while specifying that it's an intermediate position

      You misread the job description. The JOB is experienced. The salary is intermediate.

    • by KermodeBear ( 738243 ) on Monday November 03, 2014 @10:38PM (#48306997) Homepage

      I was greatly amused when the HR department at my company was looking for "Pearl" developers.

      • by ArmchairGeneral ( 1244800 ) on Monday November 03, 2014 @10:47PM (#48307029)
        Well it goes with Ruby, right?
      • by Anonymous Coward on Monday November 03, 2014 @10:48PM (#48307041)

        your company has positions for oysters? That is progressive!

      • by TWX ( 665546 ) on Monday November 03, 2014 @11:26PM (#48307221)

        I was greatly amused when the HR department at my company was looking for "Pearl" developers.

        I lost out on a job because I didn't have experience with Windows XP Server.

        Honestly, it works best when HR passes on the bulk of the applications to the department that needs the staff member, and lets that director and supervisor(s) weed through them for candidates. They can even go with redacted versions that don't show the name or the alma mater of the applicant, and are limited to the last couple of disclosed jobs. It still requires a lot of labor-hours to go through that and to go through a good interview process though, and technical people that work for the company and will probably work with the new hire must be free to ask freestyle questions in addition to the HR-mandated set, to actually learn the technical capabilities of the interviewee.

      • by Anonymous Coward on Monday November 03, 2014 @11:44PM (#48307309)
        In the late 90s, while leaving an interview at one company, I came across a physical posting on the window of another business in the same building. It was for a developer, but in particular looking for someone with C, C+, and C++ experience. I had a little time to kill, and figured maybe the HR guy just didn't pay attention (enough stupid stuff ends up in ads for what are still decent jobs). Stopping in, the HR guy right off the bat emphasized that and other prereqs for the position, but said he would introduce me to the head developer anyway. They were moving some business software from Basic to C/C++ without much internal experience in the latter. Turns out the C+ requirement in this case came from the developer, not an HR guy goof, and he got rather defensive about it when asked what he was referring to. Seems nearly every interviewee so far had asked about it, and got shown the door for lack of experience as a result. Not a person I would have wanted to work for, so no loss to me.
      • by Mr_Wisenheimer ( 3534031 ) on Tuesday November 04, 2014 @02:03AM (#48307701)
      • by jandersen ( 462034 ) on Tuesday November 04, 2014 @05:09AM (#48308225)

        I was greatly amused when the HR department at my company was looking for "Pearl" developers.

        That would be somebody with a lot of mussels, right?

      • by schlachter ( 862210 ) on Tuesday November 04, 2014 @10:35AM (#48309991)

        I was told by Google HR that they do NOT require CS degrees for their computer scientist / software engineer positions. They were eager to hire me for this position despite my not having a CS degree (I have a related advanced technical degree). However, I wanted a product manager position, and they refused to even interview me for it on the basis that I didn't have a CS degree. They said a CS degree WAS required for this position. We went round and round about the absurdity of not requiring it for a computer science position but requiring it for a product management position, until I said, fuck it, this doesn't sound like the place for me. Sad.

    • by wisnoskij ( 1206448 ) on Monday November 03, 2014 @10:39PM (#48306999) Homepage
      What is even with the X years of experience with product X? Why would anyone expect that someone with 5 years experience with product X would be any more proficient than someone with 3? After mastering the basics, which normally takes on the orders of magnitude of months, not years, the amount of time that passes is not really related to the number of specifics you learn about that product.
      • by Anonymous Coward on Monday November 03, 2014 @10:56PM (#48307087)

        Remember: HR people generally don't know the first thing about what they are actually hiring for. They're told to find someone who can program in X or is decent in OS Y. After a few filters go over it, it suddenly because 5 years in X along with 5 years each in a bunch of semi-related stuff. Its just like if you tried to hire for a position for something you don't know the first thing about, but you have to figure out who the best person is.

        • by lgw ( 121541 ) on Monday November 03, 2014 @11:50PM (#48307329) Journal

          While we're happy to review any resumes HR sends our way, managers where I work spend significant amounts of time personally searching sites like Linked-in and reading resumes themselves, and directly calling candidates who look good. Our biggest problem is willingness to relocate - candidates who are already on the West Coast are so hammered by recruiters that it's hard to find anyone actually looking, but there are plenty of qualified engineers elsewhere.

          The moral of the story is: make sure your resume appears in the right places, and does a good job of selling you (protip: no one cares about "duties and responsibilities" - explain cool problems that you personally solved instead). And realize most of the programming jobs are in Silly Valley and (increasingly) Seattle, so look where demand exceeds supply, not in a town with 2 programming jobs and 3 programmers.

          • by wierd_w ( 1375923 ) on Tuesday November 04, 2014 @03:13AM (#48307887)

            The problem is that outside silly valley-- Say, in flyoverland USA, the cost of relocation is not trivial.

            Your typical house in silly valley costs more than 10 years salary elsewhere. There is not enough equity in the house they currently own to be able to afford the move.

            Sweeten the deal with guaranteed housing, and travel expenses. You will get MANY more people willing to relocate.

            OR-- allow telecommuting from another state as an option.

          • by TheRaven64 ( 641858 ) on Tuesday November 04, 2014 @07:11AM (#48308503) Journal

            Our biggest problem is willingness to relocate - candidates who are already on the West Coast are so hammered by recruiters that it's hard to find anyone actually looking, but there are plenty of qualified engineers elsewhere.

            Sounds like the real problem is that you are unwilling to relocate. Putting your company somewhere where the cost of living is high and there's a shortage of talent seems to be very popular, but difficult to understand. Why not find out where there's a pool of talent and open an office there? Or do what a number of tech companies have done and allow remote workers, then start building satellite offices where you find clusters of competent people.

            • I always wondered why tech offices were located in the centre of some crappy city or soulless business park (eg Winnersh in Reading, sigh).

              If I had a big company to set up somewhere, it'd be in an area usually frequented by tourists - there are enough people wanting to move from their shitty rat race commute that they would want to relocate to a nice area. And you'd have the side benefit of having a trapped workforce who would never want to relocate back to their grimy city commute days.

              • Ah, Winnersh. If it's always summer in California, it is always February on Winnersh Triangle station

            • People don't deliberately "put their company somewhere where the cost of living is high and there's a shortage of talent"; they start a company where they currently live (maybe even in their current home!), and if they're starting a tech company because they're tech people and previously worked in tech, they probably live in a tech area. And they're going to start by hiring other tech people who already live in the tech area. That's how these things grow (some would say fester) in one neighborhood.
            • by tippen ( 704534 )

              Sounds like the real problem is that you are unwilling to relocate. Putting your company somewhere where the cost of living is high and there's a shortage of talent seems to be very popular, but difficult to understand.

              One of the main things that drives this is how funding works. It's amazing how difficult it is to get funding if it requires the VCs to travel. Certainly a significant hurdle even for places like Austin where you have a decent-sized high-tech community.

              Since there are already WAY more companies than they'll ever fund just down the street, it's hard to blame the VCs for not wanting to get on a plane constantly. Founders know this, so guess where they tend to start their companies?

              Of course, while they ar

          • by danaris ( 525051 ) <danarisNO@SPAMmac.com> on Tuesday November 04, 2014 @07:52AM (#48308639) Homepage

            (protip: no one cares about "duties and responsibilities" - explain cool problems that you personally solved instead)

            Do you have any idea how many people will give different pieces of often totally mutually exclusive resume advice? Your "protip" sounds like a great way to never get looked at by a very large number of firms who actually let HR do all their hiring. And yes, those exist.

            Your desires, requirements, and experience are not universal. They are yours. It is important to recognize that, and at least try not to penalize other people when their experience with the hiring process doesn't match what you expect or want.

            Dan Aris

      • by whoever57 ( 658626 ) on Monday November 03, 2014 @11:18PM (#48307205) Journal

        What is even with the X years of experience with product X? Why would anyone expect that someone with 5 years experience with product X would be any more proficient than someone with 3? After mastering the basics, which normally takes on the orders of magnitude of months, not years, the amount of time that passes is not really related to the number of specifics you learn about that product.

        Perhaps there is an LCA application (part of the green card process) in progress where the applicant has exactly those skills?

      • by TaliesinWI ( 454205 ) on Monday November 03, 2014 @11:33PM (#48307267) Journal

        My personal favorite - and one I was dinged on several times before I learned to basically just lie my ass off about it - was how many servers I've been responsible for at one time. At some ISP jobs I've had, I've had to touch hundreds of unique servers while helping clients, but only had maybe 20-30 to worry about day to day. But companies hiring based on this metric want to hear that you were administering 200+, 500+, whatever number of servers on a daily basis. This is bullshit for two main reasons:

        1. No single person is personally touching dozens or hundreds of servers on a daily or even weekly basis. A _team_ of people might, but a person isn't.
        2. Once you get into a mid double digit number of servers (or sometimes even sooner) you're using automation stuff like Chef or CFEngine or BladeLogic or whatever. At that point 50, 100, 500, 5000 servers become rapidly irrelevant, because you're thinking in terms of a single task affecting an arbitrary number of servers, not a one-to-one situation. You're not logging into each individual server and firing off Windows Update every Patch Tuesday. In fact if you're wasting your time doing crap like that I would argue you're not a very good system administrator, because you're not learning and growing, you're simply caring and feeding.

        • by RabidReindeer ( 2625839 ) on Tuesday November 04, 2014 @07:44AM (#48308609)

          My personal favorite - and one I was dinged on several times before I learned to basically just lie my ass off about it - was how many servers I've been responsible for at one time. At some ISP jobs I've had, I've had to touch hundreds of unique servers while helping clients, but only had maybe 20-30 to worry about day to day. But companies hiring based on this metric want to hear that you were administering 200+, 500+, whatever number of servers on a daily basis. This is bullshit for two main reasons:

          1. No single person is personally touching dozens or hundreds of servers on a daily or even weekly basis. A _team_ of people might, but a person isn't.

          My take on this is that if there are 200+ servers, any on of which you may be required to service, the fact that you don't "touch" them all daily doesn't matter and that there's no lie involved here.

          That's like rating the fire department on the number of houses they visit instead of the number of houses they protect.

          The more servers you have to touch on a daily basis, the more likely that they're not well-configured.

        • Apple is bringing a data center to Northern Nevada, just outside Reno. Problem is, their entry level requirement is that you've worked at a minimum of 10k server data center previously [apple.com] (select Reno) for their "Site Services Tech" position it's "4+ years experience working in a large data center (10,000+ servers)..

          Problem is, there aren't any 10k centers in Northern Nevada, yet they got oodles of tax breaks to "make local jobs".

          Someone didn't think this through.
        • You're not logging into each individual server and firing off Windows Update every Patch Tuesday. In fact if you're wasting your time doing crap like that I would argue you're not a very good system administrator, because you're not learning and growing, you're simply caring and feeding.

          Until that one time the automated patching system causes the critical server to fail in some way that could have been easily cleared if a human was watching.

          Seriously, we automate all the patching we can, but some of the bizarre software running on our VMs means they have to be rebooted manually so that if something screws up, it can be fixed fast. And, yes, I know that for any critical service, there should be some sort of clustering, but generally I'm taking about VMs that interact with specific scientif

      • by TapeCutter ( 624760 ) on Tuesday November 04, 2014 @02:09AM (#48307709) Journal
        It's just lost in translation, project manager fills out some questions on a form, says xyz is mandatory, abc are "nice to have", overall 5yr experience requirement gets conflated with 5yrs experience with xyz by someone writing a job ad who has no idea what xyz means. Go and read your job description at HR, it's utterly devoid of any meaning. Of course this is fucking annoying for all concerned but the same is true for any professional position, and from the project managers POV going to HR is still better than trying to do the first cut filtering yourself.
    • The biggest clue shortage on the hiring side is requiring x years of experience with a tool or product that has only been out for less time than they're demanding.

      If they're asking for experience from before when it was out, then you need to have worked for the company that produced it. It's a way to disguise poaching.

      • Re:Poaching (Score:5, Insightful)

        by AK Marc ( 707885 ) on Monday November 03, 2014 @11:00PM (#48307117)
        But then end up only hiring liars.
        • by Anonymous Coward on Monday November 03, 2014 @11:17PM (#48307191)

          All pack animals imitate their alphas. Our leaders are the best liars in the world. They lie as easily as they breathe. Every single one of them.

          This is the example we are given to follow, because this is what brings success.

          Honest workers are liabilities. They might out you just like Snowden did. Why in the world would you want people on your team who won't get on board with how you lie to your clients?

          The interviews are made impossible to screen out the honest ones, because deceit is the foundation of success in America.

    • by AK Marc ( 707885 ) on Monday November 03, 2014 @10:59PM (#48307111)
      You left out the people advertising "entry level" with 10+ years required. That's code for "we pay well under market", and are to be avoided.
    • Comment removed based on user account deletion
  • by Greyfox ( 87712 ) on Monday November 03, 2014 @10:21PM (#48306909) Homepage Journal
    Add to the mix a huge bunch of incredibly low quality recruiters who swarm any resume update on the job boards. These can be Indian recruiters trying to find a body to fill a position to outright scams trying to convince you to buy something up front for a job opportunity, or just criminals looking to steal your identity. On the employer side, so many candidates are playing buzzword bingo to try to get through HR that it's impossible to identify a qualified candidate by looking at anyone's resume. It's a huge waste of time for everyone.

    Basically the job boards are now so useless that your best bet is to start networking in-person with as many local companies as you can. I've already run across some companies that are starting to realize this and host technology meet-ups. While this isn't the best state of affairs, at the very least we might be able to start flushing out some useless HR staff that make it impossible to even interview remotely qualified employees. It'd be funny if this entire process goes full circle and we end up with job postings in classified sections of local papers. That would probably be better than what we have now.

    • by russotto ( 537200 ) on Monday November 03, 2014 @11:11PM (#48307167) Journal

      Basically the job boards are now so useless that your best bet is to start networking in-person with as many local companies as you can. I've already run across some companies that are starting to realize this and host technology meet-ups.

      So the people who get jobs are the people great at schmoozing? Somehow I don't think that's the way to get the best people either, unless you're looking for sales staff.

    • It'd be funny if this entire process goes full circle and we end up with job postings in classified sections of local papers.

      I do see postings every once in a while with a mailing address as the only point of contact.

  • I Suspect (Score:4, Insightful)

    by wisnoskij ( 1206448 ) on Monday November 03, 2014 @10:26PM (#48306947) Homepage
    That if companies paid candidates what the candidates though that they were worth, said companies would go bankrupt.
    • Job candidates get paid exactly what they are worth. (Possibly more.)

      The job candidate decides whether or not he/she will accept the position at the terms presented.

      Employment-at-will means you can leave at any time.
    • Agreed (Score:4, Insightful)

      by Anonymous Coward on Monday November 03, 2014 @10:47PM (#48307035)

      Senior software developer here.
      We get *lots* of applications from candidates who consider themselves to be senior-level, and have a good 10 years (give or take) of working experience to back that up.

      But once we ask them to solve novel problems, they fail. They go on and on about all these sophisticated technologies that they have worked with, and how they integrated them together. But all they can do is integrate other people's solutions together. They cannot cook up solutions of their own (not, at least, if the problem is any more complicated than a simple automation script).

      So, we avoid senior level candidates these days. Interviewing them isn't worth our investment of time. We would rather hire a junior level candidate that can actually solve novel problems, and train them up.

      • Re:Agreed (Score:4, Insightful)

        by AmiMoJo ( 196126 ) * on Tuesday November 04, 2014 @07:43AM (#48308605) Homepage Journal

        Another senior software developer here.

        The problem is your interview technique. You are looking for candidates who ware good at solving problems in interviews. Many of the best developers don't work like that - in fact I'd say it's almost guaranteed to find bad ones who come up with quick solutions that aren't necessarily the best ones.

        When I have a tricky problem I think about it first. Maybe do some research online, see what other people have done. I usually have a few ideas, but just hastily implementing one is a good way to end up with some nasty technical debt later.

        I don't know what industry you are in, maybe hacking stuff together is fine (web development maybe?) In my industry products have to run for 5+ years without intervention and without crashing or getting into a state where they drain their non-rechargable batteries prematurely. They do some pretty complex stuff as well. When interviewing we look at examples of the candidate's previous work, and ask them to discuss interesting aspects of it that show their understanding and problem solving abilities.

        • I agree, whilst a simple fizzbuzz program can weed out the truly incompetent or pure scammer, anything beyond that is just luck based on the developer or the interview. People think differently in interview situations anyway, so a test is usually a very poor means of determining their ability, especially with unfamiliar tools and environment.

          One place I interviewed for set me a test of doing some code review, they gave me a visual studio project and asked me what I thought of it - not only could I demonstra

        • Re:Agreed (Score:4, Insightful)

          by chrish ( 4714 ) on Tuesday November 04, 2014 @09:34AM (#48309411) Homepage

          I call this sort of interviewing "Tech Trivial Pursuit"; it's stupid, it won't give you any indication of how the person is going to work out in your team, and it doesn't give any indication of how someone produces a real solution to your actual problems.

          It just tells you how quickly someone can come up with a reasonable solution in an interview, and/or how quickly they can remember the solution to your problem that they read in one of the "How to Interview at Google" books.

          It's worse when the people interviewing you aren't from the team you'll be working in. I feel bad for those teams... they're going to get someone who's good at answering interview puzzle questions, but maybe they're entirely impossible to work with, or total assholes in day to day situations.

          Yeah, yeah, Google's very successful and rich. But it's not because of their broken interview process.

  • by Anonymous Coward

    There's plenty of crappy coders out there who think they're way better than they really are.

  • by bfwebster ( 90513 ) on Monday November 03, 2014 @10:34PM (#48306973) Homepage

    Eight years ago, Ruby Raley and I published (in Cutter IT Journal) an article entitled "The Longest Yard: Reorganizing IT for Success" (you can read it here [brucefwebster.com]). Our basic premise is that the current "industrial" model of IT hiring/management -- treating IT engineers like cogs or components -- is fundamentally flawed, and that a model based on professional sports teams would likely work much better. Having spent 20 years analyzing troubled or failed software projects, I believe we need a significantly different approach on hiring [brucefwebster.com] and retaining [brucefwebster.com] the right IT engineers. ..bruce..

    • Like hiring sports teams in what sense? Like the NFL draft? Big companies get to pick who they want from each year's graduating class, with little if any choice on the part of the new-minted engineers, and most of the graduates don't ever get to use their skills professionally?

      When we hire we look for specific skills that are relevant to our business. Maybe that's what you mean. We try to be careful about what's an absolute must (e.g. knows C++) and make the rest of the qualifications "preferred" or "des

      • by AK Marc ( 707885 )
        You don't hire based on the person's stats alone. You don't hire based solely on past performance. You need to hire based on fit and potential. The problem is that the hiring managers and HR can't gauge potential, so they look only at past performance as a gauge for future performance (despite all the disclaimers to the opposite for investments).
  • by SolarStorm ( 991940 ) on Monday November 03, 2014 @10:38PM (#48306991)
    If you are simply responding to job postings, you have to play the job posting game. The best jobs and hires I have done have come from a little bit of let work. Find out who the guy "really" doing the hiring is and get an email/phone call/coffee with that guy. 90% of the time, if he likes you, he will get you on the interview list.
  • by bigsexyjoe ( 581721 ) on Monday November 03, 2014 @10:51PM (#48307059)

    Well, you get a lot of applicants to any job these days. A lot of people are looking for work. But you need to find appropriate candidates.

    You can't hire anyone too young, because they don't have the skills and haven't proven themselves at a real job. You don't want to hire anyone over 35 because the field moves quickly and you don't want someone who doesn't keep up.

    You also need people who have the hot skill right now. Ruby used to be really hot, but now we are looking for Python. Can you train a Ruby programmer to be a Python programmer? When you are running a business you can't take the risk to find out!

    You're really looking for about five years experience and experience with the right technologies. This doesn't sound to hard, but a lot of these people are asking for outrageous amounts of money!

    Furthermore, you need the right cultural fit. At my company, we all wear hoodies. We wouldn't want to hire someone who wears a fleece. We need someone who breathes code. Last week I interviewed someone who was a good match, except he said he swam in code! We had to cut that interview short.

    Also, you can't hire people with too much self-esteem. People with self-esteem are always asking if they can be managers and constantly leaving you just because someone offered them more money. So in addition to the exact right amount of experience, in the right field, and cultural fit, you need someone who is a little bit broken that you can build up into your perfect coder.

    It is all very difficult. And we are a firm anyone would want to work for. We can only pay $50,000 a year, but you get to work with really cutting edge technologies like Python! So I'm sure if we have difficultly finding the right people, anyone would.

    • by wiredlogic ( 135348 ) on Monday November 03, 2014 @11:21PM (#48307211)

      Also, you can't hire people with too much self-esteem. People with self-esteem are always asking if they can be managers and constantly leaving you just because someone offered them more money.

      Not necessarily. A smart manager grooms his own replacement. If his superiors are confident someone can slip into his place, a promotion is more likely. I've had people ask about my management aspirations in an obvious tell that they are looking for that person.

  • by AchilleTalon ( 540925 ) on Monday November 03, 2014 @10:51PM (#48307063) Homepage

    "For example, some of the most successful companies find their talent through engagement with the technical community, participating in hackathons or offering seminars on hot topics such as Scala and Hadoop. These companies play a long game in order to lodge in the consciousness of the candidates they hope will apply next time they're ready to make a move."

    So, you are supposed to work during the day and participate in hackathons during the evening and week ends. These are looking for slaves. I can't believe this is the model someone consider as being successful. Why only in IT this kind of things happen? Do you ask a lawyer to do hackathons? Participate in contests for a slice of pizza and a flat beer? Do IT employees considered people with families, with kids, with a right to do something else not related to computers during the week ends, during the evening? This world is broken.

    As a IT prospect, do you respect yourself enough to refuse this kind of slavery?

    • BTW, if the company is looking for candidates offering seminars on hot topics and each company in the town is looking for candidates offering seminars on hot topics I believe this requires a shit-load of seminars on hot topics in the town to run weekly and given the number of seminars on hot topics in town, I guess no one is available to attend seminars on hot topics or willing to pay for seminars on hot topics because too many seminars on hot topics make hot topics cold. How many positions can you fill wit
  • by jonwil ( 467024 ) on Monday November 03, 2014 @10:58PM (#48307107)

    I am currently searching for a development job and everyone seems to want 3 years experience or 5 years experience. I am seeing "graduate" jobs asking for 2 years commercial experience.

    And its impossible to even get your foot in the door because of the "IT Recruitment Firm" who will reject any resume that doesn't match exactly what they are looking for.
    If I could just get to the point where someone would actually TALK to me and find out what I can do and just how good I am at writing code, I might have a chance...

    • by lordlod ( 458156 ) on Tuesday November 04, 2014 @01:34AM (#48307607)
      The catch here is that a degree is a very poor first step.

      If you have recently graduated think of the worst person you just went through university with. The one who plagerised all their assignments and never seemed to get caught, who struggles to understand the difference between a loop and an if block, the person you would fake a heart attack to avoid getting stuck with in a group project.

      This person has the same qualifications as you do.

      In fact, the person described probably has better qualifications on their CV because they are more happy to lie about them.

      You need to figure out how you differentiate yourself from them. As someone hiring that person is the absolute last thing I want to end up with and I will happily chuck 50 maybe CVs to avoid them.

      This differentiation is where things like prior work experience, open source contributions and memberships of local user groups plays a role.

      Btw, being in Aus have you signed up for linux.conf.au yet? lots of recruitment happens in forums like this.

  • by BUL2294 ( 1081735 ) on Monday November 03, 2014 @11:06PM (#48307149)
    So, as I've been in the market for a few months, I'm finding that many of the jobs that glossed over me a few months ago are coming across again... Whether it be a recruiter contacting me (I remember applying for this a while back), a new posting on the company's job search portal of choice (they changed 5 words in the job description), or even a new approach (look, now they're recruiting from my MBA school for this position)... Needless to say, it's infuriating.

    Sure, I recognize that I only have 85% of what you're looking for in terms of a skillset; or that you want to pay $5000/year less than my absolute salary floor... But if that job has been open for 3-6 months, the damage caused by it being open (presumably because someone left, and now there's a void that everyone else on the team is not really able to fill) has far exceeded whatever small training costs or whatever you would have to spend on me...

    Another issue is that too many companies are still thinking it's the financial crisis, when new recruits were happy to accept 50% cuts in salary to avoid foreclosure or vehicle repossession. This was best described to me by one recruiter--"three asses, one seat". While I've seen some absolutely batshit JDs (where 2 people in the country might have all of these skills), I recently saw one that pissed me off... A company wanted someone who was a SQL Server DBA/BI stack/TSQL & reporting guru, an Oracle DBA/PL-SQL programmer, and a Linux server manager in downtown Chicago--for $95k/year. Good luck finding such a person, with competing technologies, for less than double that...

    Another problem that I'm finding is that some jobs are sub-sub-contracted out. I recently saw one in Chicago that needed expert experience in Informatica MDM. Max pay was $46/hr W2. Turns out that MegaCorp contracted out to CompanyX who opened up to numerous companies, CompanyY contacted me with this max rate, asking me to be an employee of CompanyY. My convo w/recruiter: "So everybody has their hands in the cookie jar, and there's nothing left for the guy who's actually doing the work?--What do you mean?--Well, someone with that skillset should be in the $75-100/hr range, but since 2 levels above want to keep their 100% profit margin, $50 becomes $100 and $100 becomes $200, which MegaCorp is probably being billed somewhere around there..."

    Finally, don't get me started on "the foreigners"... It seems the boiler-room stock antics of the '80s and '90s have moved offshore, where in some cases I get calls from multiple people about the same job from the same company... They're all in a feeding frenzy, just trying to be the first to pass along my authorization to represent--never mind that I may not be qualified for the role in question. (One conversation went like this... "Well, where in Chicagoland is the job?--Let me submit you and I'll tell you.--You mean you won't tell me where the job is until I agree to let you represent me? It could be an impossible commute...--I need to submit you first...--Fuck off...")
    • by russotto ( 537200 ) on Monday November 03, 2014 @11:16PM (#48307189) Journal

      Sure, I recognize that I only have 85% of what you're looking for in terms of a skillset; or that you want to pay $5000/year less than my absolute salary floor... But if that job has been open for 3-6 months, the damage caused by it being open (presumably because someone left, and now there's a void that everyone else on the team is not really able to fill) has far exceeded whatever small training costs or whatever you would have to spend on me...

      These are not real positions. They are non-jobs. There's tons of them. Lots of reasons they exist -- recruiters fishing for resumes to put in their database, ad to satisfy some visa requirement by not finding anyone, internal corporate requirements, etc.

  • by DaveAtFraud ( 460127 ) on Monday November 03, 2014 @11:11PM (#48307169) Homepage Journal

    I'm getting three to five e-mails and or phone calls a day from headhunters. I'm very senior (30+ years in the business) so I'm not cheap. 2007 through 2010 I couldn't buy a job. What changed is the labor market. It just got a lot tighter. It may not be the dot com days when if you could say computer you got hired but it's looking a lot better.

    The last laugh is that a lot of hiring managers and HR dweebs haven't gotten the memo and are still pulling the same old bullshit. If you run into one of those, keep looking. There's someone out there who doesn't need a glass navel to see where they're going.

    Cheers,
    Dave

  • by Karmashock ( 2415832 ) on Monday November 03, 2014 @11:28PM (#48307237)

    Managers should be the ones hiring and firing people. HR's job should be managing employee paperwork. The actual task for hiring people should be done by the managers themselves.

    Will this mean that hiring practices become much more chaotic and lack uniformity? Yep. Guess what... when you get hired your managers are going to be different and the jobs you're getting hired for are going to be different. So why pretend that the hiring process has to be uniform when the work environments you're applying for are not uniform?

    Now some will argue "this will take time from the manager's other jobs etc"... well that means either you don't have enough managers or you're over complicating the process.

    Ultimately, the manager should get some face time with whomever is applying for the job. He/she should ask the new potential hire some questions to get to know them... and then go from there.

    I seriously don't understand why we even bother with HR in regards to hires? Anyone actually know?

    Give department heads budgets for their departments as well as responsibilities they must fulfill by given deadlines. If they're competent they'll work it out. If not then they won't. HR is not doing anything to make that process easier. If anything what they're doing is putting an artificial barrier between the manager and the potential employee. Possibly screening out people the manager might otherwise want to hire.

    And if these stupid job apps are just ruses so they can hire someone specific then why even go through that game? Just let the manager hire his friend or whatever. Cut to the chase please and stop polluting job listings with bullcrap jobs that aren't actually open.

  • by Kagato ( 116051 ) on Monday November 03, 2014 @11:28PM (#48307239)

    HR BS is one of the reasons I haven't dealt with FTE gigs in a decade. You can make more money in IT being a consulting and at most companies the consulting pimp deals directly with the IT manager. HR is rarely in the loop, often after the contracts have been signed.

    The shortage of workers is real but not for the reasons most people think. When I started working as a programer 15 years ago it was pretty common to see interns and college hires in development departments. Then starting in 2001-02 it plummeted. Some bean counter figured out they could hire H1B labor at about the same money as a college hire, why wouldn't you go with the "experienced" candidate. In the last decade i've only seen a handful of college hire programmers.

    Ah, but here's the rub, after spending nearly a decade not investing in the next generation of IT they are having a hard time finding resources. This fact did not go unnoticed to the H1B consulting companies. I've actually seen client's jaws drop when WiPro told them they were jumping their rates to well over $100/hr across the board.

    As a bright spot I've seen a nice uptick in college hiring at mid cap companies. A lot of them are on-shoring as well after getting burned.

  • by Cliff Stoll ( 242915 ) on Monday November 03, 2014 @11:36PM (#48307277) Homepage

    Can't resist tooting my own horn. These are from my Klein bottle website:

        TOPOLOGY CONSULTANT Part-time design of low-dimensional manifolds in glass, wool, plastic, titanium, niobium, pentium, and unobtanium. Ideal candidate is fresh out of college with 20 years experience in applied topology; and can solve Poincare's, Heawood's, and Hodge's conjectures. Pay & benefits are epsilon above unemployment. Compensation package includes trillions in worthless stock options.

        GLASSBLOWER Construct borosilicate manifolds using lampwork. Handy with glass lathe, oxy-hydrogen torch, and bandaids. Must know the usual cuss words to describe breaks & cracks. Experienced in minor burn treatment. Special bonus if you know the difference between inside and outside.

        MANIFOLD OPERATOR. Curvaceous, conformal Riemannian vector field desires normalized Ricci tensor with nice eigenvalues. Will relocate within proper metric space. No polymorphic permutations, please.

        From http://www.kleinbottle.com/job... [kleinbottle.com]

    • by wierd_w ( 1375923 ) on Tuesday November 04, 2014 @04:28AM (#48308139)

      [This is a joke answer, to a joke post. The only whooshing sound I hear, is the sound of this joke reply going over your head.]

      Greetings Mr Stoll,

      I would like to apply for position #2, GLASSBLOWER.

      I would like to point out however, that they oxy-hydrogen torch you specified may not be the appropriate tool for working with borosilicate glass, as it may not be able to achieve good melt or annealing temperatures with that formulation. A properly fitted acetylene torch with a hot-head and forced air would typically achieve greater temperatures, and is the more common-place appliance for use with this medium. Under very specific conditions I suppose an oxy-hydrogen torch may be suitable and even desirable, where an oxidizing flame would be appropriate, however the lower flame temperature, and invisible nature of the flame would make its use a difficult prospect. (Not to mention, lampwork tends to be small, ornate handwork details-- such as worked glass sculpture or beads-- not blown glass vessels. Those are typically done with a pot furnace and a glory hole.) I would also like to point out that any real shape can be defined as a manifold, which was one of the major points of the poincare conjecture, which was recently proven by a Russian mathematician who famously rejected the Fields Medal for his accomplishment, and told the press to stop calling him when they interrupted his mushroom hunting. I presume your company focuses mainly on non-orientable surfaces, such as klein bottles, (as per your name), moebius loops, and similar topologies-- however, this then makes your insistence upon knowing the difference between "inside and outside" a tricky matter-- the defining characteristic of an unorientable manifold is that there IS NO DIFFERENCE between the inside and the outside. To fill a klein bottle, one needs to submerge the vessel, then turn it end over end several times in the presence of a gravity well. After that, its unique shape will allow either gravity to retain the liquid, or atmospheric pressure will prevent the liquid from escaping through the narrow "neck". Again, there is no true inside nor true outside to this object, as per its geometrical definition. Any retention of liquid is merely an interesting and novel artifact of the interplay between the manifold, fluid viscosity and meniscus formation, and atmospheric pressure. (It is important to point out that superfluids such a s liquid helium will not be constrained by the a-fore mentioned technique.) I am familiar with this particular manifold, and could produce vessels of this configuration, should I be required to do so.

      I am reasonably well versed in minor burn care, having had to treat several such injuries over the years. Depending on the severity of the burn, topical application of a cool compress can be an effective remedy, followed by a topical ointment (Such as bacitrin or neosporin) and a bandage to discourage infection and topical agitation. For more severe burns, a more specialized ointment and more intensive care is required-- such as the use of something like silver sulfadiazine cream. This is applied topically to the burned area several times daily with the frequent changing of sterile gauze bandages, as this ointment can cause the burn to produce a clear liquid exudation during treatment. As far as I know, that specific preparation requires a prescription when intended for human use however. I do not advocate the use of veterinary grade pharmaceuticals in humans, no matter how fiscally attractive the option seems, and irrespective of the availability of such veterinary preparations.

      Typically, however, one should be wearing proper personal protective equipment, such as gloves, eyewear, and a fire resistant shop apron, which should minimize the risks of this happening. Appropriate foot protection is also a must; Full toe shoes, preferably with steel toe. I have appropriate foot and eye wear, but will need to obtain a suitable apron, and a sheer pair of aramid fiber gloves. I presume your company can either prov

  • by account_deleted ( 4530225 ) on Monday November 03, 2014 @11:53PM (#48307341)
    Comment removed based on user account deletion
  • by NotSoHeavyD3 ( 1400425 ) on Tuesday November 04, 2014 @12:32AM (#48307465) Journal
    Here's an analogy I use for the "IT shortage" and no it doesn't involve cars. Imagine if you will your friend comes over your house. He starts tell you how he was out in the sun all day and has never been so thirsty in his life. He tells you he feels light headed and thinks he's having heart palpitations from dehydration. Feeling concern for your friend you go to your fridge and get a nice cold glass of filtered tap water with ice and bring it to him.

    Your friend looks at this and then looks at you as though you had totally lost your mind. You ask "What's wrong?" He tells you, "Look when I said I was thirsty what I meant is I wanted a non-alcoholic raspberry lime rickey. Of course made with 7-up, not that cheap store brand stuff and of course freshly squeezed limes and definitely Zyrex syrup. What's wrong with you man?"

    Two things come to your mind. The first is your friend is kind of an asshole. The second is he isn't that thirsty and should shut the fuck up about how he thinks he's going to die from dehydration.

  • by Darlok ( 131116 ) on Tuesday November 04, 2014 @12:33AM (#48307467)

    There are two fundamental dichotomies that hide under this argument, and they've been going on for years, if not decades.

    First, there's the disconnect between large business and small business. Second, there's the disconnect between what people have previously been paid (or their peers have), and what they are actually worth. This is coming from a guy who has hired 5 software developers so far this year, and has 2 slots still available...

    A lot of developers are looking at what happens at Google and Microsoft (aside from the layoffs...), and try to use that as a standard when they apply for a position at a 50-person shop in the midwest. This creates an expectation disconnect where someone gets an offer for $65k, but won't take it because they've been convinced by the Internet, their Career Planning & Placement department, or the job postings on career boards, that their skills are worth $90k.

    This is an "expectation shortage", and results when there are not enough candidates willing to take the positions that ACTUALLY EXIST. It's all well and good to say that employers are under-paying developers, and looking for cheap labor. But the market does set rates, and the fact is that most software projects away from the coasts just don't support paying developers $120k/year - at least not sustainably.

    The second disconnect occurs when people misconstrue what it takes to be hired and promoted in the majority of companies, other than the mega-corporations who can have 200 people doing the same job. The sad fact is that you pretty much have to be a specialist to GET a job, and then you have to be a generalist to KEEP it. The specialists who stay in their pidgeon-hole are always the first against the wall when the next re-org comes. But the generalists who have 75% competency in an array of skill-sets rarely make the cut during interviews, but have enormous job security in their current positions -- though often feel themselves "stuck" in positions where they may not feel like they're advancing quickly enough.

    This is a failure of cultivation and and expectation problem on the part of employers. It creates a market distortion where people are encouraged to specialize, and then dumped back onto the market with inflated expectations of their overall worth when that very specialization becomes a liability. (Ruby, anyone...?)

    From the inside, I think it's undeniable that there is a shortage of quality, trained developers, with attitudes and ethics that will lead to long-term advancement and quality employment. That doesn't mean that there is a shortage of bodies with the raw skills necessary to do the job. But, in the end, that hardly matters... companies aren't hiring automata, even if some of them want to pay as though they were.

    There are ample failures on both sides of the equation, and large companies are exacerbating those problems with their treatment of many H-1Bs and "mass hiring" of fresh graduates (at insanely inflated salaries) who then get culled 9 months later.

    But candidates are also making the problem worse by viewing software development as a single, unified market, and clinging to the belief that just because Company X in Boston could afford to pay $x for a given product/project, that their skills are still worth $x when they move to Company Y in Pittsburgh, creating software for a completely different industry.

    The end result is a shortage of jobs that don't require specialists to get through the door, and a shortage of employees able to adjust their expectations to the realities of the market we are in. When you meet in the middle, it's a real shortage, regardless of how it came to pass.

    • by professionalfurryele ( 877225 ) on Tuesday November 04, 2014 @03:35AM (#48307969)

      "But the market does set rates" - You clearly don't understand how markets work. If you make an offering and no one takes it (assuming the reasons why aren't some substantial intervention in the market by some large actor), your offering is below market rate. That is pretty much the definition of what those words mean. Either you don't need the position filled (it will bring in $X dollars and cost $Y and X Y), or you need to pay more.

      If those software houses in Pittsburgh cant sell software for a profit offering developers market rate then the market doesn't need the software those software houses provide because it costs too much to make. Either company Y needs to (and can afford to) pay more, or it needs to shut up shop because it is not viable (or at least not do the project it cant afford to hire people for). The one thing it cannot do is complain that it has to compete with other companies both in selling it's goods and sources it's raw materials (which include human resources).

    • Comment removed based on user account deletion
    • Back when I was really, really at the top of my game, when I was really an experienced and skilled coder, I couldn't find squart, or was considered a hardcore unemployable for some unfathomable reason. You make a few valid points, but overall I have to disagree with the thrust of your thesis. Fundamentally, those doing the hiring are clueless, which is why so many frauds get hired, and the real programming talent is filtered out.

      Recently, the local news wondered if the Seattle area would have more tech
  • by havoc ( 22870 ) on Tuesday November 04, 2014 @01:07AM (#48307537)

    I'm a "former" developer and current IT hiring manager. I am trying to fill a couple of developer positions. I worked with HR to craft the job description that best described the job opening... Without any crazy years of experience requirements. It is a senior level position though. At any rate, we have received only two qualified candidates in two months. And we have received only four or five resumes so it's not as if we have been weeding out a ton of candidates before interviewing them. One received a promotion from their current employer before we could bring them back for a second interview, the other was asking for almost double what we could have offered plus wanted to telecommute from out of state half the week. We just are not seeing candidates. Where do developers go when they are looking for jobs? Job boards are expensive and we can't afford to hit every one of them.

    • by professionalfurryele ( 877225 ) on Tuesday November 04, 2014 @03:16AM (#48307897)

      You aren't paying enough. It is sort of obvious. Youe offering is below market so no one applies and those that do apply get promotions or can reasonably expect much better pay and conditions. Either you don't need the position filled, or you need to pay more to fill it.

      Can I ask, why is it when it comes to hiring technical staff business people have such a hard time understanding supply and demand. You never hear them saying 'Why cant I buy a top of the line server rack for $1?", but are shocked that no one applies for their job offered at half market rate.

    • Show us the description and the salary or GTFO

  • by ruir ( 2709173 ) on Tuesday November 04, 2014 @04:16AM (#48308103)
    After many years in the industry, and being in both sides of the fence, I think I already saw it all. From bitchy interviewers, to clueless ones, to the inexperience and naive, to the mechanical ones that are just there to make a tick on the requirements, to the bureaucratic ones...The most efficient HR process I have ever witnessed was Amazon, where the actual techies are interviewing, and they are typically nice too. The best interviewer I ever met, was only by skype and was like a friend when talking (no, no illusions there, but the guy was really good). The best ever single hire call I had was a brit guy that seemed to be on a rant after a couple of beers, but extremely nice and attentive. The more nice approach again by other brit. The worse interviews I had where collectively from Gibraltar, they seem to be lost, do not know what they want, their job descripts are totally mixed up, often they seem to want it all, a jack of all trades who knows nothing, and to top if off, they often offer less than you are earning. The worst interview of all was by a medical company, cynical HR corporate bimbo who asked me what I was doing there as I already had a nice job. On the other side of the fence, I met everything, specially when interviewing for entry level helpdesk people, from the naive guy that was the expert on the field because he installed linux at home, from the Indian with lots of credentials and certifications who could not answer the more basic questions, to the guy that came to the interview high on drugs, or the nice lady who did not know what she wanted to do for a living and was there just because the job was nice.
  • by Clent ( 717085 ) on Tuesday November 04, 2014 @11:59AM (#48310819)

    Awesome, the companies are learning to market themselves. How unhelpful.

    In any corporation, workers are just another capital expense. It is delusional to see yourself as any different to your employing corporation than the chair your ass is in. Both are seen as replaceable cogs, the corporate machinery will continue to chug along with or without you.

    As some point, software engineers will need to accept that this is a tradesmen profession and we are fools to ignore history.

    Every employer forces you to sign a contract upon hire.

    Until we have our own contract, we will always be on the losing side of negotiations. We need a guild, a union, whatever you want to call it. We need representation if we ever hope to be treated as the tradesmen we are.

  • by LessThanObvious ( 3671949 ) on Tuesday November 04, 2014 @05:27PM (#48313551)

    There is definitely a shortage of senior people who really have a clue. Everyone I know that I would ever recommend hiring, already has a job and they have jobs at "A" companies. The companies really having trouble getting "A" people are the "C" companies. Companies are going to have to stop writing off everyone that failed to get back on the horse immediately after the recession ended. Companies are going to have to give young people a chance to enter the industry and actually help them develop. When everyone outsourced every job they could to offshore vendors in 2003-2010, they killed the pool of candidates for the long term. Many of those workers who had a ton of experience left and never came back. Many of those young workers never got the chance to develop into senior workers. Companies now want nobody with less than 8-10 years experience yet there aren't enough "A" or even "B" players that entered the industry at that time. More H1-Bs is only a cop-out to bandage a systemic problem that business doesn't know how to hire, develop and retain people to maintain the pipeline.

Your own mileage may vary.

Working...