04 Sept 2026
The same listing surfaces in your feed for the third month running. Same title, same four bullet points, a fresh date on top. You already applied to it in June and heard nothing. Learning how to spot ghost jobs starts right there, in the card itself, because ghost jobs, duplicate reposts, and fake job postings all sit in the same results list as the roles someone is actually trying to fill this week.
The usual answers do not help much. "Half the market is fake" changes nothing about which twelve tabs you have open on Monday morning, and "just apply to more things" does not tell you where. Both leave you sorting by feel, which is how good listings get skipped and dead ones get four applications.
This article gives you three things you can use tonight: a way to tell three different problems apart, twelve signals you can read in a listing along with what each one does not prove, and a five minute check to run before you spend an evening on an application.
Quick answer: Listings that waste your time fall into three groups: a ghost job, a duplicate, and a scam. The card itself usually tells you which one you are looking at. Rank ghost jobs lower, apply once to a duplicate through the right path, and stop responding to a scam and report it.
A ghost job is a listing from a real employer that no active hiring process sits behind right now. The company exists, the job description is genuine, and your application still goes nowhere, because nobody on the other side is currently moving candidates through a process for that card.
Why an employer keeps such a posting up is a separate question with several distinct answers, and it changes what you should expect from the role. That breakdown belongs to why companies post ghost jobs. For your purposes here, the motive does not change the move: you are deciding how much of your week a card deserves.
A duplicate is one real opening that reached your results list several times. A scam is a listing with no employer or no job behind it, aimed at your money, your documents, or your identity data. Same search page, three completely different responses.
| Type | Who is behind it | What it costs you | How it usually shows up | Your move |
|---|---|---|---|---|
| Ghost job | A real employer whose posting has no active hiring behind it right now | Evenings, attention, and slots in your weekly application budget | A card that returns with identical wording, high posting age, vague scope and no named team | Apply if the fit is strong, rank it below verified openings, expect no timeline |
| Duplicate listing | The same employer, plus aggregators, job feeds, and one or more staffing agencies | Repeat applications for a single opening and a record you can no longer read | Near identical text on several sites, or one role split across many cities | Find the canonical card and apply once, ideally through the employer's own system |
| Scam | Someone who is not the employer, or an operation with no job at all | Money, ID documents, bank details, account access | Free email domains, lookalike company names, an offer with no real conversation, payment or ID requests | Stop responding, send nothing, save everything, report the listing |
Every section below points back to this table. When a signal fires, the useful question is not "is this real" but "which of these three am I looking at, and what does that type deserve from me."
Most advice hands out signals as verdicts. That is how people end up skipping perfectly real openings because a card is six weeks old. The third column below is the one that protects you: it says what each signal does not prove.
Read the table as a scoring tool, not a filter. Two or more signals from rows one through eight means rank the card lower and check before you apply. Any single signal from rows nine through twelve means stop, because those are about money and identity rather than wasted time.
| What you see in the listing | What it usually points to | What it does not prove | What to do |
|---|---|---|---|
| Identical text reposted across several months | Ghost or duplicate | That the employer never hires; some teams refresh cards on a schedule | Compare the two versions word for word before applying again |
| High posting age with no edits to requirements or location | Ghost | That the role is dead; long searches for specialized roles are common | Apply lower in your priority list, not first thing Monday |
| No team, no manager, no first project named | Ghost or pipeline collection | That the job is fake; some employers publish thin descriptions | Run the specificity test in the section below |
| No pay range, while the same employer names ranges on other cards | Ghost | Anything on its own; practices differ by employer and location | Compare against that employer's other current listings |
| The role does not appear on the employer's own career site | Duplicate or scam | That it never existed; feeds lag and cards expire unevenly | Search the career site by title, then by requisition ID |
| Requisition ID missing, or different IDs on cards with identical text | Duplicate | Fraud; syndication rewrites identifiers all the time | Treat the career site version as canonical |
| Wording like "always accepting applications" or "join our talent community" | Pipeline collection, not a specific opening | That your application disappears; some pipelines do convert | Apply if the fit is real, expect no process, do not follow up weekly |
| A generalized employer ("our client, a leading firm") and a broad location | Staffing agency listing, legitimate but often reposted | Deception; this is a normal format | Ask the four questions in the agency section before sending a resume |
| The apply button leaves for a domain unrelated to the employer or any recognizable applicant tracking system | Scam risk | Guilt; small employers use varied vendors | Stop, verify the domain from the career site, apply only from there |
| Recruiter messages arrive from a free email domain or a lookalike company domain | Scam | Nothing else you need; treat it as a stop | Do not reply, verify through contacts you found yourself |
| An offer, or an entire interview, handled inside a chat app with no live conversation | Scam | Remote hiring in general; real remote processes still include calls | End the conversation, save the thread |
| Any request for payment, equipment fees, a check to deposit, SSN, or bank details before a written offer | Scam | Nothing; this is the clearest line in the article | Send nothing, report the listing, keep the evidence |
The point of the middle column is your own sanity. A card with two soft signals is a lower priority, not an accusation, and you have limited evenings to spend on either.
The date on a listing is rarely the date the job opened. A repost resets the counter, so "posted 3 days ago" can describe a card that first appeared in March. Relative labels like "30+ days ago" hide the actual age entirely, and some cards carry the date the aggregator ingested them rather than the date the employer published anything.
That is why the two most repeated rules in job search videos do not survive contact with real listings. "Older than 30 days means fake" and "older than 90 days means dead" both sound decisive and neither one is supported by anything you can check. Specialized roles, roles with licensing requirements, and roles in small markets routinely stay open longer than that.
So use age for sorting, not for judgment. A long stretch with no visible edits pushes a card down the queue, and that is all it does: no particular cutoff has anything checkable behind it, so treat the one you pick as an ordering convenience rather than a verdict on an employer. A fresh card gets applied to first because your application lands while someone is still reading the pile.
To find the real age, open the employer's career site and locate the role by title. Note the requisition ID and the date shown there. Then compare the description on the board with the description on the career site, looking for changed requirements, changed locations, or changed compensation language. A card that has been quietly edited is usually attached to something live.
The counterexample matters: some always open listings are honest. High turnover roles, shift based roles, licensed trades, and seasonal peaks keep cards up while genuinely hiring, and the tell is that those listings change over time rather than repeating word for word. Why an employer would keep one up is covered in why companies post ghost jobs.
Instead of reading between the lines, count what is actually named. A requisition written by someone who needs a specific gap filled usually contains most of the following six items.
The fewer of these a card closes, the more likely it is collecting resumes rather than filling a defined hole. That is a probability, not a diagnosis. Plenty of real openings are written by someone in a hurry, and internal templates strip detail out of good jobs all the time.
Pay ranges deserve care. Whether a range appears depends on the employer, the platform, and where the role is based, and requirements differ across states, so a missing range on its own proves nothing. The comparison that carries information is internal: if the same employer publishes ranges on ten other current cards and not on this one, that is worth noting. This is general information, not legal advice, so check current rules for your state through official sources.
If the description leans on phrases you cannot verify, like "fast paced environment" or "wearing many hats," the job posting language decoder covers what those phrases tend to signal about the work itself.
Duplicate job listings are not a trick. They are what happens when a single requisition gets syndicated. Aggregators pull cards from employer career sites automatically, employers push feeds to several boards at once, two or three staffing agencies work the same client role, and a multi location requisition splits into one card per city.
To find the canonical version, look for four things: matching description text, a requisition ID that appears on more than one card, the earliest first posting date you can establish, and the presence of the role on the employer's own site. The career site version is the one that feeds an actual applicant tracking system record.
Then apply once. Sending the same resume through three boards does not raise your odds, and it can create duplicate candidate records that make your status unreadable to everyone including you. If you are unsure which path to pick, applying on a job board or the company website walks through the tradeoffs.
One exception worth naming: if an agency card and an employer card describe the same role, choose one channel and stay in it. Applying through both can put two submissions of your resume in front of one hiring manager, which usually helps nobody.
An agency card reads differently. There is no employer name, just "our client, a leading company in the sector." The location is broadened to a metro area. The contact is a recruiter rather than a hiring team. None of that is a red flag, and treating agency listings as fake will cost you real interviews.
What is true is that agency cards are often reposted and worth verifying before you send a resume, because agencies keep a bench of candidates ready for roles that may or may not be active this month. So ask before you send anything. Four questions, in a short message or on the first call:
The fourth question matters more than it looks. If two agencies submit you to the same employer, ownership of your candidacy can become confused, which is a problem you have to untangle from the outside. Ask for named consent per company and put it in writing.
Everything above is about time. This section is about money and identity, and the correct response is different: you stop, you do not negotiate, and you do not try to confirm your suspicion by playing along.
Treat these as stop signals: a company name or logo that nearly matches a well known brand, with a domain that is off by a character or a hyphen; recruiter mail from a free email domain; a job offer extended without a single live conversation; a request to pay for equipment, software, or training up front; a check sent to you with instructions to deposit it and return part of the amount; onboarding paperwork requesting SSN, bank details, or ID scans before a written offer; pay well above market for an entry level role; a push to move the conversation into a personal messaging app; any mention of cryptocurrency or gift cards; and pressure to decide within hours.
You do not need several of these. One is enough to close the tab.
The rule is simple and it is the one people skip: verify a contact using information you found yourself, never the phone number or email address contained in the message. A scam message will happily give you a number that a confederate answers.
Open the employer's official site directly, not through a link in the email. Compare the applicant tracking system domain on the apply page with the domain on the career site. Check whether a recruiter profile connects to a company that visibly exists, rather than checking whether a company exists because a profile says so.
If you want written confirmation, keep it to three lines and use placeholders for your own details:
"I am looking at a posting for [role title] dated [date] on [source]. Could you confirm whether this requisition is currently active? If it is, could you tell me who is handling it?"
Keep it short so the company can answer it quickly, and send it to a contact you found on the official site.
Order matters here. Each step either ends the check or feeds the next one, so run them in sequence rather than picking favorites.
Five minutes is the point. A check you skip because it takes twenty minutes protects nothing, and the first two steps alone often tell you whether a card deserves more of your evening.
A normal application asks for a resume, contact details, a general work authorization question, and sometimes voluntary demographic questions you can decline. That is the whole list at the application stage.
These do not belong anywhere before a written offer: your Social Security number, your full date of birth, scans of your passport, driver's license, or immigration documents, bank account or routing numbers, and background check consent collected outside the employer's official portal. Details like these usually belong after an offer, collected through an official employer controlled system you reached from their own site.
Three habits reduce the damage if a card turns out to be a scam. Use a separate email address for your search. Keep your home address and personal photo off public profiles. Refuse to complete an onboarding form until you have a confirmed offer in writing, and say so plainly if asked; a legitimate employer should be able to explain its process and route sensitive forms through an official channel.
The worry that applications exist mainly to harvest personal data comes up constantly, and it is not something you can confirm or rule out from outside a company. What you can control is the boundary above. This is general information rather than legal advice, and requirements vary by state and employer, so verify current rules through official sources.
Nothing dramatic happened. You sent a resume into a card that was not moving, which costs you an evening, not a search. Log it, do not reapply every time the same requisition reappears, set one follow up window, and close the entry when the window passes.
Silence is not evidence either way, and the ordinary explanations have nothing to do with whether the job was real. What silence after an application actually means covers the causes, and when a recruiter goes quiet mid process covers the version that hurts more, after several rounds.
If the card crossed into scam territory, reporting is a short, procedural task. No channel promises an outcome, and none of this is legal advice; the value is that you stop the exchange and keep a record.
| What happened | Where to report it | What to save |
|---|---|---|
| A listing looks fabricated or the description matches no real role | The reporting function on the platform where you found it | Screenshot of the card, its address, posting date, your application confirmation |
| Someone is using a real employer's name or branding | The employer, through a contact you found on its official site, plus the platform | Full message with headers, sender domain, the listing, any attachments |
| Someone requested money, a check deposit, or payment details | The platform, government consumer fraud reporting channels, and your bank if any money moved | The whole thread, payment instructions, account details you were given, dates |
| You already sent ID documents or bank details | Your bank or card issuer, and identity theft reporting channels | A written timeline of what you sent and when, plus every message and receipt |
If identification data left your hands, the standard protective steps apply, including placing a freeze with the credit reporting agencies and watching account activity. Do it the same week rather than waiting to see what happens.
Add four columns to whatever tracker you already use: first posting date, how many times the card has reappeared, source (board, agency, or career site), and the result of your five minute check. Read it once a week.
The reading is simple. If a large share of last week's applications went to cards you never verified, that is the thing to fix first, ahead of rewriting your resume again. Counting your own "share of fake jobs" by feel produces a number that changes with your mood; counting verified versus unverified applications produces something you can act on.
If you use Global Work AI, features like AI Job Recommendations and AI Auto Apply change how quickly you can send applications, not whether a given card has hiring behind it, so the five minute check stays yours to run.
A ghost job is a posting from a real employer with no active hiring behind it at the moment, so the cost to you is time. A scam has no employer or no job at all behind it, and the cost is money or personal data. The response differs: ghost jobs get ranked lower in your queue, scams get closed and reported.
Check the employer's own career site first, since a role removed there while still visible on a board usually means the card is stale. Compare requisition IDs and dates between the two, and look for edits to the description over time. If it is an agency listing, ask the recruiter directly whether the requisition is active right now.
Not necessarily, and you usually cannot tell from outside. A repost can follow a changed requirement, a paused budget, a candidate who fell through, or a routine refresh of an aging card. If you interviewed and then saw the role reappear, one direct question to your contact about what changed is more useful than guessing.
No. Whether a range appears depends on the employer, the platform, and the location, so absence alone tells you very little. The comparison worth making is with that employer's other current listings; if most of them name ranges and this one does not, note it as one soft signal among others.
An offer with no live conversation, any request for payment for equipment or training, a check you are asked to deposit and partially return, requests for SSN or bank details before written offer paperwork, and contact from a free or lookalike email domain. Pressure to decide within hours belongs on the same list. One of these is enough to stop.
No. Pick the canonical path, usually the employer's own career site, and apply once. Multiple submissions create duplicate records rather than extra visibility, and when two agencies submit you for the same role, ownership of your candidacy gets disputed instead.
You cannot tell from the speed. Instant rejections generally come from an automated screen checking conditions the employer configured, such as location, work authorization, or a required credential. It says something about the filter you hit, not about whether hiring is happening.
Run this before your next batch of applications rather than after.
None of this makes hiring faster or turns a quiet week into interviews. What it removes is a known way to lose evenings: sending careful applications into cards that were never going to answer, and handing information to people who were never going to hire you.
04 Sept 2026
A diagnostic for applications that disappear without a reply. Audit your last 30 applications, find which of four stages is breaking, and fix that one instead of sending more.
04 Sept 2026
A route instead of a list of forty jobs: how to tell what actually gates the role you want, what employers accept in place of a degree, and how to prove it. Includes a gate-type decision table, an evidence worksheet, a search kit, and the wording for the education field on an application form.
04 Sept 2026
A tool-agnostic spec for tracking applications: which columns earn their place, one status vocabulary with transition rules, and the formulas that tell you what is due. Build it in Sheets, Excel, or Notion in one evening.
09 Sept 2026
A copy-and-adapt template for online job applications, field by field. Covers the answers most people stall on: salary expectations, reason for leaving, contact permission, and knockout screening questions.
04 Sept 2026
A follow-up guide for applications that went quiet. Wait windows by stage, a channel-by-situation table, and six short scripts you can adapt in two minutes.
07 Sept 2026
A role-by-role look at IT careers: what each job involves, typical pay, and how to get started.
