Live data from Hacker News

The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

wired.com

71–80 of 96 posts

Re: The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

#71
post #68

Earlier quoted context omitted.

Yes; the background investigation produced a police report which I hadn't mentioned in my application. At the time of the gas station incident, I didn't know that I had just created a paper trail that would damn my background check. On one hand I understand how a discrepancy in the background check would raise concern, but on the other hand I feel that the police report easily shows no wrong doing on my part, and tha…

All of that would likely be true of a regular employer. Probably even would be good enough for the military. But the people you were dealing with, as a rule, don't believe in happenstance, or coincidence. And they absolutely live by attention to detail. I don't know much about your situation, but based on what you've shared, you tripped a lot of alarms.

/shrugs

Well then congrats to the NSA; they successfully weeded out a spazzy dork

Re: The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

#73

Earlier quoted context omitted.

Yeah, I read it several times, and it still came out to me as addressing only the final application. But now that you point it out, it seems more likely to address all applications. Regardless, that's about as far as I got because my two personal experiences with polygraphs tells me they're about on the same level as dowsing rods. "Have you ever used marijuana?" "No", he said, higher than a kite having smoked a bowl…

what kind of job hooks you up to a polygraph to ask if you've used marijuana and doesn't bother to give you a gc/ms screen?

The kind where the management doesn't actually care if you toke up privately, but wants a good excuse to diqualify anyone they don't like for whatever other reasons.

Re: The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

#74
post #31
post #2

And here I thought having to do FizzBuzz for two different interviewers was onerous.

Onerous? If you think 6-20 lines of code is onerous, you really should reconsider your career choice. Polygraphs can produce errors that may be used as a wrongful justification for an employer to dismiss your application. ...on the other hand A fizz buzz application that produces errors _should_ be used as a justification for a potential employer to dismiss you entirely.

It was a joke. Except for the part where I had to do it twice.

Re: The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

#75
post #68

Earlier quoted context omitted.

Yes; the background investigation produced a police report which I hadn't mentioned in my application. At the time of the gas station incident, I didn't know that I had just created a paper trail that would damn my background check. On one hand I understand how a discrepancy in the background check would raise concern, but on the other hand I feel that the police report easily shows no wrong doing on my part, and tha…

All of that would likely be true of a regular employer. Probably even would be good enough for the military. But the people you were dealing with, as a rule, don't believe in happenstance, or coincidence. And they absolutely live by attention to detail. I don't know much about your situation, but based on what you've shared, you tripped a lot of alarms.

Only if the agents do not read the folder.

Forgetting to pay at the pump once in your life can hardly be called criminal behavior.

Re: The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

#77

Earlier quoted context omitted.

...received a phone call from the police telling me to go pay for the gas. I figured it was just an honest mistake and didn't think anything of it So, given that you paid-up for the gas when requested, you didn't intend to permanently deprive the owner of it which suggests that technically it wasn't larceny and could have been sloughed-off as a misunderstanding. Given you were dealing with an NSA interview, sounds li…

>Would you really want to work for an organization that plays those sort of mind games? reply No, I don't anymore. But at the time I was excited for the opportunity

You dodged a bullet.

Re: The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

#78

I once was gassing up at a station, and for whatever reason the card reader on the pump wasn't charging, but would let me pump gas anyways. So me, and everyone else who'd used that pump that day, received a phone call from the police telling me to go pay for the gas. I figured it was just an honest mistake and didn't think anything of it. Fast forward a bit, to where I am undergoing a polygraph examination for the NS…

How did the police get your number?

Re: The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

#79

Earlier quoted context omitted.

That senior devs with decades of experience fail. I've literally seen someone who supposedly wrote firmware for the space shuttle fail fizzbuzz.

If the candidate was verifiably a NASA engineer the person half assed it probably just didn't care. I'm surprised that person just didnt respond with a very intricate set of functions that resulted in a middle finger. That's honestly insulting to use that as a test for a senior. Clearly there was no vetting process prior to a coding evaluation and the hiring process needs a lot of work.

They worked for one of NASA's contractors, not NASA itself.

Have you been involved in the hiring process? Most of the people actively looking for work don't have a job for a reason. It's not 'insulting' to see if you can even vaguely do the job in an interview.

There's only so much vetting you can do before the 'can you vaguely code your way out of a wet paper bag' step.

Also: you didnt used to work in Boulder recently, did you?

Re: The Lie Generator: Inside the Black Mirror World of Polygraph Job Screenings

#80
post #61

Earlier quoted context omitted.

That senior devs with decades of experience fail. I've literally seen someone who supposedly wrote firmware for the space shuttle fail fizzbuzz.

You sometimes have to be careful and look if people are overthinking the problem. I have been in interviews where I was desperately looking for an efficient solution for a problem and couldn't find one while the interviewer only wanted to get a simple for loop.

Having sat in that interview he wasn't overthinking it. Despite writing firmware for decades he had never heard of the modulus operator, and when we explained it to him, he didn't see the point of it.

Remember those people in college who contributed nothing to the group project, but still somehow squeked by with a C? Those people now have jobs, and some have impressive resumes, particularly from .gov contractors where less than mediocrity reigns unfettered.

Post reply on HN