What is LinkedIn Job Scraper?
LinkedIn Job Scraper runs a LinkedIn job search for you and returns the listings it finds, one record per job. You give it a job title such as “data engineer” and a place such as Berlin, add filters if you need them, and get back a table with the employer, the full description and the way to apply.
Each listing also carries a profile of the hiring company: industry, headcount, headquarters and website. One search is often enough for a job shortlist, a hiring-signal list or a pay check for a role.
You ask
Find data engineer jobs in Berlin on LinkedIn and show company, workplace type, applicants and posting date.
It runs
From your AI assistant over MCP or from your code over REST
You get
- The job
- Location and workplace
- Applying
- Pay
- Hiring company
- Shortlist roles fasterSearch one title across several cities and read the descriptions without opening each listing.
- Spot hiring signals for salesA company posting five data roles is building a data team, and the employer profile comes with every job.
- Track a job marketCount listings by title, seniority and workplace type every week and watch the mix change.
- Feed a job board or newsletterPull fresh listings by title and location from your backend on a schedule.
- Compare posted payCollect the salary ranges employers publish, with currency and pay period.
What data does the LinkedIn job scraper extract?
Every listing comes back as one record with the job, the way to apply and a profile of the employer. These are the fields our test search returned.
The job
- Job title and LinkedIn job ID
- Full description, as text and HTML
- Employment type
- Experience level
- Job function and industry
- Posting date and expiry date
- Listing state and close date
Location and workplace
- Location as LinkedIn shows it
- Country and country code
- Remote, hybrid or on-site
- Remote work allowed flag
Applying
- Job page URL
- Easy Apply link when offered
- Employer's own apply URL
- Applicant tracking system name
- Applicant count label
Pay
- Salary range and currency
- Pay period
- Whether the employer provided the salary
- Benefits when listed
Hiring company
- Company name, ID and LinkedIn page
- Industry and specialties
- Employee count and size band
- Headquarters and office addresses
- Website, followers and description
Fields the employer leaves blank come back empty, and in our test only 1 of 10 listings carried a salary. A few listings also name a recruiter from the hiring team; we leave those names out of the sample. To read one job you already have a link for, use LinkedIn Job Details.
Sample output: data engineer jobs in Berlin
The table at the top of this page is a real search for “data engineer” in Berlin, Germany, sorted by relevance, run on 16 November 2026. LinkedIn reported 350 matching listings and we asked for the first 10. The record below is listing 9 in full, the only one that published pay.
One result in full
One listing in full: #9, the only one with a salary
- Title
- Senior Data Engineer - Terminal.exe
- Company
- All Your BI
- Location
- European Union
- Workplace
- Remote
- Employment
- Full-time
- Level
- Mid-Senior level
- Salary
- 85,000 - 99,000 EUR a year, provided by the employer
- Posted
- 30 Oct 2026
- Expires
- 6 Feb 2027
- Applicants
- Over 200
- How to apply
- On the employer's site
- Industry
- Data Infrastructure and Analytics
- Company size
- 11-50 employees, 104 on LinkedIn
- Company headquarters
- Rotterdam
What this sample tells you
6of 10
6 of 10 titles contain “data engineer”. The rest are platform, analytics and forward deployed engineering roles that LinkedIn ranks as close matches, so filter titles before you count demand.
1of 10
1 of 10 lists a salary: 85,000 to 99,000 EUR a year. 9 of 10 send applicants to the employer's own site, and 4 name the applicant tracking system behind it.
4of 10
Applicant counts are LinkedIn's labels. 4 of 10 say over 200 and come back as 200, one says among the first 25. Read them as bands, not exact counts.
7of 10
7 of 10 are in Berlin itself. The other 3 are tagged Germany, EMEA or European Union: remote roles open to a wider region that still match a Berlin search.
How to scrape LinkedIn jobs with your AI assistant
Connect AI/ML API
Click Try it now, pick your client and add the MCP server. You sign in with your AI/ML API account, and no LinkedIn login is needed.
Describe the search
Name the job title, the city or country and any filters: remote only, posted this week, senior level, specific companies.
Get the listings
Your assistant runs the search and shows each job with its employer, workplace type, applicants and posting date.
Narrow it down
Ask it to drop off-title roles, sort by date, pull the requirements out of the descriptions or save a CSV.
Searches to try
Use the AI/ML API MCP LinkedIn Job Scraper tool. Find data engineer jobs in Berlin on LinkedIn and show title, company, workplace type, applicants and posting date in a table.
Use the AI/ML API MCP LinkedIn Job Scraper tool. Search LinkedIn for remote product designer jobs in the United Kingdom posted in the last 24 hours, mid-senior level only.
Use the AI/ML API MCP LinkedIn Job Scraper tool. List LinkedIn jobs for “backend engineer” at Stripe, Revolut and Wise and compare them by location and seniority.
Use the AI/ML API MCP LinkedIn Job Scraper tool. Find machine learning engineer jobs in Amsterdam, keep the ones with a posted salary and sort them by the top of the range.
Search filters that shape your results
Describe the search in words and your assistant sets these filters. In code you pass them yourself, and every filter applies to every job title in the request.
| Filter | What it controls | Tip |
|---|---|---|
| Job titles | Search queries, each run as its own search. LinkedIn's boolean operators work | Run “data engineer” and “analytics engineer” separately to keep counts clean |
| Locations | Cities, regions or countries as LinkedIn names them, or LinkedIn geo IDs | Write “United Kingdom”, not “UK”, which LinkedIn can read as Ukraine |
| Companies | Up to 10 company names or company page URLs | Use the company page URL when several companies share a name |
| Posted within | Last hour, 24 hours, week or month | Use 24 hours for a daily alert |
| Workplace type | Remote, hybrid or office | Remote roles may carry a region such as EMEA instead of a city |
| Employment type and level | Full-time, part-time, contract, internship or temporary; internship to executive | Pair with the title to split junior from senior roles |
| Salary | Minimum pay bands from 40k+ to 200k+ | Few listings publish pay: 1 of 10 in our test |
| Easy Apply and under 10 applicants | Keep one-click applications or listings with few applicants so far | Useful when you want to apply early |
| Job function and industry | LinkedIn function codes such as engineering, and industry IDs | Narrows broad titles such as “manager” |
| Sort, start page and jobs per search | Relevance or date; pages of 25 up to page 40; how many jobs per title and location | LinkedIn returns at most 1,000 jobs for one search |
LinkedIn also widens a city search with remote roles open to the region. Our Berlin search returned listings tagged Germany, EMEA and European Union, which is why the location column matters when you count jobs per city.
What people build with LinkedIn job data
Job search shortlist
Search your title in three cities, drop listings with over 200 applicants and read the rest side by side.
TitleApplicantsLocation
Hiring signals for sales
Find companies posting data roles, then pitch the tools those teams will need, with company size and website from the same record.
CompanySize bandWebsite
Talent market reports
Count listings per title, seniority and workplace type each week to show how demand shifts in a city.
Experience levelWorkplacePosting date
Salary benchmarking
Collect posted ranges for one role across countries and note how many listings publish pay at all.
SalaryCurrencyPay period
Job board and newsletter feeds
Pull new listings every morning by title and location and publish them with the apply link.
Job URLApply URLPosting date
Recruiting benchmarks
See which applicant tracking systems competing employers use, how many applicants their listings draw and when they expire.
ATSApplicantsExpiry date
LinkedIn job scraper API for your code
In your code
REST · your AI/ML API key, JSON records back
The same search runs over REST with your AI/ML API key. Your backend sends titles, locations and filters and gets JSON listings with the fields above, ready for a job board, a lead list or a hiring dashboard.
Deduplicate by the LinkedIn job ID when you merge searches, because one job can match two titles. Use MCP for one-off searches in a chat and REST for scheduled pulls. Start with the Toolbox REST quickstart.
Other ways to collect LinkedIn job listings
Which method fits depends on whether you are looking for one job or tracking a market.
| LinkedIn job alerts by email | LinkedIn's official job APIs | Your own scraper | ||
|---|---|---|---|---|
| Setup | Connect once with your AI/ML API account | A LinkedIn account and a saved search | Partner approval; built for posting jobs, not reading them | Headless browser, proxies, pagination and parser fixes |
| Inside an AI chat | Yes. Over MCP | No. No | Only if you build it | Only if you build it |
| Best for | Repeat searches with filters from chat or code | Personal job hunting | Applicant tracking systems that post jobs | Teams with engineers to keep it running |
Pricing
Pay as you goBilled per run from your AI/ML API balance
- No subscription
- No seat fee
- One balance for every tool
LinkedIn Job Scraper is billed from your AI/ML API balance by the number of listings a search returns, with no subscription or seat fee. Our 10-listing test search cost under two cents. Set the number of jobs per search to keep the cost predictable, and check the current price in your dashboard before large pulls.
FAQ
Is it legal to scrape LinkedIn job listings?
Job listings are posted to be seen, and collecting them for a job search, research or a job board is common. LinkedIn's User Agreement still prohibits scraping and LinkedIn enforces it, so decide how its terms apply to your use. Recruiter names that appear on some listings are personal data under laws such as GDPR. This is not legal advice; ask a lawyer about your case.
Do I need a LinkedIn account or cookies?
No. Our test search ran with a title and a location only. The tool has optional fields for cookies and a proxy, and you can leave them empty. Don't paste your own LinkedIn session cookie into any scraper, since it lets the tool act as your account.
How many jobs can I get from one search?
LinkedIn returns at most 1,000 jobs for one search, in pages of 25. Set how many you want per title and location, and for wider coverage split the search by city or by posting date.
Does it include the full job description?
Yes. Every listing carries the description as plain text and as HTML. Our 10 descriptions ran from about 2,900 to 5,900 characters, enough for your assistant to pull out skills and requirements.
Can I get salaries?
When the employer posts one. Only 1 of our 10 listings carried a salary, with currency and pay period. Ask your assistant to keep only listings with pay, or use the salary filter.
Can I search jobs at specific companies?
Yes. Add up to 10 company names or company page URLs to the company filter. For a company's own profile, offices and posts, use LinkedIn Company Scraper.
How is this different from LinkedIn job alerts or the official API?
Alerts email you new jobs for one saved search, and LinkedIn's job APIs serve approved partners who post jobs. LinkedIn Job Scraper returns the listings as data you can filter, merge and store, from chat or code.
Can I use it from Claude, ChatGPT or Cursor?
Yes. Add the AI/ML API MCP server once and describe the search in a sentence, with the title, the place and the filters you care about.
How fresh are the listings?
Each run searches LinkedIn at that moment. Our test listings were posted between 28 October and 14 November 2026, and every record carries its posting date and expiry date.
Run your first LinkedIn job search
Connect once, then describe the role and the place in plain English.