Slashdot Mirror


Hounded By Recruiters, Coders Put Themselves Up For Auction

An anonymous reader writes "When Pete London posted a resume on LinkedIn in December 2009, the JavaScript specialist stumbled into a trap of sorts. Shortly after creating a profile he received a message from a recruiter at Google. Just days later, another from Mozilla. Facebook reached out the next month and over the course of the next two years, nearly every big name in tech – attempt to lure him to a new employer. He received 530 messages in all, or one every 40 hours ... the only problem? Pete London didn't exist."

233 comments

  1. how many of the jobs didn't exist as well? by Joe_Dragon · · Score: 5, Insightful

    how many of the jobs didn't exist as well?

    or are 3-4 recruiters all going after the same job??

    1. Re:how many of the jobs didn't exist as well? by Iamthecheese · · Score: 4, Insightful

      Recruiters copypasta the same interview "offer" to their whole mailing list. After getting as many replies as possible they forward them to the the company. "look how many resumes I can give you!" In the end it's about the same odds as mailing your resume to arbitrary companies. I think it's deceptive and evil.

      --
      If video games influenced behavior the Pac Man generation would be eating pills and running away from their problems.
    2. Re:how many of the jobs didn't exist as well? by elliot.mackenzie · · Score: 3, Informative

      All recruiters say they don't don't do this, but they do. All of them. And they don't even bother to manage independent lists these days they just run groups on LinkedIn. I wouldn't mind so much if I had to pay a few hundred quid for the service, but if you do manage to find someone passable in the 642 CVs they send you, they'll charge you 10%-15% of their salaried rate for at least a year and often forever for contractors. I can search linkedin too, but it doesn't cost me $3000 a year when I find someone.

    3. Re:how many of the jobs didn't exist as well? by DavidClarkeHR · · Score: 2

      how many of the jobs didn't exist as well?

      or are 3-4 recruiters all going after the same job??

      It's a stereotype: Just like used-car salesmen, the majority of recruiters are helpful, knowledgeable and genuinely want to help.

      Even though most people in IT are friendly, knowledgeable, social and shower every day, there is a terrible, persistent stereotype that persists because everyone has a bad experience at one point with a used-car saleperson, recruiter or slovenly IT worker. The people who perpetuate those stereotypes are frequently bad at their job, to boot.

      --
      - Nec Impar Pluribus, or so I'm told.
    4. Re:how many of the jobs didn't exist as well? by Meski · · Score: 1

      How many of the job descriptions and requirements are wrong, for that particular job and salary?

    5. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      well, some don't. but they are guys working in the company giving out those jobs. you know, actual recruiters out of actual need and not just fisherman spammers.

      then there's the other sort who act as middlemen and happen to magically be notified when people are laid off at some other firm and are notified that some other company xyz needs someone with exactly his skillset(and these setup the laid off guy as contractor in the xyz, because the company xyz uses "recruiters" who can't recruit for shit but the company xyz can pay for contract work).

      anyways, anyone who wants a job at google/fb/wherever can apply for it themselves without middle men - but it's not like it's worth it without having inside contact nowadays.

    6. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      Sounds like real estate.

    7. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 1

      You pay 30k a year?

      No wonder you have to search hard.

      CAPTCHA: ripoff

    8. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 5, Informative

      Hey, Matt Mickiewicz here, co-founder of DeveloperAuction (which got mentioned in the Forbes article).

      I've been at the receiving end of this "recruitment spam" more times than I can count... staffing agencies haven't changed in 30 years... by having VC-funded start-ups put the offer before the interview we're trying to change the status quo. If you have 4 years at Google and a Stanford Computer Science Degree you shouldn't have to deal with a lowly recruitment sourcer who thinks "Rails" is a form of transportation :)

      First auction had $30m in job offers on 88 engineers, second auction generated $80m in job offers on 150 engineers. There's a huge need for something better in this space...

    9. Re:how many of the jobs didn't exist as well? by AK+Marc · · Score: 5, Informative

      My wife is a recruiter, and when I was in college, I took a job as a used car salesman. Both jobs are full of liars. I quit selling cars, as the management was ordering me to lie. Even if I could sell the car telling the truth, they'd rather I lie to do so. For recruiting, the game is about numbers. My wife is now an internal recruiter (hiring people for high-turnover customer service jobs), but her experience with recruitment companies is that they do more to get in the way than to fill positions, to make sure they get their pay. They don't just hand off three good leads, but they hand off one and only one lead and coach the lead to help them get the job, even if that coaching is to explicitly hide weaknesses that might affect performance.

      I would consider both professions almost 100% filled with liars. The stereotype got there because it's true.

    10. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      If $3000 is 10-15% of what you're paying, you can go fuck yourself

    11. Re:how many of the jobs didn't exist as well? by AK+Marc · · Score: 4, Interesting

      No, I run across recruiting companies that get "exclusive" contracts with companies, then try to get jobs for their favorites. One of the larger recruiting companies in this area splits up their areas and the recruiter for my area got mad at me for passing up a poor fit, and wouldn't submit me to any other jobs, and many that sue recruiters use them because they don't have their own internal recruiters, so there is no way to apply without going through a recruiter. I've been blocked from applying more by recruiters than submitted to a job by a recruiter. And when I finally did find what I was looking for, it was direct, and I didn't deal with a recruiter, even though I did see the same job listed with recruiters, I'd already seen it direct.

      They'll deliberately lie in the advertisement to hide who it's for as much as possible and make it so that if you were reading their ad and one for the same job from a competing recruitment firm, you wouldn't know it was the same job, so they can waste as much time of yours as possible to prevent you from applying any other way, even if they end up not submitting your application.

    12. Re:how many of the jobs didn't exist as well? by pavera · · Score: 5, Interesting

      So, these companies are really bidding an average of $350-$500k/yr for developers in these auctions?

      And isn't your "4 years at google and a *Standford* CS degree" just the same arbitrary requirement as a recruiter that thinks "rails" is a form of transportation?

      I have 15 years of software development experience, have run 2 startups (one as CEO, one as CTO), and been a team lead or senior engineer on multiple projects at both startups and established companies. I have extensive experience with C, C++, Java, Python, PHP, Perl, Javascript, SQL, and lots more... And, I'd be just as excluded by you because my CS degree is from the University of Utah, and I haven't worked at Google as I would be by the recruiter who's never written a line of code and doesn't know that someone with my background can learn Ruby and be proficient in a week or 2 at most.

      I also went to sign up on DeveloperAuction, and was disappointed that you give so much weight/prominence to github projects. I have many side projects, but not of the public nature, and I chose not to pay someone to host my source code privately when I can do that just fine myself thank you. (What self respecting software developer doesn't have 4-5 servers in their basement to host/play with personal projects?)

    13. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      Unless working for a marketing company is your thing, google/fb aren't worth it even with an inside contact.

    14. Re:how many of the jobs didn't exist as well? by NotSanguine · · Score: 5, Informative

      It's a stereotype: Just like used-car salesmen, the majority of recruiters are helpful, knowledgeable and genuinely want to help..

      I'll agree with the helpful part. Of course they want to help. That's how they make their living. As for knowledgeable? Not so much. In my 20+ year IT career, I've met exactly two (out of dozens) recruiters who actually had some sort of clue beyond keyword recognition. Many of the interviews arranged for me by recruiters were a complete waste of everyone's time since they didn't understand the job spec or my resume.

      But that's not the real problem. The real problem is the *lying*. I've caught recruiters lying *to* me and I've caught recruiters lying *about* me.

      On the whole, recruiters make things *more* difficult for those seeking jobs and waste an enormous amount of hiring managers' time. I suppose it's possible that I was just unlucky that the dozens of recruiters I've dealt with are the "bad apples," but that's not so likely.

      --
      No, no, you're not thinking; you're just being logical. --Niels Bohr
    15. Re:how many of the jobs didn't exist as well? by AK+Marc · · Score: 2

      Given that I'm a married man of less-than-average girth who was introduced to /. by another married skinny guy, and none of the rest apply to either of us, I'd have to say that the stereotype is incorrect, provably so, from my perspective.

    16. Re:how many of the jobs didn't exist as well? by aXis100 · · Score: 4, Funny

      It's clearly not true. Some of us are android-fanbois.

    17. Re:how many of the jobs didn't exist as well? by czth · · Score: 2

      So, these companies are really bidding an average of $350-$500k/yr for developers in these auctions?

      You're not understanding that there might be multiple job offers per person. This makes the numbers almost, but not quite, meaningless.

      What I'd like to see to start is # of offers per person and (can be calculated from that) average amount per offer, and then perhaps some breakdown and analysis to determine what resume items increase offer count and offer amount. To gain credibility they should tell the number of offers, but I wouldn't expect them to give the latter details up; that data and what they learn from mining it is can be a competitive advantage for DeveloperAuction. But they could reveal enough of what they learn to be interesting and show they have a good caliber of developers/employers without giving away the farm. For example: most popular technologies, or how years of experience or age correlates with offers.

      I also went to sign up on DeveloperAuction, and was disappointed that you give so much weight/prominence to github projects. I have many side projects, but not of the public nature, and I chose not to pay someone to host my source code privately when I can do that just fine myself thank you. (What self respecting software developer doesn't have 4-5 servers in their basement to host/play with personal projects?)

      Hear, hear. Of the several open source projects I've contributed to, only one is on GitHub; and I keep my personal projects on a local subversion server (moving to git for newer stuff and I expect I'll transition the svn all to git soon).

    18. Re:how many of the jobs didn't exist as well? by AvitarX · · Score: 1

      Sounds more likely it was for a lifetime of servitude.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    19. Re:how many of the jobs didn't exist as well? by KingMotley · · Score: 1

      Obviously, there is more than 1 offer per engineer per auction. Wasn't that hard to figure out.

    20. Re:how many of the jobs didn't exist as well? by KingMotley · · Score: 0

      ...

      If you can't figure out how "First auction had $30m in job offers on 88 engineers, second auction generated $80m in job offers on 150 engineers. There's a huge need for something better in this space..." is not the same as "So, these companies are really bidding an average of $350-$500k/yr for developers in these auctions?", perhaps then he should exclude you.

      "First auction had $30m in job offers on 88 engineers" does not mean there were 88 job offers. You fail at simplistic algebra and/or reading English and/or converting English to algebra.

      Just sayin...

    21. Re:how many of the jobs didn't exist as well? by tompaulco · · Score: 2

      It's a stereotype: Just like used-car salesmen, the majority of recruiters are helpful, knowledgeable and genuinely want to help.
      You're right. 99% of recruiters give the other 1% a bad name.
      I have known a couple of recruiters that were genuinely clueful and did try to put the right people with the right skills into the right positions. However, a large number of recruiters I have worked with were not knowledgeable at all about skillsets or about the marketability of certain skillsets.They genuinely tried to help, but there was simply no way that they were going to be able to help without knowing something about the skills I had. That probably represented about 30% of the recruiters I have dealt with. The other 69+% of recruiters were Indian shell companies searching for cheap H1B labor to place and wouldn't submit an American for an open contract if you held a gun to their head. The first clue to these scams is when they ask about your H1b status. They don't even pretend to be legitimate by putting "I am a citizen" as a valid response on their contact sheet.

      --
      If you are not allowed to question your government then the government has answered your question.
    22. Re:how many of the jobs didn't exist as well? by tompaulco · · Score: 2

      Huh, I always thought the apple fanboi stereotype was a skinny, vegan, prius driver.

      --
      If you are not allowed to question your government then the government has answered your question.
    23. Re:how many of the jobs didn't exist as well? by Zontar+The+Mindless · · Score: 1

      What about the relatively skinny, opinionated, fairly well informed, linux-fanboi, somewhat social slashdot reader stereotype who lives in an apartment that's above ground and sleeps with a real live woman who's not his mother (and not yours, either)?

      --
      Il n'y a pas de Planet B.
    24. Re:how many of the jobs didn't exist as well? by pavera · · Score: 4, Insightful

      sure, I didn't completely understand/put together the multiple offers/engineer thing... as a previous poster pointed out. But as the previous reply stated, that basically makes the numbers meaningless so why share them at all except to brag... In that case its just a case of statistics (of the lies/damn lies variety)... They picked the biggest number they had (total value of all offers, regardless of whether all offers could be accepted) and put it next to the smallest number they had (number of engineers) to get an "ooh wow" effect.

      It has nothing to do with their potential revenues as that is based on accepted offers, hence my assumption of 1 per person. It is then impossible to infer anything about how many offers each engineer got, or how much the individual offers were for (although, on average each engineer did get offers worth 350-500k/yr... just might have been spread over multiple offers). Each engineer could have received an average of 5 offers of $68k/yr each and that would hardly lead to any of the conclusions of the original article... IE that there is a labor shortage, or that companies are having a hard time finding people willing to work (or even that "there's a huge need for something better in this space").... But again you can't tell anything from these numbers without the total number of offers, or the average number of offers per engineer....

      My mistake was assuming that the numbers had some meaning... Unfortunately they don't. No reason to get all uppity though, sure I made a mistake. I can own that :)

    25. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 3, Interesting

      I stopped working with recruiters entirely. They are useless middlemen, and I'm not shy about telling them so.

      Any company that hires exclusively through recruiters is likely to be dysfunctional anyway. Stop wasting your time and only speak to people who work for the company with the job opening.

    26. Re:how many of the jobs didn't exist as well? by KingMotley · · Score: 1

      Yes, the numbers given really are pretty pointless if you wanted to figure out what the average offer was, or offer range, or anything else fairly useful. He didn't supply nearly enough information to do that.

      It could have been ~450k companies all bidding $1 on the same 88 engineers. Or 1 company that bid $2,999,912 on a single engineer, and $1 on 87 others. Or a bunch of different scenarios. The numbers really are only vaguely important to him because the assumption is that he's going to collect some number that is less than 15% of that $30m for the first week. Grats to you Matt on coming up with what appears to be a relatively new idea, and hope it pays off well for you and your team.

    27. Re:how many of the jobs didn't exist as well? by KingMotley · · Score: 1

      Heh, and typing fail, I dropped a digit. Oh well. What's 27m between friends.

    28. Re:how many of the jobs didn't exist as well? by metlin · · Score: 1

      Given that I can squat and bench almost 1.5x my body weight and rock climb, row, and run long distance regularly, I will have to say that's false as well. The last time I checked using bodpod, I had about 14.33% body fat (no six pack though, only the beginnings of a four pack -- I think I will need to go down much lower for that).

      Never been anti-social in my life, either. If anything, I am as extroverted as they come (and it's a pre-req for what I do for living). Never had trouble picking up a girl at a bar, either.

      I am, however, certainly opinionated Mac using Slashdot reader. :-)

    29. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      You are thinking Sinofski ;-P

    30. Re:how many of the jobs didn't exist as well? by arose · · Score: 2

      That's private sector efficency for you.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    31. Re:how many of the jobs didn't exist as well? by Areyoukiddingme · · Score: 1

      And some of us don't own a tracking device that can make phone calls you insensitive clod.

    32. Re:how many of the jobs didn't exist as well? by psergiu · · Score: 1

      30k USD a year ?
      That is a nice sallary for Eastern Europe.
      That is a HUGE sallary for India or China.

      --
      1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
    33. Re:how many of the jobs didn't exist as well? by Kreigaffe · · Score: 1

      Well of course you don't sleep with your mother. There's only room in my bed for 2.

      OH ZING! some things, must be said.

      --
      ... still waiting for this free-as-in-beer free beer I keep hearing about. :|
    34. Re:how many of the jobs didn't exist as well? by GNious · · Score: 1

      Was under the impression that pay in Romania is lower than in China (at least for lowest-rung factory employees)

    35. Re:how many of the jobs didn't exist as well? by 1s44c · · Score: 2

      I stopped working with recruiters entirely. They are useless middlemen, and I'm not shy about telling them so.

      Any company that hires exclusively through recruiters is likely to be dysfunctional anyway. Stop wasting your time and only speak to people who work for the company with the job opening.

      I agree although I can't afford to take the risk that recruiters have a job that I can't find myself. Dysfunctional companies pay the bills too.

      All the good companies I've worked for don't use recruiters exclusively or in a few cases don't use them at all.

    36. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      That was my experience back then. I'd get a phone call from one recruiter for a position, then another three or four would call in the following two days for the exact same position. Same with the online regional job adverts. A regional website with "over 500 jobs" would replicate the same position 5 to 10 times, which left only 30. Out of those 30, 28 of them would have expired or filled. So there were only two new jobs each day.

      Then there were a few recruiters who would seem to play dirty tricks by calling me up and just waffle for ten to thirty minutes about how wonderful a certain position was. Invariably, there was another recruiter who at the same time was desperately trying to call me because a client wanted to give me a telephone interview.

    37. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      And isn't your "4 years at google and a *Standford* CS degree" just the same arbitrary requirement as a recruiter that thinks "rails" is a form of transportation?

      He was just giving an example of someone who has an obviously solid pedigree. Don't be such a dick.

      I have 15 years of software development experience

      Me too. I wrote a program in BASIC back in Jr. High, tinkered with various scripting languages, wrote a few "hello world" applications. That's still enough to legally say I have "15 years" of "experience".

      nd, I'd be just as excluded by you because my CS degree is from the University of Utah

      It was an inclusive statement, not an exclusive one. At the risk of infuriating the "No True Scotsman" Gods, I propose that no True Software Developer should have any problem understanding that.

      and doesn't know that someone with my background can learn Ruby and be proficient in a week or 2 at mos

      And yet you fail to consider that the employer might want to hire someone who doesn't need to waste 2 weeks of payroll just to become "proficient".

    38. Re:how many of the jobs didn't exist as well? by Karlt1 · · Score: 1

      I've worked with plenty of recruiters and I can say that I have never had a bad experience. I prefer working through them. They have all asked what type of job I was looking for, have prepped me for the interview and didn't submit my resume for jobs that we agreed was not a good fit for. I have never gotten an interview through a recruiter where I didn't get an offer from the company.

      The last time I worked with recruiters, I had two job offers within four days of the time I started looking.

    39. Re:how many of the jobs didn't exist as well? by AmiMoJo · · Score: 1

      Actually mailing your resume to random companies is a better approach. If it looks interesting they will probably file it, and then when a job does come up rather than spending money on recruitment they will just open their resume folder. I got my first job that way.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    40. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      I think you'd be lucky to find a recruiter that took as little as 15% (forever) for a contractor. It's more like 20-30% or more if they can get away with it. I heard of one guy who found out that his recruitment agency was taking 40%. This is why the contracts often include a clause stating that the contractor must not discuss his pay with the client (or they'll both realise they're being ripped-off by the recruiters who do almost nothing at all once the paperwork is signed).

    41. Re:how many of the jobs didn't exist as well? by erp_consultant · · Score: 2

      Not so sure about the user car salesman part but for recruiters, yeah, I'd tend to agree there. I get contacted by recruiters a lot and most of them are FOS in my experience. They will build up whatever company they represent and tell you whatever you want to hear. If that involves throwing in a few outright lies, so be it. Their goal is to get bodies in the door. Your job satisfaction is not their concern.

      They are salespeople, plain and simple. Part of the problem is the compensation model. They are not paid based on retention they are paid based on how many positions they fill. In some respects it is in their favor to have high turnover...that way they can make more commissions by filling more seats. It is not in their interest to attract quality candidates but simply to attract candidates of any kind.

      These days when I speak to a recruiter my standard position is that everything they tell me is a lie until I can verify it independently.

    42. Re:how many of the jobs didn't exist as well? by erp_consultant · · Score: 1

      "The other 69+% of recruiters were Indian shell companies searching for cheap H1B labor to place and wouldn't submit an American for an open contract if you held a gun to their head" - It's gotten to the point now that I won't even speak to a recruiter with a thick Indian accent. What many of them do is sub to a sub to a sub. It's like the Nested Russian Doll model. Each of them take $1 an hour or so. Vultures.

    43. Re:how many of the jobs didn't exist as well? by crazyjj · · Score: 1

      how many of the jobs didn't exist as well?

      Thank you! My experience with recruiters has been that the majority of the "jobs" they pitch are as fictional as Alice in Wonderland. Usually they're just fishing. When you press them for specifics, they disappear. I suspect the majority are way more interested in some sort of information they can sell than helping anyone get an actual job. That's why I laugh every time I hear some green programming or CS grad bragging about all the recruiters contacting them. The fact that they think that means they're going to waltz into a six-figure job, fresh off the boat, cracks me up.

      "A Google recruiter contacted me" usually translates in reality to "Someone CLAIMING to be a Google recruiter contacted me," which soon turns into "He asked me a lot of questions, and then never called me back."

      --
      What political party do you join when you don't like Bible-thumpers *or* hippies?
    44. Re:how many of the jobs didn't exist as well? by Anonymous Coward · · Score: 0

      Your website fails. Profile doesn't save start / end dates for each position.

    45. Re:how many of the jobs didn't exist as well? by mdf356 · · Score: 1

      And isn't your "4 years at google and a *Standford* CS degree" just the same arbitrary requirement as a recruiter that thinks "rails" is a form of transportation?

      He was just giving an example of someone who has an obviously solid pedigree.

      It's not obviously solid. I was a TA at Cornell for a few years. Some of the people who graduated were smart. Some weren't. I assume the same is true of people working at Google; after 4 years some will be getting promotions and responsibility, and some will be looking for an exit since they aren't getting promoted.

      I'd interview the above theoretical candidate exactly the same as I would someone with a degree from University of Utah and no company I'd ever heard of on their resume. Because both smart and dumb people can be found everywhere.

      --
      Terrorist, bomb, al Qaeda, nuclear, yellowcake, kill, assassinate. Carnivore is dead... long live Echelon.
    46. Re:how many of the jobs didn't exist as well? by Draknor · · Score: 1

      It's not about "solid" vs "not solid", it's about probability.

      Someone who has a Stanford CS degree & worked for 4 years at Google has a higher probability of being a good candidate than someone with an IT degree from the University of Phoenix and no GitHub account.

      Is it certain? No.
      Is it more probable? Definitely.

      It's like fishing -- big, prize fish CAN be anywhere in the lake (or river), but there are certain underwater features they prefer. Go where those features are, and you have a higher probability of finding a big fish. If I want a big fish for a reasonable expenditure of time & effort, I'm going to go where my odds are the greatest. And maybe I don't catch the BIGGEST fish, but as long as it's big enough for my needs - it gets the job done.

  2. Guy who was indicted for false interviews? by Anonymous Coward · · Score: 1

    Wasn't there some guy who went on interviews for high paying jobs, the type where you got flown in, put up and even given money? He would intentionally throw the interview at some point, ensuring he didn't get the job he wasn't qualified for yet enjoying a free vacation. Somehow he got found out and was convicted for fraud. Anyone know this story?

    1. Re:Guy who was indicted for false interviews? by Anonymous Coward · · Score: 0

      When living in the U.S., I went to two different interviews over a period of three months at a company in Germany. Was flown over business class (this was in the early '90's) and put up in a nice hotel. The first time I was really serious about working for the company, but it didn't work out. The second time I had no intention of working for the company, but wanted to enjoy the experience again. They offered me the job the second time, but I turned it down. The interviewing manager was pissed at me...

    2. Re:Guy who was indicted for false interviews? by Anonymous Coward · · Score: 1

      If he lied on the CV he sent in about his experience/qualifications? Quite possibly.

      If he sent in a totally genuine CV but was just in it for the free holiday? Can't see how that's fraud.

    3. Re:Guy who was indicted for false interviews? by Anonymous Coward · · Score: 1

      Why throw the interview? You can always reject their offer.

    4. Re:Guy who was indicted for false interviews? by Anonymous Coward · · Score: 1, Funny

      Personally, I ask the interviewer(s) if s/he will suck my cock. Worst case: I don't get the job (free vacation!). Best case: I get the (blow)job (free sex vacation!)

    5. Re:Guy who was indicted for false interviews? by Zontar+The+Mindless · · Score: 1

      Sounds like the thing to do if your notion of a "vacation" includes "being on the receiving end of a multi-million $$ lawsuit and possible criminal charges".

      --
      Il n'y a pas de Planet B.
    6. Re:Guy who was indicted for false interviews? by Anonymous Coward · · Score: 1

      Wow, Julian Assange reads Slashdot! Who knew...?

  3. seriously? not this again by CAIMLAS · · Score: 4, Insightful

    Not this shit again. "We can't find talent!"

    Quite obviously employers have a very different definition of talent than people who actually have said talent and capabilities. It's either that or we are in an all-out war with employers at this point over wages and foreign worker importation/outsourcing - take your pick.

    This seems to me to be yet another ploy to push for more H1B workers and to justify outsourcing. There's no two ways about it.

    "Not enough qualified applicants" my ass. I happen to be aware of quite a few competent people who are out there looking for positions in "in-demand" fields. Guess what? They're getting stonewalled.

    (Sorry, you're going to be hiring 5 green programmers for every 2 experienced, and 5 experienced for every expert - that's just the way it is. You can't only staff experts unless you're willing to pay expert rates. It's not good for anyone.)

    If, in fact, they really think there is a lack of qualified people, here's their problem: there has been a breakdown of communication, and their formalized hiring processes, excessive HR, and outsourced employee sourcing (you know, headhunters) are at the root of the problem. Finding (and keeping) good employees is the single most important part of maintaining and growing a business. Why would you push that responsibility to someone else? What ends up happening is that headhunters (of all kinds) do end up finding qualified applicants who are looking for work - we just write them off as spam, telemarketers, or insincere requests without so much as a second notice because of how unprofessionally we're addressed. (Hint: having an Indian "initial contact" team for your HR is not a good idea; neither is using an automated system for requesting potentially qualified applicants to submit a resume via eg. LinkedIn - you're only going to get desperate people, not those who are capable.)

    The culpability for this problem sits squarely on the employer.

    --
    ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    1. Re:seriously? not this again by Anonymous Coward · · Score: 2, Interesting

      "Not enough qualified applicants" my ass.

      Too many qualified applicants, but not enough talented candidates. That is the real problem.

      Anyone who has worked in Software can tell you that, the top 5% of engineers are often many times (3x-10x) as productive as the bottom 50%. There is no shortage of Qualified Candidates (people who have experience in the job), only a shortage of the top 5% of engineers (people who would do well in ANY software job). When employers say talented this is what they mean. Unfortunately most people identify themselves in the top 5% and don't realize they aren't.

      My basic problem is I work in one of the least attractive positions at a very attractive company. The only way I get top 5% talent is through risk management of college recruits who I think will work out to be the new top 5%.

    2. Re:seriously? not this again by A+bsd+fool · · Score: 2, Interesting

      You've taken a rather myopic view of the situation, wouldn't you say? There's plenty of blame to go around, and at the end of the day, it all comes down to two simple factors: capitalism at work, and the fact that there are no perfectly rational actors on either side.

      Lets look at some of what you've put forward from an employers perspective.

      1. You can't staff experts unless you're willing to pay expert rates.

      Oh yes you can, in an economy like this one, unemployment what it is. You're selling your labor, and it's a buyers market.

      2. Finding (and keeping) good employees is the single most important part of maintaining and growing a business

      Wrong. This is something that the labor force at large would really like to be true, and it's as big a fallacy as the "They don't dare fire me, I'm an irreplaceable cog / this place would fall apart without me" attitude. Minimizing employee turnover enhances efficiency and profit margin, but it's not the "single most important" factor by a long shot. The single most important factor is that you can convince your market that they need or want your product or service. Just as important is that you can provide that product or service at a price they're willing to pay for it without taking a loss. Everything else is tertiary and simply a matter of efficiency and margins.

      3. you're only going to get desperate people, not those who are capable

      See point 1. In this economy there are plenty of people who are BOTH desperate and capable. The two states are not mutually exclusive. There is a simple three dimensional map you can mentally construct here. On the X axis, plot how your skills match up with the position. On the Y axis, your income if you take the job. On the Z axis, how much effort you're willing to put forward to get the job..

      You must come to an agreement with the company in terms of the X and Y, but the Z is entirely up to you. Not responding to recruiters because they are emailing you blindly from a outsourced Indian firm is entirely a Z axis phenomenon. I won't make a value judgement on the wisdom of making that choice, because it's personal, and depends heavily on your current position on the Y axis -- if you're out of work and might end up homeless soon, it's a stupid idea. If you're comfortably employed and the Y axis bump wouldn't be much, then telling them to get stuffed (as I, too, often do) is not an irresponsible move on your part.

      This is all partly practical, and partly playing devils advocate to someone who seems a bit heavy on the sanctimonious side. If the competent people you know are getting "stonewalled" there are simple reasons why, and almost all of them boil down to one thing: disagreements about this persons value to the company. Maybe the person is overvaluing their own skills or capabilities, or maybe they aren't doing a good job of demonstrating them to the employer. The only alternative is that the company doesn't need to hire someone right now, and are just testing the waters to see what kind of candidates are available. Several years ago I went on an interview and was told point blank about an hour in that they weren't *actually* looking to hire for another 6 months to a year. I was furious with them for wasting my time, but kept my temper in check and departed without burning any bridges. This has only happened to me once though, in almost 20 years in the field.

    3. Re:seriously? not this again by pete6677 · · Score: 5, Insightful

      Also, if your company wants to hire "top 5% talent" then you need to be a top 5% employer. Top talent does not want to piss away their career in the IT department of Bank of America, for instance. If you're trying to hire top talent but are an average company, then you are the equivalent of an old fat bald dude trying to date young supermodels. It ONLY works if there's a lot of money involved.

    4. Re:seriously? not this again by AK+Marc · · Score: 4, Insightful

      There's always the silent "for the price we want" at the end of the "we can't find talent" statement.

    5. Re:seriously? not this again by sribe · · Score: 1

      ...here's their problem: there has been a breakdown of communication, and their formalized hiring processes, excessive HR, and outsourced employee sourcing (you know, headhunters) are at the root of the problem.

      Yes, exactly!

    6. Re:seriously? not this again by sribe · · Score: 2

      Just as important is that you can provide that product or service at a price they're willing to pay for it without taking a loss.

      The ability to do that depends directly on the employees you hire.

    7. Re:seriously? not this again by pavera · · Score: 3, Insightful

      I agree with your premise there are lots of "developers" who have worked on a project that used technology X... And realistically only a couple members of any team are producing 70-80% of the code, but the recruiting agencies and HR depts are a huge part of the problem. I am (no really) in that 5%, but I have the hardest time finding jobs, because I've worked all over the map... From designing huge networks, to automating deployment of tens of thousands of network devices, to DB design/DBA type work, to software design, development, etc both web and client based. HR departments are so keyword driven, they don't know what to do with my resume. I'm repeatedly told by recruiters "Well, this company only wants java experience, so you're out because you have other experience on your resume". Or: "Your C++ experience isn't recent enough"... Sure it was 2 years ago, I'm sure the fact that I've been integrating a large C codebase with python to make it scriptable for the last 2 years I've forgotten all my C++... (And oh no that reminds me... its now been 4 years since I used java professionally.. I'll probably never get another java job again... or is that a good thing?)

      I regularly teach myself new tech, and really enjoy working in the field, but the miscommunication between development and hiring managers/outside recruiters is very painful to deal with. I shouldn't have to explain to someone who's never written a line of code that there is very little difference between all these languages, and that I know I would be productive on a project written in C, C++, Java, C#, Python, PHP, Perl, Ruby, Javascript, or SQL within 2-3 days at most. Hell, I was one of the most productive Foxpro programmers at one job I had (no I don't list foxpro on my resume) and I don't even know the language, but I could sit down in code review with the foxpro developers and find/fix bugs all over the place.

      On a different note
      Why is the position so "unattractive"? Because you're only offering $50k/yr for 6 days a week plus a rotating 24 hr on call day? Where's it located? is it strictly an entry level position?

    8. Re:seriously? not this again by Anonymous Coward · · Score: 0

      Finding (and keeping) good employees is the single most important part of maintaining and growing a business.

      Bullshit - it is profit - so for most businesses cheaper very often better.

    9. Re:seriously? not this again by Anonymous Coward · · Score: 0

      What they mean is qualified and will work for shit wages crap benefits no pensions etc..
      Our perspective employees are all hip to our shit and cant be bamboozled any more.

    10. Re:seriously? not this again by alexmin · · Score: 1

      "you're going to be hiring 5 green programmers for every 2 experienced, and 5 experienced for every expert" - but what to do if you are a small shop and only hire a guy every couple years? For every 10K strong multinational there are 1000s of those small shops.

    11. Re:seriously? not this again by aztracker1 · · Score: 1

      If they're in the Phoenix area and looking for developer work, let me know... The market is pretty tight here in terms of availability.

      --
      Michael J. Ryan - tracker1.info
    12. Re:seriously? not this again by aztracker1 · · Score: 2

      It doesn't matter if there is 20% general unemployment, if the field you are in is under 2%, then the market is not a buyers market for jobs in your field. That's how it is for software development in a lot of cities right now.

      --
      Michael J. Ryan - tracker1.info
    13. Re:seriously? not this again by Anonymous Coward · · Score: 0

      Show me one half way competent Ruby developer who can't find work? Unless they are utterly insane (or have some other "challenge" to being hired) they have a great job. Unemployment isn't high among developers of any kind right now, but I only know from personal experience for Ruby. I'm okay, probably around the 50th percentile in quality and I landed my first job for a great company without even trying (was self employed with practically nothing to show for it before interviewing for this job). And we'd love to find even a couple more like me although I'd prefer more experienced developers myself). And this isn't a problem due to not being will to lok outside the US, we'd be more than happy to find developers anywhere in the world.

    14. Re:seriously? not this again by turbidostato · · Score: 2

      "1. You can't staff experts unless you're willing to pay expert rates.
        Oh yes you can, in an economy like this one, unemployment what it is. You're selling your labor, and it's a buyers market."

      You should review your statistics 101. Unemployment may be what it is but it is far from 95% in any IT/IS field, so if you really want/need the top 5%, it's difficult you will find them unemployed. On a side note, if it's about just mere "experts", not necessarily top notch, well, it could be true that it's easier to find them at lower wages than in better times, but that doesn't mean you won't need to pay "expert rate" for experts, just that "expert rate" will be lower (but still higher than "entry level rate").

      "Just as important is that you can provide that product or service at a price they're willing to pay for it without taking a loss. Everything else is tertiary and simply a matter of efficiency and margins."

      And you should review your economics 101 too. Being able to sell at a profit instead of at a loss is "simply a matter of efficiency and margins" too.

    15. Re:seriously? not this again by __aaltlg1547 · · Score: 4, Interesting

      "Not enough qualified applicants" my ass.

      Too many qualified applicants, but not enough talented candidates. That is the real problem.

      Anyone who has worked in Software can tell you that, the top 5% of engineers are often many times (3x-10x) as productive as the bottom 50%. There is no shortage of Qualified Candidates (people who have experience in the job), only a shortage of the top 5% of engineers (people who would do well in ANY software job). When employers say talented this is what they mean. Unfortunately most people identify themselves in the top 5% and don't realize they aren't.

      My basic problem is I work in one of the least attractive positions at a very attractive company. The only way I get top 5% talent is through risk management of college recruits who I think will work out to be the new top 5%.

      I don't really agree with your 5% / 50% breakdown, but we could quibble all day on where to draw the line between talented and ordinary workers. (The world is not JUST programmers.) The point I want to make is that if you're hiring, you can try all you want to get the best candidates to fill each position, but no matter how hard you try, business in general ends up with about the same mix of unusually productive workers and average to below average workers. If you're getting a little better than an average workforce for your industry, you're doing well. If you manage to get a stable of mostly high performers, you're doing extraordinarily well.

      You won't change the equation by hiring H1-B foreign workers either. They're a similar mix of top performers and worker bees and you will still end up hiring your share of people who look good on paper and interview well but don't do that great on the job. All you've done is expanded your already-large pool of possible hires and made your choices more difficult.

      The bottom line is to get as good as you're probably going to get, you need about ten resumes of people who look good on paper and sound plausible on the phone. You pass those on to the hiring manager, who manager narrows this down to a group of 3 or 4 who almost certainly could do the job and you interview only those people. The one who seems most competent (if he or she's not personally objectionable) is good enough because the real bottom line is you can never be sure how good they really are until they're on the job.

      Forget "finding talent" and "only hirig the best." You will always hire some who don't meet your standards. So what? You either train them to be efficient workers despite their shortcomings of you fire them and move on.

    16. Re:seriously? not this again by curunir · · Score: 2

      My department has been hiring for months with very little success. There really are a shortage of qualified candidates right now.

      But here's the thing...we're in San Francisco where there's a lot of competition. In other parts of the country, there really is a shortage of jobs. Tech work clusters in certain areas. This allows what you're saying to be completely true *and* what is being said in the article to be completely true. You'll noticed that developerauction.com limits itself to SF, LA, NY and Boston...that's where the desperate employers are.

      I do sympathize about the formalized HR process...I've been in a constant fight with our HR department over the job descriptions that are posted. They claim that it's worthless to post an ad without a job description. They want things along the lines of, "You'll work closely with Product Management to develop features for our flagship product." My contention is that this is basically implied...every corporate development job can be described that way. I prefer to have the post talk about what we do, what kind of developer we're looking for and our development philosophy. It's an ad that I think would work well if it was posted to the more specialized job boards (Github, Craigslist, etc) but then they post it to Dice and Monster and blame me when it gets almost no response.

      I've responded like this in the past when someone claims that employers are being disingenuous, but I'll do it again...if there are any good Java or front-end JavaScript developers in the SF bay area, respond and I'll tell you how to apply...these are $150k+ jobs, so we're not low-balling candidates.

      --
      "Don't blame me, I voted for Kodos!"
    17. Re:seriously? not this again by DarwinSurvivor · · Score: 2

      Then hire greens and keep them for 5 years until they are no longer greens.

    18. Re:seriously? not this again by alexmin · · Score: 1

      "until they are no longer greens" - at which point they will leave to greener pastures because they are no longer "green" (and rightfully so.) Been there, done that myself, seen it bazillion times. Large corp can have on-site hands-on university, small shop cant afford it.

    19. Re:seriously? not this again by mjwx · · Score: 1

      Also, if your company wants to hire "top 5% talent" then you need to be a top 5% employer. Top talent does not want to piss away their career in the IT department of Bank of America, for instance. If you're trying to hire top talent but are an average company, then you are the equivalent of an old fat bald dude trying to date young supermodels. It ONLY works if there's a lot of money involved.

      Unless you go to a foreign country where the meaning of "a lot" is much lower.

      Which some companies are fighting tooth and nail to do.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    20. Re:seriously? not this again by Anonymous Coward · · Score: 1

      100% agree. At the same time, depending on the company and position, this can still mean a lot of time spent looking through resumes and candidates.

      I happen to be a hiring manager for our company and interview a lot of people. We have complicated systems that require quite a bit of time to understand the technology and rationale behind their design. Sadly, we have to reject vast majority of applicants for several reasons. Here are top 4:
      #4: people don't want to work with old technologies (every technology becomes old after one year nowadays - the only companies that don't deal with them are startups),
      #3: people come for a programming/software engineering position and fail a very basic programming test,
      #2: people know they come to a 10 person team in a 50 person department and want to be the director in 5 years,
      #1: people don't give rat's ass about the company they are applying to (we're not on either coast and with about a year of upfront training to become minimally productive, we can't afford people leaving after 6 months - we don't hire for a specific project).

    21. Re:seriously? not this again by Anonymous Coward · · Score: 1

      Yes, but when 80% of companies insist on only hiring "talent" that tends to leave to the supposed "top 5%" in rather (artificial) short supply.

      No other "industry" is so infected by this language plague, where being competent and average is seen as outright inferiority. We need more liberal arts and humanities grads who can better parse the bullshit hyperbolic language used by illiterate engineers and business grads. (I write this as a comp sci / philosophy double major.)

    22. Re:seriously? not this again by Darinbob · · Score: 1

      The recruiters aren't very smart about it. I get calls all the time at work (not a published number) promoting jobs where they're looking for "rock stars". You're not going to get many high quality people with long term experience where that is an attractive offer. Either "rock star" means you're on the road playing a different city every night, or it means they want you to be one of those asshats that you hate working with. Or they promote the pre-IPO thing (lack of job security, probably lower than average pay).

    23. Re:seriously? not this again by Anonymous Coward · · Score: 0

      Anyone who has worked in Software can tell you that, the top 5% of engineers are often many times (3x-10x) as productive as the bottom 50%. There is no shortage of Qualified Candidates (people who have experience in the job), only a shortage of the top 5% of engineers (people who would do well in ANY software job).

      Well, that is reality for you. 5% is one in twenty, and you expect them to do a job of a three to ten common ones. I think you are wasting time waiting for the talent, instead of hitting it off with what you have available, unless "talent" stands for "suckers" because you are not paying them their worth.

    24. Re:seriously? not this again by vipw · · Score: 1

      But on the other hand, that does sound like a shitty place to work.

    25. Re:seriously? not this again by 19061969 · · Score: 4, Interesting

      This.

      I was at an interview just last week for a position at a large UK telecoms company. The salary was probably 45th percentile for the country, and I was told with a straight face that I had to prove I was the "world's best of the world's best".

      For the first time in my life, I actually walked out of an interview. I'm quite good at my job and get shit done well with everyone happy. I might (or might not) be world class but I don't know because I've not had the opportunities to work at the large trendy tech companies; but this condescension is only allowed if they're paying a truly awesome salary.

      If they're paying shite wages and the manager is a twat, they will never be world's best of world's best, no matter how much they want to be.

      --
      bang goes my karma... again...
    26. Re:seriously? not this again by Anonymous Coward · · Score: 1

      So in the end it again comes down to the money side. If there is a shortage of skilled workers in that area, why are people not offering higher salaries to encourage more skilled people from other parts of the country to move there? Of course that means a significant pay increase compared to the rest of the country, to justify moving away from friends and family. Supply and Demand at work.

      Maybe you are very generous with job offers. I don't know. Maybe the skilled people 'over there' don't realise they might have a good deal if they are willing to move.

    27. Re:seriously? not this again by DarwinSurvivor · · Score: 2

      If you can't even retain the employees you spent 5 years working, why should any experienced working quit their current job to work for you? In case you didn't notice, I bolded "keep", as in "if don't piss off your greens, eventually they'll become the senior developers you've been looking for".

    28. Re:seriously? not this again by Anonymous Coward · · Score: 0

      The real problem is HR doesn't have any accountability. Fuck HR. One time, long ago, I applied for a job. This wasn't the only time this happened. I immediately got a reply back from HR saying the position was filled. Which, I actually liked the fact that they replied. Most of the HR cocksuckers won't even do that. They're too 'busy' or something, too full of themselves. So I took a different job and then about a month in that job the manager at the company calls me up and says, "I've been looking at your resume and really like what I see. I would like to hire you." I replied, "Your HR department sent me a rejection letter about a month ago. I took this other job instead." He was really pissed off.

      The point is HR is deciding the fate of a lot of companies, even more so the any of the corporate officers. That is bad. Until HR is dismantled we will continue to see more and more bullshit. HR is not needed. Payroll is payroll, HR is not needed. Hiring should be done by the managers themselves, HR is not needed. Legal issues should be handled by lawyers, HR is not needed. There is no reason to have a HR department. Especially a department that is making hiring and firing decisions with no clue about what they are doing. Fuck HR. Never talk to HR. They are not your friend. They will destroy your company.

    29. Re:seriously? not this again by Sardaukar86 · · Score: 1

      For the first time in my life, I actually walked out of an interview. I'm quite good at my job and get shit done well with everyone happy. I might (or might not) be world class but I don't know because I've not had the opportunities to work at the large trendy tech companies; but this condescension is only allowed if they're paying a truly awesome salary.

      Thank you. By standing up for yourself you show that kind of arrogant PHB behaviour up for exactly what it is and do us, your fellow professionals in the workforce, a big favour.

      Quality results cost money but in the long run usually cost less. Companies that understand this are the ones that stick around.

      --
      ..Mullah or Pope, Preacher or Poet, who was it wrote: "Give any one species too much rope and they'll fuck it up"?
    30. Re:seriously? not this again by silentcoder · · Score: 1

      > I was furious with them for wasting my time, but kept my temper in check and departed without burning any bridges. This has only happened to me once though, in almost 20 years in the field.

      If a company does that to me, I'll send them a bill for my time at market consultant-developer rates. They may not like you realizing it but there is a massive opportunity cost - in the time they wasted from me I could have made that much money, since they took that time under false pretenses I would demand they pay me for it.
      If they then refused, you bet your ass I'd sue them.

      --
      Unicode killed the ASCII-art *
    31. Re:seriously? not this again by Anonymous Coward · · Score: 0

      Wouldn't matter if you were proficient with C++, they want to know that you had experience with STL as well. But if you pass the third party C++ and STL online exams that HR sends you a link to, they would then want to give you a technical test on your knowledge of "design patterns", or rather know that you had a fold-out chart on your wall.

    32. Re:seriously? not this again by gbjbaanb · · Score: 1

      The java... its a good thing :)

      I have the same problem in many respects, I have a lot of C++ skills, yet I was turned down for a position writing C++ on Linux because I didn't have enough Linux experience - admittedly, I have little commercial development experience on Linux (there's not many jobs for Linux over the last 15 years) but I have a fair amount of sysadmin exp on the platform.

      But I guess, the little boxes weren't checked and so I failed to get past the recruiter gateway.

    33. Re:seriously? not this again by rollingcalf · · Score: 3, Insightful

      Do your job ads mention the $150K+ salary?

      Many job ads don't mention the salary. If you're not listing the salary, developers will only have your reputation as a company and the type of work described in the ad to use as their basis for deciding whether to apply. If those aspects are not outstanding, you'll get mostly unemployed applicants (who will be rare in San Fran), not already-employed developers who want to know that they'll get a salary increase.

      --
      ---------
      There is inferior bacteria on the interior of your posterior.
    34. Re:seriously? not this again by Anonymous Coward · · Score: 0

      "The culpability for this problem sits squarely on the employer."

      I have to totally agree. My current employer was busy outsourcing the department, and the ball finally rolled into my court. The company brought in some "experts" from Chicago. I had one meeting with this group. They were BS from the start. No documentation, no real product. Totally snowed the execs, who then signed the contract with them. The Chicago people then stopped talking to me at all, saying they didn't need any "old" technology help.

      I started looking, and have found recruiters like buzz words. After a lot of useless interviews, I have started looking through private channels.

      In the meantime, the Chicago project went fubar. The data could not be reconciled, did not balance, produced no interfaces to G/L and still, being "very complicated", had zero documentation.

      My employer asked me to cleanup the mess. I have gotten my first raise in almost 10 years, since it had been made clear that my knowledge was not needed. And I am still looking, thank you very much.

    35. Re:seriously? not this again by Anonymous Coward · · Score: 0

      Yea well, you actually might have to give the people you employ a raise when they gain more experience. If the only way to get a raise is to switch companies it's not hard to guess what employees are going to do.

    36. Re:seriously? not this again by erp_consultant · · Score: 1

      If a company did that to me I would immediately deduce that they are not a company I would ever want to work for. Their first, and last, contact with me has been based on lies. That bridge has already burned. At that point I would probably tell all the interviewers to go fuck themselves and leave. Then I would tell everyone I know about the experience. Word spreads fast in the IT field.

    37. Re:seriously? not this again by erp_consultant · · Score: 2

      And if you hire subpar employees your profit will suffer due to lack of productivity and high turnover.

      People that are skilled in HR (yes there are a few of them) realize this. One of the big trends now is identifying so called "top talent" in an organization. These are the people that are not easily replaceable, the ones you don't want to lose. These individuals will have no trouble finding another job. In fact, if they are really good they probably have already been contacted by a competitor.

      Finding, and keeping, top talent is a huge priority for elite companies. It's not always about money, although that's certainly a major part of the equation. It's about treating people the right way, giving them challenging work, a career path, training.

    38. Re:seriously? not this again by Anonymous Coward · · Score: 1

      You sir, have no idea what IT at bank of America is like :)

    39. Re:seriously? not this again by Anonymous Coward · · Score: 0

      But here's the thing...we're in San Francisco where there's a lot of competition. In other parts of the country, there really is a shortage of jobs. Tech work clusters in certain areas. This allows what you're saying to be completely true *and* what is being said in the article to be completely true. You'll noticed that developerauction.com limits itself to SF, LA, NY and Boston...that's where the desperate employers are.

      Minor nit: in the major tech hubs, there is *negative* unemployment for software developers. In the rest of the country, there is below-normal to normal unemployment for software developers (in the 3-5% range). E.g., I'm in Minneapolis and receive 1-2 inquiries a month, despite the fact that I'm happily employed at my current position.

      The flip side to that is that salaries in the Midwest are growing at a slower rate than in the tech hubs. Consequently, I am fully expecting Slashdot to be full of vitriol towards "outsourced" software development in Minneapolis instead of India in 3-5 years.

    40. Re:seriously? not this again by gatesstillborg · · Score: 1

      Seconded!

      Btw, karma is for sissies! :)

    41. Re:seriously? not this again by Anonymous Coward · · Score: 0

      Why are people not offering higher salaries to encourage more skilled people from other parts of the country to move there?

      I think we are. $150k/year is pretty good and that's the floor...but we've offered much higher. Add in great health insurance (medical, dental and vision), RSU grants, 20% yearly bonus, ESPP program, 401k with 125% match, $5k/yr educational benefit, $650/yr health benefit (gym, trainer, etc), $900/yr commuting benefits and you're looking at a package that's well over $200k.

    42. Re:seriously? not this again by neurovish · · Score: 1

      I've responded like this in the past when someone claims that employers are being disingenuous, but I'll do it again...if there are any good Java or front-end JavaScript developers in the SF bay area, respond and I'll tell you how to apply...these are $150k+ jobs, so we're not low-balling candidates.

      Is $150k in San Francisco really that great though? Using two different cost of living calculators to translate San Francisco to Raleigh, NC (which is close to average), $150k turns into either $74k or $86k. How accurate is that? Are people living around San Francisco that underpaid for where they live compared to workers someplace that isn't insanely expensive? Even using the high $86k number, that sounds more like a good side of average programmer with 5 years experience. $150k is what good programmers I know in central FL with ~5 years experience are making, and cost of living there is under the national average.

    43. Re:seriously? not this again by mdf356 · · Score: 1

      Why are people not offering higher salaries to encourage more skilled people from other parts of the country to move there?

      I think we are. $150k/year is pretty good and that's the floor...but we've offered much higher. Add in great health insurance (medical, dental and vision), RSU grants, 20% yearly bonus, ESPP program, 401k with 125% match, $5k/yr educational benefit, $650/yr health benefit (gym, trainer, etc), $900/yr commuting benefits and you're looking at a package that's well over $200k.

      For how many years experience, though? And anyways, one has to live in San Jose or wherever else in the valley to have this job. You'd need to offer me a lot more money than that to get me there.

      --
      Terrorist, bomb, al Qaeda, nuclear, yellowcake, kill, assassinate. Carnivore is dead... long live Echelon.
    44. Re:seriously? not this again by drew_eckhardt · · Score: 1

      I agree with your premise there are lots of "developers" who have worked on a project that used technology X... And realistically only a couple members of any team are producing 70-80% of the code, but the recruiting agencies and HR depts are a huge part of the problem. I am (no really) in that 5%, but I have the hardest time finding jobs, because I've worked all over the map... From designing huge networks, to automating deployment of tens of thousands of network devices, to DB design/DBA type work, to software design, development, etc both web and client based.

      If you don't need to beat recruiters off with a stick it's because you're not using linkedin, live in the wrong place, or have big resume problems.

      If you're at a career point where you're not satisfied with the jobs within your social network you need a linkedin presence (I'm trying for a start-up home run so I can retire and bootstrap my own companies without giving up my middle class lifestyle. Connections at big companies, small companies unlikely to see exponential growth, and startups with bad business plans don't get me there).

      If you're really into writing software you should probably live someplace where there are lots of businesses where doing that well is essential to the bottom line. There's the SF bay area and every place else (41% of 2011 venture capital spending went to Silicon Valley and San Francisco ranks high too). Austin, Boston, Boulder, Raleigh, and Seattle/the East Side are most of the rest. Those places have higher costs of living where the salaries don't quite compensate although you probably spend more time working than anything else and are likely to be happier with the better job and a smaller home where you spend less of your time.

      List all of the key words you've worked with. Eliminate those you don't want to do again (for instance, I don't like dealing with the Microsoft tool chain or library issues so I don't admit to having worked with C# even though I did so as a Microsoft employee.). Now you have your bases covered for recruiters, big company HR, and their key-word matching software.

      Sort into categories somewhere along the expert / experienced / other continuum so you are not mis-representing your skills to the technical staff that interviews people and makes hiring recommendations.

      If you are answering recruiter's emails and phone calls but not getting interviews it's because you have resume problems. The meat of your resume is written for engineers and managers. Engineers want to see what you personally accomplished technically. Managers want to see what you did in terms of leadership to deliver products sooner / more predictably / with lower cost and how your technical and non-technical contributions improved the bottom line.

      If you're interviewing but not getting job offers there are problems with you.

      I need to see that senior candidates have built bigger and more complicated things than junior candidates. I accept that in many situations candidates were limited by what was on the table, although after enough positions if they're not doing big things it's because they're either not interested or not capable in which case I'm better off hiring a less experienced candidate that I can grow.

      I expect senior candidates to have practical experience with process and the things surrounding writing code and value doing them well because it makes delivering products faster, more predictable, and more pleasant for everyone. I've seen some real stupidity from executives "test code doesn't ship to customers" "we'll add quality later" and accept that many people spend time working in such environments, although after enough positions if they're not doing things it's because they're not interested enough in their craft do do a little side reading and experimenting or they have attitude problems ("I'm too good for unit testing!") in which case I'm better off hiring a less experienced candidate that's more likely to be trainable.

      I look fo

    45. Re:seriously? not this again by __aaltlg1547 · · Score: 1

      100% agree. At the same time, depending on the company and position, this can still mean a lot of time spent looking through resumes and candidates.

      I happen to be a hiring manager for our company and interview a lot of people. We have complicated systems that require quite a bit of time to understand the technology and rationale behind their design. Sadly, we have to reject vast majority of applicants for several reasons. Here are top 4: #4: people don't want to work with old technologies (every technology becomes old after one year nowadays - the only companies that don't deal with them are startups), #3: people come for a programming/software engineering position and fail a very basic programming test, #2: people know they come to a 10 person team in a 50 person department and want to be the director in 5 years, #1: people don't give rat's ass about the company they are applying to (we're not on either coast and with about a year of upfront training to become minimally productive, we can't afford people leaving after 6 months - we don't hire for a specific project).

      Stop interviewing new college grads. The only real show stopper is #3. Here's why:
      #4 -- What do you expect of kids? Either you take the time to teach them or you hire experienced programmers.
      #2 -- What do you expect of kids? Experienced programmers know they're not going to climb the ladder that fast.
      #1 -- Why should they give a rat's ass about your company? They can start caring when you hire them. If your company likes to keep people and see them develop and offer opportunities to do bigger things as they grow into their role, tell them that. Talk about how long some of your senior people have been with the company. That won't impress everybody, but the kind of people it does impress are the kind you are looking for.

    46. Re:seriously? not this again by MadKeithV · · Score: 1

      Unless you go to a foreign country where the meaning of "a lot" is much lower. Which some companies are fighting tooth and nail to do.

      Having quite some exposure to developers from a country where "a lot" is a lot less than "a lot" over here (over here being western Europe in my case): the best of those "cheap" developers are rapidly getting smart, and realizing that they can make several orders of magnitude more money if they move to where employers are willing to pay more. Quite a few of the "cheap" top developers are no longer staying in the "cheap" locations because they know they are worth more and can get those jobs if they want.
      So the cries you hear might actually mean that cheap-arse employers are finally starting to find it difficult to exploit cheap but great developers from low-pay countries.
      In fact, the point made in the GP's post is valid: the company I work for is nowhere near top 5%. We have some excellent talent from (not necessarily any longer IN) eastern Europe, and we try to coddle them as much as we can, but we have lost several of them to places like Google in London and Geneva. We don't blame them, in fact we congratulate them, because we care about our people enough to let them go if they get an offer we can't possibly match (financially or in "sexiness" of the job and company they are going to). Some of them come back to us after being burned out on "big company culture" too. It's the best we can do.

    47. Re:seriously? not this again by Anonymous Coward · · Score: 0

      If, in fact, they really think there is a lack of qualified people, here's their problem: there has been a breakdown of communication, and their formalized hiring processes, excessive HR, and outsourced employee sourcing (you know, headhunters) are at the root of the problem. Finding (and keeping) good employees is the single most important part of maintaining and growing a business. Why would you push that responsibility to someone else? What ends up happening is that headhunters (of all kinds) do end up finding qualified applicants who are looking for work - we just write them off as spam, telemarketers, or insincere requests without so much as a second notice because of how unprofessionally we're addressed. (Hint: having an Indian "initial contact" team for your HR is not a good idea; neither is using an automated system for requesting potentially qualified applicants to submit a resume via eg. LinkedIn - you're only going to get desperate people, not those who are capable.)

      The culpability for this problem sits squarely on the employer.

      Dude you hit the nail squarely on the head. I've been looking for a job now for 3 months. I have over 15 years in my field. I'm Chief of Network Security where I work now but found unqualified to be the Senior Security Solutions Officer because I did have "solutions" in my job title. Yep I was talking to an Indian person.

      Its hard enough dealing with an English speaking person that doesn't understand the tech but when you add a language barrier your totally screwed on the interview. Even state governments are using India based headhunters. It would seem like the right thing to do if a state government war going to out-source hiring they would use a company based in thier own state and keep their money local. I

    48. Re:seriously? not this again by mjwx · · Score: 1

      Unless you go to a foreign country where the meaning of "a lot" is much lower. Which some companies are fighting tooth and nail to do.

      Having quite some exposure to developers from a country where "a lot" is a lot less than "a lot" over here (over here being western Europe in my case): the best of those "cheap" developers are rapidly getting smart, and realizing that they can make several orders of magnitude more money if they move to where employers are willing to pay more. Quite a few of the "cheap" top developers are no longer staying in the "cheap" locations because they know they are worth more and can get those jobs if they want.

      This has been happening for decades. Not just with Developers too.

      If an Indian developer or engineer is that good, he doesn't stick around in India and work for Indian wages. He comes do Australia and works for Australian wages. They dont always retire back in India too.

      So the cries you hear might actually mean that cheap-arse employers are finally starting to find it difficult to exploit cheap but great developers from low-pay countries.

      Exactly,

      However there is no shortage of cheap-arse places providing cheap-arse labour to exploit. The problem these cheap-arse employers are having is that these places are no longer offering good cheap-arse labour.

      On the flip side, these poorer countries are complaining of a brain drain to richer nations. The same thing Australia complained about in the 90's when the AUD was fetching less than 0.5 USD and the top Australian engineers were going to the US or Western Europe.

      --
      Calling someone a "hater" only means you can not rationally rebut their argument.
    49. Re:seriously? not this again by toddestan · · Score: 1

      Yeah, but are they getting paid what someone with 5 years of experience commands now that they have it? If you're paying them what they got as a "green" + 3% per year then don't be surprised when they jump ship.

  4. Re:Click-whoring post. How could this get approved by mwvdlee · · Score: 4, Insightful

    Click-whoring; yes.
    Plagiarism; no.

    Just because they cut and paste a few sentences from a much larger copyrighted article, doesn't mean they are infringing on the copyright, despite what copyright pimps would like you to believe.

    --
    Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
  5. cut down unqualified candidates or cut out good pe by Joe_Dragon · · Score: 1

    cut down unqualified candidates or cut out good people though a 3rd party HR system that looks for key words / name of school / etc over real skills.

  6. did he say he will work for free on his resume? by sku158 · · Score: 1

    or he'd pay to work?

  7. Thumbs up! by Janek+Kozicki · · Score: 3, Insightful

    This is a great idea, and I think that it is going to work. I experienced myself how badly some companies are trying to recruit skilled people. Many people I know received a job offer from google, me included. Also once I received a weird phone call from another country, because a recruiter at citrix googled my cv, and he was thinking that I will abadon my job and move with family to another country. This recrutiting market is just crazy.

    This is why I think that DeveloperAuction will do a lot of good.

    --
    #
    #\ @ ? Colonize Mars
    #
    1. Re:Thumbs up! by Penguinisto · · Score: 4, Informative

      Blowing off mod points here, but damn... I had to agree with you.

      I've lost track of how many headhunters call me up, thinking that I'd just drop everything and move to Dallas, Little Rock, Boston, Virginia, Seattle, SanFran, LA, you-name-it. Oh, and I'm supposed to be there in two weeks. For a six month contract. The guy usually has a heavy Indian accent, and always promises that the salary is larger than what I make now.

      It tends to crumble when I demand that the agency fly me out on their dime, pay any and all relocation costs, and oh, yeah - get all its fees from the employer. It shuts them up in very short order.

      Don't get me wrong, there are good headhunters out there, but I usually stick with the ones who are local, and that I know of personally. Cold-callers have always led to disappointments, and I'm in no hurry to give them a second chance.

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
    2. Re:Thumbs up! by Rob+the+Bold · · Score: 3, Insightful

      It tends to crumble when I demand that the agency fly me out on their dime . . .

      This alone is a pretty good weed-out question. When a potential employer isn't willing to put actual balance-sheet money on the line they can figure on "playing the percentages" and just bring in as many candidates as possible, sometimes without even scrutinizing resumes and applications to ensure a potential match on paper. The most egregious example I've seen was a relative that drove hundreds of miles there and back to an interview set up by a recruiter. She found out at the interview that she didn't have enough experience in a particular area for the job -- a fact that would have been obvious if they'd examined her resume ahead of time. Probably would have also been a good idea to make sure recruiters were also aware of the "must-haves" for the position. But hey, no one was out anything -- except the candidate, right?

      --
      I am not a crackpot.
  8. Age vs experience... by Teun · · Score: 3, Insightful
    From the Forbes article:

    “Good engineers are never unemployed and never seeking jobs.”

    Unless they're living in India and over 40...

    --
    "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    1. Re:Age vs experience... by Anonymous Coward · · Score: 0

      Unless they're living in India and over 40...

      Here's an idea - instead of linking back to a Slashdot post about a story... how about linking to the FREAKING ACTUAL STORY!?

    2. Re:Age vs experience... by KZigurs · · Score: 4, Insightful

      But of course - in a body shop you don't want experience, as your product is billable time, not results.

    3. Re:Age vs experience... by c_sd_m · · Score: 2

      From the Forbes article:

      “Good engineers are never unemployed and never seeking jobs.”

      Unless they're living in India and over 40...

      Or by choice. In a two-weeks of vacation world, I've walked out of a crappy job and spent a few months checking things out and figuring out what I wanted to do next. I could've done it while I was still working but I had enough savings and wanted a break. Ended up making up the savings I spent in a year or so at the new job too.

    4. Re:Age vs experience... by maeglin · · Score: 2

      From the Forbes article:

      “Good engineers are never unemployed and never seeking jobs.”

      Unless they're living in India and over 40...

      Or by choice. In a two-weeks of vacation world, I've walked out of a crappy job and spent a few months checking things out and figuring out what I wanted to do next. I could've done it while I was still working but I had enough savings and wanted a break. Ended up making up the savings I spent in a year or so at the new job too.

      I'm doing this right now. I left a high paying job because I was more than a little tired of it and I'd knew I'd never be able to stop spending my spare time on "putting in the extra effort" instead of job seeking. At this point, I'm just looking for something interesting in an new location -- pretty open ended job search criteria. Unfortunately, I'm currently getting more recruiter calls than actual interested party call backs but I'm confident my choice to force myself to move on will pay dividends in the long run.

    5. Re:Age vs experience... by mysidia · · Score: 2

      But of course - in a body shop you don't want experience, as your product is billable time, not results.

      Naw.... certain jobs have a certain number of hours that are billed, if the technician finishes it 50% faster, the full standard price for the job will still be billed; if you have more experience and can do the jobs faster, that means you do more jobs for the same number of hours of wages, which equals more profit for the company....

    6. Re:Age vs experience... by rockmuelle · · Score: 1

      Since this thread is about hiring talented developers for fun projects, I'll throw this out (using the criteria from the parent):

      Interesting: genome sequencing (an actual "big data" problem that's not just about selling stuff to people more effectively)
      New location: Austin, TX

      http://www.lab7.io/jobs/

      -Chris

    7. Re:Age vs experience... by Anonymous Coward · · Score: 0

      I would like to point out that living in India and over 40 as a developer you probably already made enough to live off the rest of your life and easily support some family members.

    8. Re:Age vs experience... by MurukeshM · · Score: 1

      Because the parent newspaper being linked to, the Times of India has slowly become the equivalent of toilet paper.

    9. Re:Age vs experience... by evil_aaronm · · Score: 1

      Ditto here. After nearly six years commuting five hours, one-way, weekly between NYC and Podunk for a job that got less and less interesting, even if the pay was good, I finally said, "Hasta Las Vegas," and came home to enjoy my life and do whatever the heck I want. Currently, it's electronics, which I never got to work with as closely as I wanted as a software developer. I'm carefully burning through savings, but the house is paid off, car almost, and by keeping other expenses low, I should be able to stretch my savings for almost a year. At some point, I may feel like I need to go back to work, but for now, bottom line: Life isn't too bad. I can stop and smell the roses. If I want to stay up until 3:00 am on a Monday morning learning about "multiplexers and bilateral switches" or post on /., I can.

      So, Forbes, suck it.

    10. Re:Age vs experience... by hackula · · Score: 2
      Read the position descriptions. You will not get what you are looking for for these. You want someone with a BS or higher in CS, with 5+ years experience, with scientific software experience, with C/C++/Python experience (3 languages used in totally different spaces, where it would be unlikely (read impossible, even though bullshitters will claim otherwise) for someone to be an expert in all three), experience with high performance clustered computing (when you are also asking for a low level C guy who is unlikely to have written many web applications period), experience with every front end web technology you could think of, SQL, noSQL, graphics tech...... oh yeah, and you will not pay that well. No offense, but who the hell are you expecting to find?? Anyone who would walk into the interview claiming this skill set is an obvious interview troll.

      Good luck to you, but you are going to need to narrow your criteria down if you hope to find someone who it an expert in any of the areas you are looking for.

    11. Re:Age vs experience... by Anonymous Coward · · Score: 0

      "Note that we are a startup. Apply with realistic expectations. We know this position could easily command a high rate, but we can't do anything crazy just yet."

      Sure thing. Tell you what, post the jobs again when you have adequate venture capital to do the crazy things you're attempting to do.

    12. Re:Age vs experience... by Anonymous Coward · · Score: 0

      Pffft. i finished my job 2 weeks ago. I am a good engineer and currently unemployed. Am I looking for another job? Not just yet. Maybe next week.

  9. Re:Click-whoring post. How could this get approved by Anonymous Coward · · Score: 5, Insightful

    Copyright isn't the issue. Quoting from copyrighted content is fair use.

    Plagiarism, on the other hand, is trying to pass off someone else's work as your own.

    In this case, the summary says "an anonymous reader writes..." when the actual author is not anonymous and not the submitter of the story.

    Heck, at the very least put "J.J. Colao writes for Forbes..." That would be honest, but this is just shitty journalism.

  10. Re:Click-whoring post. How could this get approved by K.+S.+Kyosuke · · Score: 1

    Just because they cut and paste a few sentences from a much larger copyrighted article, doesn't mean they are infringing on the copyright, despite what copyright pimps would like you to believe.

    Is is plagiarism if the summary claims that the cited passage was written by "an anonymous reader" when in fact it was openly written by "J.J. Colao".

    --
    Ezekiel 23:20
  11. Computer matching and recruiters by Jonah+Hex · · Score: 4, Interesting

    I get hit hard every day due to some of the esoteric terms in my resume (I'm a Windows OS/apps rollout and migration specialist), and end up having the primary tier of recruiters contact me first, then a week or two later the second (larger) tier hit me with the exact same job. The worst aspects of it are the recruiters ignoring my geographic/telecommuting preferences and wanting me to constantly "network" for someone to fill their positions. It becomes discouraging to waste so much time filtering the same exact irrelevant positions over and over. - HEX

    1. Re:Computer matching and recruiters by canadiannomad · · Score: 1

      I totally agree with this. I'm constantly on the road, and have no plans to return to cubicle work. I prefer to work from the beach, thank you very much. Recruiters constantly ignore my telecommuting requirement. Not that there is a shortage of work for talented developers who look.

      --
      Hmm, the humour and sarcasm seem to have been be lost on you.
  12. This is confusing by Anonymous Coward · · Score: 2, Insightful

    "Good engineers are never unemployed and never seeking jobs." But this recruiting firm wants the equivalent of 15% of your first years wages to match talent and an employer. Couldn't a good engineer (and a smart one!) just cut a deal directly with the employer and pocket some of that? Should be a no-brainer - enigneer wants job and employer wants engineer. Why the middleman?

    1. Re:This is confusing by uncqual · · Score: 2

      Couldn't a good engineer (and a smart one!) just cut a deal directly with the employer and pocket some of that?

      Often, yes (at least at a smaller company that doesn't have a lot of "cast in concrete" rules). It's likely to be in the form of a sign-on bonus which pays out after six or twelve months. It just becomes part of the cost of hire and if a recruiter doesn't need to be paid, there's more flexibility on the sign-on bonus.

      In fact, if you are introduced to the company through an outside recruiter and get a good sign-on bonus, it's possible that the recruiter kicked in some of the bonus out of their fees. This is especially true if the bonus is increased during the negotiation process (the recruiter is facing losing 100% of the commission if the company refuses to pay enough of a bonus to entice the candidate so they will often decide to "top off" the bonus to make the placement -- the contract between the recruiter and the hiring company dictates this and the candidate is never aware of it). In fact, I've never raised my contribution to a sign-on bonus during negotiations with a candidate sourced through a recruiter taking a cut of the first year salary - but often the sign-on bonus goes up because the recruiter kicks in something.

      So, a tip, if you're a candidate going through an outside recruiter, always request a sign-on bonus late in the negotiation game (to help compensate for loss of seniority in vacation time or whatever justification you can come up with). You might as well get a cut of the recruiter's fee and this is about the only way to do it. As the recruiter's supplier, you have quite a bit of flexibility.

      --
      Why is there an "insightful" mod and why isn't it "-1"? If I wanted insight, I wouldn't be reading /.
    2. Re:This is confusing by GeckoAddict · · Score: 1

      From the article, the employee actually pays that as a finder's fee on top of the salary, it doesn't come out of the engineer's salary.

    3. Re:This is confusing by Anonymous Coward · · Score: 0

      That may be true, but the engineer can say "if you hire someone equally competent through a recruiter, it will cost you $SALARY*1.15, rather merely $SALARY. Given that, I would like to request a salary of $SALARY * 1.10."

  13. Reminds me a contact from Google by loufoque · · Score: 5, Informative

    That reminds me a recent exchange I had with Google. Some guy from Google contacted me on linkedin saying Google was interested in my profile.
    Since my profile is fairly atypical, I am a researcher, a technical consultant, a CEO of a tech start-up, an open-source enthusiast and member of several major standardization efforts, I was wondering what they had to offer.

    I gave the guy my number and he called me. It was apparent that he hadn't even read my resume, and when I explained it he didn't seem to understand what I was saying. He actually expected me to resign from my job, freshen up bachelor's level computer science stuff and then come for an interview. He wouldn't even tell me how much they'd be able to pay me; just that "you know, Google has the best, and everyone there is quite satisfied with their salary".

    If you're going to try hiring people randomly with keywords on linkedin, a good idea might be to check who you're pitching to.

    1. Re:Reminds me a contact from Google by phantomfive · · Score: 5, Insightful

      I've solved that problem by telling all recruiters that my minimum is $160k first thing. If I get it, great. If not, I'm happy where I am.

      --
      "First they came for the slanderers and i said nothing."
    2. Re:Reminds me a contact from Google by Anonymous Coward · · Score: 0

      No its not, it's the same as online dating. You shotgun your pitch to as many women as possible, it doesnt matter if they realize its a shotgun approach or not, (they realize its part of the game if they do) and bite at the hook.

    3. Re:Reminds me a contact from Google by Anonymous Coward · · Score: 0

      The company mentioned in the Forbes article story, DeveloperAuction, seems to be trying to change the way this process works by having employers put the offer BEFORE the interview.

    4. Re:Reminds me a contact from Google by c0l0 · · Score: 4, Interesting

      A Google recruiter (from Google Ireland) contacted me a few months ago due to having found my personal website (which is in German, but transported the important information nevertheless, it seems - and yeah, he definitely HAD read my resume. That said, noone cared much about what I did or did not do with my current job, noone asked me to quit it before starting the interviewing process or anything downright crazy like that.), and asked if I was willing to do a phone interview. Sure thing, I said, and after passing the first interview, I did two longer follow-ups on the phone, and finally one just recently on site in Dublin (Google was nice enough to pay for the trip and accommodation, and Dublin is a very nice place that I had always wanted to visit anyway), and last Friday, I've been offered a very attractive position in their Site Reliability Engineering team due to all of this - so I do have first-hand experience with all stages of Google's interviewing process.

      Almost everything I had to do in the interviews involved stuff you're supposed to learn when studying Computer Science at a university that deserves its name, and I think that's a very good and reasonable thing. I've always been a fan of the "concepts, not implementations/products"-kind-of-education. I think that's especially important at Google - their infrastructure is so vast and powerful and unlike any other in the industry that the overwhelming majority of people who take a position there won't have seen anything even remotely like it in terms of scale, and they will probably find very little there that's overly "familiar" to them: Most of the software you can get away with running at a small- to medium-sized IT shop, despite any glaring and maybe-no-so-glaring inefficiencies, will fall apart at the scale Google would need to have it work at, so they'll implement something on their own and run that to do that job. Read the GFS paper for one such (albeit a bit dated) example. That's where all that "bachelor's level computer science stuff", a nuisance that apparently, in the eyes of some, only inhabitants of ivory towers should be allowed to care about, comes in again. So I think it's perfectly reasonable and in their best interest to test for that kind of knowledge and skills in their interviewing process.

      --
      :%s/Open Source/Free Software/g

      YTARY!
    5. Re:Reminds me a contact from Google by Anonymous Coward · · Score: 0

      That's funny, I turned down a recruiter who was screening me for an SRE position not six months back. Strangely Google don't understand that not everyone wants to sell their house and move to a stupidly expensive capital city just to work at Google.

    6. Re:Reminds me a contact from Google by sribe · · Score: 1

      That reminds me a recent exchange I had with Google...

      My experience was the opposite. I was contacted by someone who had definitely read my resume, and was asking for someone with (some of) my skills to work on the kind of stuff that I like. (I wasn't in a situation where I could actually consider working for them--but it was refreshing anyway to get a cold contact that was so appropriate.)

    7. Re:Reminds me a contact from Google by wonkey_monkey · · Score: 1

      Some guy from Google

      Definitely not "some guy from a company paid by Google per candidate"?

      --
      systemd is Roko's Basilisk.
    8. Re:Reminds me a contact from Google by jnelson4765 · · Score: 1

      Interesting - looks like they're doing a major recruiting push, since I'm in the interview process myself. I'd wanted to move to San Francisco, and saying that to the recruiter kind of surprised them. I don't live in a high-tech city, so the recruiters aren't anywhere near as vigorous, but I'm having the feeling that Google has just about tapped out the talent pool that's available in their local areas, and has sent recruiters after the less well traveled paths.

      I wasn't even in the market, but when a company like Google calls, you tend to respond...

      --
      Why can't I mod "-1 Idiot"?
    9. Re:Reminds me a contact from Google by Anonymous Coward · · Score: 0

      I ask $180K, $160 is too low.

    10. Re:Reminds me a contact from Google by Escogido · · Score: 1

      I had the same experience with a recruiter for Google. I mostly have game design and production experience on my resume and since my background is in engineering, those skills listed as "side" skills probably matched his keywords. I didn't realize that at the start of the interview and was wondering why would Google be interested in a game designer. The conversation went on for at least quarter an hour, he was asking me for my experience with different software development platforms and I kept wondering why does that even matter. At a certain point I realized what was going on and said "actually I'm not interested in a software developer position"; his tone immediately changed and he quickly wrapped up the call after that.

      I was wondering if my resume looked like an engineer's and went back and looked at it - nope, it didn't, at least not to me. I was getting software developer position offers every once in a while so eventually I added "Please do not contact me for positions in software engineering" to the "contact me for" part on LinkedIn. I still do get these from time to time :)

    11. Re:Reminds me a contact from Google by Overzeetop · · Score: 1

      He didn't mention he expected 8 weeks of personal leave per year, Cadillac health, and a day a week for personal projects. He's saving that for the negotiations, no doubt.

      --
      Is it just my observation, or are there way too many stupid people in the world?
    12. Re:Reminds me a contact from Google by loufoque · · Score: 1

      No, he was a google employee, UK based

    13. Re:Reminds me a contact from Google by swillden · · Score: 5, Informative

      Almost everything I had to do in the interviews involved stuff you're supposed to learn when studying Computer Science at a university that deserves its name, and I think that's a very good and reasonable thing. I've always been a fan of the "concepts, not implementations/products"-kind-of-education. I think that's especially important at Google - their infrastructure is so vast and powerful and unlike any other in the industry that the overwhelming majority of people who take a position there won't have seen anything even remotely like it in terms of scale, and they will probably find very little there that's overly "familiar" to them

      This is very true. Pretty much everything in Google's tech stack is homegrown. Most of it because there is (or was) nothing out there that was capable of doing the job. Some of it because it doesn't even occur to Google engineers to look. Google doesn't sneer at technologies not invented at Google... Google doesn't even notice them. :-)

      That's only part of the reason for the CS-heavy interview approach, though. I'm an interviewer at Google (though a relatively inexperienced one, at least in interviewing the Google way), and I'd say the real reason Google asks the sort of questions it does is because it's the only way the company has found to get a handle on what it really wants to find out about candidates: Problem-solving ability. Technical jobs at Google all require people who can think on their feet, who can quickly absorb the salient points of a problem, rapidly identify areas that need to be defined, then define, implement and analyze a solution. That ability could perhaps be tested with other sorts of problems, but CS provides a wealth of potential problems for discussion along with a well-defined common set of concepts and language which both interviewer and candidate are (or should be) intimately familiar with.

      Some experienced candidates (like loufoque, apparently), find it insulting to be asked questions a kid straight out of school should be able to answer. They want the interviewer to give due deference to the value of their experience. The problem with that is that experience can be fudged, and it is simply not true that you can judge a candidate's real experience by asking about their previous work. I've met many who can talk the talk with the best of them, but when you start asking them to solve problems on the spot their weaknesses start to become very apparent. I do admit that some people just struggle with the on-the-spot nature, and might be able to devise great solutions given time to go off and think, but such people wouldn't do well in Google's fast-paced technical culture anyway.

      But don't think this means Google doesn't value experience. It does, a lot, because of the judgment that comes with experience. But experience can easily be judged by reading the candidate's resume, so there's really no value in spending time in the interview trying to evaluate it.

      So, the interview focuses on evaluating ability and cultural fit. CS theory is a useful tool for evaluating the former, and it's not unrelated to the latter. Assuming the candidate does well in the interview, experience becomes relevant later in determining compensation and placement (Google doesn't generally hire for specific positions; Google hires good people, then figures out where to put them).

      One final caveat about Google's interviewing approach: It rejects a lot of good people, and everyone at Google knows it. It's broadly accepted among engineers at Google that virtually any one of us could be interviewed again and have maybe a 30% chance of being rejected. Maybe 50%.

      This is decidedly sub-optimal.

      The problem is that no one knows how to identify top talent accurately other than by hiring them and putting them to work for a few months. Doing exactly that is a big focus of Google's internship program -- it's one of the very best sources of good permanent hires -- but trial peri

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    14. Re:Reminds me a contact from Google by swillden · · Score: 1

      Strangely Google don't understand that not everyone wants to sell their house and move to a stupidly expensive capital city just to work at Google.

      Did you ask about other locations? Google has many.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    15. Re:Reminds me a contact from Google by simoncpu+was+here · · Score: 1

      Some guy from Google contacted me too, and I wished he screened me by asking how to design a solution for a very deep and technical problem, instead of expecting me to memorize things that can easily be googled or browsed through the man pages.

      Fresh graduates have an edge with Google's hiring process. I've been developing software for quite some time now, but I no longer remember the Big O thingy for standard sorting algorithms.

    16. Re:Reminds me a contact from Google by wonkey_monkey · · Score: 1

      I got a call from someone saying he was calling "from HSBC" wanting a reference for an ex-employee only to work out a few minutes into the call that he was calling from a company employed by HSBC to do their recruitment. All UK based.

      --
      systemd is Roko's Basilisk.
    17. Re:Reminds me a contact from Google by Anonymous Coward · · Score: 0

      I wasn't even in the market, but when a company like Google calls, you tend to respond...

      Why, have you always wanted to find new ways of bombarding people with ads?

    18. Re:Reminds me a contact from Google by TheRaven64 · · Score: 3, Insightful

      I'd say the real reason Google asks the sort of questions it does is because it's the only way the company has found to get a handle on what it really wants to find out about candidates: Problem-solving ability.

      There are two problems with this. The first is that even Google admits that it doesn't work. The most successful people inside Google are the ones that had one or more negative reports during the interview process: exactly the ones that would be rejected in the normal process. Second, Google isn't short of people who can solve problems, and being able to solve problems isn't even an especially rare skill. Google is short of people who can identify the problems that are worth solving, and the interview process does nothing to address that.

      --
      I am TheRaven on Soylent News
    19. Re:Reminds me a contact from Google by olau · · Score: 1

      I do admit that some people just struggle with the on-the-spot nature, and might be able to devise great solutions given time to go off and think, but such people wouldn't do well in Google's fast-paced technical culture anyway.

      I had a good laugh when I read this. :)

      Of course, I've never been to Google so probably shouldn't laugh. But it's funny anyway. :)

    20. Re:Reminds me a contact from Google by swillden · · Score: 2

      I'd say the real reason Google asks the sort of questions it does is because it's the only way the company has found to get a handle on what it really wants to find out about candidates: Problem-solving ability.

      There are two problems with this. The first is that even Google admits that it doesn't work. The most successful people inside Google are the ones that had one or more negative reports during the interview process: exactly the ones that would be rejected in the normal process.

      Cite? I've seen the internal stats on correlation between interview ratings and subsequent performance and while the correlation is imperfect, I've never seen anything that would indicate what you're saying.

      Second, Google isn't short of people who can solve problems, and being able to solve problems isn't even an especially rare skill. Google is short of people who can identify the problems that are worth solving, and the interview process does nothing to address that.

      Hmm. This is a more interesting assertion.

      First, I'm not sure I agree that identifying the problems that are worth solving is either particularly hard or particularly rare. However, if we adjust your statement slightly to "people who can identify the problems that are most worth solving and can achieve the most value for the least effort", (note that "value" needn't be -- and at Google mostly isn't -- financial) then I'd agree that such ability is extremely valuable and very hard to find. I think Google probably has more of it than most companies, but more would always be better.

      Second, if good problem solvers are hard to identify (and they are... else Google's process wouldn't reject so many of them), good problem choosers are almost impossible to identify.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    21. Re:Reminds me a contact from Google by swillden · · Score: 1

      I do admit that some people just struggle with the on-the-spot nature, and might be able to devise great solutions given time to go off and think, but such people wouldn't do well in Google's fast-paced technical culture anyway.

      I had a good laugh when I read this. :)

      Of course, I've never been to Google so probably shouldn't laugh. But it's funny anyway. :)

      I'm not sure what aspect of it you're laughing at... but it's nothing less than the truth. Technical discussions at Google, whether water-cooler discussions, or design review meetings, or whatever else tend to be very fast-paced, with lots of ideas being raised and discarded in rapid succession. This is pretty typical of engineering discussions wherever I've worked in my ~25-year career, but the culture at Google and the nature of people Google hires (those who do well in rapid-fire, on-the-spot technical discussions) turn it up. It's a lot of fun, IMO, but not for everyone.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    22. Re:Reminds me a contact from Google by Anonymous Coward · · Score: 0

      Funny, I interviewed with Google and when I had the first engineer phone interview he sounded burnt-out and disinterested. All he wanted me to do was solve a code problem. No interview questions beyond that. I got the impression Google is not the hotspot of innovation it thinks it is. The interviewers also had no idea what position they wanted to fill, it seemed more like they were just fishing.

      I've done more than 100 interviews and know that this approach will lose too many good candidates. If you can't engage with them, you'll never find out whether they fit the position or not.

    23. Re:Reminds me a contact from Google by swillden · · Score: 1

      Funny, I interviewed with Google and when I had the first engineer phone interview he sounded burnt-out and disinterested. All he wanted me to do was solve a code problem. No interview questions beyond that.

      I'm sorry you thought he sounded burnt-out -- maybe he was having a bad day for some reason -- but yes, all you'll do in a phone screen is a code problem. The purpose of the phone screen is to determine if the candidate is likely enough to succeed to be brought into a face to face interview, and the quickest way to determine that is with a code problem. I should point out that most of the face-to-face interview questions will also be code problems, or at least problems that involve some amount of coding.

      I did a lot of interviewing during the 15 years I worked for IBM, too, and some before that, and while I never found an approach which is as effective as what Google does, I was gravitating towards focusing primarily on coding in my interviews. It really is the most effective way to separate those who can talk from those who can do -- and it's astonishing how many candidates can't do something trivial like inserting a node into a sorted linked list.

      The interviewers also had no idea what position they wanted to fill, it seemed more like they were just fishing.

      Correct. As I mentioned in my post Google doesn't generally hire for specific positions. The interview and hiring process just tries to find good, capable people, and placement is a separate process after that. This does create something of a problem in that candidates have to be sold on the company rather than on the specific position or the team. In fact, I think most hires don't even know what they're going to be working on when they accept the job offer (I didn't). Countering that is the fact that mobility is high within Google and it's expected that most employees won't stay in their original position very long anyway. People can gravitate to what they enjoy the most, and there is more than enough cool stuff going on in Google that anyone can find an awesome job for themselves.

      The one caveat is location. If the team that does what you really want to do is located in another city, changing jobs means relocating. Personally, out of all the stuff Google does I'd most prefer to work on Android security, and Android security team has offered me a job... but I don't want to live in California. So instead I do something which isn't quite as fun but lets me live in Colorado.

      I've done more than 100 interviews and know that this approach will lose too many good candidates. If you can't engage with them, you'll never find out whether they fit the position or not.

      As I said, there is no "fit with the position" to be determined. That's for later. I realize this isn't what people are accustomed to. Losing good candidates isn't generally a big problem for Google, however, because the company (rightfully) has a reputation as a fantastic place to work. It does happen, and that's unfortunate, but it's rare enough that there are bigger problems that need to be addressed first -- like figuring out how to stop outright rejecting so many good candidates, without letting poor candidates through.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  14. I love you! by Anonymous Coward · · Score: 0

    Will you father my baby?

    1. Re:I love you! by houstonbofh · · Score: 0

      Will you father my baby?

      Your right. It is almost as bad as Russian bride spam.

  15. RTFA by techno-vampire · · Score: 3, Informative

    I know this is Slasdot, but out of curiosity I took a moment to RTFA: the part quoted as the summary here is the only place in TFA that the phony profile's mentioned. The rest of it's nothing more than a puff piece for the head-hunting firm behind it. Yet Another Case where the "editors" didn't bother to check what they were accepting.

    --
    Good, inexpensive web hosting
    1. Re:RTFA by Anonymous Coward · · Score: 2, Interesting

      Yes, this is not actually a Forbes article. Forbes lets anyone publish a "blog", which many spammers and scammers use to make their crap look legitimate. Same deal with Examiner.com articles.

  16. Sounds about like my voicemail... by Golbez81 · · Score: 0

    I sometimes wonder if head hunters are worse than bill collectors.

  17. Re:Click-whoring post. How could this get approved by Anonymous Coward · · Score: 0

    How are you to know I am not J.J. Colao?

    - J.J. Colao

  18. Re:Click-whoring post. How could this get approved by theshowmecanuck · · Score: 4, Insightful

    How does this rate "interesting". If it was plagiarism there wouldn't be a link to the actual story. You can't tell someone they are trying pass someone else's work off as their own when they provide the original work. Especially when it is just a couple lines on a news aggregator site to give the readers a clue what the article is about.

    --
    -- I ignore anonymous replies to my comments and postings.
  19. Did Pete London... by Anonymous Coward · · Score: 0

    ... register here at /. ?

    Because even non-existing he could get a lot of automatic karma while ACs -- even existing ones -- are pushed under the carpet...

  20. Re:Click-whoring post. How could this get approved by superwiz · · Score: 1

    The question is not whether you are him or not. It is whether you represent yourself to be him or not. Plagiarism is copying without proper attribution.

    --
    Any guest worker system is indistinguishable from indentured servitude.
  21. Re:Click-whoring post. How could this get approved by kelemvor4 · · Score: 0, Redundant

    Copyright isn't the issue. Quoting from copyrighted content is fair use.

    Plagiarism, on the other hand, is trying to pass off someone else's work as your own.

    In this case, the summary says "an anonymous reader writes..." when the actual author is not anonymous and not the submitter of the story.

    Heck, at the very least put "J.J. Colao writes for Forbes..." That would be honest, but this is just shitty journalism.

    You must be mentally impaired or trolling, or this is your first time ever on slashdot. It's not journalism at all so saying it's "shitty journalism" is not relevant. An anonymous reader wrote in that there was a story on another site and provided a summary. This tips off the Slashdot users to go comment without reading the article or sometimes without even reading the summary. One or two users will actually read both and have a bit of sport trolling the group that did not. It's a cycle.

  22. Such Bullshit by MacGyver2210 · · Score: 2

    Good engineers are never unemployed and never seeking jobs.

    Biggest falsehood ever. I bet this is the reason most unemployed coders are still unemployed, and these companies have announced a false 'shortage' of engineers.

    FWIW, if anyone's hiring, I am a coder that would like a better job...

    --
    If the only way you can accept an assertion is by faith, then you are conceding that it can't be taken on its own merits
    1. Re:Such Bullshit by Anonymous Coward · · Score: 0

      You're missing the point: if you're ever unemployed and struggling to find a job, you're not a good engineer.

    2. Re:Such Bullshit by Anonymous Coward · · Score: 0

      I've had recruiters tell me this diatrbe too. Contacted me saying they specialize in recruiting engineers; their specialty is that "the best aren't looking" and therefore I must be part of that group since I'm currently employed. Gee thanks ego, but no bite from me.

    3. Re:Such Bullshit by Anonymous Coward · · Score: 0

      if you're ever unemployed and struggling to find a job, you're not a good engineer.

      That used to be the case, it isn't anymore.

      In this economy, it's quite possible to be the best at what you do and willing to work for half what you used to make, and still not be able to find a job in your field. The rules have changed (let's hope not permanently).

    4. Re:Such Bullshit by Anonymous Coward · · Score: 0

      I've had recruiters tell me this diatrbe too. Contacted me saying they specialize in recruiting engineers; their specialty is that "the best aren't looking" and therefore I must be part of that group since I'm currently employed. Gee thanks ego, but no bite from me.

      Not sure which meaning of diatribe you're aiming for here.

    5. Re:Such Bullshit by Anonymous Coward · · Score: 0

      "a bitter and abusive speech or piece of writing". Thanks for reading your own link.

    6. Re:Such Bullshit by hackula · · Score: 1

      Which platforms/tech are we talking here? Maintream tech jobs seem to be booming in my area (not the valley or anything). Put rails, C#, or node.js on your resume around here and you have to beat them off with a stick. Even PHP seems to be doing well here. I really cannot imagine not finding something fairly quickly. If you have any of these on your resume, and have not gotten through the interviews, then you may need to ask yourself if you are sexually harassing the interviewer or something.

  23. Re:Click-whoring post. How could this get approved by Anonymous Coward · · Score: 0, Troll

    It's not journalism at all so saying it's "shitty journalism" is not relevant.

    Hey, if this site claims to be a "news" site, then it is journalism. They should do their fucking job and actually, you know, write a summary.

    An anonymous reader wrote in that there was a story on another site and provided a summary.

    Exactly. Provided someone else's summary.

    This is where the disagreement lies between actual news sites and aggregators. The news sites say it's plagiarism and the aggregators say it isn't - they're just "search utilities" like Google.

    Call it what you will - I call it fucking lazy.

  24. Is a LinkedIn profile even worth it? by Anonymous Coward · · Score: 0

    I've been tempted to setup a LinkedIn profile and put up my resume. I've held back because I don't want to give the impression I'm looking for a new job. OTOH, I *feel* that I'm underpaid for the skills, education and experience I have. I'm also looking to switch career and willing to see what I'm offered.

    I get why people setup profiles and can see some of the benefits.

    Any advice or good reading for the LinkedIn shy? Is it even worth it?

    1. Re:Is a LinkedIn profile even worth it? by tompaulco · · Score: 1

      I've recently had an experience with LinkedIn that is making me value it less and less. It came up and asked me if I had the following skills, and then listed about 20 skills, about 15 of which I had. I didn't know whether to hit "no" because I didn't have all of them or "yes" because I had a lot of them. I hit "yes". Now, LinkedIn says I have a couple of skills that I don't actually have. I tried to find a quick way remove those skills, but didn't have all day to try to figure out how to do it, and five minutes of looking around my profile yielded no results, and led to a rabbit trail where LinkedIn was trying to get me to update my whole life history. The same thing happened when I tried to change my title in my existing company. It wanted me to put a new company name in and everything. I just gave up and now my profile has false and outdated information. If I was hiring, I would not use a LinkedIn profile as a good indicator of what skills or even what employer somebody had.

      --
      If you are not allowed to question your government then the government has answered your question.
    2. Re:Is a LinkedIn profile even worth it? by psergiu · · Score: 1

      LinkedIn is a good way of seeing where all of your old colleagues, friends and classmates are working now.
      I set-up my LinkedIn account to not accept InMail and the only contact info i gave is: "call me, i have the same phone number you knew".
      I log-in once a couple of months and reject/ignore all requests from people i don't personally know (recruiters) and accept the ones from friends/colleagues/classmates ...
      If i'll ever go job-seeking, with only a couple of clicks i'm open to all recruiters.

      --
      1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
    3. Re:Is a LinkedIn profile even worth it? by rwa2 · · Score: 1

      Yeah, that sounds about right. I'd always been suspicious about the utility and value of LinkedIn, though I know several co-workers who swear by it. I suspect that it's not sufficiently better, than say, Facebook, aside from the fact that everyone attempts to be a bit more professional.

      I'd recommend a more traditional job-search site, such as monster.com . I've gotten just about all of my jobs over the past 12 years through recruiters searching through there. These are used by companies when they're ready and somewhat desperate to hire, so I find it much more effective than trying to target a few employers when they probably don't/won't even have budget approved for positions for a few months out. Also the recruiters will usually be more than happy to help you tweak your application to best suit their clients, which is actually a big help.

      The signal/noise ratio can be somewhat low, as you might expect... I use an alternative email account reserved for mailing lists and website bots, but it's not the spam-magnet I would have expected and have successfully been able to opt out of most of the other recruiter mailing list DBs that pull profiles from monster.

      My largest gripe is that recruiters often won't care to honor your location preferences, so you'll get spammed with several short-term contracts in bumfark nowhere. But it's not a big deal and sometimes kinda interesting to sift through.

  25. Auction? by NetNinja · · Score: 3, Insightful

    What is happening is you are running into the sales game. Don't think just because someone is caling you that they have a job for you.
    I am not going to go into percentages here but a good number of these so called offers are B.S.

    They are sales people. They are doing what they are suposed to quote un quote do what sales people do in a cold calling envrionemnt. It's the numbers game.
    They get paid if they get some sort of information from you. Even a referal get's them a stale Twinkee of the week award.
    They don't read your resume, because if they did they would offer you a interview appointment right then and there.
    Or if they do ofer you an interview appointment it's to come to thier boiler room operation where all you hear are noisy phone calls and no privacy. it's like walking into an H&R tax office so that people who are waiting arround can hear what you make and what deductions you can't take.

    Don't waste your time. Don't even give them more than 1 min on the phone.

    Here is how a successful phone call should work.

    Ring ring.
    Hello?
    Hello Mr. so and so. I was looking over you resume and I am interested in your skills. We have a position open at a company _______ fill in the blank.
    Starting Salary $$ benefits and whatever else they have to offer.
    What would be the best time for you to come in for the interview?

    If they don't have that down just hang up.

    People love to waste your time. In fact there would be more millionares per capita if people were paid on the sole premise to waste your freaking time.

    This is a bogus article because if you put yourself up for auction you arent going to get any offers and in fact I don't think people have the time to play let's see who we can get for X ammount of dollars. You better be a well known superstar if you think you can offer yourself to the highest bidder.

    Most large organizations have outsourced your so called superstar programming experience to India anyway. These companies don't care if they get a workable product that serves the customer, all they care about is how quick thier project gets launched and how much money they saved up front. It's the same stupid shortsighted bullshit that American cars manufactures use. get the product out at all costs and when the recall happens fire the head of the engineering division because we decided to go with the low ball 20 cent micro switch over the $1.00 one that causes parking brakes to disenguage.

    1. Re:Auction? by Anonymous Coward · · Score: 0

      I removed my phone number from my resume and put a big, red, bold notice above the fold saying *** NO RECRUITERS ***

      So I don't get cold called. I get cold e-mailed, and many of the e-mails claim they "left me a voice mail".

      If I ever respond to these people, I usually ask them to name the company and the salary range they are offering. They never, ever do it. They assume as a matter of course that you will contact the company behind their backs and apply for the same job yourself. From this, I can discern two things. First, they are useless and they know it. Second, they assume you will cut them out of the loop, because they are fundamentally dishonest and are projecting that onto you.

      Never let a recruiter get you onto the phone unless you first have it in writing the name of the company, the full description for the opening, the expected salary range, and an agreement that if the recruiter does not submit you for the position, you may apply to it yourself. I don't care how desperate you are for work; if you can't get these things, the recruiter was not going to help you find a job anyway! Stop wasting time with useless middleman salesmen and spend that time cold calling HR departments of companies in your local technology park instead.

    2. Re:Auction? by Anonymous Coward · · Score: 0

      Hey - Matt Mickiewicz here from DeveloperAuction. Basically you broke down the solution the exact solution we're trying to offer - VC funded start-ups tell the potential candidates upfront - the position, the salary, the signing bonus, the equity component, and then use that to drive interviews. It optimizes the process for the Engineer side, and saves a TON of time. After 14 days, you end up with 7, 10, or 15 offers, pick the 4 or 5 coolest companies, do a phone interview with those and go from there.

      $78 million in job offers on 150 Engineers in the last auction. We don't let staffing agencies, recruiters, or "sourcers" onto the platform - it's usually the Co-Founder/CEO/CTO/VP of Engineering that's reviewing profiles and submitting indicative offers.

  26. Re:Click-whoring post. How could this get approved by steviesteveo12 · · Score: 1

    Well, are you? The odds are 7 billion to one.

  27. Re:Click-whoring post. How could this get approved by TapeCutter · · Score: 2

    How about looking up the definition of "summary", the fact that it is a "summary" removes the possibility of plagerisim.

    --
    And did you exchange a walk on part in the war for a lead role in a cage? - Pink Floyd.
  28. How to cut down on endless recruiter spam by Stiletto · · Score: 4, Insightful

    When I was a software engineer (12+ years of experience), I had recruiters contacting me pretty much daily, with all sorts of wonderful breathless urgency, about how they were "so very interested" in my software skills and would love to chat about their crappy entry-level job or temp position. Annoying as hell, and the recruiters have only gotten more and more desperate as the software job market starts picking up.

    Fortunately, I now get contacted about once a month (if that) by recruiters. How, you ask?

    Simple. I did a little career move over to the technical marketing side, and changed my job title on LinkedIn to "Senior Product Manager". BAM! The recruiter contacts stopped pretty much overnight. Every once in a while, I get the occasional "I notice you were once an engineer, want to come back??" message which I politely decline, but no more annoying stream of desperation. I suppose if I ever become serious about changing companies, I could always put "Senior Software Engineer" back on LinkedIn and dive through the recruiter spam.

    When you think about it, it's kind of revealing. It shows the mentality out there--people think the only thing software companies need is a steady supply of engineers. Apparently, software simply leaps from the engineers' fingertips, right into the customer's shopping cart, with no product definition, schedule, market requirements analysis, etc.

    1. Re:How to cut down on endless recruiter spam by Anonymous Coward · · Score: 3, Funny

      When you think about it, it's kind of revealing. It shows the mentality out there--people think the only thing software companies need is a steady supply of engineers. Apparently, software simply leaps from the engineers' fingertips, right into the customer's shopping cart, with no product definition, schedule, market requirements analysis, etc.

      You should look into Agile. It makes all that stuff irrelevant. All you need is a bunch of programmers, a wall of index cards, a daily status meeting, and rows of tables lined with computers. The software practically writes itself. If it's not what you want, pivot.

    2. Re:How to cut down on endless recruiter spam by Stiletto · · Score: 1

      LOL, we do Agile. You still need product/market fit, and someone to describe to the engineers what to pivot to.

    3. Re:How to cut down on endless recruiter spam by hackula · · Score: 1

      ... Or Cowboy Coding. One Man. One Computer. One Brain Holding It All Together.

  29. How much for the cute blonde one? by retroworks · · Score: 1

    And do they accept bitcoins?

    --
    Gently reply
  30. Re:Click-whoring post. How could this get approved by Cillian · · Score: 2

    Hang on, what? Are you saying if I write something, then repeat what I wrote in an anonymous context, that's plagiarism?

    --
    -- All your booze are belong to us.
  31. That'd be okay by MichaelSmith · · Score: 1

    I wish I could be hounded by recruiters

  32. Simple skill by michaelmalak · · Score: 3, Interesting

    I'm surprised at the number of people who don't know the skill of dealing with telemarketers on the telephone: "I'm not interested"

    Dealing with recruiters is similar and simple: "I currently make $X, and would consider a change for a 30% increase."

    1. Re:Simple skill by Anonymous Coward · · Score: 0

      ...and suddenly they realize that you're currently making way more than they're offering :-/

  33. Re:Click-whoring post. How could this get approved by Anonymous Coward · · Score: 4, Funny

    Hang on, what? Are you saying if I write something, then repeat what I wrote in an anonymous context, that's plagiarism?

  34. Re:Click-whoring post. How could this get approved by reboot246 · · Score: 5, Informative

    For Pete's sake, people! It's not "cut and paste"; it's "copy and paste"!! The two operations are not the same thing.

    You'd think a bunch of geeks would get it right.

  35. Why is this surprising? by Tony+Isaac · · Score: 4, Insightful

    If you're making up a fake resume, you can say whatever you want to...whatever you know recruiters are looking for! Why is it so surprising that a custom-tailored--but false--resume would attract attention from recruiters? Real resumes usually carry some baggage, and other less-than-ideal unless you've had a flawless career. Fake ones can be perfect.

    1. Re:Why is this surprising? by robogun · · Score: 1

      When 1% of the resumes are attracting 80% of the job offers, there's a problem with picky-ass employers expecting perfection for peanuts

  36. Re:Click-whoring post. How could this get approved by steviesteveo12 · · Score: 1

    Yes, and you'll have to promptly sue yourself.

    It would only make a difference if it was true, of course.

  37. Re:Click-whoring post. How could this get approved by Anonymous Coward · · Score: 0

    Okay, I am looking at Merriam-Webster, which says "summary" is: "an abstract, abridgment, or compendium especially of a preceding discourse."

    Now I'm looking at the definition of "plagiarize" which is: "to commit literary theft : present as new and original an idea or product derived from an existing source."

    Can you tell me what in these definitions makes it impossible to "present as new and original an abstract, abridgment, or compendium especially of a preceding discourse derived from an existing source"? Cuz as far as I can see, that's exactly what the submitter did. Except, it's not even a summary - it's the fucking introduction of the article itself!

  38. Just use commonly searched tech words by ArobenX · · Score: 1

    I actually just ran into this situation myself.

    I didn't even have a LinkedIn profile until about a month ago when I ran into an ex-coworker who wanted to connect with me. I've been happily employed developing Android apps at my current company since I graduated university about a year and a half ago, but I figured what the heck, I might was well throw my experience up on my profile for shits and giggles.

    Within one week, I was contacted by recruiters at Facebook, Amazon, Google, and a couple lesser-known local companies.

    Really all it comes down to is picking words that get a lot of search hits and shoving them in your profile.

  39. A question for the community... by Anonymous Coward · · Score: 0

    First some context:
        I've been a Software Engineer (or developer with extensive design and architecture experience if you prefer) for 18 years. Without posting my resume, suffice it to say that I have a great deal of experience that many companies and recruiters find desirable. When I post my resume, I generally get between 70-90 calls within the first week. About 20% of those will be for jobs requiring relocation even though I clearly post that I am not interested in relocating. I only use one job posting website to cut down on the number of calls I have to take. As a contractor, I have to do this two to three times a year most years (thank god that I'm on a three year contract now). As such, keeping references is VERY hard for me to do because they get pestered to death every time I'm looking for work. Every single recruiter wants to verify them personally, and during any given search that can be up to 100 calls (that's high, but it has certainly happened).

        With all of this popularity, I still have yet to break through the 110k barrier on income. Why? Business Managers (MBAs) with comparable experience and projects under their belt are making at least three times that much. Why? In most of my contracts and every W2/Fulltime job I've ever had I have to learn as much or more about how the business works and what policies, processes, procedures and rules exist, have existed over time and may change. I've designed and built as well as implemented CMS, CRM, ERP, Authentication, Physical Access Management and many other essential core business processes. So with all of my knowledge and experience why is it that salaries for my profession lag so far behind salaries for business managers?

    1. Re:A question for the community... by hackula · · Score: 1

      The average project manager is making nowhere near 330k. MBAs making more than Software Engineers is generally a myth. My has been the director of an MBA program at well known university for years, and I can say that developers start out at about twice what the average MBA does. Business guys and software devs rarely break the 150k salary unless either of them go into business themselves. Tech people tend to compare small-town programmers to wall street tycoons. We could just as easily compare IPO'ed startup founders to MBAs working as insurance salesman and come to the opposite conclusion. I am glad I am where I am. My roommate graduated from his MBA a couple years ago, around the same time I started working as a developer. I now make twice as much without any 50k grad school debt and the gap is continually widening. Its a bad time to be a humanities grad.

  40. You guys are lucky. by SwampChicken · · Score: 1

    Because most of the spam I get is from course invitations, not recruiters...

  41. This may sound racist... by Anonymous Coward · · Score: 0

    ...but never, ever, ever accept let your resume be submitted by a guy with an Indian accent calling from New Jersey. There are a lot of them, and none of them actually have an in with the local company they're "recruiting" for. They're just grabbing the job off the wire and calling blind in hopes of striking paydirt.

  42. Posting Word and other document type resumes by boddhisatva · · Score: 1

    Word has a little box under properties fro "keywords". The keywords are not visible in the Word document but a search through Word resumes will see those keywords. And there seems to be no limit on the number of keywords. Same is true for HTML and other types. You dump in a huge list IT and comp sci words and every search hits on your resume. You get a phone call "I'm calling you because of your experience with ...(not having actually read your resume, you hear shuffling of paper as he goes through your resume looking for the skills he searched on.)

  43. Re:Click-whoring post. How could this get approved by Anonymous Coward · · Score: 0

    Its entirely possible that the quotes were cut from a copy.

    You'd think a geek would account for edge cases.

  44. Slashvertisement. Don't read by tompaulco · · Score: 1

    'nuff said.

    --
    If you are not allowed to question your government then the government has answered your question.
  45. Re:Click-whoring post. How could this get approved by devleopard · · Score: 2

    You just noticed that? A significant number of submissions (and on some days, a majority) do the exact same thing.

    I remember when Slashdot submissions required some original thought, and the quality of your submission might determine if it was picked over others submitting the same link.

    Much of the fault falls on Slashdot editors. It should take less than ten seconds to reject a submission based on a copy-and-paste summary. Of course, that'd harm their page views for ads, so gotta keep the stories coming no matter what, right?

    That's why a laugh when I see any discussion about the evils of corporate greed. Impartial with regard to Google? Maybe if the big G wasn't a primary source of revenue. This isn't new however. About ten years ago, I made a hobby of grabbing screenshots of Slashdot where they were pimping Microsoft in banner ads - sometimes even on the same page as articles about MS. A couple are here:

    http://web.archive.org/web/20020929185648/http://www.mr-bill.net/

    --
    The best thing about a boolean is even if you are wrong, you are only off by a bit.
  46. Re:Click-whoring post. How could this get approved by Will.Woodhull · · Score: 4, Informative

    Re-read the introductory line to TFSummary:

    An anonymous reader writes

    Now for those for whom English is a second language, AND native English speakers who have never learned to use the language properly, realize that the word "writes" can take either of two distinct meanings in this context:

    1. In both the context of written discussion as well as the more general context of broad English usage, "writes" means the same thing as the newer word "authors" means: "to write" or "to author" means to construct new sentences and paragraphs using alphanumeric characters.

    2. In the specific context of written discussion only-- not in the general case-- "writes" means to contribute a piece of text to the discussion. The origin of the text is not a part of the concept. The word "contributes" is an exact synonym and in formal writing (to use yet another definition of "write") it is probably always the better choice.

    But slashdot is not formal writing and because there are so many ESL participants, the use shorter words is better than polysylabic ones. Using "writes" as a synonym for "contributes" is the more appropriate choice. And in this sense, it says only that someone contributed some text, without implying that the text was an original creation.

    The summary is not plagiarism. This is most especially evident to anyone who goes from RTFS to RTFA and sees that TFS is a repetition.

    --
    Will
  47. My way of handling recruitment by CBravo · · Score: 2

    I never respond to recruiters unless I find proof they actually read my resume.

    Lately I have been doing the selections. Boy. I wish people would simply pass the Codility test, find the nullpointer in our test and understand sql injections. I never trust a resume again; have to verify it.

    --
    nosig today
    1. Re:My way of handling recruitment by Areyoukiddingme · · Score: 1

      You have candidates that claim to know SQL, yet don't know what a SQL injection is? Is it any wonder employers whine about the quality of candidates. I'm an absolutely terrible database guy (by the standards of database guys). I write butt-simple SQL, when I write it at all, and I do more in code than I should, instead of letting the database do it for me, and I still know you can't trust user data.

      And I'm unemployed because I refuse to live in California. Too many rats in a box.

    2. Re:My way of handling recruitment by Anonymous Coward · · Score: 1

      Had a guy put SQL on his resume, then when asked at the interview how to get all the data from table Sample didn't know what a select statement was.

      We had another that when asked the same question started walking us through how to use Excel to highlight all the rows, copy/paste into something else...

    3. Re:My way of handling recruitment by Anonymous Coward · · Score: 1

      Oftentimes folks don't realize that the difference between a crappy dev vs a good (not great, just good) dev is like 100x, not "they're just 1-2x better". And yet that crappy dev whod use Excel to highlight stuff would get perhaps 50k a year and a good dev perhaps 100k a year.

    4. Re:My way of handling recruitment by hackula · · Score: 1
      Yuck. I get shit like this all the time too. I make potential hires solve FizzBuzz in their language of choice before proceeding. Most can't. It has saved a whole lot of time. I am still amazed at how many people outright lie about their experience, or if they didn't lie, are so shamefully inept at their job. If you call yourself a programmer and cannot solve FizzBuzz...PLEASE....STOP! For reference, here is FizzBuzz:

      "Write a program that prints the numbers from 1 to 100. But for multiples of three print “Fizz” instead of the number and for the multiples of five print “Buzz”. For numbers which are multiples of both three and five print “FizzBuzz”."

    5. Re:My way of handling recruitment by CBravo · · Score: 1

      We had a one that sorted a list by javascript. When asked, explicitly, what he would do with 1 million records he said 'the same'.

      --
      nosig today
  48. Re:Click-whoring post. How could this get approved by tbird81 · · Score: 1

    No, but a person who accepts and publishes your anonymous submission without checking that you are in fact the author of the work is putting himself in a dodgy legal position.

    The problem isn't really the lazy AC who submitted the copypasta (it's better than the 99% spam that clogs the firehose) - it's the lazy editor who didn't bother to check for originality and authenticity.

  49. Re:Click-whoring post. How could this get approved by GiganticLyingMouth · · Score: 1

    Wait... you actually read TFA??

  50. Re:Click-whoring post. How could this get approved by Anonymous Coward · · Score: 0

    Well, are you? The odds are 7 billion to one.

    2.5 billion to one.

    Out of 4 billion English writers 1 billion end everything with 'do the needful', and 0.5 billion claim to love Jesus so much you have to send them money.

    Yes - I made those numbers up.

  51. Re:Click-whoring post. How could this get approved by 1s44c · · Score: 1

    For Pete's sake, people! It's not "cut and paste"; it's "copy and paste"!! The two operations are not the same thing.

    http://www.vincentchow.net/wp-content/uploads/2008/08/copypaste.jpg

  52. Github, yow by Anonymous Coward · · Score: 0

    I've been staying away from github which seems too Facebook-like for comfort. I host all my own git repos on my own domains.

  53. Re:Click-whoring post. How could this get approved by KevReedUK · · Score: 1

    Is that all we aspire to be now here at /.? Just a news aggregator? Oh, how we have fallen!

    --
    Just my $0.03 (At current exchange rates, my £0.02 is worth more than your $0.02)
  54. Re:Click-whoring post. How could this get approved by Anonymous Coward · · Score: 0

    Slashdot can be many things. News aggregator is one thing that it is. It doesn't have to be the only thing.

  55. Re:Click-whoring post. How could this get approved by superwiz · · Score: 1

    Here's the exact problem. There is no way to know if copycat AC was you or not. While this is clearly a parody, there is no way to tell if the 2nd post was something you cleverly posted to create a satire or if someone derived on your work and made a satire out of it.

    --
    Any guest worker system is indistinguishable from indentured servitude.
  56. LinkedIn has become very annoying by DrXym · · Score: 3, Informative

    LinkedIn has gone from being a semi useful way to keep track of colleagues to being a meat market. If you accept invites from agents you WILL be spammed without remorse from now until forever. At least that's my experience. It's best not to accept invites from agents at all and be careful about what groups you join too since I've had explicit spams identifying as a member of some group to justify the spiele that follows. I expect agents just see LinkedIn as cheaper than Monster.com andsimilar and LinkedIn has obliged them with tools which mine the data. That might be great for agents and LinkedIn but it makes me quite averse from using the service at all.

  57. The recruiters don't exist either by roc97007 · · Score: 3, Informative

    I've found that many of the recruiters aren't real either. A high percentage originate offshore, have some obscure short-term contracting job a long way from your current position and want some kind of handling fee from you. It's this century's 419 scam.

    My adventure began when my company announced outsourcing a few years back. I ended up transferring to another group and staying on, but for about a year I explored all those annoying recruiter emails and cold calls. More than half of them did not sound real (for a lot of the same reasons a 419 scam doesn't sound real -- unlikely profits, terrible writing skills, difficult to understand on the phone, obviously no technical or recruiting skills) and it eventually came down to wanting a handling fee from me to process the job application. Now, maybe somewhere there are recruiters that operate this way, but my experience has been that legitimate recruiters charge the company, not the recruit. Buyer beware.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    1. Re:The recruiters don't exist either by Anonymous Coward · · Score: 0

      Yep, absolutely... candidates should never get asked for money. With DeveloperAuction, we took it a step further and are even offering a 20% cash back on our fee to engineers, therefore writing them a $3000-$6000 check on their first day at a new job.

  58. Why permanent employment wins - for most by sethstorm · · Score: 1

    Contract/consulting work ends up costing more for the individual(where it effectively nullifies the advantage) and removes the ability to tap into the scale and knowledge of an established organization. In addition, it removes the ability to effectively plan for the long-term.

    On the other hand, practicing career monogamy, as close as possible, sidesteps the issues as indicated in the article.

    --
    Twitter supports and protects racists - by smearing their critics with the "Hate Speech" label.
  59. GitHub is crap by Anonymous Coward · · Score: 0

    I agree, github is the facebook for coders looking for dates. I don't understand the draw. I want my code earning money, not being freely given away.

    I do send patches to F/LOSS projects, occassionally.

    Most of the code I've written over the years cannot be released. It isn't mine. I was a worker for hire, hence the code was owned by the company or a government. Some was flight control code that can never be released.

    OTOH, I don't know javascript and don't ever plan to learn it. If I wanted to learn javascript, I'd join a popular F/LOSS project creating javascript libraries.

    Lastly, I'm retired now, so money is not something I worry about. I retired a few years ago at age 42. I'm not god-wealthy, but I'll never worry about money again. I spent 2 months overseas this year, so far, traveling in 3-4 star hotels. Not on the cheap.

    There is more to life than some job, but doing something really cool in your life IS great. I've done that. You've seen my work, but less than 100 people in the world have ever used my "life changing" code directly. I'm positive.

    For fun, I'm in a free Ruby-on-Rails class taught by the local Rubist group. I have a similar background to you, but would say Ruby has subtlties that you do not appreciate. Hacking something together in ruby is easy. Creating a work of art in Ruby is harder. Or perhaps I'm not as good at coding as you.

  60. Engineer != Computer Programmer by Anonymous Coward · · Score: 0

    Some of us who are real, actual engineers must remind all of you that Comp Sci is not engineering! Being a software engineer requires one to actually have engineering knowledge. Engineering = applied physics; comp sci = applied math. Big difference.

  61. Re:Click-whoring post. How could this get approved by sco08y · · Score: 1

    Is that all we aspire to be now here at /.? Just a news aggregator? Oh, how we have fallen!

    Don't forget the shitty book reviews!