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."

73 of 233 comments (clear)

  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 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...

    5. 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.

    6. 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.

    7. 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?)

    8. 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
    9. 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.

    10. 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.

    11. 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).

    12. 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.
    13. 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.
    14. 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 :)

    15. 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.

    16. 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.
    17. 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.

    18. 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.

  2. 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: 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.

    6. 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?

    7. 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
    8. 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.

    9. 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.

    10. 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!"
    11. Re:seriously? not this again by DarwinSurvivor · · Score: 2

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

    12. 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...
    13. 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".

    14. 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.
    15. 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.

  3. 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?
  4. 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.
  5. 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 KZigurs · · Score: 4, Insightful

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

    2. 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.

    3. 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.

    4. 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....

    5. 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.

  6. 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.

  7. 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

  8. 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 /.
  9. 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 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!
    3. 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.
    4. 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
    5. 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.
  10. 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.

  11. 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.
  12. 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
  13. 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.

  14. 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.
  15. 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.

  16. 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.
  17. 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."

  18. 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?

  19. 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.

  20. 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.

  21. 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.
  22. 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
  23. 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
  24. 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.

  25. 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.