Remote hiring changed the interview. The person on the screen may be exactly who they claim to be, or they may be a borrowed photo, a generated face, or someone else sitting in for the real applicant. A fake job applicant photo check is the cheapest way to find out which one you are dealing with, and it takes minutes, before you spend anyone’s time on a call.
Short answer: Run the applicant’s photo through a reverse image search, check the file for camera metadata, look for AI headshot tells, and compare the face with the profile, the portfolio and the person on the video call. No single check proves anything on its own. Together they show whether the photo belongs to a real person, or appeared from nowhere.
A fake job applicant is someone who applies under an identity that is not theirs, or an identity that does not exist at all. Gartner’s research splits the problem into three shapes. A ghost worker is a real person using a fake identity to collect a remote salary while doing little or no work. A fabricated persona is a fully invented identity, with a generated headshot, a made-up work history and a polished profile. A proxy interview is a real candidate who has someone else sit the interview for them. The photo is the first thing all three have in common, and it is the first thing you can check.
Why is the photo the cheapest check to run first?
Most of the fraud in a hiring pipeline hides in text. A work history can be invented, a reference can be a friend, and a CV can be tuned to match your job description word for word. Checking those claims takes calls, emails and days. A photo is a file, and a file carries evidence you can read in minutes.
The scale of the problem is no longer a rumour. Gartner reported in July 2025 that 6% of the 3,000 job candidates it surveyed admitted to interview fraud, either posing as someone else or having someone else pose as them. The same research found 39% of candidates had used AI somewhere in the application process. Gartner predicts that by 2028, one in four candidate profiles worldwide will be fake. That last figure is a forecast, not a measurement, and it should be read that way. Even so, it tells you the direction of travel.
There is a sharper version of the same problem at the serious end. The FBI warned in a public service announcement in October 2026 that North Korean IT workers are using stolen identities, AI face swaps and paid facilitators to take remote jobs at Western companies, and that the regime receives an estimated 85 to 90% of the revenue those workers generate. The same announcement says the workers pay Americans to appear on camera, sit in on job interviews and keep company laptops connected from US homes. Most employers will never meet that kind of operation. But the checks that catch it are the same checks that catch an ordinary fake applicant, so they are worth building into every remote hire.
One more Gartner finding matters for how you design the process. In the same research, 62% of candidates said they were more likely to apply when a role required in-person interviews. A photo check is not a replacement for meeting someone. It is the step that earns the meeting.
How do you run a fake job applicant photo check?
This is the whole method in one place. Run the checks in order, from cheapest to most effort, and stop advancing the candidate until the flags are explained. The ranking asset for this guide is this table, and every section below walks through one row of it.
| Check | What it catches | What it cannot prove |
|---|---|---|
| 1. Reverse image search | A stolen photo: a stock image, a model, or someone else’s profile picture | A clean result never proves the person is real |
| 2. AI headshot tells | A generated face: over-smooth skin, impossible light, empty background | Visual tells miss most modern generated portraits |
| 3. Detector score | Pixel-level signs of generation a human eye cannot see | A score is a probability, never a verdict |
| 4. File metadata read | Camera and editing history when it survives | Missing metadata is normal: platforms strip it on upload |
| 5. Original file request | The full-quality file, which searches and detectors need | Nothing on its own: a real applicant may not have it |
| 6. Consistency across profile, portfolio and video call | One face that does not match its own history | A mismatch can have an innocent explanation, so ask |
Two rules sit above the table. First, run the same checks for every candidate at the same stage of the same role. A check you run only on the applicants you already doubt is not a process, it is a bias. Second, never reject someone on one row of the table. A flag means verify more, not reject now.
How do you reverse search an applicant’s photo?
This is the first check because it answers the most useful question: has this face appeared anywhere else on the internet, under a different name? A stolen photo is the easiest fake to catch, and a reverse search is how you catch it.
- Ask for the original file. Do not search the small thumbnail from LinkedIn or your applicant tracking system. Platforms resize, recompress and strip the image, and a search on that version misses matches. Ask for the headshot as a file, framed as an admin request: you need a print-quality photo for the internal directory. Most real applicants send one without a second thought.
- Search it on Google Lens. Upload the file at lens.google.com, or use the upload-by-URL option if you have the photo’s web address. Read the exact matches first. If the face appears on a stock photo site, a modelling portfolio, or another person’s professional profile under a different name, the photo is stolen and the application stops here.
- Search it on TinEye as well. TinEye indexes a different corner of the web and regularly disagrees with Lens, so one engine is not enough. Note the earliest indexed date on any match. A photo first indexed years ago, on a page that has nothing to do with your applicant, is a strong signal.
- Read the results like an investigator, not a scoreboard. A match to the applicant’s own company page, speaker bio or byline is a good sign: the photo belongs to a person with a public history. A match to a stock library is a bad sign. No match at all is neither. It may mean the photo is new, private, or generated, and you cannot tell which from the search alone.
Worked example: a real headshot, searched live on 15 November 2026. To show what the results actually look like, we ran the check on a real professional headshot: a 1,254 by 1,254 pixel PNG of a data scientist, published on Wikimedia Commons on 25 August 2026 by the subject themselves, under a CC BY-SA 4.0 licence. The file is 1,637,480 bytes and carries no camera metadata at all, which is normal for a PNG that has been exported and uploaded. We ran that exact file through TinEye, Google Lens and the Hive AI detector demo.
TinEye found 0 matches across its index of 86.7 billion images, and said so in its own words: it has probably not yet crawled any page where this image appears. The photo was only published on 25 August 2026, so a zero here is a crawl gap, not a clearance and not an accusation. Google Lens never produced a result at all. After the usual-traffic check was cleared, Lens failed three times to fetch the image at its web address, showing “No image at the URL” on both the exact-match and visual-match tabs. No Lens count is reported here, because none was obtained. A failed search is not a zero.
The Hive AI detector demo gave the most instructive result of the three. It scored the photo 99.9% likely to be AI-generated, named the source as gptimage2 at 99.9%, scored it 0% likely to be a deepfake, found no Content Credentials, and showed the verdict “This input is likely to contain AI-generated or deepfake content”. Read that again. This is a real photograph, taken of a real person, published by the subject themselves. The detector was wrong, at the highest confidence it can express.
That is the lesson of the worked example, and it is the reason this guide keeps saying a score is never a verdict. The reverse search found nothing, because the photo is too new to have been crawled. The Lens search failed, because the service could not fetch the file. The detector called a real photo AI-generated with 99.9% confidence. If an employer had rejected this applicant on any one of those results, they would have rejected a real person for nothing. Run all three checks, read them together, and let the live call do the final work.
What does an AI-generated headshot look like?
Generated headshots have improved fast. The obvious tells of earlier models, wrong finger counts and melted ears, are rare in portrait-focused outputs now. What remains is subtler, and it is worth learning, even though visual inspection alone will miss most modern generated portraits.
| Tell | What to look for |
|---|---|
| Skin | Unusually uniform texture, smooth at every pore, with no natural variation |
| Light | Perfectly even, flattering light from all directions at once, with no real shadows |
| Background | A generic soft blur with no identifiable place, no office, no studio, no outdoors |
| Ears and hairline | Ears that do not quite match, or a hairline that blurs into the background |
| Glasses and jewellery | Frames that bend oddly, earrings that do not match each other |
| Metadata | No camera data, no capture date, or generator tags in the file |
For everything the eye misses, use a detector that reads pixel-level generation artefacts. Run the original file, not the thumbnail, and read the score as a probability. A high score is a strong signal to verify further. A low score is not a clearance. The worked example below shows the other side of the same coin: a detector scored a real headshot 99.9% likely AI-generated. Detectors disagree with each other, and a generated face that has been through a messaging app or a social platform has been recompressed, which weakens the signal further. Our guide to how to tell if an image is AI generated explains the tools and their limits in full.
One caution matters more than the rest. Some candidates use an AI-generated or AI-retouched headshot for cosmetic reasons, without any intent to deceive. A generated headshot on its own is a flag, not a finding. It becomes a serious signal only in combination: a generated face, a thin profile, unverifiable references and a CV that mirrors your job description word for word. Judge the combination, never the photo alone.
What can the photo file itself tell you?
Ask for the original file, then read it. A real photo taken on a camera or a phone usually carries EXIF data: the device model, the lens, the aperture and shutter speed, a capture timestamp, sometimes a location. An AI-generated image has no camera data, or it carries generator tags from a text-to-image tool. A headshot that lists an image editor, or a generator, in its metadata has been through a pipeline no ordinary portrait needs.
Missing metadata is not a red flag on its own. LinkedIn, WhatsApp, Slack, iMessage and most applicant tracking systems strip EXIF data on upload, for privacy reasons. A perfectly honest candidate will hand you a stripped file again and again. What matters is the pattern: a file with camera data that matches the story, against a file with nothing at all, plus a generated-looking portrait, plus a profile with no history. One empty file means nothing. Three empty signals together mean verify.
There is a practical point here too. Detectors and reverse searches both work better on the original file. A LinkedIn thumbnail has been resized and recompressed, which wrecks match quality and everything you would check next. If the candidate cannot or will not provide the original, note it and move on to the live checks. Do not make the file itself a test the candidate must pass.
How do you check the photo against the profile, the portfolio and the video call?
The photo check does not end with the file. A real person leaves a trail, and a fabricated persona does not. Compare the face with everything else the candidate has given you, and watch for the places where the story breaks.
Start with the profile. A real professional in any field accumulates a network over time. A profile with 50 connections after ten years of claimed employment is suspicious. Read the endorsements and recommendations too: fake applicant rings sometimes endorse each other, so if the recommenders also have generated-looking headshots or paper-thin profiles, the endorsements are fabricated. Check the work history against the photo’s own timeline. A headshot first published years ago, attached to a profile created last month, deserves a question.
Then check the portfolio. Ask the candidate to open a real piece of work from a project they described, a codebase, a spreadsheet model, a design file, and walk through a decision they made. A real professional can do this. A fabricated persona cannot produce real work artefacts on demand. Ask what they would have done differently. The answer matters less than the ease with which it comes.
Finally, check the face on the video call. This is where the photo meets the person, and it is the check a still image cannot replace. Ask for a live, unscheduled video call with the camera on. During the call, ask the candidate to wave a hand in front of their face and turn their head side to side. Real-time face-swap tools still stumble on hand occlusion and hard profile turns, and security researchers at Palo Alto Networks’ Unit 42 have documented the glitches: a hairline that does not move naturally, eyes that slide rather than move, lip movement lagging half a beat behind the audio. Frame it as routine: you run a quick check at the start of all your video interviews. If the candidate suddenly has technical difficulties, or the camera stays off, pay attention. Our guide to how to check if a video is AI generated covers the live-call tells in detail.
Watch for the proxy interview as well. The person on screen is real, but someone else is supplying the answers, off camera or through an earpiece. Long pauses before simple answers, eyes drifting to one spot off screen, and answers that arrive in a different voice than the one asking the questions are all worth noting. None of these proves anything alone. Together with a flagged photo, they justify a second, unscripted call.
What should you do when a check flags something?
Pause the process, do not end it. A flag is a reason to verify, and verification has a sequence.
- Note exactly what flagged, and where. “TinEye found this face on a stock site” is a fact. “The photo looks fake” is an opinion. Write the fact down.
- Run the remaining checks. A reverse search hit plus a detector score plus a thin profile is a pattern. Any one of them alone is not.
- Ask the candidate a direct, factual question. “We found this photo on a stock library under a different name. Can you explain that?” A real person usually has a short, checkable answer. A fabricated persona does not.
- Hold a live, unscripted video call and ask the candidate to walk through real work. This is the verification step no generated face can fake.
- Decide on the whole picture, and record the reasons. If you reject, reject on the pattern, not on a single score.
Never accuse a candidate publicly, and never share a flagged photo with other employers or post about it. If the applicant is a real person whose photo was stolen, they are a victim too. If they are a fraud, a public accusation creates a legal problem you do not need. Keep the process private, factual and written down.
How do you run photo checks fairly?
Photo checks touch real people, and they can go wrong in ways that have nothing to do with fraud. A detector can flag a real photo. A reverse search can surface a photo a candidate did not know was public. A hiring manager can read a flag differently depending on who the candidate is. So the process needs rules of its own.
Apply the same checks, at the same stage, to every candidate for the same role. Tell candidates in the job advert or the application form that you verify applicant photos before interview. Keep the photos only as long as the hiring process needs them, and delete them when it ends. Do not store face data in a spreadsheet, a shared drive or a chat thread. Face data is sensitive personal data in the UK under data protection law, and some US states, including Illinois, have their own biometric privacy rules with real penalties for casual handling. This is general information, not legal advice: if you hire at volume, or across borders, get advice on the rules where you operate before you build the process.
There is a useful boundary to keep in mind. Photo checks are about the photo. Right-to-work and identity document checks are a separate compliance step, handled through your normal HR process, and they are not covered here. Do not mix the two, and do not ask a candidate to send you identity documents so you can test a photo. That request is exactly the kind of thing a scammer would ask for, and a careful candidate is right to refuse it.
Our guide for the other side of this problem, how to check a job offer scam from its photos, is written for candidates. Reading it will show you what a careful applicant expects from a careful employer, and it keeps your process honest.
What mistakes do employers make with applicant photos?
- Searching the LinkedIn thumbnail instead of the original file, then trusting a clean result.
- Treating one signal as a verdict: a detector score, a missing metadata field, or a thin profile, on its own.
- Treating a clean reverse search as proof the person is real. A generated face has never been photographed, so it has nothing to match.
- Skipping the live video call, and hiring someone no one in the company has ever actually seen.
- Running the checks only on the candidates they already doubt, which turns a process into a bias.
- Keeping applicant photos after the hire is decided, in places where they do not belong.
The photo check is a small habit, not a security product. Run it the same way every time, write down what you found, and let the live call do the final work. A fake applicant’s photo is usually the weakest part of the fraud, because it is the only part you can check in minutes, without the candidate’s help, before you offer anyone a laptop, a login, or a salary. Use those minutes.
For the wider picture, our complete guide to photo scams covers the same photo-first method across every scam format, and our face search and photo privacy guide covers what a face search can and cannot do. The photo is the cheapest check in hiring. Run it before the interview, every time.
FAQs
Can you check a job applicant’s photo before the interview?
Yes, and you should. Run a reverse image search on the headshot, check the file for camera metadata, and compare the face with the profile and portfolio. Do the same checks for every candidate at the same stage of the same role, tell candidates the checks happen, and keep the photos only as long as the hiring process needs them.
Does an AI-generated headshot mean the applicant is fake?
No. Some candidates use an AI-generated or retouched headshot for cosmetic reasons, with no intent to deceive, and detectors can also flag a real photo: in our own test, Hive scored a real headshot 99.9% likely AI-generated. Treat a generated-looking photo as a reason to verify more, never as a reason to reject on its own.
What if a reverse image search finds nothing?
Nothing on its own. A photo that is new, private or generated has nothing to match, and search engines do not crawl every page: our worked example found zero TinEye matches for a real photo published weeks earlier. Move on to the file check, the detector and the live video call, and let the combination decide.
Can you ask an applicant for the original photo file?
Yes. Ask for the original file as an admin request, for example for a print-quality photo for the internal directory. The original searches and scores far better than a LinkedIn thumbnail, which platforms resize, recompress and strip. If the candidate cannot provide it, note that and rely on the live checks instead.
How do you check the person on the video call is the applicant?
Hold a live, unscheduled video call and ask the candidate to wave a hand in front of their face, turn their head side to side, and walk through a real piece of work on screen. Face-swap tools still glitch on hand occlusion and profile turns. If the camera stays off or the call keeps failing, pause the process and verify.
Is it legal to run a photo check on a job applicant?
Photo checks are allowed, but face data is sensitive, so run the same checks for every candidate at the same stage, tell candidates the checks happen, and delete the photos when hiring ends. Rules differ by country: the UK has data protection law and Illinois has biometric privacy rules. This is general information, not legal advice: get advice first.







