I think the original author should name everyone involved. I understand why he didn't, but people can only get away with this shit because they do it anonymously and no one talks to each other.
This is a much less extreme example, but years ago my former landlord threatened to kill me over a small claims court case (http://jakeseliger.com/2010/08/28/dont-rent-an-apartment-fro... if you're curious) and I wrote a post about what happened using his real name. Perhaps not surprisingly, since then I've gotten two emails thanking me for the story—one from someone who'd rented from him and had a bad experience and one from someone who avoided him.
In general it's a good idea to keep non-public conversations non-public, but when the people starting those conversations rely on them in order to do nasty stuff the principle should no longer apply.
Be careful giving this advice.
This only worked because A) (minor) you filed a police report and B) (major) he didn't have enough money to drag you through a serious defamation lawsuit.
If he decided to drag you through a defamation lawsuit, you would likely have lost because you wouldn't have had enough resources to defend aggressively.
It's good to out bad actors, but do make sure that you aren't putting yourself in a vulnerable situtation.
Unless you're in America, land of the dysfunctional legal system, home of the brave.
Remember the British guy with the Nazi fetish? The tabloid that published that story lost even though it was true. In other countries (notoriously India), criticizing a government employee's performance is defamation (even if true).
Edit: Looks like Canada also allows for truth as a complete defense to defamation. That makes two nations out of 180+.
As with US and Canada 'truth' is a defence against defamation here also: http://www.medialawjournal.co.nz/?page_id=273
"The publisher will succeed with a defence of truth if it can prove, on the balance of probabilities, that the story was true. Minor errors may be excused, but not those that go to the heart of the defamatory sting or stings."
So guess you can add NZ to the list, but there are no doubt others - how about France, Australia, Austria.. Senegal?
Perhaps it is actually the UK that is the outlier in this regard?
Citation needed.
If you stuck to reporting facts, how would that put you in danger?
1. It's fairly simple to post a fake review.
2. Yelp has been accused of what amounts to blackmail by offering to hide bad reviews if businesses buy advertising on Yelp.
3. It's not rocket science to see how 1 & 2 could team up
4. There is no objective standard for a good or bad review, so how do you accurately quantify the aggregate? If the restaurant was out of the dish the reviewer wanted because it was a half hour before closing on a busy night, that one star review carries the same weight as someone who legitimately had terrible service, cold food, and got food poisoning.
This amounts to Yelp being nothing more than the yellow pages, in my opinion. I don't see how this would change for other services.
(4) is addressed by volume. That's easier for something like restaurants than apartments or recruiters though.
Also, anyone can post reviews, which the companies take advantage of. We had an HR person at my previous company whose job responsibilities included posting one positive (4-5 star) review of the company per week on Glassdoor and similar sites. As you can imagine, doing so is a much cheaper way of dealing with negative reviews than suing the websites.
Is it possible that Google liked your product and subsequently thought you might be a good hire, but didn't like your product as a potential acquisition? That is where I think the difference lies. Were you contacted as "I'm from Google and we are interested in you", or "I'm from Google and we are interested in your product"? That is a big difference. The fact that you specifically mention "Their recruiters" would lead me to believe it was the former, but if they mention your product (beyond some acknowledgment of it) that might fall into a gray area.
Thousands of people abandon small side projects and independent businesses every year to join companies as an employee. Just because a company is recruiting someone who happens to have some product doesn't necessarily mean that the hiring company has interest in both the person and the product.
In the post above, the whole bit about being from "Google Corporate Development" is shady. We're only hearing one side of the story, but it seems someone at Google is using a famous name and the fuzzy promise of an acquisition to try to trick him into coming to California for a job interview.
I agree that being contacted by "Corp Dev" is shady if there is no intent on a potential acquisition. That said, I don't find it shady at all if a Google recruiter contacts talented technologists who happen to have some sort of side project.
If DHH gets a call from Google, they'd better have interest in Basecamp. If some Ruby dev who has a small product with 500 customers gets a call from Google recruiters (not corp dev), the dev shouldn't assume it's an acquihire situation. There is, as usual, some gray area of course.
If you look at the opening emails from the two Googlers (X and Y) then it's abundantly clear that the emphasis was on, in X's case, the company, and in Y's case, the product.
And more to the point: at no point did they say what a recruiter should say at the opening of any (honest and professionally delivered) cold call. Which is of course: "Hi, I'm Z and I'd like to talk with you about joining the engineering team here at FooBar."
Finally, it's extremely difficult to interpret the fact that they chose to identify themselves as comping from Corporate Development (rather than Recruiting, or even Engineering) as anything other than a (rather clumsy) attempt at misdirection.
Anyone distracting someone who could be spending time on their own business, or billing hourly, with a business offer, should be incredibly concerned about a Lost Opportunity suit. Come up with a way to value the time that you spent, attach it to an opportunity cost, and bam, your dishonest business partner has caused your other business dealings to fail.
I don't want to encourage further abuse of the legal system, but IMO it is an abuse of the legal system to engage in an act you know to be unlawful or harmful, but difficult or costly to enforce.
The emails you are referring to pertain to the linked article, and have nothing to do with my comment here.
If a recruiter's goal is to shave off $5,000 or $10,000 from your ask then they are wasting time because they could likely just as easily find someone who can fill the position at that compensation level.
I only talk to one recruiter. If I want a particular job I know is going I will direct him to it and he will handle any side lining from other recruiters.
Works a treat.
http://blog.alinelerner.com/why-talent-agents-for-engineers-...
what would your top three features be? (in an actual, online agent, actually on your side.)
First off, I can see how you might miss out on a lot of potential clients because you don't know just how good they are. You could reduce this miss rate by getting good at fishing out details from people you approach or who approach you. Even be prepared to write their resumes. I'd recommend having a technical person on staff to assist with the buzzword bingo and alphabet soup.
Second, a lot of people simply might not know how to negotiate a job search, but wouldn't really be lucrative enough to chase as clients. By-the-hour consulting might turn into a decent revenue stream. Then they can come to you in a few years when they are ready to chase the big bucks.
Third, there's a lot of wishful thinking out there that causes seekers to not chase or turn down perfectly good jobs because of that haunting vision of landing that whopper $120K+ job. (in Atlanta) Being able to tactfully talk them into a perfectly good $85K job could work out well for both of you. I've seen lots of really good guys strike out interviewing for those unicorn jobs because the company has ridiculously selective criteria. I know a guy holding out for $110K but doesn't want to go where he could legitimately make that money with his skills, e.g. a Java shop. He spent down his savings and told me it's going to hurt pretty soon if he doesn't find one soon.
One of the things that the recruiter who found me my job did for me was to interact with the company for me. I told him my concerns, and he either talked me through them or relayed them, through the filter of someone whose seen this all before, to the company. Had I had to do this directly with the company, I wouldn't have done so well, and I might have gotten passed over.
When my company wanted to keep me on a contract basis three months after his job was technically over, and I was prepared to walk, I called him, and he calmed everyone down and got the company to bring me on full time. Had I had to negotiate it myself, I might have said something unwise and a bad decision would have been made.
Now that I'm on the other side of the table, I find myself playing the same role my recruiter played for me as far as the interpersonal dynamics is concerned. I talk through his concerns, I discuss the money aspect with him, advocate his case, and protect him from HR bullshit.
I don't see a purely online web agent as bringing any more value to the table than (just another) job board.
Thanks for your input, though my question was specifically to lugg and asked "can you imagine what, if any, part of this could be done purely online". Still, your thoughts on a different subject have been interesting and thanks for them. You can also send me email if you'd like to write more.
- Honed my CV (more like made me rewrite it), it was full of fluff pieces and bullshit that made ME happy. He basically took a red marker to all the things that weren't purely factual and provable (or at least explainable.) He was an ex developer and current on tech so he knew what he was talking about in regards to what needed to be said and what wasn't. This could easily be done online with google docs and a skype call.
- Answered all the dumb questions every developer wants to know but really shouldn't be asking a prospective employer in an initial interview (can I wear shorts and a tshirt? how much $$$? flexitime? holidays? beer on friday? - This would be solved by an FAQ employers could fill out.
- Filtered jobs I'd call awful on anyway (multiple reporting lines, under paying, no source control, one man bands, etc etc This is easy for development, just make sure it passes the joel test.
- Found opportunities that actually match my skill-set (Full stack PHP Developer with javascript tendencies) - Sort of job board style sites attempt to solve this but suck at it pretty badly, because who pays their bills?
- Interview prep happens but its essentially just reminding me to be myself and if I don't have an answer say so. I don't know what would be worth it to you for putting this online but you could certainly do some last minute reminder calls with the candidate and follow up directly afterward to ensure everything went well / any issues can be discussed while they're fresh.
Sorry if that doesn't help much, a lot of it requires a person and a phone, I'd certainly start in those areas though, do things that don't scale n all heh.
Feel free to email me if you want any further info, don't follow HN too much.
If you can afford the travel, come and mingle at some startup events. Berlin is obviously the best city to do that, although Cologne (where I'm located) and, I imagine, Munich/Dusseldorf/Hamburg are pretty good too.
When I hire, I don't think about trying to find more people to interview. Instead, I think about designing the interviewing process such that it's short, simple, and fun for the person being interviewed—because the people who I most want, have the least time and patience for me and the most alternatives, so I have to make choosing to "try my job on" as easy as possible.
When I do this, word spreads (both among those who get hired, and those who don't) that "you may as well go and see if you like them, it's not too much of a hassle" and the result is far more inbound (qualified!) leads, and far less friction in outbound lead-gen.
So it's all a game, don't hate the players, hate the rules. It makes it hard to know when someone is legit though. I think that's one reason why investors are over reliant on their networks, as the signal/noise ratio is too low in SV. "Fake it till you make it" is the motto.
However, I don't think I can complain too much. Without all the hypes, we wouldn't have this favorable job market. Not sure how long it's going to last, but at least it's good for now.
There are no rules. Trying to paint this turd with catchy slogans isn't helpful either.
For example, "don't start a nuclear war" isn't an explicit rule by some world government, but it does seem to be a rule all the world-leaders are implicitly following. For another, "don't appear to be physically weak in prison" is a "rule" that everybody knows, despite no single authority enforcing it. The environment itself—made up of the other players and their incentives—enforce it, through their self-interested reactions.
If I _were_ to do so, it would sound like "There's no point in hating the rules, because the rules don't care. Hate the players, because they are the ones who care enough about them to follow them."
I don't care if these rules are explicit or not; I care that they don't produce the outcome I want. And the people who follow those rules are not absolved by weakness, ignorance, self-interest, or any other excuse in failing to resist those rules.
(There's no rule that says anything done in self-interest is correct. Sometimes it is correct to make sacrifices for others.)
https://www.theinformation.com/Google-Was-Willing-to-Beat-Fa...
(He was also rejected by twitter)
Start collecting pseudonyms and storylines in a github repo? This could make for an entertaining movie script, where a Skynet-like company uses advanced surveillance technology to triage a talent pipeline.
Startups encounter a random obstacle course and are only recruited after clearing a statistical threshold of surviving economIc warfare. When a candidate says no, they are moved to a different level of the game. All the while, the recruiting algos grow smarter as they generate new startup obstacles and observe how the talent responds.
The Exam experimented with this concept, http://m.youtube.com/watch?v=bkdt2Sygew0
This article just seems to be a real world example of PG's essay this month about "don't talk to corp dev." [1]
If you are a lone engineer, but is capable of making a successful app, you have a certain aptitude for programming. This is useful to google. The recruiter is making a bet that this lone engineer is not business savvy enough to know how much their true worth is, and if the bet worked, google would've been able to low-ball hire a really good engineer. They failed this time, but you don't hear about the times this strategy succeeds, because those 'acqui-hires' might've even been celebrated by the "victim" as success!
And the $300-$500k+ salaries that Google is frequently throwing at engineers these days are worth more than the marginal chance you'll make a multi-million dollar exit event.
So I'd hesitate to call anyone hired by Google a "victim."
It's not the absolute amount that matters - it's how much they are "underpaying".
If the diamond could be worth $10M when polished, but also could be worth $0 because of flaws you can't yet see, and there's only a 20% chance that it will be worth $10M, then $2M is exactly the right amount to take. And in this particular case, I'd take the $2M every time, because that's the exact expected value of 20% odds of a $10M valuation.
And when you have your own company, there is always some level of risk. The chance of $10M may be far less than 20% -- and there may be a 1% chance of $200M.
It's only if you think your diamond has either already been polished to the point of being worth more than $2M, or you feel your own odds of success at polishing are better than 20%, that you should say no to the offer.
The original author believed that, which is perfectly fine. He had previous experience with selling a company, and so he may have even been right.
But those with less experience may actually do well to sell unless someone with more experience is around to tell them they're sitting on a diamond mine that's worth way more than the offer. Or you can roll the dice based on your own appraisal of the odds; that's fine too.
I've actually been in the situation where I did say no to terms I didn't find good enough, but then later the company failed and I ended up owning 100% of nothing. So having them "underpay" for me would have ended up with me owning 40% of something at least, since they were going to fund it to the next level.
It's easy to take a look at the odds and guess wrong -- and it's also easy to be an armchair quarterback and tell people that they should have taken a chance instead of the easy cash. As a result of my experience, I'd likely lean toward the easy cash at this point, but feel free to make your own decisions as you see fit.
If it's a solo founder, and especially if they're not being recruited to work on a similar sort of project, I don't think there's anything to make it an "acqui-hire" instead of a "yo, shut down your company and come work for us".
Please don't feed the troll.
Well, yes, as those places don't employ you.
I find this hard to believe because if you are smart enough to work at Google then you should be smart enough to know your rights. If the harassment is persistent and comes from multiple perpetrators then she can build a timeline to show HR, a lawyer, or the EEOC.
It's a nasty world out there. Such unwelcome outcomes explain why many smart people with legitimate grounds for pressing charges ... choose not to do so.
(I don't know anything about Victoria Lease's situation, just this response had hints of victim blaming)
You're making several assumptions here that are not necessarily founded on reality.
I agree with this article's characterization of it as a scam, as they are pretending to be something they are not. This is manipulative and dishonest. What I experienced was less heinous but had the same elements- misrepresentation, name dropping, attempts at emotional manipulation with tone and timing (the first call being so dead, then enthusiastic in the second- very "HR recruiter", not corp dev.)
Worse, once I'd eventually figure out what was going on, and put one of them off of me, a few weeks later another would show up, with another variation.