Other--SideStart a conversation →
ENFR

How do you spot a fake candidate when hiring a remote developer?

Fake applicants with invented or stolen identities now target remote developer roles, crypto included, across Europe. The warning signs on paper, on video and between the offer and the start date, the checks to add to your hiring process, and what to do if you have already hired one.

Other--Side6 min read

In brief

To spot a fake candidate, look for details that don't hold together from one stage to the next, such as a long career with a thin public trail. Other signs are references that only reply by email, a face or voice that changes between video calls, and a new delivery address or payment destination just before the start date. Check at every stage, not only at the interview.

You have shortlisted a remote developer whose CV fits the role almost too well. The interview went smoothly, the references replied within an hour, and the start date is next week. Some candidates who look like this are not who they claim to be, and crypto teams are among their targets. This guide shows how to spot a fake candidate at each stage of hiring, and which checks to build into your process.

A fake candidate is not the same as a pseudonymous one. Many good crypto developers work under a stable handle that is not their legal name, and their public work builds a track record you can check. The guide on how to vet a pseudonymous developer covers that case. A fake candidate is different: the identity itself is invented or stolen, so the details stop holding together once you look closely.

Why fake candidates target crypto teams

Many documented cases come from North Korea. Its IT workers apply for remote jobs abroad under false identities, and their operations have spread to Europe. Projects were found in the United Kingdom, and personas sought work in Germany and Portugal. Some of that work was in crypto, including smart contract development on Solana. A smart contract is a program that runs on a blockchain and often holds money.

The same report describes one worker who ran at least 12 personas, invented online identities, across Europe and the United States. This worker supplied fabricated references and used other personas they controlled to vouch for themselves. Payment went through cryptocurrency and money transfer services that make the money hard to trace.

The first goal is a salary. The risk does not stop there, though. Some of these workers have copied company code and held it to ransom, and recently fired ones have threatened to leak their former employer's data.

Spot a fake candidate before the interview

Most warning signs on paper are small inconsistencies. One alone proves nothing, but several together deserve a direct question.

  • Details that don't match. Check that names, addresses and dates stay consistent across the CV and any background check. Then compare the CV with the person's GitHub, LinkedIn and portfolio site.
  • A long career with a short trail. Ten years of experience should leave traces: code accepted by other projects, talks, posts, people who mention the person. A recent profile with few links to anyone else is a reason to look harder.
  • References that only write. References that reply by email, fast and in glowing terms, may be other personas of the same person. Contact each referee by phone or on video, not by email alone.
  • A CV built for your advert. A profile that repeats your job description almost word for word deserves a closer look. Ask about one project on it in detail, and listen for what only someone who did the work would know.

Warning signs during the interview

Fake candidates have used artificial intelligence and face-swapping software in video interviews, which replace a face on screen in real time. Some have also tried voice-changing software. So a single video call is not enough on its own.

Plan several live calls with the camera on, and keep the same interviewers for each. If the face, the voice or the level of English changes from one call to the next, ask why. When the role needs a legal identity, ask the person to hold their identity document up to the camera during one of these calls.

Ask questions that the real author of the work answers easily. Pick a pull request from their history, a change they proposed to someone else's code, and ask why they wrote it that way. Ask what went wrong in a project they list, and what they would do differently now. A person reading from a script tends to give general answers.

The walk-through call after a paid test task is a strong check too. Someone who did the task explains every choice without effort.

Warning signs between the offer and the start date

Watch for changes of address or payment platform during onboarding. Typical requests look harmless at first.

  • Sending the company laptop to a different address from the one on the contract.
  • Paying into an account or a payment service in another person's name.
  • Switching the payment method a few days before the first invoice.

Each request can have an honest reason, so ask for it. A laptop sent to another address may end up in a laptop farm. In that setup, a helper keeps company laptops connected from the country where the job is based, while the worker logs in to them remotely from elsewhere.

Paying a developer in crypto is not a warning sign in itself. What matters is that the person you hired receives the money, at a destination agreed in the contract and not changed at the last minute.

Checks to build into your hiring process

Good checks work best when they run at every stage, not only at the interview.

  1. Verify identity in steps. Run identity checks during interviewing, onboarding and throughout the engagement of any remote worker. For a role that needs a legal identity, agree upfront when it will be checked.
  2. Call the references. Phone or video, never email alone, and ask each referee how they worked with the candidate.
  3. Use more than one live call. Keep the camera on and the same interviewers throughout.
  4. Test real work. A short paid task, followed by a call to discuss it, tests skill and authorship together.
  5. Give access in steps. Start with what the first task needs, and keep production keys and company funds out of reach.
  6. Prefer company devices. Personal computers used through a virtual desktop may lack the logging tools that would show unusual activity.

If you think you have already hired one

Act quietly and in the right order. Remove access to code, systems and company accounts first, then end the contract. Recently fired fake workers have threatened to leak their former employer's data, so the access must go before the conversation.

Keep the logs, the messages and the payment records. Pay no further invoice until you have spoken to a lawyer.

Where to start

  1. Write down which roles can stay pseudonymous and which need a legal identity, and at what stage.
  2. Compare each shortlisted CV with the candidate's GitHub, LinkedIn and portfolio.
  3. Call every referee by phone or video.
  4. Hold at least two live video calls with the same interviewers.
  5. Give a short paid test task and discuss it on a call.
  6. Refuse last-minute changes to the delivery address or the payment destination without a clear reason.
  7. Give access in steps, on company devices where you can.

Hiring developers with Other--Side

Other--Side recruits for licensed operators, platforms and service providers in regulated markets across Europe. Technology is one of the functions we cover, alongside compliance, operations, product, finance and country leadership. Before you meet a candidate, we check them against the rules of your market, and we look at whether someone will stay before we look at whether they are free. See our services, or start a conversation about the developer you need.

  • fake candidates
  • hiring developers
  • remote hiring
  • hiring fraud
  • web3

Frequently asked questions

Is a pseudonymous developer a fake candidate?

No. A pseudonymous developer works under a stable handle with a public track record you can check. A fake candidate uses an invented or stolen identity, so the details stop matching once you compare the CV, the profiles, the references and the calls.

Can a deepfake fool a video interview?

It can. Fake candidates have used face-swapping and voice-changing software in video interviews. Hold several live calls with the camera on and the same interviewers, and when the role needs a legal identity, ask the person to hold their identity document up to the camera.

What is a laptop farm?

It is a place where a helper keeps company laptops switched on and connected from the country where the job is based. The real worker logs in to them remotely from somewhere else, so the employer sees a connection from the expected country.

Should you stop hiring remote developers because of fake candidates?

No. Most remote candidates are genuine, and remote hiring is how you reach many crypto developers. Build checks into each stage instead: consistent details, references called by phone or video, several live calls, a paid test task and access given in steps.

What should you do if you think you have hired a fake candidate?

Remove access to code, systems and company accounts before you end the contract. Keep the logs, messages and payment records, and pay no further invoice until you have spoken to a lawyer.

Further reading