The Posting Has Been Up Since June. Should You Apply?

A three-month-old job posting can mean the role is dead, the hiring manager is picky, or the company runs an open pipeline. Here's how to tell the difference before you spend two hours on an application.

By JobPost Team · Sep 26, 2026 · 4 min read

You find a posting that fits. Then you notice the date: June 11. It is now September. The instinct is to close the tab.

Don't, yet. A stale date is real information, but it points to at least five different situations, and only two of them are a waste of your time.

What A Three-Month-Old Posting Actually Means

The posting date tells you when the listing went live. It tells you nothing about whether anyone is reading the applications. Those are separate facts, and job boards do not distinguish between them.

Here is what an old date usually means, roughly in order of how often it happens:

  • The role was filled and nobody took the posting down. Common at companies where the recruiter left, the ATS auto-syndicates to five boards, or the posting lives on a careers page that nobody owns.
  • The role is frozen but not cancelled. Budget got paused in Q2. The req is still open in the system. Someone will unfreeze it, possibly in October, possibly never.
  • They are hiring continuously. Support, sales, trades, nursing, warehouse, driving, customer-facing retail. The posting is a permanent front door. There is no cohort and no close date.
  • The hiring manager has rejected everyone so far. Sometimes because the bar is genuinely high. Sometimes because the spec is impossible — three specific technologies, ten years, and a salary band that fits none of it.
  • It was never a real job. Compliance postings for roles already earmarked internally, agency listings built to collect résumés, and phantom postings that exist to make a company look like it is growing.

The last one gets the most airtime online and is the least common of the five. The first two are far more likely, and neither of them is about you.

The Signals Worth Ten Minutes

Before you write anything, spend ten minutes checking whether the role has a pulse. Most of this is public.

Check whether the posting has been edited. Many boards show a separate "updated" date, or the listing quietly reappears at the top of search results. A posting from June that was refreshed last week is an active posting with an old creation date. That is a very different animal.

Check the company's own careers page. If the role is on Indeed and LinkedIn but gone from the source, it is closed. If it is still on the source, someone is maintaining it.

Check for duplicates. The same title reposted in July and again in August usually means a real, unfilled need — and often a spec problem or a pay problem. That is worth knowing before you negotiate, not after.

Check whether the team is growing elsewhere. If the company posted four other roles on the same team in the last month, the June posting is probably part of a live plan. If June was the last thing they posted at all, treat the whole company as frozen.

Check the hiring manager. If the person who would own this role changed jobs in July, the req is in limbo regardless of what the posting says.

Apply, But Apply Differently

If the role fits and the signals are neutral or positive, apply. A stale posting has one advantage worth naming: the flood of applicants arrived in the first week, and it is long gone. You are landing on a quiet pile.

But change your approach in three ways.

Ask directly, in the first line

One sentence in your cover note or your message to the recruiter: "I noticed this role has been posted since June — is it still active, or has the scope changed?" This does not read as presumptuous. It reads as someone who pays attention. A recruiter with a dead req will often tell you so, and sometimes tell you what else is open.

Cap your effort

A fresh posting at a company you want might justify a tailored cover letter and a portfolio piece. A June posting justifies twenty minutes. Send the tailored résumé, skip the custom work sample, and hold the deep effort for the interview if it comes.

Find a human

Old postings are where cold outreach earns the most. The ATS pile is stale by definition; a note to the hiring manager or a person on the team is not. You are asking one question — is this real — and that question is easy to answer, which makes it easy to reply to.

When To Skip It

There are cases where the answer is genuinely no.

Skip it if the posting is over a year old with no edits. Skip it if the salary range in the posting predates a market that has moved, and the company has not touched it. Skip it if the spec is internally contradictory — junior title, senior requirements, no band — because a role that has been unfillable since June will still be unfillable in November. Skip it if applying costs you real time: a portal that wants your full history retyped, three essay questions, and a timed assessment before a human sees anything.

That last one matters more than the date. The real question is never "is this posting old" — it is "what does this application cost me, and what is the chance it goes anywhere." A ten-minute application against a 20 percent chance is a good trade. A ninety-minute application against the same odds is not.

A June posting in September is a lower-probability lead with lower competition. Treat it like one. Send it, note it, and keep moving.