5 ms·
How to stop recruiters posing as applicants
- jiggy2011 14y agoYep, because a recruiter couldn't pay someone $5 to beat this.
- bdcravens 14y agoI'm sure this is far more complicated than the full-blown mobile apps I see advertised for $100 by developers overseas.
- civilian 14y agoDevelopers often cost $100/hr. It'd take at least half an hour to teach a recruiter how to use Postman. I think you're off by an order of magnitude. It also has the precondition that the recruiter is willing to learn.
- jiggy2011 14y agoJust wrote a python script to do this in ~3 minutes (will resist urge to post source code) for recruiters who know how to use the command line. Would take me another ~3-5 to build a web front-end in flask. So let's call it 10 minutes all in. At $100 per hour that is $16. And you can get developers who would be capable of doing this for way less than $100 per hour (like $10 per hour) so $5 is about right.
- jon-wood 14y agoIf a recruiter can get past this then best of luck to them. We still won't pay the usual ridiculous hiring fees, but we'll at least be willing to listen!
- lucb1e 14y agoRecruiters pose as applicants? What for?
- deleted 14y ago[deleted]
- bdcravens 14y agoTo communicate with a hiring manager that otherwise might not give them the time of day. Flip side of posting fake jobs to get resumes.
- lucb1e 14y agoI'm afraid I still don't get it. A recruiter wants to contact someone managing hiring in some company (or his own company)? How does posting a fake application help, it'll be found out in no-time..?
- flexxaeon 14y agoI don't think they pose as applicants as much as they use the contact method (usually email) to solicit their services, even sometimes ignoring when the hiring company specifically says "please no recruiters." If they are posing, it would be pretty easy as well, as they could send in resumes & CV's of job seekers they represent. Recruiters also pose as companies posting 'jobs', and from what I've seen when looking for gigs it's likely they solicit in the other direction as well. How low they sink, who knows.
- deleted 14y ago[deleted]
- inerte 14y agoThe recruiter will probably get the full name, position and true email address of the hiring manager. Plus, if the charade goes a few more emails, more details about the job.
- cpeterso 14y agoThe recruiter may be representing a "stable" of clients (programmers) looking for jobs. The recruiter would want to talk to the hiring manager to sell them on (any of) their clients (shotgun approach), without figuring out which resumes might actually be a good fit. Alternatively, the recruiter might want more details from the hiring manager about the open position, so they could hunt for applicants to bring back to the hiring manager.
- t0 14y agoI've seen a few of these before. Here's an interesting one if you can figure it out. http://web.archive.org/web/20120722010228/http://forrst.com/jobs/details/305-PUT_thetalented_me_at_work_Social_Media_Developer http://web.archive.org/web/20120722010228/http://forrst.com/...
- joshmcmillan 14y agoHa, that's a clever one.
- tlrobinson 14y agoI'm not sure I'd be able to get over their incorrect usage of the PUT verb.
- runarb 14y agoGoogle had a nice one back in 2004 also: http://articles.businessinsider.com/2011-07-22/tech/30049105_1_innovation-problem-website http://articles.businessinsider.com/2011-07-22/tech/30049105... But probably wouldn't work so good today. The first one to find the solution would probably post it on twitter, then the recruiters could follow :)
- jon-wood 14y agoGreat example - Google's billboard ads were the inspiration when I put this together.
- downandout 14y agoI wasn't aware that this was even a problem. I would think that using a tactic like this would immediately turn any contacts they made into enemies, rendering this a futile exercise. They also effectively made an API for anyone that feels like flooding them with millions of applications containing random data. All in all, like a cold medication that happens to cause cancer, I'd say this is a solution to a small problem that opens the door to dramatically larger problems.
- hkmurakami 14y agoI'm guessing the logic might be that there's a certain percentage chance that once communications are open with the hiring manager, the recruiter may be able to talk his/her way into getting the hiring manager to look at some of the recruiter's candidates. From an EV perspective: Contacting company as a recruiter: 0% or very low % of success Posing as an applicant at first: - x% chance of initial reply from hiring manager - y% chance of "conversion" of manager into "client" - x*y is perceived to be greater than other options I imagine that the recruiter can either, (a) submit a "real" resume that he/she has, or (b) submit a "fake" resume that looks really good, eliciting a response, then bait and switching to a different "real" candidate, saying that the initial one is no longer available.
- jon-wood 14y agoIt isn't a huge problem, but it was enough of a problem to be annoying, and I had an afternoon to spare so threw this together with the hope it would also attract some attention from inquisitive hackers. You could indeed flood us with applications using it, but if you did we could also screen them out pretty easily, or just turn the service off.
- GhotiFish 14y agoyou are really convinced of this. How is this any different from just having an online form to fill out? The only difference I can see is the web browser is filling out post details, rather than you just crafting it manually. Are you a recruiter? Don't be sour grapes :P
- diminoten 14y agoAm I the only one who finds the phrase "json encoded hash"... inaccurate? Maybe someone can enlighten me, but is JSON really an "encoding"? And what exactly do they mean by "hash"? They want the JSON to be a fixed length? How would you like my JSON hashed? How are you going to pull my data out of the hash? And as a 'field' called response? Don't they mean, "as the value of a field called response"? Is this part of the test, deciphering the jargon soup? Because if I'm understanding this correctly, a bunch of terms just got misused in a very short sentence, which would put me off of applying here.
- lysol 14y agoIt's not. It's a serialized object.
- diminoten 14y agoThe JSON object is serialized? How?
- deleted 14y ago[deleted]
- gburt 14y agoIt's turned in to plain text that can be re-created in to the objects. From Wikipedia [1]: "[...] serialization is the process of translating data structures or object state into a format that can be stored (for example, in a file or memory buffer, or transmitted across a network connection link) and "resurrected" later in the same or another computer environment" [1] http://en.wikipedia.org/wiki/Serialization http://en.wikipedia.org/wiki/Serialization
- mattchamb 14y agoI also cant make sense of it. Do they want me to send them a hash of all my details? I don't think that would be very useful in letting them contact me.
- 14y ago
- asveikau 14y agoWhat I see here is one group of people (the company with the hiring page) doing the standard "fun/playful/lightweight engineering task" that people have been doing for years to filter applicants. Then some unrelated person tweets that this will prevent recruiters posing as applicants. Now the HN thread is assuming this is the only purpose and questioning if this problem is worth it. Has it not occurred to anyone that what one dude says on twitter is the primary purpose might not be so?
- greenyoda 14y agoExactly. This is just a web-oriented version of "fizz-buzz".
- downandout 14y agoWhether or not they had recruiters posing as applicants in mind when designing this, it doesn't change the fact that this particular task is ill advised. The first person that becomes remotely disenchanted with them will flood them with random applications. I'd bet almost anything that they will have to scrap this exercise and start over.
- shubb 14y agoI don't see how it is more open to abuse than just giving an email address. You could send someone 1000 messages if you wanted.
- asveikau 14y agoIs the ability to hammer the POST interface really much worse than the ability to send lots of mails to a jobs@company.com alias? Sure, maybe people's email configurations are better equipped to deal with spam, but you can send email in a script, too.
- rickhanlonii 14y agoI disagree. Were it to become a problem, it would be trivial to deal with an application flood. Among many options, provide a unique 'application key' on the instructions page which expires after first use. If you're really concerned, or it becomes a problem, just add a Captcha-like requirement to get your application key. Besides, as asveikau points out, the risk is no different than any other application acceptance system. Take applications by mail? Fine, I'll buy a roll of stamps and make a few stops to the post office.
- shubb 14y agoJust like you wouldn't make it hard to pay for your product, I think making it hard to apply for jobs at your company is a bad move. Because most people are applying to a 'better' job than the one they have now (Cooler? More money? More responsibility?), they know that most initial applications will come to nothing. If you believe your CV will get a reply 1/5th of the time, spending more than the 5 minutes it takes to send over a slightly customized CV is foolish. There are a lot of other people that don't require this much effort. Time is better spent writing to them. This is going to get plenty of replies, because it's on Hacker News, but if it was getting the traffic more organically (i.e. if this was widespread), I'm not sure it would get a single one. Yeah sure, for the applicant he wants, this is solved with, notepad, curl, 10 minutes, but it's still more effort than emailing it to his rival.
- jon-wood 14y agoWe put this in place to automate the screening of applicants after our first round of advertising yielded a glut of people who could barely write code, and no one who was actually worth taking past a phone screen. Since then we've been receiving applications of a far higher calibre, and many applicants who went onto a full interview after phone screening. We definitely receive fewer applicants, but that's a trade off we're willing to make.
- jon-wood 14y agoWell this would explain why my phone has been going crazy all evening! I'm the person who put this process in place for Hubbub (which incidently is a great place to work, you should apply). I'll quickly skim through comments and post some answers now, but it's 0014 here so I'll probably catch up with the rest tomorrow. If you have any questions feel free to drop us a line on developers@hubbub.co.uk (unless you're a recruiter!) As a final note, we have much more detail at http://developers.hubbub.co.uk/ http://developers.hubbub.co.uk/, including information about the year's supply of bacon on offer to both successful applicants and the people who referred them.
- GhotiFish 14y agoYou mean to tell me that if I work for you, you'll supply me with bacon, for a year? I can't tell if you are making a pun. If you are, it's a good pun.
- jon-wood 14y agoI mean literally. One of the perks is a year's supply of bacon, as in smoked back bacon from pigs. Specifically some of the best bred pigs in the UK!
- windsurfer 14y agoYour post advocates a (X) technical ( ) legislative ( ) market-based ( ) vigilante approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.) ( ) Spammers can easily use it to harvest email addresses ( ) Mailing lists and other legitimate email uses would be affected ( ) No one will be able to find the guy or collect the money ( ) It is defenseless against brute force attacks (X) It will stop spam for two weeks and then we'll be stuck with it ( ) Users of email will not put up with it ( ) Microsoft will not put up with it ( ) The police will not put up with it ( ) Requires too much cooperation from spammers ( ) Requires immediate total cooperation from everybody at once (X) Many email users cannot afford to lose business or alienate potential employers ( ) Spammers don't care about invalid addresses in their lists ( ) Anyone could anonymously destroy anyone else's career or business Specifically, your plan fails to account for ( ) Laws expressly prohibiting it ( ) Lack of centrally controlling authority for email ( ) Open relays in foreign countries ( ) Ease of searching tiny alphanumeric address space of all email addresses (X) Asshats ( ) Jurisdictional problems ( ) Unpopularity of weird new taxes ( ) Public reluctance to accept weird new forms of money (X) Huge existing software investment in SMTP ( ) Susceptibility of protocols other than SMTP to attack ( ) Willingness of users to install OS patches received by email ( ) Armies of worm riddled broadband-connected Windows boxes (X) Eternal arms race involved in all filtering approaches (X) Extreme profitability of spam ( ) Joe jobs and/or identity theft ( ) Technically illiterate politicians ( ) Extreme stupidity on the part of people who do business with spammers (X) Dishonesty on the part of spammers themselves ( ) Bandwidth costs that are unaffected by client filtering ( ) Outlook and the following philosophical objections may also apply: (X) Ideas similar to yours are easy to come up with, yet none have ever been shown practical ( ) Any scheme based on opt-out is unacceptable ( ) SMTP headers should not be the subject of legislation ( ) Blacklists suck ( ) Whitelists suck ( ) We should be able to talk about Viagra without being censored ( ) Countermeasures should not involve wire fraud or credit card fraud ( ) Countermeasures should not involve sabotage of public networks ( ) Countermeasures must work if phased in gradually ( ) Sending email should be free ( ) Why should we have to trust you and your servers? ( ) Incompatiblity with open source or open source licenses ( ) Feel-good measures do nothing to solve the problem ( ) Temporary/one-time email addresses are cumbersome ( ) I don't want the government reading my email ( ) Killing them that way is not slow and painful enough Furthermore, this is what I think about you: (X) Sorry dude, but I don't think it would work. ( ) This is a stupid idea, and you're a stupid person for suggesting it. ( ) Nice try, assh0le! I'm going to find out where you live and burn your house down!
- leeny 14y agoWait, why do recruiters pose as applicants? Is this a common problem? Also, Parse (and a few other companies whose names escape me now) have been doing this for a while. https://parse.com/jobs https://parse.com/jobs (scroll down to "Apply to Parse!")
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- aquarion 14y agoA few jobs back we did something similar, and posted in the ad that people could apply by solving http://unhelpfulclue.aqxs.net/lookup.php http://unhelpfulclue.aqxs.net/lookup.php (Resulting email changed) Technical tests before screening appear to be getting more common. Currently job-seeking, I'm getting a little frustrated by the number of times I have to prove that I can actually implement variants of Fizz Buzz. It'd be nice if I could submit a link to a previously completed Codility test or something... (Yeah, it'd be nice if they accepted Github links or something as proof of technical competence, but as someone on the other side I don't really want to have to validate a hundred random OSS projects and check the province of the code in them)