I'll give you an example I've experienced myself:

I save all the jobs I apply to, so it's fairly easy to check/compare and I found plenty of cases where job ads get reposted after some time.

In one instance, I applied for a role in December '25, got a (boilerplate) rejection email a couple of days later (although my profile directly matched the job requirements and I had previous experience working in that specific field), job ad goes offline and re-appeared 3 months later - exact same time and job description.

▲

crazygringo 3 hours ago | parent | next [-]

That's not a ghost job. That sounds like they picked some resumes and rejected the rest and hired someone, and then three months later they either needed another person to also do the same job, or it didn't work out with the original hire so they opened the hiring back up.

	▲	tagyro 3 hours ago \| parent [-]
		if you believe that, I have a bridge to sell you This is not an isolated case, I have multiple job ads that get reposted every couple of months

▲

sib 2 hours ago | parent | prev [-]

Sorry, but why is that a problem? If they didn't find someone, they closed the posting, then reopened it later, what is the issue?

Or, as in some cases, perhaps they did find someone? I've been at companies where we hired many engineers sequentially over time using the same job description. Should we just have arbitrarily changed the JD?

	▲	thewebguyd 2 hours ago \| parent \| next [-]
		> Should we just have arbitrarily changed the JD? No, but unique IDs for postings could help in that situation. If you want to hire, say, 10 engineers, you have 10 separate job postings with their own unique ID, they get taken down as each position gets filled. Gives candidates visibility into how many positions the company is hiring (am I competing against 1,000 for 1 position or for 10 positions?), and clear visibility that hiring is happening and how many roles are left to fill. > If they didn't find someone, they closed the posting, then reopened it later, what is the issue? Closing & reopening is the problem, I suspect. Forces a re-application in some cases. I'm not sure how much any kind of legislation can help here though, just sounds like government overreach. I don't think there's really any good solution. Easy enough to say "you can't post a job to "just collect resumes" you must actually be hiring, and intend to hire someone" but that doesn't account for situations where maybe the company did actually intend to hire, but later on mangement changed their mind...would that be considered a ghost job?
	▲	FireBeyond 2 hours ago \| parent \| prev [-]
		Yeah, much as it sucks, there's a gap between "we were never going to hire anyone" and "you must hire someone, if you put up a job ad".