Should You Apply to a Job Posted 30 Days Ago? (How to Tell If It's Still Alive)

Short answer: apply, but spend four minutes verifying the job is still open first.

The reason the advice you've been given feels useless is that it answers the wrong question. "Is 30 days too old?" has no general answer, because a posting's age barely correlates with your odds. Median time to fill a US role runs around 44 days, which means a 30-day-old posting is usually somewhere in the middle of its own hiring process, not past the end of it. And in a survey of more than 1,000 hiring managers by Clarify Capital, 68% said they had roles sitting posted for over 30 days.

The question worth asking is "is this requisition still open, and is it open to someone like me?" That one is answerable in four minutes, and the answer is often no for reasons that have nothing to do with the date.

What the date on the posting actually means

Almost nothing, for one specific reason: the date you see is the date of the current listing, not the date the job first appeared.

• A repost resets the clock. When an employer or its applicant tracking system re-lists the same requisition, the counter goes back to zero. LinkedIn sometimes shows a "Reposted" label if you hover over the posting age, but it never tells you the original date or the number of repeats. Indeed reposts get a fresh date with no label connecting them to the original.
• Free and basic postings expire on their own. Many platforms pause a job automatically once it hits an applicant cap or a time limit, regardless of whether anyone was hired. A recruiter who re-lists a paused job did not necessarily fail to fill it. They just ran out of posting window.
• Aggregators lag the source. A job board that scraped the posting from the company's career site will often keep showing it for days or weeks after the company removed it.

So the posted date is a floor on the real age, never a ceiling. "Posted 2 days ago" can mean four months. That cuts both ways, and it's the reason "apply in the first 48 hours" is weaker advice than it sounds.

The four-minute liveness check

Do this before writing a single custom sentence. It takes less time than reading the job description twice.

Step 1 is the one almost nobody does, and it resolves the majority of cases. If the role is gone from the company's own board, it's closed, and the copy you're looking at on a job board is a ghost of a real job rather than a scam. If it's still there and the form submits, the req is open and the date is noise. More on which site to use once you've confirmed it's live: apply on the company website or LinkedIn/Indeed.

Why real jobs stay posted for 30+ days

This is where most advice goes wrong. It treats a long-lived posting as proof of a ghost job. Sometimes it is, but there are at least six boring explanations that each have different implications for you.

That last row is the one no ranking article mentions, and it explains a meaningful slice of long-lived technical postings. Under the PERM labor certification rules at 20 CFR 656.17, an employer sponsoring an employee for a green card must place a job order with the state workforce agency for 30 days and complete its recruitment steps 30 to 180 days before filing. The posting has to exist and has to be visible to the public. It just isn't a vacancy in the sense you mean. Tells: an oddly specific requirements list that reads like one person's resume, a wage figure stated with unusual precision, and a mail-in or email-only application route alongside the normal one.

If the posting also fails the basics — no company name, a Gmail contact address, a request for bank details — you've got a different problem entirely. Run it through the fake job posting checklist.

Does applying early actually help?

A little. Less than you've been told.

Applying in the first few days means you land while the review queue is short, which genuinely matters at employers who screen in daily or weekly batches. But three things blunt the advantage:

1. The queue isn't reviewed in order. Recruiters sort and filter. Screening-question answers, location, and work authorization reorder the list before anyone reads a resume.
2. The scorecard often isn't written yet. Postings go up before the hiring manager has settled what they want. Week-one applicants get measured against a moving target; week-four applicants get measured against a decided one.
3. A knockout rule doesn't care what day it is. If one of your screening answers falls outside the allowed range, the timestamp is irrelevant — see rejected within minutes of applying.

Speed is worth having, which is why cutting the time per application matters more than racing the calendar. But it ranks below meeting the posting's stated hard requirements and below the application actually being readable. A strong application in week four beats a rushed one on day one, every time. Ten good applications beat a hundred bad ones still holds.

The decision table

Age plus one signal, not age alone:

The cost asymmetry is what should drive this. A verified-live application costs you 10 to 20 minutes. Being wrong about an old posting costs you one of those slots. Being wrong about a fresh posting that was actually a four-month-old repost costs you exactly the same. There's no version of this where screening by date saves you real time, and screening by date throws away roughly half the market.

If you've already applied and heard nothing

A 30-day-old posting plus three weeks of silence doesn't mean you were rejected. It frequently means the req is parked. Three things worth doing:

• Check the portal status, not your inbox. "Under review" and "no longer under consideration" are different states, and the email often never comes. Why you're not hearing back covers the full set of reasons.
• Follow up once, at the two-week mark. One short message to the recruiter, and no reference to how long the job has been posted. Scripts: how to follow up on a job application.
• Watch for the repost. If the job re-appears with a fresh date and you never got a decision, that's a legitimate moment to apply again or to message the recruiter. A repost after your application usually means the pipeline didn't convert, not that you were ruled out.

And if the posting then disappears for good while you're still "under review," you've learned something useful about that company's req hygiene rather than about yourself. Position filled but still posted explains the reverse case, where the job is dead and the listing isn't.

The real bottleneck

Here's the thing worth noticing about this whole question: people ask "is this posting too old?" because applications are expensive. When each one takes 25 minutes of retyping your work history into a form that already has your resume, you start rationing — and rationing by date is the easiest filter to apply, even though it's close to random.

Make applications cheap and the question dissolves. You stop needing a rule for which postings deserve an application and start applying to every live req you're a genuine fit for.

That's what JobRizzer is for. It's a Chrome extension that autofills the repetitive fields across Workday, Greenhouse, Lever, Ashby, iCIMS and LinkedIn Easy Apply from your resume, so the boring part of the form is done and your attention goes to the screening questions and the liveness check above. You review everything and submit yourself — nothing is auto-applied.

The bottom line

Thirty days is not too old. Apply.

Spend four minutes confirming the requisition still exists on the company's own careers board, because that single check separates the live jobs from the stale listings far better than any date does. Then treat the age as a budget signal rather than a yes/no: fresh posting, normal effort; 45-plus days with a repost, keep it quick; explicitly closed, skip and watch for the re-list.

If old postings are a big share of what you're seeing, that's worth reading as a market signal rather than a personal one — are ghost jobs real covers why so many listings outlive their vacancies, and how long it takes to find a job sets a realistic clock for the search overall.