Search Job Listings

Search Job Listings queries live job openings across the whole market and creates a row per opening.

A job post is the most legible buying signal a company publishes: it names the team that is growing, the tools they expect you to know, and the problem they are hiring to solve.

What it does

• Searches openings across all companies, not one company at a time
• title (or keywords) is the only required input — everything else narrows the result set
• Titles and locations are lists, so one run can cover several roles across several cities
• Filters reach past the job itself: job function, industry, company size, organization type, founded year, whether the poster is a recruiting agency
• A tight published_at window is what puts you in front of the hiring manager before the role fills

To check openings at companies you already have rows for, use the Company Job Listings enrichment instead — that fills a column, this creates rows.

How to use it

1. Open the table and click Table → Import → Search Job Listings
2. Enter the titles and locations you want
3. Narrow on company size, industry and posting date
4. Exclude recruiting agencies unless you sell to them
5. Run it, map the output fields to columns, and click Create Rows

Common use cases

• Sell to a team that is being built. “Hiring 3 SDRs” means budget approved and process gaps, both at once.
• Target by tech stack. A job description lists the tools a company runs, which no firmographic database keeps current.
• Catch reqs in the first 24 hours. Narrow the posting window and you are early rather than fourteenth.
• Filter agencies out. Excluding recruiting agencies is the difference between a list of employers and a list of intermediaries.
• Score hiring velocity. Several openings on the same team is a stronger signal than one.

Best practices

• Run one narrow search per role family rather than one broad search that returns everything
• Keep the posting-date window tight — a 90-day-old req is usually filled
• Exclude recruiting agencies unless they are your buyer
• Dedupe on company domain; a company hiring five roles returns five rows
• Enrich the hiring manager, not the job — the posting is the signal, the person is the contact
• Keep the job URL and title columns; they are the personalization line in the first email

Where to next

• Find People Within Company — turn a hiring company into contacts
• Is Hiring — the same signal as a column on existing rows
• search_linkedin_job_openings — run the same search from an AI client over MCP
• Hiring signals course — the full play, end to end