In the past month we've seen a dramatic, seemingly coordinated, increase in engineering applicants whose resumés and backgrounds appear qualified, but who refuse to use their cameras during Zoom interviews and who often can't answer specific questions about their backgrounds. We've wasted a significant amount of time on comms and interviews with over a dozen of these candidates. Anyone else experiencing anything similar?
His resume said he'd worked for a company called "Data Service Group" (https://dataservicegroup.com/) for the last 5 years or so. Their website contains this sentence: "Over the past decade, our customers succeeded by leveraging Intellectsoft's process of building, motivating."
Wait... Intellectsoft isn't the name of this company. Did these "Data Service Group" people steal Intellectsoft's website?
Turns out, if you Google the quoted sentence above, you get TONS of websites for other fake companies that all contain that sentence:
https://www.google.com/search?q=%22Over+the+past+decade%2C+o...
I'm still not really sure what was going on with that as we politely rejected him and never heard from him again.
If you look up the company on LinkedIn, it appears to be made up of hundreds of immigrant DevOps engineers: https://www.linkedin.com/company/data-service-group/
> Turns out, if you Google the quoted sentence above, you get TONS of websites for other fake companies that all contain that sentence
It looks like that text is part of the default template for a commercial WordPress theme named Engitech[1]. If you check the live preview and browse to the "Main Home" template, you'll find it there.
I wonder how many of these "companies" paid the $59 licensing fee? :^)
[1] https://themeforest.net/item/engitech-it-solutions-services-...
Their tactic seemingly consisted of running the website through a free tool like Lighthouse, picking one or two low hanging fruits and then presenting them as world-ending problems they can fix for cheap. I'm sure the follow-through would have left the site in a worse state and suspect they may actually have a backchannel income via SEO backlinks or malware as the price they would initially quote seemed low even for a country like Pakistan.
I wouldn't be surprised to learn that there are actually layers of these Potemkin company websites used for various purposes.
He took extremely long to do anything and then when he presented the work, it was very wrong and obviously copied from a bunch of stack overflow answers.
To this day I'm astounded my employer hired him and even more so that it took 2 months to fire him. Just think, he was on a senior salary for a couple of months for doing nothing... not a bad scam if you can do that a few times a year.
In your case, sure he had a salary for two months, but that can not be the plan? Do people just expect that if they are hired, they'll sort of figure it out along the way? If that's the case, then maybe go for a more junior position and hope there is good on the job training.
Years ago, I worked as a test engineer. One issue that repeatedly turned up when trying to get information about one of the tools we used, was that forums, mailing-lists, you name it, would get swamped by Indians who just wanted the answers to some standard hiring quiz. They just wanted to memorize the 150 or so answers, so they could get a job. Knowing those answers wouldn't help me in my day to day work, or at least very little, so what did they expect would happen if they got hired? Sure you can scam your way though a job interview... Then what? Your new colleagues is going to notice your shortcomings rather quickly.
Why even try?
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 based on their experience and knowledge, but if a few lines from the documentation answer your interview question then it's a bad interview question.
What if the candidate had an exceptional memory and had simply memorized the docs? Would that have been acceptable? Of course not. Your job as an interviewer is to ask questions that looking something up in the docs won't answer. After all, when you're in the job, Googling something is a perfectly acceptable strategy.
Deleted Comment
daily job: google answers to questions.
You could also do interview questions.
Deleted Comment
"4k+ ACTIVE CLIENTS, 35+ PROJECTS DONE...10 GLORIOUS YEARS"
I imagine then, there's at least 3965 clients that aren't super happy. At 3.5 projects completed per year, it's going to be a long road.
You see, they must have started with one client, in year one, and thereafter achieved an average growth rate of 151.33% per annum.
My Excel model:
In the tenth year, they would have 4001 clients. However, they would have passed 35 clients about five years prior, and therefore the implication is simply that that is the cohort that is completing now and projects last on the order of five years.The salary for these employees isn’t exactly great. If I’m not wrong they still work through these witch companies and get their wages garnished. So these employees generally try to jump ship once they come to the US.
A second pool is the metric ton of immigrant students who come study an MS in vaguely computer related degrees - typically CS MS degrees are a bit more discerning but one example is this MIS degree from a BUSINESS SCHOOL in TAMU that’s just an Indian immigrant degree mill churning out people without much coding abilities at all.
Both these groups now go to these “consultant firms” in the US which take their money, fill out their resume with fake experience and train them to pass your interviews. I have heard all manner of illegal crap including person A attending the interview (even in person) and person B actually turning up for work. How many times have you looked closely enough to confirm it’s the same dude anyway.
These people are shrewd. Doing all of this does take brains. They’re just shit at coding. Some do actually improve over time but some never do.
Source: Indian dude who had college roommates, relatives, friends, acquaintances, etc all do various versions of these shenanigans.
Only way to protect yourself is to have a culture fit interview component, confirm their LinkedIn history isn’t super shady and have at least an informal verification step post offer to ensure you don’t let a rat into the ship.
It makes me wonder if they are just getting into a completely different program with the "American university" name. Do you have any insight into this?
I see what you mean (<https://mays.tamu.edu/ms-management-information-systems/>). Clear signaling toward foreign applicants.
H-1B visas should be given out using an auction system. The minimum salary for the position should be some percentage of resulting price.
I think this would go a long way to ensuring that companies use the program for what it was intended for and stop the abuses.
If you have Python on your CV, and I ask you how the garbage collector works, I don't want you to read some stack overflow summary to me. I want to hear your own description, so I can make a judgement how deep your knowledge of Python internals goes.
Anybody can type specific questions into Google. But if it comes to producing performant code, you need to have that knowledge in the back of your mind, because nobody is going to tell you to google that.
It’s one thing to openly use web search as a tool and another to pretend you know something when you don’t.
It’s usually fine to say “I don’t know, I’d have to look that up”. That’s what you’d actually want on the job, honesty and professionalism.
People make mistakes all the time. What you want is a culture where they can admit those mistakes so that the team can engineer them away from happening again.
If a candidate is willing to lie over something so small as looking up an algorithm then that would be a big red flag to me.
800 419 2567
It only happened once ever. But I just keep on checking.
I've interviewed several candidates that were clearly googling questions. Some I thought were scammers, others not so much.
The funny thing is that they were all on camera. You can see the pause,you see the slight head turn and the eyes gaze away from the camera, you hear the click clack of typing and then the sudden recitation of a perfectly worded dictionary answer.
What was your reaction? Would you prefer they be more subtle of the poorly kept secret that most of this job is simply trying to figure out why the code isn't running and looking for specific error codes from other people's projects?
I'm being sincere, because I'm studying AI and ML and I kind of doubt most CS majors could describe 85% of the concepts we cover at the undergrad level let alone describe the use of the sigmoid function and soft max when building a gradient descent algorithm in a NN if put on the spot; I know this because when I went searching for this they often say that even their professor sucked at describing it so much that they had just glossed over it entirely and admitted they would look it up when working with TF in the future.
https://ceid.utsa.edu/iotsecuritylab/home-5/
As we got into it, the candidate often asked me to repeat the question. I was happy to do so, but after a few times, I was already taking care to speak slowly and clearly, and it was still happening a lot.
Then I noticed a quiet murmuring sound after I'd asked a question. It was like .. a TV on in the next room or something. I ignored it at first, assuming it was someone else in the next room, but then it seemed like it was only happening after I'd asked a question, and before the candidate answered.
I was now pretty suspicious, but confused: what was going on? The candidate was flubbing the interview anyway -- their understanding was pretty shallow and they didn't appear at all confident in the material, so I wrapped up the interview, and showed them out.
As we were walking to the door, I stood beside them for the first time. And that's when I saw the earpiece: the candidate had a hearing aid-like earpiece in, with a wire running into their collar.
I was basically too surprised to do anything, and by this point we were at the elevator, so I just let them leave.
The way I figured it, afterwards, was that they had someone on a radio who they thought would help them with the interview. But either the radio was noisy or they just needed more time for the answer, so asking me to repeat the question was for the benefit of their remote assistant. If they'd been better at it, even had I seen the earpiece, I'd have assumed it was just a hearing aid. Fortunately, even with the remote assistance, they didn't pass.
Never happened again, but I can tell you I casually check everyone I've interviewed since for earpieces.
https://www.youtube.com/watch?v=iaSUOFleNRU
It's nearly 40 years old and it still makes me laugh every time.
Although that did happen, but I think that was the recruitment agencies: they'd debrief their candidates after their interviews, and the next time they sent someone in, they'd be prepped for the whiteboard design exercises we'd used previously. I ended up with a dozen different questions that I rotated, which seemed to be enough.
General interview questions were often prepped too. Our phone screen question list had to grow quite long before it seemed like the effort to cram/prep was too much trouble.
[1] https://www.businessinsider.com/north-korean-crypto-job-cand...
[2] https://www.theregister.com/2022/05/17/fbi_korea_freelancers...
[3] https://www.wired.com/story/north-korean-it-scammer-alert/
This is something I've argued before: In the 40s, the US intelligence services could call up famous, brilliant people like Claude Shannon, ask him to fix some problem and never talk about the problem or his solution to it.
If they tried that today, most would tell them to go fuck themselves.
Now you may think things would be different in North Korea. In some ways they might be, but they obviously have a lot less top talent to commandeer in the first place, with their lack of modern technology and childhood nutrition. And even then, there are less confrontational ways to say no where open defiance is out of the picture. In North Korea, if you're very competent at anything, you might be quite careful in who you reveal that to in the first place.
and of course, plenty of Russians and Iranians are non-Asian (in appearance, Persia is in Asia of course)
We had one person we hired as a contractor, but then her voice changed on the phone, and started calling people by their last names in chat. It looked like it was someone that subcontracted another who then quit, and the first was trying to hold onto the contract as long as possible.
Another answered complex questions during the interview, but after the start they knew nothing.
A third contractor I knew was trying to do two jobs at the same time. Unfortunately while he was supposed to be working for one company he was making public github commits for the second. He was shown the door that day.
Tangentially, another contractor "lost" two macbooks assigned to him. Apparently right after travelling to Colorado after they legalized weed.
I mean this literally how contractors work. Unless they were taking your IP and using it for another company I don’t see the issue.
It's just like a lawyer's billable hours.
If you're setting their hours, doesn't that make them an employee rather than a contractor, legally speaking?
Happened at a company I worked at many years ago. Working from home was new, one dude who we all thought was suspect anyway got a call from his bosses boss and answered the phone with the wrong company name and it was over.
To make an example of him they made him pay back some of his salary (his contract had him on call and available 24/7). Ran into him a while later and he confirmed he paid them back.
Not a fake candidate but a slimy guy.
/r/overemployed is a sub full of people sharing strategies about how to maintain multiple jobs at once. Some of those folks have 3 or more jobs. Industries of focus seem to be tech and sales.
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.
The random people who are up for hire from India — there's a good chance they're up for hire because they couldn't get anything else.
You get what you pay for. And the best are probably not even in the market.
Precisely, and they know what they're worth, so they won't be cheaper anyway.
I'm not "writing off" a billion people. But. It's like finding a needle in a haystack.
I did some research when this happened, and they even have a name for this [1]
Coincidentally, our experience with people from Easter Europe is quite the opposite: Of all the people we hired from there, all except one were stellar (And the "one" was also good, just that he had some greys ethically: Had a disagreement with our boss, and disappeared over a weekend after siphoning large amounts of data from our system)
[1] https://thepolicytimes.com/chalta-hai-attitude-holding-india...
But only a few weeks later he was back, in the same building, but using a different name on a different floor working as a Senior Software Architect.
He got caught because someone in the DB department recognized him, called him by his old name and they pretended they never new him.
I haven't seen it recently, but I am now in a position where we have good recruiters who filter people before I ever see them.
Tons of calls for technical tests of individuals to prevent fraud/bad hires. No one does a technical interview for talent agency recruiters to make sure their company can filter candidates well though.
Well you get what you pay for.
Anyone who is doing this, you're destroying trust and making life hard for the rest of us.
And guess what, when I decided to be an asshole, think only of myself and not give a fuck about the companies, voila, my renumeration started to go up and up and up (making 10x more now than when I was a 'company man').
Stop being an idiot (not parent, in general) and start looking for yourself only, in a few years you will see the rewards.
Designing and making products is what I do for living as my own business. Never really had people's distrust when explaining them what / how I've done things. Of course I also have list of clients and reference letters from them along with phone numbers so if someone is in doubt they can check.
As a senior remote US employee I don't see how any of the companies I interviewed with would even allow past screening not turning on camera or other tricks like this.
If a job offer results in 20 genuine applicants, the company might set up 20 calls.
If the same job offer results in 20 genuine applications and 480 fraudsters, the seconds spent on a CV need to drop drastically for a HR person to make the decision to interview a candidate. And if the fraudsters do well faking a CV, and HR only has time for 20 calls, there are going to be a lot of false negatives (genuine candidates not getting a call back).
Dead Comment
Sadly, they don't care.
This is why we can't have nice things.
"You really should have used the enhanced for loop for that .." or "You really should have used a Lambda there" etc.
After years of tech screens like this over the course of my coding career I can't say Im not enjoying a little schadenfreude over this.