Basically my company interviewed a candidate who was fantastic. Checked all the boxes, nailed the interview, and had extremely relevant work experience. We made an offer. He accepted. A few weeks later on his first day the guy in the Zoom was definitely not the guy I interviewed. All the other interviewers agreed. Not the same guy.
We've had a number of candidates in the pipeline who seemed to be obviously lying about their identities who didn't make it to an offer but this case seemed different somehow. I cant quite put my finger on it.
I'm just curious to hear how many of you have experienced something similar. Is it common? Is there something obvious I'm not thinking of to help avoid these situations?
We may have passed on other candidates because of the strength of this one guy. This has put us in a pretty unfortunate position.
Some maybe noteworthy facts: we're a 100% remote company. The candidate was US based and said they didn't need visa sponsorship. They only spoke to one in house recruiter, an HR rep, and 3 people in engineering for the interviews. I discovered after the fact that one of the name brand companies on their resume was actually not the company we thought it was but one with the exact same name in a different industry.
We seldom see all the people whom we interviewed for the teams, as devs, being present in the meetings that they are all expected to be present (of course it is most often the timezone difference that is the mentioned reason). Or people who join have their camera turned off, so no way to see them.
Code quality that comes, is not on par with the skillset we evaluated during the interviews and I suspect the whole consultancy is doing something similar with presenting top engineers in the interview and then moving them between many teams. Leaving the less skilled engineer to do the work.
If you have the budget, I highly recommend moving your compensation points up and focusing on top engineers in remote locations. It's much easier to vet people who have an established online track record and you can tap references from well-known companies. Unfortunately this way you will miss out on some great candidates that haven't yet established themselves, so you still have to branch out.
For remote work we require video interviews and cameras on during meetings. We'd make an exception if someone really needed accommodations to keep their camera off for some reason, but otherwise it's cameras on. I know some people don't like this, but it improves communication and team cohesion in a noticeable way. It also immediately highlights fraud like this.
Get your security team involved. You should be tracking where remote employees access your VPN and company services. Don't be afraid to ask about discrepancies and changes. If someone has logged in from one IP or region for the first 4 weeks and then suddenly you're seeing new logins from a different city or country, investigate. I don't care if people travel, but we need to firmly understand the security situation.
Watch out for people with frequent excuses for missing meetings, having to turn their camera off, excuses like "my camera isn't working today", and so on. Send everyone known-good webcams and company laptops.
And as always, performance management is key. Managing remote is harder than managing in person, and I say that as someone who manages remote and loves remote teams. You need strong performance management practices in place and clear ways to measure it. People who aren't getting their work done should show up quickly in your system and warrant additional manager investigation.
But if someone shows up in Zoom who isn't the person you hired, lock it down ASAP. Don't let being "nice" get in the way of handling an urgent security situation. Someone you didn't hire who hasn't agreed to your contracts is in your system, and that's a red alert emergency.
She absolutely killed the Byteboard technical assessment, and seemed like a good cultural fit during my initial screen. I advised the technical interviewer that he didn't need to go too deep; I was satisfied with her answers on the technical assessment. Then something odd happened - she completely bombed the interview. The interviewer told me that she couldn't even answer the most basic questions e.g. "what tech stack does your employer use?" I was thoroughly confused about that, but still passed her on to the VPE to help us get to the bottom of the discrepancy. Our VPE confirmed the previous technical interviewer's assessment.
We came to the conclusion that she could not have completed the technical assessment on her own and obviously didn't move forward from there.
This is just companies getting back the same treatment they've been subjecting their customers to for over a decade.
In business this is called "business process outsourcing", aka send off sensitive data & permissions to sweatshops in third-world countries.
While it's a shame that it happened to what I assume is a legitimate small/medium business that doesn't do the aforementioned practice, I have absolutely zero sympathy for any big company that does the above and suddenly ends up at the receiving end of it.
The market has reacted, and as more and more things go remote it allows the "little guys" to take a stab at it with varying degrees of success.
(to be clear, I do not condone this behavior despite being approached several times to be a "front" for foreign developers - however, I totally understand the market dynamics that push them to do this)
I suggest calling the candidate in person for 1 day at a co-working location and meet them in person once you are ready to make an offer. Pay for their time since you have anyway decided to hire them. Yes, this adds cost to you but it will be a huge deterrence for fraud. If a candidate doesn't like it, they can move on.
- The biggest and most obvious is that they don't have a functioning webcam that clearly shows who they are. If I encounter this, the interview ends immediately.
- Another one is, if you do hire a person, they suddenly want to be paid through some unrelated company. ("Oh, it's my brothers company, I do this for tax reasons").
There are other red flags which aren't as certain, but should definitely raise your suspicions:
- The CV has been professionally designed or laid out.
- The most recent job entry is a vague "Remote contractor" or similar which doesn't list specific companies they've worked for.
- The name on the email doesn't match the name on the CV.
- You get a series of emails following up after a few days, as though someone is running a drip email campaign.
- The application email is sent directly to any of your employees, rather than to your standard recruiting email address, almost as though someone has used a sales tool to find internal contacts.
These last 5 points can occur in legitimate applications, but when you see them, it's a sign that additional suspicion is warranted. These fake employees are generally not individuals, but professional operations.
Any decently sized company has employment contractual provisions for misrepesentation of facts, expertise, and experience during the hiring process. Use that, hire one of the other candidates you interviewed, and fire them.
The only unfortunate thing here is having to read about this because your team failed in their due dilligence. That's a team/company failure, and this looks more like fluff spin for a narrative than anything else.
Your people didn't do their jobs, and lost costs vetting a potential hire who wasn't a good hire because of it. That's the business you are in. You knew the risks.
Prior to the first interview you should have covered an introduction and some of the expected vetting processes (i.e. Should we choose to extend an offer... there are requirements for an in-person report for HR to check I9 and other forms (i.e. potentially a certification of the facts they submitted as part of the process ...), and the required process of reporting instances of fraud to IC3/FBI). [It is often across state lines].
That's just some examples, I'm sure you can figure it out with your legal team if this is really an issue, because its seriously not that hard. You set up a process that gives bad actors enough rope so that if they cost you money in bad faith, there will be consequences.
Some time ago (~6 months) my company was looking to hire a programmer.
We don't have a established process for this as it was some years since we hired a coder, but then we are in the industry (hiring) so published a couple of adverts here and there and we got the thing rolling.
Most of the applicants were seriously under qualified, and my colleagues had to go through a lot of rubbish in the form of CVs in order to find suitable candidates.
But a few of them were good enough to at least make it to the interview step, and off the invitations went.
One of'em candidates - Let's call him "Rajeed" - promptly accepted the meeting, and due to the small amount of people that made it that far - let me remind you, first interview - my colleagues were slightly excited, but at the same time also weary as our experience with coders from India is far from stellar.
You can imagine my colleagues surprise when they opened the Zoom session and Rajeed was nowhere to be found. Instead, there were two person of whom we knew nothing about - apparently they were running some sort of coding shop - and when my colleagues asked for Rajeed they just said "Oh, it's OK, it's OK. You can talk to us."
For obvious reasons the meeting didn't last long.
We ended up hiring a coder from Poland that, even thought he was decent, was miles ahead of the rest of the candidates.
First off, a lot of comments indeed recommend insisting on a functioning webcam. This might be uncomfortable for some (and shouldn't be a mandatory, long-term "webcam mandatory" policy), but explaining the reasons behind it should make the vast majority of people be fine with it at the start. Long-term, a culture where people feel comfortable having their cameras on regularly is also good so people turn it on voluntarily, even beyond deterring fraud (personally I prefer seeing someone's face rather than a profile picture).
Second, this kind of behavior is only going to get more common; there's no way to deter it in advance. The best you can do is optimize your hiring pipeline for faster turnarounds so you can quickly react when you detect such behavior and it doesn't cost you as much. Maybe an initial, short "contract to hire" system is better, as it allows you to delay all the employment-related formalities (which are slow and costly) to after you've already confirmed the candidate isn't a fraudster.
Finally, the reason people do this kind of fraud is because they won't get in if they stay honest. If you actually need development services, does it actually have to be an employee? Maybe you can just be open to contractors or outsourcing agencies, let them in "honestly" with appropriate contract terms that protect both sides, and then it reduces the incentive for the "fake" employees to lie to you if they can get in legitimately.
He was based in Southeast Asia, and on his resume it looked like he met all of the competencies we needed -- including English proficiency.
But on the call, I noticed that whenever I asked him a question, he would turn off his camera, pause for 10-20 seconds, answer the question, then turn his video back on.
It turned out that the man was using a translator and really didn't speak any English whatsoever.
I have no idea how he expected to be able to do the job if he had been hired, but I guess he thought it was worth a shot.
In talking with the remote staffing firm, they were extremely apologetic. He had apparently pulled the same trick with them, but they didn't do video interviews, so it was harder to pick up on.
There's typical ones where an engineer will stack their resume with buzzwords that they don't understand at a basic level. An example of this is putting Kubernetes on ones resume but not being able to explain the different workloads. People don't often call this fraud, but I do when it crosses some magical threshold. The reason I call it fraud is that fraud, to me, generally implies intent to deceive. About a year ago I discovered on Reddit there were people coaching others through lying on their resumes and in interviews with the reasoning that "everyone does it" and "you'll learn on the job".
The second kind I've encountered is more analogous to what you experienced, though we never hired any of these folks. Retrospectively I think one of the things that helped us avoid hiring these folks is that we don't refer to an engineers provenance. Early on I took the stance that just because you say you're from Google, or any other large engineering firm, doesn't mean you're the right fit for the team. We had candidates invest in a 2-3 hour take home exercise that was pretty easy, it mostly tested your API design skills but because it involved code we got some good peeks into what that would look like in a contrived scenario. Second, we ask that candidates bring an example of projects they've worked on, starting with ones they led. This one is a little harder to fake the funk on, especially if the candidate is Senior+.
A lesser form of fraud, but still insidious at this point, are the templated resumes that misrepresent work experience. They will list a top line item in "work history" of something that sounds like tech startup, but in actuality isn't a company at all. It's just an open source project, that no one actually uses, with a website. Apart from the items listed, the candidates never have any legitimate work experience. It smells like a way to get resumes past any ATS keyword filtering and/or less-experienced recruiters.
And usually, the candidate hasn't really written much code at all in the repo. Just a smattering of readme updates, config changes, and maybe some bug fixes amounting to less than ~100-200 SLOC over the span of months.
In 100% of these cases we've seen so far, the resumes look exactly the same, including formatting/layout/etc. The projects all exist under the "OSLabs Beta" github orb [1] and the resume also lists a tech talk they did under the "SingleSprout Speaker Series" moniker. Most often, there is no actual evidence of them doing this talk, but in many cases you can find someone else doing the same talk topic on youtube if you search.
SingleSprout is a recruiting organization, so it seems at least somewhat likely that they are the ones shepherding this process, though I have no evidence of that. It could just be that they partner with this OS Labs entity as part of their candidate funnel. Whatever the case may be, this is at best (if I'm being charitable) a gross misrepresentation of candidate experience.
N.B. I am 100% OK with hiring folks based on (F)OSS experience. An active github is actually something I select for and, if its available, I will spend significant time reviewing such that I can have a meaningful discussion with the candidate about their work. These candidates are different entirely (for hopefully obvious reasons).
[1] https://github.com/oslabs-beta
EDIT: Wanted to add some clarification here that this post is about the candidates involved, on the topic of hiring woes that OP brought up, but not about the specific entities I mentioned. It may just be incidental that all of the resumes we've seen have had the aforementioned patterns. It is not my intent to malign any of the orgs I referenced.
The guy that showed up (in person!) for the job was definitely not him, and asked rudimentary questions ("how do I access the terminal", "what programming languages should I download", "how do I install git", etc). We gave him the day in case it was just a bad morning or something, but ended up firing him the next day for misrepresenting 'his' experience.
HR dept's are simply unable/ill-equipped to handle this new reality. Honestly, at larger org's this is really an upper management issue first and foremost, as HR dept's are sort of benefiting from these frauds. ( Before you go off on that last sentence, I did say 'sort of' - and I personally believe in 'you get what you incentivize'...so)
My PM, who was also on the call, had looked up the name on the resume and found the linked in of guy whose resume had been stolen. We notified him that someone was using his resume and actually ended up interviewing him! We came close to hiring him but his salary ask was out of our price range.
It was even worse, I was simply the guy in the meetings, the actual work was done by another dev that I translated for.
The best way to prevent it on remote teams is having the actual team in the interviews.
I managed up to 3 other devs while having a full time job on my end. Managing 3 daily meetings is no easy task.
The missions where short and we got fired only once, but that’s because the dev who was supposed to do the work was not up to the task.
After we finally fired him I did a little digging. His resume was very similar to 100's of others found across linkedin, a list of devops keywords basically. Almost all of the people he had "worked" with in a previous company had the same text and even looked very similar.
I'm pretty sure that the company gets these people in the door and they try to last as long as possible earning western senior dev salaries. Rince and repeat a few times a year and it probably earns them a decent amount.
He gave a technically sound answer to every question, but I was extremely skeptical. For one thing, he wholeheartedly agreed to the design outlined in my "honeypot" question where the solution would be something prone to triggering immense technical debt. He also dismissed the "soft" question about a time he encountered a challenge.
His most recent work experience was at a competitor where a former colleague works (we're in a niche space). That friend told me he encountered the same thing, including a candidate who recently claimed to work at my company and was moving (I never heard of the name nor could find mention in Slack/AD).
I have a friend who had someone else go through the interview process for him and ended up getting hired at one of the top 10 largest banks in US. Not only that, but because he was grossly under qualified for this job, he hired someone to teach him how to do his job. He works his normal 8-5, then he screen shares with this guy and they work together to complete his tasks. I'm a bit surprised that this worked and that they still haven't caught on, he has been working there for 8-10 months now. He has been sharing company intellectual property of a top US bank to foreigners for 8-10 months. The saddest part about this is that, he isn't a dumb, he is knowledgeable enough to get a decent job without cheating. In fact he has worked, both legally and ethically, for reputable companies.
Our company is pretty much entirely remote, but the interview process includes an initial screen (on video, about 45 mins), and then about 4 hours of interviews, again all on video, with about 8 different people. Point being, we know who you are. Do people think humans can't recognize faces or voices? Do some companies interview without a face-to-face conversation? I honestly just don't understand how this works, or how someone could think this could work.
We got suspicious pretty quick and eventually forced the guy we hired into a call and confronted him about it. His excuse was that it was his roommate online because he had some unexpected errand or something that morning.
The candidate didn't even come to us from one of the big faceless recruiters, but from one we've worked with in the past who's provided several of our current team members.
It's the first instance of that happening since we've gone remote, so I foresee us doing some more verification day 1, etc. for future hires.
And a few years ago, after we were acquired by a large enterprise company, we had several instances of the big contracting firms sending us different people than who we interviewed, or even catching the interviewee being a stand-in for someone else on their computer doing the work, etc. And this was prior to us being remote, so we'd get completely different people showing up in our office back then, etc. Our process at that time was to basically reinterview as soon as they stepped through the door, and then usually walk them right back out. Eventually, we were able work around having to hire from those firms.
Really though, for all prospective hires it's a leap of faith to assume performance in the interview will translate into performance in the actual job, and you need to be prepared for that not to be the case. Whatever safeguards you have in place to protect you from someone who isn't as good as they seemed to be should presumably also protect you from someone who isn't who they seemed to be.
There was no way for me to verify this guy was real, he couldn't give me his address because of "tax reasons" and wanted me to use his "wife's address" for his W-2 and legal paperwork.
Just all around fishy. After a bit he just stopped responding in the call, hung up and never responded to emails again.
---
Unrelated, I've had many chinese nationals reach out to purchase my freelancing profile so I guess this is a common scam.
However there was a post here or on Reddit (the line is blurry sometimes) where some developers from a specific Asian country described several cases. They made it sound like a frequent, organized thing, like a consultancy or some kind of racket. Most of them cited desperation and a "fake it until you make it" culture as the reasons for lying.
In my opinion this is bound to happen at places where people are poor and unhappy. And it's not limited to the software industry.
What surprises me the most is that you have managers that not only end up getting in business with them but they are not able to find what it is really going on. And in some big companies some managers know what is going on and are fine with it!
- Name / ethnicity / accent don't add up. By itself these weren't necessarily direct red flags, but combined with others it's been a common pattern.
- A lot of background noise of others talking. Can't really make out what the others are saying but sounds like a bunch of other people interviewing.
- Long pauses before answering questions, and often times the "candidate" looking somewhere off camera.
- Very short direct answers. When they do answer, it's very short and direct with no further elaboration. Any follow ups, even simple ones are follow but long pauses as well.
I asked around and while what you encountered is one way they cheat, there are many ways the do it. I collected all possible ways candidates cheat and redflags to look out for when interviewing candidates in my blog post.
(here is post link) https://thinkingthrough.substack.com/p/how-to-catch-a-cheati...
* if this falls under self-promotion, I can remove it.
I ended the conversation as soon as the plan was revealed, and was struck by just how brazen the dude was just blatantly asking me to lie for them professionally after exchanging like 2 messages.
Contracting agencies were the worst with the bait-and-switch game though, even prior to H-1Bs.
Faux identities, sub-hiring for work, outsourcing to low cost countries, even stuff like hiring actors for interviews and intimidation tactics (sic) plus a lot lot more.
Hiring (especially remotely) is a game and at some level you need to incorporate some anti-fraud techniques.
Now someone pulls some dirty, saucy tricks on you and you're crying about? Cry me a fucking river. Boo hoo.
But this was more employer-fraud, not employee.
Also about hiring fraud, I saw many positions that were advertised, interviews were performed, the "right" person was hired - all the interviews were fake, the positions were arranged for certain people from the very beginning. It is quite common in some companies and positions in my country, including international companies with local branches.
The simplest way to discover is ask the color of your shirt.
On a more positive note my last interview was very fair and on topic.
What happened was the fraudsters asked the candidates to buy some hardware on their own claiming we will reimburse them. Then they said they are sending them money to reimburse them but they made a mistake and sent too much and asked to send back the difference.
Another variant was they asked them to buy computers and then send to fraudster's address ostensibly for software installation.
We tweaked our website so that candidates browsing our website learn we never do such things, we explained the hiring process and especially the communication.
OTOH I experienced the reverse. Shady offers where red flags kept popping up after accepting the 1st interview round. E.g. the (ext.) recruiter lying about the funding or the company revealing shortly before signing the contract that the runway is just half a year. Not surprising that some applicants aren't 100% truthful either...
This sort of situation seems to have become very common in the last couple or three years.
We can try to detect / avoid it in the future but ultimately my takeaway is to avoid generic question lists for remote technical interviews, and instead try to hammer into one of their projects.
Finally, out of frustration I just ask him straight out "why did you put these things on your resume if you don't have experience in them?" to which he said "the recruiter told me to".
As far as I'm aware, we never worked with that recruiter again.
Had the exact same thing happen, yeah. One person interviewed on camera and used their ID for employment verification (EVerify/I-9). Someone else was joining meetings instead, initially with their camera off, and then when confronted and turned camera on, was DEFINITELY not the same person.
Because, think about it a minute:
Why should the top-talent overseas slaver away for your startup for low compensation?
Taking India as an example: There are top companies in India which would give top talent a competitive salary for India, along with corresponding status and responsibility.
So, why should top talent there take your similarly paid remote job which lacks the social standing and credibility that comes by working for a top-tier Indian company? Even if you pay higher than the local top-tier company, the difference in pay should be high enough to offset all other things that the candidate is losing by not taking a job in a respectable local company. This kind of social status is quite important because of social pressure from parents, family peers in many cultures. Not unlike how top-tier candidates still prefer to work for reputable companies in San Francisco instead of going for somewhat higher pay in no-name startups.
To recruit and keep top tier talent overseas, you will have to treat them just like how you were treating your local candidates. If you try to weasel your way out of it through scammy business practices - underpay, overwork, sweatshops etc - you will reap what you sow - scammy candidates.
Luckily enough, asking them to program while on camera makes it easy to suss out people who are not what they seem.
And if they do not have their webcam on during the interview loop, it is an automatic no-hire.
More info in our blog post: https://www.ethicalads.io/blog/2022/09/watch-out-ad-scammers...
Too sleazy for me. I'm basically selling my brand to another company. If companies get smart and create an employee blacklist, it becomes a lot harder for me to be employed down the line. (Hrm, maybe I should start a blacklist.)
Honestly don't know if it's true or just a story but now we only hire remote in the US and after the initial screens we fly out candidates for in-person (pay for the flight and -if needed- hotel).
I wonder if there's an opportunity in the future to tie work identity and work payments to a crypto wallet - i.e. "Your Github is tied to the wallet address, you apply to the job with the wallet address, you log into work accounts with the wallet address, and we pay you at the wallet address." Almost like the next evolution of Yubikeys.
How did you due diligence the candidate? Background check? Docs to confirm they are US based?
We still gave the guy until the end of the week to prove he could be useful.
He wasn't, so we let him go, but we would have kept him on if he was competent. Despite the fraud. Because it was such a pain to find a good dev at that time (not easy now, but not as hard, subjectively)
I get how this would be a thing when you're hiring from other territories. Got to step up the checks and balances in that scenario.
He was on the job only one day.
Here’s what I was sent.
> Hope you're doing well.
> We're a tightly-knit team of full-stack developers and we need someone who can help us with client communications. Most of our developers are not native English speakers and we often face communication issues. That's why we need someone who's based in the U.S and has technical background.
> The main responsibility will be taking job interviews on our behalf. You should be able to join the meetings under someone else's name.
> This is an hourly engagement and the rate is $40 ~ $80 / hr depending on your experience.
> Please kindly reply to this email if you're interested.
You would save so much hassle with a (relatively) small investment.
This was immediately suspicious and I hate slimeball recruiters so I made them arrange an interview and ghosted them. One of the recruiters called to chew me out while I was returning home from a successful interview for a real job.
The amount of cheating that I ( and my fellow professors ) have seen during these past few years has absolutely exploded (in a way that is beyond belief, and I've been doing this for a while).
The techniques others have outlined/alluded to ( camera off, a big life event just happened, looking off camera, noise, etc ) are all things that I've been seeing. And whilst this is nothing to be lauded, after all how many vectors are there, I do think that perhaps a solution is looking towards academics. (just saying...)
The startup had a lot of other problems, that one was the most awkward. It folded not very long afterwards.
plenty of mob types are making mob money on this scam while we type, as excellent young engineers struggle to make $3k USD per month.. I will guess. Overall seems like collateral damage for the relentless wage-war with outsourcing.. from the engineer side, I tend towards "this is the (outsourced workforce) bed you made now you are getting it back"
In the remote world, it's going to be difficult to address, but it's happened also in the old physical world — albeit less frequently.
Ahh, yes: https://news.ycombinator.com/item?id=30150343
Which referenced: https://www.askamanager.org/2022/01/the-new-hire-who-showed-...
I'm unclear on what the desired outcome is. A shitty company that can't evaluate on-going employees and let them slide for 30-60 days?
What do you mean by this? Like the face is another person? can you go into more detail about "not the guy I interviewed"? maybe it's just that zooming/remote work inherently requires more trust.
I had to get my "badge" 1h away. Had to be sponsored, multiple forms of ID, and an active paperwork on file. Full handprints were taken for both hands. Pictures as well.
Basically if I tried even KIND OF, I'd be going to federal prison. No ifs, ands, or buts.
In that case, someone pretended to be Connor Tumbleson to get hired.
My resume has been edited to fit each job.
He just didn't do any work. Got fired ofc.
Is that better?
They would reuse code with both companies.
That was a freaking mess.
TLDR: Giant staffing firms suck for everyone
If so, I'd like to talk to you and do some customer-validation interviews. Please find my email in my profile.
The benefits would be that instead of having fixed-staff that is sometimes poorly allocated, you could spin up inexpensive reliable staff on demand and it would be easily managed through a clean messaging/chat interface---Slack, Whatsapp, Twitter DM, your choice---with your external chief-of-staff. It also greatly increase the bus factor of your company. It would avoid hiring fraud and focus on matching high-quality inexpensive candidates to appropriate projects, and do project management for you.
If every function of your company (marketing down to content writing, development of every single company, all design etc.) is completely fancy and bespoke or you don't want to decrease your bus factor because you are moving way to damn fast to have any process or knowledge sharing outside of key team members, I guess this offer isn't for you. But perhaps also you've haven't completely bought into a sexiness/coolness mythology, realizing this mentality that everything must be in-house that isn't a great fit for 99% of companies. Perhaps you are open to modular boring solutions for certain company functions that aren't actually part of your core values / differentiators / skill area.