Live data from Hacker News

Ask HN: Anyone having issues with job applicant fraud?

news.ycombinator.com

301–310 of 419 posts

Re: Ask HN: Anyone having issues with job applicant fraud?

#301

Earlier quoted context omitted.

They’re referring to people who are incompetent and take roles in which they are not qualified to take. In the case I was referring to, the developer who showed up for the job couldn’t even write a single line of code. We caught this quickly, but not immediately. There were certainly monetary damages from onboarding costs and time wasted, and non monetary damages from reputation with our customers.

Just to be specific in case you didn't know, "overemployed" refers to the practice of having multiple jobs both secretly and simultaneously.

FWIW I too thought it meant the opposite of underemployed.

I didn’t realize the “fraudulent holding of two jobs simultaneously” had acquired this name.

Apparently there are other definitions as well, used in economics. One being when workers want to work less (even for less money) but can’t… which is sort of the opposite of the two-jobs thing I guess:

https://www.encyclopedia.com/social-sciences/applied-and-soc...

Re: Ask HN: Anyone having issues with job applicant fraud?

#302

Earlier quoted context omitted.

He would stall for a good 15-20 seconds after each question I asked... and then spit out a perfectly worded answer. He was googling my questions and then reading the documentation aloud to me. If he's just Googling everything then he sounds like a senior developer to me! I'm half-joking. Obviously you want people who understand the problem you're asking, and who have a good knowledge of the domain, and who can answer…

This whole problem seems like it would go away with more sophisticated interview questions. Interviews should be precisely about stuff that you can't just google. Googling information is pretty much a required basic competency nowadays, right next to reading and writing.

One would hope so, but as someone who has a support aspect to their role I can guarantee you that this competency is lacking in an astonishing proportion of people. From the lowliest admin to the most senior dev with a PhD in computer science there are people who are entirely incapable of googling for information (or reading the effing manual). Don't even get me started on C suites

Re: Ask HN: Anyone having issues with job applicant fraud?

#305

Earlier quoted context omitted.

Not terribly surprising, since companies have more or less refused to actually train anybody since the 80s or so.

What’s the point of training people when there’s at will employment

"What if we train them, and they leave?" — "What if we don't train them, and they stay?"

Re: Ask HN: Anyone having issues with job applicant fraud?

#307
Let me give you a perspective of why people might legitimately not want to do camera during interviews.

A little about me: I've started doing remote work 15 years ago - long, long before the modern remote push. I've been coding for 30 years; I started with 8 bit micros; I can probably work with any technology and any deep problem you throw at me; I've led and launched projects worth billions of dollars. I prefer to work remotely because I hate commuting and open plan.

I've started denying camera interviews for a while now. I still do voice, but no camera, for the following reasons:

1. It impacts not just my earnings, but whether I'll be considered in the first place. There's a lot of sexism and racism happening in tech.

Sexism: if you're presenting as female, or presenting as male but don't look like Jim Halpert from the office, you can get looked at differently, which happened to me. This applies to people who are older, people who have visible tattoos or piercings, people who have blue hair, scars, etc.

Racism: you only need to look at other replies here with people talking about how bad eg Indian developers are. This extends to people of other skin color as well. In Europe there is a huge amount of racism against white Europeans from eastern Europe and from the Balkans and Europeans from Latin countries; in Asia there is racism against people ethnically from other Asian countries; in America there's racism against pretty much everyone; etc. This is endemic. One look at someone's face can be enough to disqualify them at a company that has this problem.

Ageism doesn't even need to be explained.

Based on the three points above, by demanding camera interviews you betray yourself as a company which doesn't have the issue of systemic bias against minorities figured out yet.

Incidental information leaks: The background - the location where you are - is important as well. Is the person located in their bedroom with a single bed? Probably a flat share, pay them less, they'll take it. Are they in their garden? Hmm, they are probably worth what they ask for. Is it dark outside whereas it's light where you are? Uh oh, remote work with someone who's not in your time zone! Better start worrying!

Especially the last one is egregious. Dev work is mostly solitary, asynchronous work; most of the time there's a lot of overlap even between eastern Europe and west coast US which is plenty of time for meetings and pair programming if necessary. People who insist on such things are usually inexperienced with remote work. Misconceptions like these destroy opportunities that can work out very well otherwise. I've had people make comments about "oh it's light out over there" many times in my career and it's always lead to a no-hire.

2. Issues that remote work solves can be brought to light in an ugly manner. For example, maybe the person feels they are not attractive, and are just generally shy around people in person - something that a lot of technical people share; their performance in front of a camera will be worse. Being shy when physically around other people perfectly fine for remote work. Maybe the person has special needs. Maybe they have to use an oxygen tank, or are missing an eye, or teeth, or a hand, or are sitting in a wheel chair, or are obese. Maybe the tapestry on their wall falling off and they haven't had money to fix it due to an economic downturn or because someone in the family had cancer so that's where the money went. None of this is stuff that the employer needs to know - but they are things that none the less can impact the recruitment and later career by a lot.

3. I experience fewer of the issues brought up in 1 and 2 than most others; however, I still deny camera interviews to see what will happen. Being this worried about job applicant fraud betrays that you likely can't afford it. Job applicant fraud is a little time off your hands and a little money as well. That fraudulent applicant wasted maybe 3 hours through interviews across people in your company, and maybe up to $10k wasted money. If you can't factor this into your business, it means to me - an experienced developer who has plenty of choice - that you can't afford me at all, and that working for you, should it happen, will be precarious. I'll probably skip over you. It is my experience that the most resilient companies - and ones that are well established already - absolutely don't care about seeing your face on camera.

Additional wasted time after the hire is mostly on your hands: either it's a complete bait and switch (smart person interviewed, substituted by someone unsuited) - and that's something you figure out on the first day - or it's someone who's never been good enough, and you weren't a good enough interviewer to figure this out in the several hours you've spent with them; at that point you'll probably take a few weeks to figure out that they're not great at their job, but that's on you.

--------

TLDR: a camera interview is purely a disadvantage to minorities and people who aren't well off by leaking things that are for good reason illegal to ask about; a job interview where this is demanded or implied betrays the company is standing on a shaky foundation.

Re: Ask HN: Anyone having issues with job applicant fraud?

#308
post #7

This is exactly why the technical interview process is what it is. No point wasting time asking about backgrounds and describing past projects (all of it can be easily faked). Make them write code in front of you live as part of the screening round.

The goal of an interview is to let great people through. It's not to see how well people code while you're watching their every keystroke. I used to make people write code in front of me. I've missed out on some excellent candidates that don't perform at their best with that kind of pressure. What I do now is ask people to share some code with me that they're proud of. Before the interview I look through it. Then on…

> What I do now is ask people to share some code with me that they're proud of.

What if they dont have code to share?

Re: Ask HN: Anyone having issues with job applicant fraud?

#309
post #96

Not only have I seen this several times, I've also encountered multiple instances of "over-employed" software engineers, who are doing 2-3 full time salaried positions from home, at the same time. This is surprisingly easy to get away with unnoticed in the US tax system, as you get a separate W2 from each employer. It's genuinely a lot more difficult to do this in some other countries. There's even this service now o…

Yeah but that doesn't look fun. My roommate is doing this now. I think it's insane, they sit at their desk with three computers working all day long. They're stressed out and burning out rapidly. No thanks.

Maybe they want to do this for a couple of years and save money for a house deposit, once you get the house, just stick to one job.

Re: Ask HN: Anyone having issues with job applicant fraud?

#310
post #128

Earlier this year, I interviewed this guy who gave me really strange vibes. He would stall for a good 15-20 seconds after each question I asked... and then spit out a perfectly worded answer. I google'd some specific, peculiar phrases I remembered him saying after the interview and found that the phrases came straight out of places like the Kubernetes documentation, word for word. He was googling my questions and the…

Wow, that company is 73% at Unix Administration AND 80% at Network Solutions. If only they were 70% at Python I'd have hired them for a project. I need a company with those stats.

you're taking a gamble unless you engage a company with at least 25% elemental and regulatory resistances
Post reply on HN