Skip to content

200 US Software Engineer Postings, Checked for Ghost-Job Signs

Compiled by Sharif-Ali Asadullayev (GetDiogenes, Baku), with analysis and drafting assistance from Claude (Anthropic).

We ran 200 recent US "software engineer" postings through Diogenes' ghost-job check, twice. About 1 in 5 were flagged as high-risk, and almost all for one reason: a staffing agency advertising for a client it didn't name. This is our AI's judgement of the postings, not proof that any job is fake.

At a glance#

We took 200 recent "software engineer" postings from a large US job board and asked Diogenes' AI whether each one showed the signs of a ghost job. We ran the whole set twice.

Run 1 (21 Oct)Run 2 (22 Oct)Average
Flagged high-risk47 of 200 (23.5%)42 of 200 (21.0%)22.3%
Average risk score33.6 / 10029.4 / 10031.5 / 100

"Flagged" means the AI judged the posting high-risk for being a ghost job. Nobody confirmed any verdict with an employer. Read every number here as "how often postings look like this", not "how many jobs are fake".

What got flagged, and why#

Each posting got a risk score from 0 to 100 and one main reason. The scores split cleanly: in run 2, no posting scored between 31 and 59, so the cut-off between "high-risk" and "not" did not decide many cases.

Main reason (run 2)Flagged postings
Staffing agency posting for an unnamed client, or a general talent pipeline40
Role depends on the company winning a contract1
Posting set to stay open until 1 January 21001
Total42

A staffing-agency posting is not fake by default. Agencies fill real jobs. But a posting for "our client" with no named employer, no team and a generic description can also be a way to collect résumés for roles that don't exist yet. From the posting alone, you can't tell which, and the AI scored that uncertainty as risk. Six more postings were noted as agency posts but scored low; some of those named the employer they were hiring for.

In run 1, about 30 of the 47 flags gave the same main reason. Most of the rest were "vague description" flags, which we think were partly caused by the short text the AI was given (see the method section).

Older postings, more flags#

PostedPostingsFlagged, run 1Flagged, run 2
In the last 7 days11712 (10%)8 (7%)
8 to 30 days before4724 (51%)22 (47%)
31 to 60 days before3611 (31%)12 (33%)

This is mostly the same finding as above, seen another way. Agency postings sat in the older listings: in run 2, 9 of the 117 newest postings were classed as agency posts, against 23 of the 47 from 8 to 30 days old. In this sample, a posting still up after a month was more often an agency's standing ad than an employer's open seat.

What to do with this#

If the posting is from a recruiter or staffing agency, ask before you send your résumé:

A good recruiter answers these easily. If they won't say whether a real opening exists, treat it as a pipeline, and don't count it as an application.

For any posting: check the date, look for the same role on the employer's own site, and be wary of end dates far in the future or roles that depend on a contract not yet won.

One view from Reddit#

When we shared the first run on Reddit, one commenter replied: "Most are data mining. They resell the info that you give them for free." Our data can't test that. It shows that most flagged postings came from agencies that didn't name the employer. It says nothing about what happens to the résumés afterwards.

Method, limits and citing#

Limits:

We built GetDiogenes, which checks job postings for ghost-job and scam signs. This report uses that same tool, so read it as our tool's view of these postings.

Cite as: Asadullayev, S.-A., with Claude (Anthropic). 200 US Software Engineer Postings, Checked for Ghost-Job Signs. GetDiogenes, October 2026. getdiogenes.com/research/200-software-engineer-jobs

Not sure about a posting? Check it free →