Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Reference Checks Can Go Wrong

holloway.com

Post reply on HN
Print view View original

21–30 of 31 posts

Re: Reference Checks Can Go Wrong

#21

Post by kop316 »

clubm8 wrote: post #8

Wow, a single offhand comment could doom a candidate from ever being hired? I wish the same high standard applied to companies interacting with candidates. I've had a Google engineer literally scream at me in an interview. I've also had their recruiters reach out to me for a role, schedule an interview that seemed to go well, then completely ghost me. I do not judge a company that doesn't hire me, even if they don't…

It does apply to companies. Its called people just won't apply there. However, those people don't make blog posts about it.

For example, if I look for a new job, there is no way I will apply to Google (I say if because I see no reason to look for a new job).

Re: Reference Checks Can Go Wrong

#22

Post by CM30 »

Over here in Europe, your references generally don't say very much about you beyond confirming you did indeed work for that company and how long you actually worked there for.

This is to avoid issues like in the article, which can apparently leave the referee open to legal action if the candidate can say the bad reference cost them a job offer or something similar.

Is that different in the US? Do references usually mention the negatives about an applicant as well?

Re: Reference Checks Can Go Wrong

#23

Post by notus »

m463 wrote: post #18
notus wrote: post #4

I haven't had a reference check in a long time. The last company that asked for them didn't even check them. Any hiring people out there feel that reference checks provide any meaningful insight?

On the other hand, I agreed when a friend asked if I could be a reference for him. I got called, sang his praises only to be asked, "Are you looking for any opportunities ..." Recruiting off the reference list is a shitty thing to do.

Seems only shitty if they are recruiting you to place your friend. Otherwise it could be read as, "hey these two developers seem to like each other and have worked together and we need more people". It could feel like a safer bet to hire people you know will get along.

Re: Reference Checks Can Go Wrong

#25

Post by x0x0 »

influx wrote: post #19
RcouF1uZ4gsC wrote: post #14

> Google was his number one choice, but he had to decide whether it was safe to reject the other offers he had. He started to press me more, “Jose, I need certainty. I need to know that I’m going to get this offer.” So I said, “Look, I’m sure you’re going to get the offer. My recommendation is that you wait.” The candidate learned a very valuable lesson: Never believe any assurances that the recruiter gives you about…

Just so folks know you can sign an offer and later retract if another position comes up. It’s relatively common.

Only assholes do it though.

Because when my preferred candidate signs, I tell other candidates no.

If you have any respect for people, you don't do this stuff.

Re: Reference Checks Can Go Wrong

#26

Post by saghm »

notus wrote: post #23
m463 wrote: post #18

Earlier quoted context omitted.

On the other hand, I agreed when a friend asked if I could be a reference for him. I got called, sang his praises only to be asked, "Are you looking for any opportunities ..." Recruiting off the reference list is a shitty thing to do.

Seems only shitty if they are recruiting you to place your friend. Otherwise it could be read as, "hey these two developers seem to like each other and have worked together and we need more people". It could feel like a safer bet to hire people you know will get along.

Sure, but this discourages people who would otherwise be willing to provide references; if someone is willing to freely give you their time to talk to you about one of your candidates, it seems courteous not to potentially waste more of it by giving them an unsolicited offer.

Re: Reference Checks Can Go Wrong

#27

Post by pkaye »

CM30 wrote: post #22

Over here in Europe, your references generally don't say very much about you beyond confirming you did indeed work for that company and how long you actually worked there for. This is to avoid issues like in the article, which can apparently leave the referee open to legal action if the candidate can say the bad reference cost them a job offer or something similar. Is that different in the US? Do references usually m…

If the reference still works at that company, typically the HR will restrict information to confirming period of employment and the title. They don't want to deal with the legal risks. However if the reference is no longer at that company I guess they could be very open.

Re: Reference Checks Can Go Wrong

#28

Post by clubm8 »

throwawaygoogs wrote: post #20

Many years ago, I was approached by a Google recruiter for a position. After a couple of phone screens and a brief onsite, I returned for a ~4 hour set of interviews. After the last interview, with someone who would have been my peer if hired, she starts asking me about my background: where I'm from, what I studied in college, and if I was Jewish (!?). I believe she was Jewish and she said this in a fairly congenial…

Just so you know, something like that would possibly lead to a settlement or something (not a lawyer).

It's my understanding you take findings of fact to juries - which costs companies money to send lawyers to.

The woman would be put under oath (deposed), and probably admit it (I'd hope). But regardless it might still go to trial, and thus they might deem it logical to give a fraction of that as a settlement.

Re: Reference Checks Can Go Wrong

#29

Post by cozos »

rabidrat wrote: post #9

If you can't give a 100% positive reference, tell the person before they include you as a reference. Then when giving a reference, make sure it is 100% positive. Google (and in fact, most companies) only want to hire candidates who appear flawless. To me, "appears flawless" is a red flag itself, but I think hiring committees see any potential negative as possibly the tip of a terrible iceberg. So even though we all w…

What about when they ask "what is this person's biggest weakness"?

Re: Reference Checks Can Go Wrong

#30

Post by ohyes »

cozos wrote: post #29
rabidrat wrote: post #9

If you can't give a 100% positive reference, tell the person before they include you as a reference. Then when giving a reference, make sure it is 100% positive. Google (and in fact, most companies) only want to hire candidates who appear flawless. To me, "appears flawless" is a red flag itself, but I think hiring committees see any potential negative as possibly the tip of a terrible iceberg. So even though we all w…

What about when they ask "what is this person's biggest weakness"?

They’re too nice and they work too hard.
Post reply on HN