LinkedIn Is Retiring the Date Filter. Ask for "Under 10 Applicants" Instead

If your job search ran on "Past 24 hours," a seniority checkbox, and a bookmarked URL with f_TPR=r3600 in it, LinkedIn is pulling the rug. Members are now seeing a notice that classic filter-based job search is being gradually retired in favor of natural-language AI search, and r/jobs and r/recruiting are full of complaints that alerts have gone useless. You can still apply first. The method is different now, and the people who switch early get the advantage the date toggle used to give them.

What did LinkedIn actually retire?

LinkedIn is phasing out the filter-based job search (location dropdowns, seniority checkboxes, the date-posted toggle) and replacing it with an AI search box where you describe the job in plain language. The retirement started in September 2026 and is rolling out gradually, so not every account looks the same today.

Liviu Tudor, founder of Calendrz, wrote it up on October 15, 2026, and his argument is that AI-driven callers never read forms in the first place; they "describe what [they want]." LinkedIn's own framing matches. Erran Berger, a LinkedIn VP, said at launch that the new search "lets members describe their goals in their own words."

This didn't come out of nowhere. Filters have been disappearing for years:

• Seniority and function filters were moved behind premium tiers years ago.
• The direct salary filter was quietly removed from job search in late 2024.
• Date posted, location, and seniority dropdowns are the current round, starting September 2026.

So losing the date posted filter is the latest step in a trend that's been running for a while. Treat any workflow that depends on a specific LinkedIn control as temporary.

Why "hour one" was never the real goal

Applying in the first hour mattered because a fresh posting has few applicants, and a short pile gets read by a person. The timestamp was a stand-in. What you actually wanted was a low applicant count.

LinkedIn's new search lets you ask for that directly. Its flagship example query is:

"finance manager roles in my network with less than 10 applicants"

Look at what that prompt does. It filters on applicant count, which the old date toggle could only guess at. A role posted minutes ago at a famous company can already have more applicants than an older role at a company nobody has heard of. When you write "fewer than 10 applicants" into the prompt, you're targeting the condition that made hour one worth it, not the clock.

How to write LinkedIn AI job search prompts that surface fresh roles

A good AI job search prompt puts every constraint the old filters handled into full sentences: recency, applicant count, location, work arrangement, seniority, and what you want left out. A single keyword per constraint isn't enough. Spell each one out.

LinkedIn's engineering write-up uses this example:

"Find software engineer jobs in Silicon Valley or Seattle that are mostly remote but not from sourcing companies, posted recently, with above median pay"

That one sentence covers recency ("posted recently"), location (two metros), arrangement ("mostly remote"), an exclusion ("not from sourcing companies"), and a pay signal. Copy that structure.

The six-part prompt template

1. Role, in two wordings. "Product analyst or product data analyst roles."
2. Level, described rather than labeled. "Senior individual contributor, not people management."
3. Location as a sentence. "Fully remote, US-based, no relocation" or "in Seattle, hybrid allowed."
4. Recency. "Posted in the last day" or "posted recently."
5. Competition. "With fewer than 10 applicants."
6. Exclusions. "Not from staffing or sourcing agencies, not contract."

Put together: "Senior product analyst or product data analyst roles, individual contributor not manager, fully remote within the US, posted in the last day, fewer than 10 applicants, not from staffing agencies."

Old filters, translated

Test each phrasing and read the first page of results. If recency phrasing doesn't sort the way you expect, lean harder on the applicant-count clause, which is the one LinkedIn chose to showcase.

Why your searches and alerts feel noisy now

Searches feel noisy because hard filters have turned into soft signals. In the new system, "remote" or "senior" counts as one relevance cue among many. It no longer works as a yes/no cut that removes non-matching jobs.

LinkedIn describes the system as a multi-stage LLM architecture: GPU-optimized embedding-based retrieval pulls candidates, and cross-encoder ranking models order them. Embedding retrieval turns your query and every posting into vectors and returns the postings closest in meaning. Closeness in meaning isn't a strict rule. A non-remote job whose text closely matches your role can rank above a remote job that matches less closely.

That explains the most common failure. When the filters disappeared, people typed "Remote" into the search bar, and according to sackhacks.com it "proceeded to bring back every job in the country, remote or not." One word is a weak signal, and the ranker outweighs it with everything else. (This mechanism is inferred from LinkedIn's published architecture, not stated by LinkedIn.)

The fix is redundancy. "Fully remote, US-based, no relocation, no hybrid days" repeats the constraint from several angles, and each phrase pulls the ranking the same way.

Fixing LinkedIn job alerts that stopped working

If your LinkedIn job alerts stopped working, the likely cause is that they were built on filter settings the new system now treats loosely. Rebuild them:

• Delete the old filter-built alerts. Don't try to patch them.
• Run your full six-part prompt as a fresh search, then save that search as the alert.
• Make one alert per constraint set. "Remote US senior analyst" and "Seattle hybrid senior analyst" should be two alerts, not one muddled one.
• Audit after a few days. If more than a handful of results break a hard constraint, add more exclusion language and save it again.
• Keep one narrow alert. Include the applicant-count clause so it only fires on low-competition roles.

The f_TPR trick may still work, for now

Your old f_TPR URLs may still load, so bookmark your one-hour and two-hour searches today and expect them to break eventually. f_TPR is LinkedIn's time-posted-range parameter, measured in seconds.

Here's how it works:

• f_TPR=r86400 is the last 24 hours (86,400 seconds).
• f_TPR=r3600 is the last hour.
• f_TPR=r7200 is the last two hours.

Run any classic search, change the number in the URL, and bookmark it. As sausagedog.io notes, the bookmark "stays a one-hour filter every time you open it."

Two caveats. First, sackhacks.com reports that you "can almost always get back to a classic, filter-driven search experience," but LinkedIn offers no universal off switch, so the route depends on your account and device. Second, nobody has confirmed whether f_TPR URLs still work on accounts that have been fully migrated. Check your own bookmarks this week. If they load the classic view, keep using them alongside AI prompts. If they redirect, you'll find out now and not in the middle of a search.

Word your profile for a semantic matcher

The AI matcher compares your whole profile against each posting, so your headline and skills need the words employers in your market actually use, and both wordings if your field has two. LinkedIn's Job Match feature evaluates your headline, skills, experience, and endorsements against job descriptions to calculate a match score.

Getting the wording wrong is a bigger risk than most people think. Refolk's index of professional profiles shows how big with one profession: recruiting.

Source: Refolk's index, October 2026 snapshot. Combined figure assumes little overlap.

Search the American way and the UK recruiting market looks 14 times smaller than the US one. Add British wording and it's about 3.2 times smaller. In the UK, the local titles alone outnumber the American-style ones by 3.4x. Agencies like Robert Walters, Morson Edge, and K2 Partnering Solutions show up among the UK employers in a sample of those profiles.

In theory, a semantic matcher should treat synonyms as close. In practice you don't control how close it decides they are. The safe move is to put both wordings in the fields Job Match scores:

• Headline: "Technical Recruiter / Recruitment Consultant | Engineering hiring, UK and US"
• Skills: list the synonym pairs your field uses ("Talent Acquisition," "Recruitment," "Sourcing").
• Experience: use the posting's wording in at least one bullet per role.

Every field has its own version of this: "product designer" vs. "UX designer," "data analyst" vs. "business intelligence analyst," "growth marketer" vs. "performance marketing manager." Pick the pairs that match your target postings.

Your resume hits the same mismatch once you apply, because the employer's screener reads it against that posting's words. Rewriting it by hand for every posting is what kills hour one. That's the work Refolk takes off you: paste the posting, and I rewrite your resume from your own history using that posting's language, without making up experience you don't have.

A one-hour application workflow that survives the change

To apply early now, run saved AI prompts that ask for recency and low applicant counts, check fit fast, and send a tailored application while the pile is still short. Here's the routine:

1. Morning check. Open your bookmarked r3600 or r7200 URLs if they still load. Then run your saved six-part prompts.
2. Shortlist by applicant count. Anything under 10 applicants goes to the top.
3. Check fit before you write. Richard Eib of Jersey Hired warns that AI inserts "another layer of interpretation" between candidates and jobs, so don't assume a result is a match just because it ranked. Read the requirements against your actual history.
4. Tailor and send. Resume rewritten to the posting's wording, plus a short cover letter that names the specific problem the role exists to solve.
5. Log what worked. Note which prompt surfaced each role you applied to. Retire prompts that keep returning noise.

Steps 3 and 4 are where hour one used to get lost, rewriting bullets for a role you only half fit. Refolk scores how well you actually fit each posting before you put time in, then drafts the tailored resume and cover letter, so an under-10-applicant window doesn't close while you're still editing.

FAQ

Is LinkedIn classic job search retired for everyone?

Not yet. LinkedIn says it began gradually retiring classic job search in September 2026, and the AI-powered search is available worldwide. The rollout is uneven, so some accounts can still reach the filter view through workarounds like the ones on sackhacks.com. Plan as if yours will lose it soon.

How do I find the newest jobs on LinkedIn without the date posted filter?

Write recency into your prompt ("posted in the last day" or "posted recently"), add "fewer than 10 applicants," and save the search as an alert. If your bookmarked f_TPR=r3600 URLs still load, keep using them too, but don't count on them lasting.

Why are my LinkedIn job alerts not working anymore?

They were probably built on hard filters that the new search treats as soft relevance signals, so constraints like "remote" no longer strictly exclude jobs. Delete the old alerts, rebuild them from full-sentence prompts that state each constraint more than one way, and check the results after a few days.

Should I change my LinkedIn headline for AI search?

Yes, if your field has more than one common title. Job Match scores your headline, skills, experience, and endorsements against postings. In Refolk's index, UK recruiting looks 14x smaller than the US market when searched with American titles alone, so put both regional or industry wordings in your headline and skills.