# The Ghost Job Score, Six Dimensions to Apply, Verify First, or Skip

*Score any single job posting on six evidence dimensions in about ten minutes and land on Apply, Verify First, or Skip, the same way any two readers would.*

- Canonical URL: https://www.refolk.ai/candidates/guides/ghost-job-posting-score
- Pillar: Reading the market
- Format: Framework
- Published: 2026-11-16
- Last reviewed: 2026-11-16
- Reading time: 22 min
- Keywords: how to tell if a job posting is real, ghost job red flags before applying, is this job posting still active, job posted 60 days ago still open worth applying, evergreen job posting should I apply, talent pipeline posting vs real vacancy

## Key takeaways

- Greenhouse classifies 18 to 22% of postings on its platform as ghost jobs in a typical quarter, but that figure covers one platform, includes frozen and cancelled requisitions, and should not be used as the prior for every job board.
- Use the posting's first date on the employer's career site, not the job board's date, because reposting resets the board date and one seeker found a job shown as a day old on LinkedIn that had been on the employer's own site for over a year.
- A single age cutoff misfires: at 90 days, 27.2% of data science postings are still live against 11.5% for data engineering, so age has to be scored against the role family's own window.
- Evergreen requisitions never match the hire, because candidates are moved to a separate, unposted headcount requisition, so a missing requisition match proves nothing on a posting that says it is evergreen.
- Ontario requires employers with 25 or more staff to state whether a posting is for an existing vacancy, so a silent posting for an Ontario role at that size is a checkable gap, while silence elsewhere is neutral.
- Refolk's index holds 97,178 people with Recruiter or Talent Acquisition titles in the US but only 1,388 in construction, so for construction roles, where the ghost share is highest, a vacancy-check message goes to a small, findable team.

Use this before you spend 40 minutes tailoring a resume and cover letter. It helps you decide whether a posting is a live vacancy someone is filling, or a talent pipeline, a stale listing, or a role that will never be filled. It is for anyone applying selectively who wants each posting judged by the same rules every time. You score six evidence dimensions in about ten minutes and land on one of three calls: Apply, Verify First (with a specific check or message), or Skip.

## What counts as a ghost job, and how common is it?

A ghost job is a posting with no intent to hire. Greenhouse's State of Job Hunting report classifies 18 to 22% of the jobs posted on its platform as ghost jobs in any given quarter. Read that as background for one platform. It is not the starting probability for the posting in front of you.

The working definition behind that figure is narrow: a posting that received at least one application and produced no hiring activity afterwards, meaning no job-test submissions and no scheduled interviews. Greenhouse reported 18.9% for one quarter, and a later quarter came in at about 19% according to the Wall Street Journal. The share varies a lot by industry:

- Construction: 38%
- Art: 34%
- Corporate services: about 31%
- Legal: 29%

Before you use any of these numbers, note four limits:

- **The definition is Greenhouse's own.** It has not published the full coding rules.
- **It counts more than deliberate fakes.** Frozen and cancelled requisitions land in the same bucket. A requisition is the employer's internal record authorising a hire.
- **The population is skewed.** Greenhouse customers lean towards mid-size and larger companies with structured hiring.
- **No figure exists for each board.** No public ghost-job share exists for LinkedIn or Indeed.

### Why a real vacancy still carries risk

Fewer postings turn into hires than they used to. One labour-market analysis quoted by CNBC found hires per 10 postings fell by half over five years, from eight to four. Bureau of Labor Statistics data has shown job openings outnumbering monthly hires by more than 2.2 million. But ghosts explain only a small part of that drop. If one posting in five is a ghost, removing them all lifts the yield only from 0.40 to 0.50 hires per posting. Most of the gap is real jobs that went unfilled.

#### Ten postings, traced to hires

| Stage | Figure | Note |
| --- | --- | --- |
| Postings | 10 | All postings in the sample |
| Not ghost jobs | About 8 | After removing the 18 to 22% ghost share (Greenhouse platform only) |
| Hires | 4 | Four hires per 10 postings in the later year of the comparison |

*Even after the ghost share is removed, roughly half of the remaining postings do not end in a hire, so a confirmed live vacancy is still a bet.*

So this score answers one question: is it worth spending tailoring time on this posting? It does not tell you whether you will get the job, and it does not tell you whether you fit. Those are separate calls.

## The six dimensions and how to score each one

Score each dimension 0, 1, or 2. A 2 is evidence the seat is live, a 1 is neutral or unknown, and a 0 is evidence against. The anchors below are written so that two people looking at the same posting arrive at the same number.

| Dimension | 2 (live) | 1 (neutral) | 0 (against) |
|---|---|---|---|
| Stated vacancy status | "Existing vacancy" line or fill-by date | Silent where no rule applies; pipeline wording only | "Not an existing vacancy"; or silent where Ontario rules apply |
| True age vs family window | Career-site age under 30 days | Inside the family band; board date only; evergreen | Past the family band |
| Repost cadence | Posted once | One repost, or reposts with new req IDs | Two or more reposts, same req ID |
| Requisition match | ID live on career site | Evergreen declared; no public req IDs | ID closed or missing, no evergreen line |
| Team and start | Named team and a start or fill date | One of the two | Neither |
| Hiring evidence | Recent hires into this team or family | Hires elsewhere only, or nothing found | Freeze or cuts announced since posting |

Set one flag before you score: the **evergreen flag**. An evergreen requisition is a standing posting that collects applicants for a role the employer hires again and again. Set the flag when the posting uses pipeline wording such as "applications accepted on a rolling basis," "hiring ongoing," or "frequently hiring for this position." While the flag is on, age and requisition match cannot score 0.

### 1. Stated vacancy status

**What it proves:** a written commitment. In Ontario, if an employer has 25 or more employees on the day it posts, the posting must disclose whether it is for an existing vacancy. A pipeline posting has to say outright that there is no existing vacancy.

**How it lies:** silence is only a signal where a rule requires the line. A US employer, or an Ontario employer under 25 staff, has no duty to say anything. Also, a posting can carry pipeline wording and an explicit vacancy statement together. Some NVIDIA internship postings read "Applications are accepted on an ongoing basis. This posting is for an existing vacancy." Score the explicit statement as 2 and don't hold the rolling-basis wording against it.

### 2. True age against the role family's window

**What it proves:** how long the seat has gone unfilled, compared with how long seats like it normally stay open.

**How it lies:** job-board dates reset when a job is reposted. One seeker found a job shown as posted within the past day on LinkedIn that had been up on Apple's own careers site for over a year. Always take the date from the employer's career site. If you can only find a board date, the most this dimension can score is 1.

Score age against the family's window, not a single cutoff:

| Population | Live at 30 days | Live at 60 days | Live at 90 days |
|---|---|---|---|
| Tech, all (n=13,434) | n/a | 33.4% | 12.5% |
| Data science (n=103) | n/a | 49.5% | 27.2% |
| Data engineering (n=252) | n/a | 38.1% | 11.5% |
| Data analytics (n=243) | n/a | 30.0% | 13.6% |
| S&P 500 career sites, evergreen excluded | 42.8% | 23.6% | 14.3% |

The tech rows come from Hotfix Jobs' study of 13,434 tech postings. The career-site row comes from Zeltru's tracker of S&P 500 careers pages. The same study found hardware engineering postings 69.2% live past day 60, and embedded engineering 67.0%.

For scoring, sort families into two bands:

- **Long-lived:** data science, hardware engineering, embedded engineering. Under 30 days scores 2. From 30 to 90 days scores 1. Past 90 days scores 0.
- **Short-lived:** data engineering, data analytics, tech generally, and any family not listed. Under 30 days scores 2. From 30 to 60 days scores 1. Past 60 days scores 0.

Live windows for non-tech families have not been published. Until you have local evidence, use the S&P 500 career-site curve as the default, which puts them in the short-lived band.

### 3. Repost cadence

**What it proves:** repeated reposting of the same requisition suggests the employer is keeping the listing visible without moving anyone through it.

**How it lies:** in volume roles, reposting often means several seats. The test is the requisition ID. New IDs across reposts point to separate openings. The same ID reposted again and again points to a listing being refreshed.

### 4. Career-site and requisition match

**What it proves:** a requisition ID that is live on the employer's own careers page means the employer's hiring system still has the role open, not just the job board.

**How it lies:** an evergreen requisition will never match the requisition the hire is made on. See the evergreen section below. Small employers often don't publish IDs at all. Both cases score 1, not 0.

### 5. Specificity of team and start

**What it proves:** a named team, a named manager, or a start or fill-by date means someone has a specific seat in mind.

**How it lies:** generic postings are sometimes real and written lazily. That is why this dimension can't push a posting to Skip by itself.

### 6. Employer hiring evidence

**What it proves:** recent hires into the same team or role family mean the employer is actually converting postings into people.

**How it lies:** if you find no hires, you have found nothing. It is not evidence of a freeze. That is why the 0 anchor needs an announced freeze or cuts since the posting went up. Testing whether the employer as a whole is cutting is a separate job, covered in its own standard in this library.

### Signals that score nothing

LinkedIn's "Actively reviewing applicants" label and applicant counters don't feed any dimension. The common explanation of the label, that a poster or recruiter recently interacted with applications, comes from third-party explainers, not LinkedIn's own documentation. Seekers have also reported that a reposted job keeps its old applicant count. Use these only as a tie-breaker in your own head, never to change a score.

#### Evidence weight, strongest first

1. **Written vacancy statement** - Ontario existing-vacancy line or a fill-by date, made under legal duty
2. **Career-site requisition** - ID live, closed, or missing in the employer's own hiring system
3. **Career-site age and repost history** - First-post date against the family window; same or new req IDs
4. **Team and start specifics** - Named team, manager, start or fill-by date
5. **Board badges and counters** - Activity labels and applicant counts; tie-breaker only

*Signals that come from the employer's own records outrank signals that come from the job board.*

## How six scores become Apply, Verify First, or Skip

Add the six scores (out of 12), then apply the rules below in order. Stop at the first rule that fires. Applying the rules in order is what settles conflicting signals, and it is why two readers reach the same call.

> **Rule:** Decision rules, applied in order
>
> 1. The posting states it is not an existing vacancy: Skip. 2. Two or more dimensions score 0: Skip. 3. Total is 5 or below: Skip. 4. Total is 9 or above with no 0: Apply. 5. Anything else: Verify First, aimed at the lowest-scoring dimension.

When more than one dimension ties for lowest, aim the check at the one higher in the evidence stack: vacancy statement first, then requisition match, age, repost cadence, specificity, and hiring evidence.

The two dimensions that carry the most weight, age and requisition match, form a quick first read:

#### Age and requisition, read together

Horizontal axis runs from Inside the family window to Past the family window. Vertical axis runs from Req missing or closed to Req live on career site.

| Quadrant | What it means |
| --- | --- |
| Live and fresh | Apply if no other dimension scores 0 |
| Live but old | Verify First: ask whether the seat is still open |
| Fresh but unmatched | Verify First, unless the posting declares evergreen |
| Stale and unmatched | Skip, unless the posting declares evergreen |

*A live requisition rescues an old posting into Verify First, and a declared evergreen status rescues a missing match.*

Each Verify First has one target. Some targets are checks you run yourself, and some need a message:

| Lowest dimension | Verify action |
|---|---|
| Vacancy status (silent, Ontario rules apply) | Message: ask if it is an existing vacancy |
| Age (board date only) | Self-check: find the career-site date, rescore |
| Repost cadence | Message: ask if the req is open and how many seats |
| Requisition match | Message quoting the req ID |
| Team and start | Message: ask which team and target start |
| Hiring evidence | Self-check: employer's layoff and hiring record |

Once a posting clears to Apply, the 40 minutes of tailoring is the expensive part, and the effort is now justified. [Refolk](/candidates) builds the tailored resume and cover letter against that specific posting from your own history, so the time you save on Skips isn't eaten up by the Applies.

**Ghost job scoring sheet**

```
Posting: <title> at <employer>
Board and date shown:
Career-site first-post date:            Age in days:
Role family:                            Band: long-lived / short-lived
Evergreen flag (pipeline wording):      yes / no
Ontario rules apply (25+ staff, Ontario role):  yes / no

1 Stated vacancy status   _/2   evidence:
2 True age vs window      _/2   evidence:
3 Repost cadence          _/2   reposts:      same or new req IDs:
4 Requisition match       _/2   live / closed / missing
5 Team and start          _/2   team:         start or fill date:
6 Hiring evidence         _/2   evidence:

Total: _/12      Number of zeros: _
Rule that fired (1 to 5):
Decision: Apply / Verify First / Skip
Verify target dimension:
Check or message sent (date):
My wait limit:
Outcome and rescore:
```

*Paste one copy per posting into your tracker; fill every line before you decide.*

## What the law requires a posting to say about vacancy status

Ontario already requires a vacancy statement. New York and New Jersey have bills that would. Where a statement is required, it is the strongest single signal you can score. Where it isn't, silence is neutral.

| Regime | Status | Size threshold | Required line |
|---|---|---|---|
| Ontario ESA s.8.5 | In force | 25+ employees | Existing vacancy: yes or no |
| New York S8877 | Passed both chambers; signature unverified | 100+ employees | Fill-by date, or "not for a current vacancy" |
| New Jersey S2136 | Out of committee; not law | Unverified | Existing vacancy and timeline |

### Ontario

Section 8.5(1)(a) requires "a statement disclosing whether the posting is for an existing vacancy or not." The rules sit in O. Reg. 476/24 and Part III.1 of the Employment Standards Act. Four details matter for scoring:

- The employer's size is counted on the day the job is posted.
- The rules don't cover a general recruitment campaign or a help-wanted sign that doesn't advertise a specific position.
- The Act sets no minimum posting duration, so how long a posting has been up says nothing about compliance.
- Interviewed candidates must be told within 45 days of their last interview whether a hiring decision has been made. This applies after an interview, not before you apply.

Toronto is where this rule does the most work. In Refolk's index, 8 of 25 sampled Canadian recruiter profiles were based there. That is a small sample, but it points the same way as common sense: many of the postings Canadian seekers see are covered by the rule.

### New York and New Jersey

New York's S8877 would require one of two statements. A job to be filled within 90 days would read "This position is for a current vacancy, and the employer intends to fill this position by (date)." A posting with no plan to fill would read "This position is not for a current vacancy, but the employer is seeking resumes to review in the future when jobs become available." If the fill date is more than 90 days away, the ad must say the position will be filled no sooner than a stated date. Filled postings would have to come down within two weeks. Proposed penalties are $2,500 per non-compliant post, rising to $5,000 if it isn't fixed within 30 days.

New Jersey's S2136 would require a statement of whether the posting is for an existing vacancy. Sources disagree on how long a no-vacancy ad could run (90 or 120 days). Penalties would be capped at $300 for a first offence and $600 after that, with each month counted as a separate violation.

How to re-check: look up the bill number on the state legislature's bill-status page. A bill isn't law until it is signed. Until then, treat a New York or New Jersey posting with no statement as silent where no rule applies, and score it 1.

## Evergreen and talent-pipeline postings

An evergreen or pipeline posting is a standing listing that collects applicants for future or repeated openings. It is not a fraudulent listing, but you are applying to a pool, not a seat. Score it with the evergreen flag on, and expect the decision to come from specificity and hiring evidence.

The mechanics explain why. GitLab's hiring handbook says no candidate is hired to an evergreen requisition. Instead, candidates are moved to an approved headcount requisition, and that team-specific requisition is not posted for applications. The University of Washington uses evergreen requisitions to support existing and anticipated openings for jobs that departments hire routinely and often unpredictably, or seasonally and in high volume. These typically stay open for six months to a year.

Two consequences follow:

- **Age is uninformative.** A six-month-old evergreen posting is behaving normally. With the flag on, age scores 1.
- **Requisition match is uninformative.** The hire happens on a requisition you can't see. With the flag on, a missing match scores 1.

> A missing requisition match proves nothing on a posting that tells you it is evergreen.

Where the line falls:

- **Pipeline wording and an explicit "existing vacancy" statement:** score the statement as 2. This is the NVIDIA pattern.
- **Pipeline wording, no statement:** set the evergreen flag. The vacancy dimension scores 1.
- **An explicit "not an existing vacancy" or "not for a current vacancy":** rule 1 fires and you Skip the tailoring. If you still want to be in the pool, a standard resume is the most to spend on it.

## The ten-minute scoring procedure

Run the procedure in order, one posting at a time, with the scoring sheet open. Steps 1 to 6 take about ten minutes. Step 7 runs only when the decision rules return Verify First.

#### Score one posting

1. **Read the vacancy line** - Look for an existing-vacancy statement, a fill-by date, or pipeline wording, and note whether Ontario's rules apply. Tag it stated vacancy, stated pipeline, or silent, and set or clear the evergreen flag.
2. **Find the true first-post date** - Open the same role on the employer's career site and compare its date with the board's. Record the age in days from the career site, or note that only a board date exists.
3. **Compare the age with the role-family window** - Place the role in the long-lived or short-lived band and score the age against it. With the evergreen flag on, score 1.
4. **Count reposts and compare their requisition IDs** - Search the board for the same title at the same employer. Record the repost count and whether the requisition ID changes.
5. **Match the requisition ID on the career site** - Search the careers page for the ID. Record live, closed, or missing, and apply the evergreen condition.
6. **Score specificity and hiring evidence, then decide** - Check for a named team, a start date, and recent hires, then total the six scores. Apply the decision rules in order and record Apply, Verify First, or Skip.
7. **Send one Verify First message if triggered** - Run the self-check or send one message aimed at the lowest dimension. Write your wait limit in the tracker before you send.

Practitioners disagree about the order. Some run the whole checklist before sending any note. Others check the career site first, on the view that the best time to get in is within one to three days of a job appearing on the employer's own careers page. The order above puts the career-site date in step 2, so you get the timing benefit without skipping the vacancy line.

## How the ghost job call goes wrong

Most errors come from reading a signal outside its context. Every failure below produces a false ghost (a real vacancy you skip) or a false live (a dead posting you tailor for). Read this section before you trust a score.

> **Watch out:** Board dates are the most common false signal
>
> Reposting resets the date a job board shows. If you score age from a board date, you will call stale postings fresh and give up the most useful dimension in the score.

1. **Treating the vacancy line as all-or-nothing.** A posting can say "ongoing basis" and "existing vacancy" in the same paragraph. Score the explicit statement. Silence from an employer under 25 staff, or from outside Ontario, is not a red flag.
2. **One age cutoff for every role.** At 90 days, 27.2% of data science postings are still live against 11.5% for data engineering, a gap of more than double. Hardware postings are 69.2% live at 60 days. A single 60-day cutoff wrongly flags most long-lived families. Volume employers stretch age further: one career-site sweep found Whataburger Restaurants with 4,193 open postings, 83.7% of them older than 90 days, at a median age of 245 days. Age there reflects the requisition type, not whether anyone gets hired.
3. **Reading board visibility as employer intent.** Indeed's employer FAQ is reported to show free job posts for up to 30 days in the US, Canada, and most of Western Europe. How long a post stays visible depends on board rules and how the employer paid, so disappearing from a board is not the same as being filled.
4. **Counting reposts without checking IDs.** In volume roles, repeated reposts often mean several seats. Only reposts that share a requisition ID score 0.
5. **Calling every missing requisition a ghost.** Evergreen requisitions never match the hire requisition. Without the conditional scoring, every honest pipeline posting looks like a ghost.
6. **Trusting platform badges.** The common reading of "Actively reviewing applicants" comes from third-party explainers. Seekers report that applicant counters carry over when a job is reposted. Both carry no score.
7. **Using 18 to 22% as the prior for every board.** That share covers Greenhouse customers only and includes frozen and cancelled requisitions. It says nothing about any particular board.
8. **Reading recruiter silence as proof.** No published reply-time threshold exists. Ontario's 45-day duty starts only after an interview, so it can't be used to judge a message sent before applying.
9. **Assuming a confirmed vacancy will be filled.** Most of the fall in hires per posting is real jobs that went unfilled. A Verify First that comes back "yes, it's open" moves the posting to Apply. It does not make the job any safer than other live postings.

## Sending the Verify First message

A Verify First message is a single, short question to the recruiter or hiring contact, aimed at the dimension that scored lowest. Send it before you tailor anything, and decide in advance how long you will wait.

There are plenty of people to send it to. In Refolk's index, people with Recruiter or Talent Acquisition titles are spread like this:

**97,178 - People with Recruiter or Talent Acquisition titles in the US, in Refolk's index**

Titles are matched on the profile headline, so this is an upper bound; sampled titles included a "Founder & CEO".

| Segment | Count | Derived |
|---|---|---|
| US, Recruiter or Talent Acquisition | 97,178 | Baseline |
| Canada, same titles | 4,765 | US is 20.4x Canada |
| US, Construction industry | 1,388 | 1.4% of US recruiters |

Construction is where these numbers matter most. It has the highest ghost share in Greenhouse's industry breakdown, at 38%, and it has a thin recruiting layer. Sampled employers in that segment include DPR Construction, Clark Construction Group, Gilbane Building, and Consigli Construction.

**1,388 - US recruiters in the Construction industry, in Refolk's index**

That is 1.4% of US recruiters, so a construction vacancy check goes to a small team where a named recruiter is quick to find; whether they reply is not established.

**Verify First message**

```
Subject: Req <ID>, <job title>: still an open vacancy?

Hi <first name>,

I'm preparing an application for <job title> (req <ID>) and want to confirm one thing before I submit:

1. Is this an existing vacancy being filled now, or a posting for future openings?
2. Is req <ID> still open, and is it for one seat or several?
3. Which team does this role sit in, and is there a target start date?

A one-line reply is plenty. Thank you.

<your name>
<profile link>
```

*Keep only the numbered question that matches your lowest-scoring dimension; one question gets answered more often than three.*

Two rules for the wait:

- **Write your wait limit in the tracker before you send.** No source sets a reply-time threshold, so any number you use is your own decision, not a finding. Choose one and apply it to every posting.
- **Rescore on a reply. Skip at the limit.** A reply that confirms the seat raises the target dimension, and you rerun the decision rules. No reply by your limit moves the posting to Skip. Leave the sheet in your tracker in case the role comes back with a new requisition ID.

## Keeping your scores honest over time

The score stays reliable only if the inputs are refreshed and you check your own calls. Three things change: disclosure laws, role-family live windows, and your own record of which calls turned out right.

- **Re-check the laws.** Look up S8877 and S2136 on the New York and New Jersey legislature bill-status pages. If either is signed, silence from a covered employer in that state moves from 1 to 0, just as it does in Ontario.
- **Refresh the live windows.** Lifespan studies are re-run regularly. Update your band assignments when a new study covers your role family, and especially when a non-tech family gets its first published window.
- **Audit your own calls.** Every few dozen postings, compare Verify First outcomes with what the scores predicted. If the same dimension keeps being overturned by replies, your anchors for it need tightening.

The ghost score and your fit are separate calls. The ghost score tells you whether the seat is real. Refolk's fit score tells you how well you match the posting. Run the ghost score first, so you only spend time measuring fit on postings that can actually hire you.

#### Before you mark a posting decided

- [ ] The age comes from the employer's career site, or the sheet says only a board date was found and age is capped at 1.
- [ ] The role family is assigned to the long-lived or short-lived band, and age was scored against that band.
- [ ] The evergreen flag is recorded, and age and requisition match were scored conditionally when it is on.
- [ ] Ontario applicability (25+ staff, Ontario role) is recorded before scoring silence on the vacancy line.
- [ ] The repost count is recorded along with whether the requisition IDs are the same or different.
- [ ] The requisition ID is recorded as live, closed, or missing on the careers page.
- [ ] No platform badge or applicant counter changed any score.
- [ ] The decision rules were applied in order, and the rule that fired is written on the sheet.
- [ ] For Verify First, the target dimension, the message date, and your wait limit are all in the tracker.

## Frequently asked questions

### How can I tell if a job posting is real before applying?

You can't prove it from the posting alone, but you can score the evidence. Check six things: any stated vacancy status, the age on the employer's career site measured against the role family's normal window, whether it keeps getting reposted, whether its requisition ID is live on the careers page, whether it names a team and a start date, and whether the employer is visibly hiring. Two or more failing signals means Skip. A mix means send one verification message.

### Is a job posted 60 days ago still worth applying to?

It depends on the role family, and the date has to come from the employer's career site. Among tech postings, 33.4% are still live at 60 days. For hardware engineering it is 69.2%, and for data analytics 30.0%. In a long-lived family, 60 days scores neutral. In a short-lived family, past 60 days scores against the posting. If the requisition ID is still live on the careers page, Verify First rather than Skip.

### Should I apply to an evergreen or 'hiring ongoing' posting?

Apply only if the other evidence supports it, and know what you are applying to. At GitLab, nobody is hired to an evergreen requisition. Candidates move to a separate, unposted headcount requisition. These postings can stay up for six months to a year, so don't count their age or a missing requisition match against them. Look at team specificity and hiring evidence instead. If the posting says outright that there is no existing vacancy, skip the tailoring.

### Does 'Actively reviewing applicants' on LinkedIn mean the job is real?

Not reliably. The explanation that it means a poster or recruiter recently interacted with applications comes from third-party explainers, not LinkedIn's own documentation. Applicant counters have also been reported to carry over when a job is reposted. Treat both as tie-breakers that never change a dimension's score. The career-site requisition and the true first-post date tell you far more.

### How long should I wait for a recruiter to reply to a vacancy check?

No published threshold exists, so set your own limit before you send and write it in your tracker. When the limit passes with no reply, move the posting to Skip. Don't borrow Ontario's 45-day rule. It only requires employers to tell interviewed candidates whether a hiring decision has been made, so it says nothing about a message sent before you apply.

### What does Ontario's existing-vacancy statement mean for me?

If the employer has 25 or more staff on the day it posts, an Ontario public job posting must say whether it is for an existing vacancy. A pipeline posting has to say there is no existing vacancy. An explicit 'existing vacancy' line is the strongest single signal in this score. A posting that should carry the line but doesn't is a gap worth asking about. General recruitment campaigns are exempt.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/ghost-job-posting-score*
