9 min read
"Open until filled" reads like a month to a job seeker. To a recruiter, it often means "we already have three names we're excited about, and this posting is here in case we need more."
You bookmark a role on Tuesday, plan to apply Saturday, and find "no longer accepting applications" on Friday. That sting isn't always about your timing being sloppy. It's about a hiring timeline that started before the post went live.
Check your resume for free on the file you'd upload tonight, not the version you'll polish next weekend. When windows shrink, a parser-ready PDF beats a perfect draft that ships late.
Below is the sequence most corporate reqs follow, what closes the public posting, and how to move inside the first 48 hours without panic-applying to everything on the board.
Quick Wins
- Apply within 24 hours on roles you'd actually take, with a parser-clean PDF.
- Save a "fast apply" resume version you can upload without redesigning layout.
- Turn on job alerts for title + company, not just one posting URL.
- When a referral exists, submit the same day they offer to refer you.
What fills the req before the posting looks "new"
Internal transfers and promotions. Many reqs open because a team already has someone in mind from another department. HR still posts externally for compliance or pipeline depth, but the manager may be comparing two internal profiles on day one.
Referral batches. When a posting hits LinkedIn or the careers site, employees forward it to friends that afternoon. Referred candidates often land in a separate Greenhouse or Workday view. That queue gets reviewed before the general applicant pile.
Silver medalists from prior searches. Recruiters reopen reqs with candidates who almost got an offer last quarter. Those names resurface before a single new application is read.
Pipeline screens already scheduled. "Posting live" and "still interviewing" overlap. The public page can stay up while the coordinator is already booking second rounds with early applicants.
This is why job postings close faster than expected for external candidates. The listing is one intake channel, not the start of the search.
And it is why silence after a late apply rarely means your resume was garbage. It often means the req moved while you were still choosing fonts.
The posting timeline from bench to closed
Timelines vary by company, but this sequence shows up often enough that you can plan around it.
Phase 0: Before the public post
The manager gets headcount approval. Recruiting pulls internal candidates and prior finalists. Referral conversations start in Slack or email. None of this shows on the careers page yet.
Your move: If you know someone on the team, ask whether the role is opening before the post. A warm heads-up beats a cold apply on day six.
Phase 1: First 24 to 48 hours live
Job alerts fire. Referrals submit. People who already follow the company apply from saved resume files. Recruiters skim the first stack for obvious fits and schedule phone screens.
Before: "I'll rewrite my summary when I have a quiet evening."
After: Upload a clean single-column PDF within 24 hours. Change the top bullet under your current role to mirror the posting title words.
Phase 2: Short list forms
The hiring manager has three to five names. Feedback loops start. External applicants who arrive now compete against candidates already in process, not against an empty req.
Before: Mass apply to twelve similar titles with the same generic file.
After: Pick two high-fit roles, tailor keywords, and submit both before Phase 2 ends.
Phase 3: Posting closes, pipeline continues
The careers site flips to closed or "no longer accepting applications." Interviews keep going. The close date reflects intake policy, not "we hired someone already" in every case, but new external applies often stop entirely.
I've watched reqs in Greenhouse move to filled after a Monday referral batch and two Tuesday screens, while the public posting still showed open until Wednesday cleanup.
Copy-paste block: 48-hour apply checklist
Copy-paste checklist (per priority role)
[ ] Posting saved + alert set for same title at this company
[ ] Resume export: single-column PDF, parser-clean contact block
[ ] Top bullet under current job matches posting title language
[ ] Apply within 24 hours (referral same day if applicable)
[ ] Optional cover letter only if required or referral path
[ ] Log: company, role, file version, date applied
Pair speed with fit. Applying fast to a role you're underqualified for still wastes a slot. Speed matters most when you'd accept an offer if it came tomorrow.
For how recruiters sort the first wave, read what recruiters see after you click apply .
Waiting habits that cost you open reqs
Waiting for the "perfect" tailored version. A good-enough file on day one beats a flawless file on day eight. Tailor the first bullet and skills line first. Polish the rest after you apply if you must.
Assuming "two weeks" means two weeks. Postings often say open until filled with no fixed end date. Treat the first 48 hours as the real window unless you have a referral or internal path.
Before: Refresh the careers page daily hoping it reopens.
After: Set a company alert and a recruiter bookmark. When a sibling role posts, you're first in line.
Ignoring referral timing. A referral submitted Thursday while the manager already has a short list from Monday referrals is late. Ask your contact to refer you the same day they agree.
Uploading a layout-heavy resume. Slow parsing does not close postings, but it can bury you below faster-read files in the first sort. Use a boring export for speed applies.
This will not fix applying to roles where you lack core requirements. It stops you from losing winnable reqs because you treated a live posting like a slow homework assignment.
For volume strategy without spray-and-pray, see quality applications vs mass applying .
Ship a clean file before the window shuts
When you only have one evening, spend it on upload readiness, not cover letter prose for an optional field.
Run the free ATS checker on the PDF you'll attach. Fix heading order and date lines before you chase posting keywords. A fast apply that parses wrong is still a slow reject.
When the form marks cover letter required, or you're on a referral path, generate a cover letter with the role title and referrer name in the opening. Keep it under one page. Recruiters read referred files quickly when the connection is obvious.
Do this now: Pick one live posting you'd take. Export a parser-clean PDF, run the checker, and apply before you close the laptop. Log the file name so you know what you sent.
Your 48-hour move list
Job postings close faster than expected because reqs often fill from the inside and the first applicant wave, not from a slow public countdown. The careers page is paperwork. The short list is the race.
- Apply within 24 hours on roles you'd accept.
- Keep a fast-upload resume version ready.
- Move referrals the same day, not the same week.
- Set alerts so the next sibling posting does not catch you flat-footed.
Job searching is hard enough without blaming yourself for a closed req that was never waiting on you. Control what you can: file quality, timing, and fit on the roles that matter.
When a posting vanishes, check whether a parallel title opened at the same company. Teams often post adjacent reqs while the first pipeline runs hot.
Read more
Frequently asked questions
Most reqs start with an internal short list, referral batch, or pipeline candidate from a prior search. The public posting is often a backup channel. Once a hiring manager picks from the first wave, the coordinator closes the posting even though your calendar still says the role looked fresh.
You can email the recruiter with a short note and a clean resume if you are a strong match, but do not expect the ATS to accept a closed req. Better move: set alerts for similar titles at that company and apply within the first day when the next role posts.
Yes for roles with referral traffic and internal transfers. Recruiters often build a screen slate from the first applicant pool. A polished file on day four can still get read, but you are competing against candidates already in phone screens.
Often. Internal transfers and boomerang employees skip the public queue. The posting may have been live for compliance while the real decision was already leaning internal. That is frustrating, but it explains why silence is not always about your resume.