Ask HN: Anyone having issues with job applicant fraud?

Post by boltzmann-brain » Sat, Sep 03, 2022, 2:17 PM UTC

UncleMeat wrote: post #350

sigmoid10 wrote: post #278

Earlier quoted context omitted.

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.

Being able to look up stuff is important but there is also a baseline of knowledge that is really important. If I'm working with somebody in a meeting and they need to stop every 30 seconds to look up a term or concept then we aren't going to be able to collaborate effectively.

Post by t-3 » Sun, Sep 04, 2022, 11:33 AM UTC

csdreamer7 wrote: post #331

Nextgrid wrote: post #279

Earlier quoted context omitted.

If he fails to deliver on the job, put them on a PIP and get rid of them. If he actually delivers good work, who cares if he cheats?

Is he actually doing the work? Is just copying code from OSS projects and does not actually understand it? Not only will this cause legal liability, but when the team is under stress will he just disappear or be able to solve an issue? He already lied once. Why not lie more?

Post by dolmen » Mon, Sep 05, 2022, 9:29 AM UTC

KronisLV wrote: post #270

paxys wrote: 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.

> Make them write code in front of you live as part of the screening round. I think there's always lots of arguing over what's the correct way to do this. Ideally, I think you'd basically have any number of options, from which you (the candidate) could pick whatever feels the most suitable: [ ] - solve an algorithmic problem in person, show code, discuss now [ ] - solve an algorithmic problem later, share Git repo, d…

Post by another_another » Tue, Sep 06, 2022, 1:01 PM UTC

erdos4d wrote: post #59

This sounds like what I wanted to do once I realized how insanely easy remote work was. I do my wife's code for her dev job and it honestly works out to like 2 hours a week for me. She spends maybe 10 hours in meetings, so it totally makes sense to put 3 or 4 front people in positions to handle the meetings and just funnel the work back to me. Sounds like they are doing a bait and switch strategy though. You should j…

Post by rentfree-media » Fri, Sep 09, 2022, 5:22 PM UTC

Lio wrote: post #274

noodlenotes wrote: post #228

Earlier quoted context omitted.

At tech companies, "contractor" usually means someone contracted from a staffing company to work 40 hour weeks during normal business hours. They're not someone who is providing an end product with the freedom to set their own schedule, like you typically think of when you hear "contractor".

That very much depends on location. In the UK a contractor could be someone from an outsourcing company as you suggest or they could be an independent service provider working on their own. This is very common in software dev here when you require someone with specific skills. If you’re the latter kind then you’d be wise to bill on deliverables rather than time. If you don’t you could run into a well known tax reg ca…