LinkedIn Job Finder

Search LinkedIn jobs the way you would by hand — then get every result as a spreadsheet instead of 40 browser tabs.

Type what you're looking for and where. Narrow by date, remote/hybrid/on-site, contract type, experience level. Get back a clean table: company, location, salary, applicant count, full description and a direct link to every posting.

Who this is for

• Job seekers — pull today's postings across five cities into one sheet, filter out the agency reposts and the roles needing clearance you don't have, and apply to the ones with under 25 applicants.
• Recruiters and sourcers — track who's hiring for what, in which markets, and how fast roles are moving.
• Analysts and founders — measure hiring demand for a skill, a title or a competitor over time.

What you get

One row per job:

Column	Example
Job title	Software Engineer, Backend
Company	Tessera Labs
Location	San Jose, CA
Remote / hybrid	remote
Posted	2026-08-16 · "2 days ago"
Salary	$200,000 - $250,000 per year, plus the sentence it was read from
Applicants	Over 200 applicants
Type & seniority	Full-time · Mid-Senior level
Industry & function	Software Development · Engineering
Description	Full text, formatting intact
Link	Direct URL to the posting

Download it as CSV or Excel, pull it through the API, or send it straight to Google Sheets, Airtable, Make or Zapier.

Salary, even though LinkedIn has no salary field. When an employer publishes pay it's written into the job description — this reads it out into one plain column ($107,900 - $195,050 per year), with the exact sentence it came from in the next column so you can check anything that looks off. Two flat columns, nothing nested. If no pay range can be read confidently, both are left empty rather than guessed at. A wrong salary is worse than a blank one.

Filters that LinkedIn doesn't give you

This is where most of the time savings are. All of them run before you're charged, so you never pay for a job you filtered out.

• Job title must / must not include — searching "engineer" on LinkedIn also returns sales engineers. This fixes that.
• Skip these companies — the usual use is cutting out staffing agencies that repost the same ten roles.
• Skip these locations — for when a country-wide search keeps surfacing one city you can't move to.
• Description must / must not mention — find roles that mention visa sponsorship, or drop every one that says security clearance.
• At most N applicants — the single most useful filter if you're applying. Jobs with 200+ applicants are usually already decided.
• Remote, hybrid or on-site — see the note below on how this one is worked out.
• Only jobs that show a salary.

Getting started

Fill in two fields:

{
  "keywords": ["product manager"],
  "locations": ["United States"]
}

A more realistic run:

{
  "keywords": ["product manager", "product designer"],
  "locations": ["United States", "Canada"],
  "datePosted": "past-week",
  "titleExcludes": ["intern", "senior director"],
  "companyExcludes": ["robert half"],
  "maxApplicants": 25,
  "maxJobsTotal": 500
}

Every job title is searched in every location, so that's four searches.

Already built the search on LinkedIn? Set your filters on linkedin.com/jobs, copy the address bar, and paste it in:

{ "searchUrls": ["https://www.linkedin.com/jobs/search?keywords=designer&location=Berlin&f_TPR=r604800"] }

Your filters come along with it — with one exception, which the run log names: LinkedIn stopped applying job type, experience level, remote/hybrid and sort order to logged-out search in August 2026, so those parts of a pasted URL are ignored on their side. Use the Full-time, contract…, Experience level and Remote, hybrid or on-site fields instead; this Actor checks those against each job itself.

Run it on a schedule

Set datePosted to Past 24 hours and schedule it daily. You get each morning's new postings before the applicant count climbs. Job IDs are stable, so it's easy to tell which are new since yesterday.

Good to know

LinkedIn caps any single search at about 1,000 results. That's LinkedIn's limit, not this Actor's — their own website does the same. If your search is broader than that, this tells you plainly instead of quietly handing you a partial list: check What was searched in the output, and the run summary says so too.

The fix is to split one wide search into several narrow ones. Instead of one search for the whole United States, list the five states you care about — you get up to 1,000 from each. Narrowing by date does the same thing.

Remote/hybrid/on-site is read from the posting, not from LinkedIn. LinkedIn ignores its own remote filter on logged-out search (re-measured 2026-08-26: remote, on-site and a deliberately invalid value all return the identical result set) and publishes no remote/hybrid label on the public job page. Other Actors still show that switch wired straight to LinkedIn's parameter; it does nothing.

So this reads what the employer actually wrote — "Software Engineer | Remote", "(Hybrid- NYC)", "this position is fully remote", "3 days a week in our Austin office" — and puts the answer in a workplaceType column on every row. It knows the difference between remote work and "remote sensing", "our remote-first culture" and "this is not a remote position".

Two things follow, and both are deliberate:

• A posting that never states its arrangement is left out, not guessed at. Most on-site jobs never say they are on-site, so filtering for on-site returns far fewer rows than exist; filtering for remote and hybrid works well, because employers advertising those almost always say so.
• The column is our reading of the text, which is why it is on the row: you can see what every job was classified as, instead of taking the filter's word for it.

"Sort by most recent" is still not offered, because LinkedIn ignores that too and a truncated relevance-ordered page cannot be re-sorted after the fact. Use datePosted or postedAfter — both still filter on LinkedIn's side.

A few other honest limits:

• Applicant counts are bands, not exact numbers — LinkedIn publishes "first 25 applicants" or "over 200", never "37".
• Salary only appears when the employer wrote one. Plenty of postings have none.
• No recruiter names or email addresses. This Actor reads public job postings; it doesn't collect personal contact details.
• Occasionally a job closes between being found and being opened. You still get the row, marked detailUnavailable, rather than silently losing a result.

Cost

You pay per job returned — not per search, not per page. Jobs filtered out don't count, and duplicates are removed across all your searches, so overlapping terms like "product manager" and "product management" never bill you twice for the same posting.

Start with maxJobsTotal set to something small to see the shape of the results, then raise it.