Guide
Job posting red flags: how to spot a ghost job
The wording patterns that mark ghost jobs, undefined scope, and commission schemes, and a free tool that decodes a posting in seconds. Assess your first role free.
Some job adverts describe a real vacancy with a hiring manager waiting behind it. Others describe a talent pool, a compliance exercise, or a role the company is still arguing about internally. From the outside they look identical, and the applicant pays the difference in wasted evenings.
The good news: misleading postings leak signals in their wording. This guide covers the phrases worth pausing on, what each usually means operationally, and the question that resolves it. If you want the fast version, our free Job Posting Decoder reads a pasted posting for these patterns in seconds, entirely in your browser.
Why job adverts mislead
Not every stale posting is a scam. Companies post roles they are not actively filling for mundane reasons: building a candidate pipeline for future openings, satisfying internal or legal requirements to advertise, signalling growth to investors, or keeping a listing live while the role's scope is still being negotiated. The recruiter is rarely trying to trick you personally. But the effect on you is the same — hours spent tailoring for a role nobody plans to fill this quarter.
The scale is not trivial. Analysis by the hiring platform Greenhouse of postings running through its own system found that roughly 18–22% qualified as ghost jobs — roles that were never filled or never intended to be filled. Employer surveys point the same direction, with meaningful shares of companies admitting to advertising roles they were not hiring for.
Ghost-job signals
The clearest ghost-job tell is evergreen language: "always accepting applications", "join our talent pool", "future opportunities". Those phrases mean the posting is a pipeline, not a vacancy. A real opening has a start date somewhere in its logic — a team that needs the work done, a backfill, a project with a deadline. When nothing in the posting implies any time pressure at all, ask why it exists.
The second tell is the missing human. Real roles have a reporting line and a team. When a posting names no manager, no team, and no context about who you would work with, the role may not be defined enough to hire for. Combined with a posting date months in the past, or a listing you recognise from the last time you searched, the odds of a live vacancy drop sharply.
A flag is a question, not a verdict — but three of these together usually mean your evening is better spent elsewhere.
Compensation red flags
"Competitive salary" with no numbers is a choice, and it is worth reading as one. A growing set of jurisdictions — Colorado, New York City, California, and Washington among them, with an EU-wide directive on the way — require salary ranges on postings. Employers in those places publish ranges because they must; employers elsewhere who publish them anyway are telling you something about how they negotiate. Silence is also information.
Commission-only compensation and "unlimited earning potential" framing deserve their own pause. Both shift the risk of the role onto you, and "be your own boss" language in an employed position often marks roles with high churn built into the business model. None of this is automatically disqualifying — some sales roles are honestly structured this way — but the posting should say clearly how the first six months pay. If it will not, the interview must.
Scope and culture red flags
"Wear many hats" reads as flexibility and often means the organisation has not decided what this job is. That matters at mid-career, because undefined scope is how you end up doing three roles at one salary, and how your next CV bullet becomes hard to write. "Other duties as assigned" in a senior posting carries the same warning.
Culture phrases decode the same way. "We're a family" correlates with blurred boundaries and guilt-priced overtime. "Work hard, play hard" and "fast-paced environment" frequently translate to understaffing. "Rockstar", "ninja", and "guru" titles usually mean the role is defined by enthusiasm rather than scope, level, or pay band. And urgency pressure — "immediate start", "apply today" — is either poor planning or manufactured scarcity; neither is your problem to absorb.
Each phrase alone is survivable. The question to bring to the interview: "Walk me through what this role owns in its first ninety days."
The junior title, senior requirements mismatch
Watch for postings that pair a junior or mid-level title with a senior shopping list: "Coordinator" roles demanding eight years of experience, "Associate" roles that own a budget and a team, "Manager" postings whose requirements read like a Director's. The mismatch is usually a salary-band decision. The company wants senior output priced at a mid-level band, and the title is where the discount is hidden.
This one matters doubly if you are mid-career, because taking a down-titled role reprices your next move too. It is also a fit question as much as a posting question: a role whose stated level and stated demands disagree cannot be assessed honestly until you know which one is real. Our guide on whether a job is worth applying to covers how to weigh seniority alignment before you spend an evening tailoring.
What good postings do
Reading for red flags works better with the positive case in view. Good postings state a salary range without being forced to. They name the reporting line, or at least the team and its size. They describe what success looks like in the first ninety days, which proves someone has thought about the role as work rather than as a wish list. They are specific about location and remote policy instead of "flexible" with an asterisk.
A posting like that is not automatically a good job — but it is a real one, written by an organisation that knows what it wants. Those are the postings worth your tailoring time, and the contrast they provide is the fastest way to calibrate your eye for everything above.
The red flags at a glance
| Red flag | What it may mean | The question that resolves it |
|---|---|---|
| "Always accepting applications" | Pipeline posting, not a live vacancy | "Is this role open now, and what is the hiring timeline?" |
| No named team or manager | Role not yet defined, or org in flux | "Who does this role report to, and how big is the team?" |
| "Competitive salary", no numbers | Pay set by negotiation leverage | "What is the budgeted range for this role?" |
| Commission-only / "unlimited earnings" | Income risk sits with you | "What do people in this role earn in months three and six?" |
| "Wear many hats" | Undefined scope, likely under-resourced | "What does this role own in its first ninety days?" |
| "We're a family" / "work hard, play hard" | Boundary and workload risk | "How do you handle crunch, and how often does it happen?" |
| Junior title, senior requirements | Senior work priced at a mid-level band | "How was the level for this role decided?" |
Decode a posting in ten seconds
You can run this whole checklist by hand, or paste the posting into the free Job Posting Decoder. It checks for the patterns above — evergreen language, missing pay data, scope and culture tells, level mismatch — and explains each flag it finds. It runs entirely in your browser: nothing is uploaded, nothing is stored, no account needed.
The posting is only half the decision, though. A clean posting can still be a weak match for your background, and a posting with two flags can still be the right move if the fit is strong — which is why fit matters more than keyword overlap. When a role passes the posting check, the next question is whether you should apply, and that is a fit question. You can assess your first role free and see the answer with reasoning you can inspect before you write a word.
FAQ
What is a ghost job?
A ghost job is a posting with no live vacancy behind it — the company is building a talent pool, meeting an internal or legal advertising requirement, signalling growth, or has quietly paused the role. The listing looks real; the hiring process behind it does not exist yet.
Why do companies post jobs that do not exist?
Common reasons: collecting candidates for future openings, satisfying policies that require public advertising, keeping recruitment metrics or growth optics up, and indecision — the role is still being scoped while the advert runs. Malice is rare; cost to applicants is universal.
Should I apply to a job with red flags?
Sometimes. A flag is a question, not a verdict — one vague phrase in an otherwise specific posting is noise. Treat two or three accumulated flags as a signal to ask direct questions early, and weigh the role against stronger options in your queue before spending an evening on it.
How can I check a job posting for red flags quickly?
Paste it into the free Job Posting Decoder. It flags ghost-job language, missing compensation, scope and culture tells, and level mismatch in seconds, in your browser, with nothing uploaded or stored.