Live data from Hacker News

The Recruiter Honeypot

ewherry.com

131–140 of 162 posts

Re: The Recruiter Honeypot

#131
post #95

Earlier quoted context omitted.

"Between linked in, google, your company's about page, github and twitter accounts, you can already figure this out in ten minutes flat" I don't think that's true at all. Some of the best engineers I've worked with have had very small online footprints (they're too busy building awesome things at their company to spend much time on Twitter etc). Now that I'm responsible for hiring, I consider knowledge of that kind o…

I understand using github/twitter a lot if you're a developer. When you work on something you might want to get some immediate feedback/testers on it. Yet still, linkedin (even though useful) scares me away a little bit. Each single time I get back, I see more and more people inventing longer and more exotic job names and descriptions, pitching around with some void statements and uploading their pictures in suits.

My problem with LinkedIn is other people. People want me to say I know them when I don't (hey, networking!). People want me to recommend them when I have only seen them in the hallway and don't even know what they do.

I am very conservative about these things. Does LinkedIn's own model disagree? Does it push people towards larger networks, instead of smaller, higher-value ones?

Am I doing it wrong, or is (seemingly) everyone else?

Re: The Recruiter Honeypot

#132
post #35

>In addition to pings from too-familiar recruiters, there were two cases that left me especially uneasy. In the first case, a former recruiting agency tried to poach Pete London and then 15 minutes later, wrote to me offering recruiting services! I was being pulled on both ends! What did you expect them to do? It's not even that scummy. It's their business model. I also feel that no poaching agreements are also bulls…

> I haven't had to make my life depend on employees as of yet

And that's where your opinion comes from.

To be absolutely clear, I am not putting you down. I am merely stating what I believe to be a fact.

I see a lot of opinions on HN that obviously come from people who have never actually run a business. Of course, everyone is entitled to an opinion with the caveat that opinions loose a lot of validity when they are not backed by "skin in the game".

Bringing an employee onboard is an expensive process. The search itself can be expensive. If you found the employee through an agency you owe the agency a finder's fee. This typically runs from 15% and could be as high as 50% of the employee's salary. To put numbers to that, if you pay someone $100K and the agency charges 25%, you, the employer, owe them $25K.

Of course, it doesn't stop there. There's a lot more to employee compensation than the agreed-upon salary and recruiting costs. A quick Google search located this calculator:

http://www.artlogic.com/resources/employee-cost-calculator/i...

Using that as a reasonable reference I calculated that, if you keep your $100K/year employee for three years your annual cost is $150K per year.

If, however, you only keep them for one year (change "Expected term of employment" to "1") the cost goes up to $170K per year.

If we look at a $150K/year employee who leaves in one year the cost of that employee sits at around $240K.

Even this doesn't paint the entire picture. Bringing someone onboard takes work and will definitely consume clock cycles. More than one team member is likely to be involved in the on-boarding process. Overall productivity will be affected during this period until the new hire comes-up to speed and can "solo" if you will. The effort isn't trivial at all and it costs thousands of dollars for every hire.

There's also a hidden "cost" which takes the form of internal competitive data that you have to trust your employees with. Nobody thinks that this is a cost until you go through the experience of training someone for months only to have them go work for a direct competitor. These things do happen, and believe me when I say that it never sits well. At that point thin ethical walls protect you from a competitor gaining a leg-up through ill-gotten insight. This very directly equates to money.

The cost of poaching by --presumably-- the very agency you might be working with is also not trivial. You just dedicated a ton of money and time to bring someone onboard and the agency convinces him/her to go elsewhere. Now you are left with a hole to fill, which will take time and money. During that time team productivity will take a hit, product delivery will suffer and you will be distracted away from product and business development in an effort to fill the hole. I can't put a precise number on this but believe me when I say that it ain't cheap.

So, yes, anti-poaching is fair and just. For some it takes going through the pain of having this happen once or twice to understand the concept.

Re: The Recruiter Honeypot

#133
post #90
post #77

Earlier quoted context omitted.

No poaching agreements are not bullshit - you are giving them privileged information (who your best people are) and in exchange you're expecting them to use that information only for the purpose directed. It's similar to an NDA. Nothing bullshit about it.

> you are giving them privileged information (who your best people are) Between linked in, google, your company's about page, github and twitter accounts, you can already figure this out in ten minutes flat. You don't even need to know that in order to recruit people. -- I feel that NDAs are kind of bullshit too, but they're typically not as expressly oppressive. Unless they stretch into noncompetes, which are incred…

care to elaborate exactly how you accomplish this in 10 min? or any other time period?

out of all the great developers i know, 1 has a technical blog (and he updates it very infrequently). Also, how do you gauge if someone is a star based on their twitter or linked in profiles?

Re: The Recruiter Honeypot

#134

Earlier quoted context omitted.

Well, a lot of recruiters present themselves to employers as helping with their recruitment problems, rather than exacerbating them. The "rational" thing for a recruiter to do is to post fake jobs with huge salaries to jobs boards to get in resumes; and to offload filtering for quality onto clients so as to get more volume through; to shop resumes around clients in descending salary order so lower paying places only…

Everything you mention I kind of consider par for the course. How would you even know if your recruiter wasn't doing that? To expect otherwise, I think, is a little naive. The economics of the recruiting business, as you pointed out, reward behaviour ranging from predatory to scummy. The best you can hope for is the guys who are merely sharks, and not scumbags. Yet, the negative aspect you mention, is still contingen…

I'm not in recruitment myself, and I agree that ideally you want your employees not to leave even when contacted by a recruiter!

I assume the idea behind refusing to work with recruiters who have been unethical in the past is to create a disincentive, in the hopes of reforming the economics of recruiting so you can get recruiters who will work with you rather than against you.

You'd imagine there would be some recruiters who would aim to behave ethically and to cultivate a reputation for being ethical, as that reputation would be valuable to a recruiter in terms of getting clients.

The one time I was job-hunting I saw some pretty unethical stuff - I once had a recruiter e-mail me a programming test along with a solution another candidate had submitted, and almost every recruiter asked for a summary of technical interview questions so they could brief other candidates. I would have thought using unethical recruiters would actively hinder your recruitment process - so there'd be no market for their services.

I mean, evidently it doesn't work that way, but I think that's the aim of refusing to work with certain recruiters.

Re: The Recruiter Honeypot

#135
post #87
post #83

> We had standard 18-month no-poach restrictions with all of our contractors that specified that those recruiters were not allowed to contact Meebo employees within 18 months of our contract expiring Whoa, wasn't there just a lawsuit where no-poach deals were determined highly illegal?

Much different circumstance (more collusion) if you are thinking of the Google/Apple/Intel lawsuit: "Apple, Google, Intel fail to dismiss staff-poaching lawsuit | Reuters" http://www.reuters.com/article/2012/04/19/us-apple-poaching-... Or Google: https://www.google.com/search?sugexp=chrome,mod=1&source...

Different circumstances, but still illegal in California because it restricts the freedom of employment of Meebo's employees.

No-poaching clauses are illegal in California, but poaching clauses can contain "referral fees" under which the poaching company must pay the original employer a substantial amount of money (usually, a year's salary of the employee poached) if they hire one of its employees during or within a year after the end of the contract period.

Re: The Recruiter Honeypot

#136
post #35

>In addition to pings from too-familiar recruiters, there were two cases that left me especially uneasy. In the first case, a former recruiting agency tried to poach Pete London and then 15 minutes later, wrote to me offering recruiting services! I was being pulled on both ends! What did you expect them to do? It's not even that scummy. It's their business model. I also feel that no poaching agreements are also bulls…

> I haven't had to make my life depend on employees as of yet And that's where your opinion comes from. To be absolutely clear, I am not putting you down. I am merely stating what I believe to be a fact. I see a lot of opinions on HN that obviously come from people who have never actually run a business. Of course, everyone is entitled to an opinion with the caveat that opinions loose a lot of validity when they are…

An employee that leaves after a year has decided that they do not want to work for you. This employee is sacrificing a year's worth of work mastering your processes, environment, and code base in order to go start over somewhere else where they need to learn a new code base.

A couple thousand dollars isn't enough to convince most people to start over- something about their current work place made leaving seem attractive. Either the job does not fit them well or have reasonable paths for advancement (both from a development and career perspective), you are underpaying the employee, the work/social environment is bad, or something significant in their personal life has changed (graduating college, spouse got a job somewhere else, ect).

Poaching isn't unfair. You never have any guarentee for how long an employee will work for you, just as your employees have no guarentee they will still have their job tomorrow. The problem in the above situation isn't poaching; the problem is the employee wanted to leave.

Re: The Recruiter Honeypot

#137

Earlier quoted context omitted.

I'm a full time freelancer. I work on several projects at a time, from large companies to startups, and most of them I only give 10-15 hours a week to. You can get a lot done in 15 hours a week if you put your mind to it. The trick in this case would really be the scheduling, 15 hours a week all done after a normal job schedule (say after 6pm) would likely not jive as well, and your productivity would not be nearly a…

My question and same to @bartonfink is still what is the work? If I am say design and build a rest backend for a company, and its say two months work at 45 hrs a week, doing 15 hrs a week telling them it will take six months cos I have other clients is a sure way not to get the gig So I amwondering what the actual meat of the work you do is? How did you land the work - is it maintenance from past fulltime gigs, is it…

the work is designing and building web applications. almost all coding, a small amount of training/consulting. generally i come into projects that were already built at least part way by someone else and need to be fixed up and have features added. though i am also doing one right now from the ground up with a small team. most of my projects involve small remote teams as well.

right now i work with 2 startups and 1 large company, as well as do occasional consulting with another large company (this is usually less than 5 hours every month). i'm all about simplicity and breaking things down into small pieces, so on all projects i am able to deliver and launch features regularly with 10-20 hrs of work a week on each. my total billable hours for the week usually are in the 40ish range.

i've found all the work through referrals pretty much, so i can't say exactly how to find it for others. i will say put as much as you can out in open source, that is the best "sales" technique i've had (often "referrals" have come from someone i've only interacted with in the open source community). also, be consistent with your deliveries, and open and honest about scheduling, as well as when something is going to take longer than you estimated. surprisingly few contractors are good at communication it seems. often i come into projects for people who were abandoned by a developer and even when they were working together only got spotty communication from that dev.

Re: The Recruiter Honeypot

#138
post #91

"Lesson 1: Recruiters rely exclusively upon LinkedIn". You might be thinking, “Really? This is obvious!” Uh... No, I wasn't thinking that, since there's a ton of places for recruiters to find candidates and LinkedIn is only one of them. Is this some kind of viral marketing piece for LinkedIn or something? I have gotten maybe 6 recruiting messages on LinkedIn in my life. I finally deleted my account after the password…

Then you must be in a tiny minority. I get an LinkedIn message every other day, pretty much. I closed my Monster account years ago after getting e-mails of insanely inaccurate matches in cities thousands of miles away.

Yeah, LinkedIn is awesome, it's the future of finding a job second only to your "connections".

Re: The Recruiter Honeypot

#139
post #77

Earlier quoted context omitted.

No poaching agreements are not bullshit - you are giving them privileged information (who your best people are) and in exchange you're expecting them to use that information only for the purpose directed. It's similar to an NDA. Nothing bullshit about it.

Poaching is a myth. You assume the only reason your folks are working for you, is they don't know about a better deal elsewhere? Every sensible employee should regard every paycheck as a renewed offer of employment. If a better deal exists, its their choice, not yours, whether they stay or not. Your only real option is to treat employees well, make sure they know you appreciate their talents, and try to generate some…

Good post. Loyalty in the workplace is also nonsense. We're (mostly) all capitalists here we should act like it. Never ever stay at a company because you "love it" or some childish notion of "loyalty". You should be there because it's the best allocation of your resource of time/knowledge.

I don't care about the company I work for and I feel no more loyalty to them then I do an online electronics store. Having said that, my employment has two goals: making me money now and making me money later. This means that I won't leave the company I'm at if someone else offers me $2 more a year. There are a lot of factors that make up my market value and all of them have to be considered. I have left one company to work at another at lower pay because I knew that move would put me in a better position several years down the road, i.e. would increase my market value. I said before I didn't care about companies I work for. Emotionally that's true. Professionally, of course I want them to do well because them failing hurts the value of the time I spent there. I also want to stay long enough to accomplish big things that I can talk about to the next place I interview for.

If you go into a relationship where you are more emotionally attached to them then they are to you you're going to get hurt. And a company is just one downsizing away from letting you go no matter how much they make you feel like "family".

Re: The Recruiter Honeypot

#140
post #35

>In addition to pings from too-familiar recruiters, there were two cases that left me especially uneasy. In the first case, a former recruiting agency tried to poach Pete London and then 15 minutes later, wrote to me offering recruiting services! I was being pulled on both ends! What did you expect them to do? It's not even that scummy. It's their business model. I also feel that no poaching agreements are also bulls…

> I haven't had to make my life depend on employees as of yet And that's where your opinion comes from. To be absolutely clear, I am not putting you down. I am merely stating what I believe to be a fact. I see a lot of opinions on HN that obviously come from people who have never actually run a business. Of course, everyone is entitled to an opinion with the caveat that opinions loose a lot of validity when they are…

I've employed people and hope to again soon and the conclusion to your post is 100% wrong. All the costs you mention are your problem. Finding talent is expensive. But it's expensive to everyone. You're spending all that money to find someone willing to invest their precious time and skill/knowledge with you instead of spending that value some other way. That doesn't make them your slave. You don't get any special rights because you spent money.

If you want to keep people give them a compelling reason to stay. Collusionary practices like anti-poaching, Noncompetes and so on are not fair and just. They are immoral and bad for the markets. Engaging in any of these practices should come with hefty fines.

Post reply on HN