Search LinkedIn job listings and extract full job details. Supports filtering by work type (remote/on-site/hybrid), contract type (full-time/part-time/contract/internship), experience level, date posted, and company. Returns job title, company, location, work type, contract type, experience level, posted date, applicant count, job description, salary, and direct job URLs. Use when user mentions linkedin jobs, linkedin job search, scrape linkedin jobs, extract linkedin job listings, find jobs on linkedin, job openings, job postings linkedin, linkedin career search, job hunting linkedin, linkedin vacancy, jobs remote linkedin, work from home jobs linkedin, linkedin scraper jobs, linkedin job data, linkedin hiring, collect job leads linkedin.
keywords + location + filters → paginated job list with full details
browser-act via Skill tool to load usage. If installation or configuration issues arise, follow its guidance to resolve then retry.This Skill's operational boundary = what the user can manually do in their browser. It accesses LinkedIn through the user's logged-in browser, only reading data already available to the user. JS code is encapsulated in Python files under thescripts/directory, invoked viaeval "$(python scripts/xxx.py {params})".$(...)is bash syntax; it is recommended to use the bash tool for execution.
eval "$(python scripts/search-jobs.py '{keywords}' '{location}' --count {count} --start {start} --work-type {work_type} --job-type {job_type} --experience {experience} --time-posted {time_posted} --company-ids {company_ids})"keywords: job title or search keywords (e.g., software engineer, data analyst)location: location name (e.g., United States, New York, San Francisco Bay Area)--count: results per API call, default 25, max 100--start: pagination offset, default 0. Increment by count for each page--work-type: work arrangement filter — 1=On-site, 2=Remote, 3=Hybrid (optional)--job-type: contract type filter — F=Full-time, P=Part-time, C=Contract, T=Temporary, I=Internship, V=Volunteer (optional)--experience: experience level filter — 1=Internship, 2=Entry, 3=Associate, 4=Mid-Senior, 5=Director (optional)--time-posted: recency filter — r86400=24h, r604800=7 days, r2592000=30 days (optional)--company-ids: comma-separated LinkedIn company numeric IDs (optional, e.g., 76987811,1441){
"total": 36015,
"start": 0,
"count": 5,
"jobs": [
{
"id": "4416832078",
"title": "Lead Frontend Software Engineer",
"company": "RowsOne",
"location": "Boca Raton, FL",
"workType": "Remote",
"jobUrl": "https://www.linkedin.com/jobs/view/4416832078",
"companyUrl": "https://www.linkedin.com/company/rowsone"
}
]
}
{"error": true} is returned, check that the browser is still logged in to LinkedIn and navigate to https://www.linkedin.com/jobs/search/ to refresh the session, then retry once.eval "$(python scripts/job-detail.py '{job_id}')"job_id: numeric LinkedIn job posting ID (from id field in search results){
"id": "4416832078",
"title": "Lead Frontend Software Engineer",
"company": "RowsOne",
"companyUrl": "https://www.linkedin.com/company/rowsone",
"location": "Boca Raton, FL",
"workType": "Remote",
"contractType": "Full-time",
"experienceLevel": "Mid-Senior level",
"listedAt": "2026-05-26T16:14:30.000Z",
"applicantCount": 37,
"description": "Lead Frontend Engineer (React / Next.js)...",
"salary": null,
"jobUrl": "https://www.linkedin.com/jobs/view/4416832078"
}
{"error": true, "message": "HTTP 403"}, the LinkedIn session may have expired — navigate back to LinkedIn and verify login, then retry.#!/bin/bash
SESSION="fb_explore"
KEYWORDS="software engineer"
LOCATION="United States"
TOTAL_ROWS=50
COUNT=25
OUTPUT_FILE="output/jobs.jsonl"
offset=0
collected=0
while [ $collected -lt $TOTAL_ROWS ]; do
batch_count=$((TOTAL_ROWS - collected))
[ $batch_count -gt $COUNT ] && batch_count=$COUNT
result=$(browser-act --session $SESSION eval "$(python scripts/search-jobs.py "$KEYWORDS" "$LOCATION" --count $batch_count --start $offset)")
echo "$result" | python -c "
import json, sys
data = json.loads(sys.stdin.read())
for job in data.get('jobs', []):
print(json.dumps(job))
" >> output/jobs_basic.jsonl
job_ids=$(echo "$result" | python -c "import json,sys; [print(j['id']) for j in json.loads(sys.stdin.read()).get('jobs',[])]")
for job_id in $job_ids; do
detail=$(browser-act --session $SESSION eval "$(python scripts/job-detail.py $job_id)")
echo "$detail" >> $OUTPUT_FILE
sleep 1
done
page_count=$(echo "$result" | python -c "import json,sys; print(json.loads(sys.stdin.read()).get('count',0))")
[ "$page_count" -eq 0 ] && break
collected=$((collected + page_count))
offset=$((offset + page_count))
sleep 2
done
echo "Done. Collected $collected jobs."
sleep 1 between detail calls to avoid rate limiting. For large batches (>200 jobs), use multiple browser sessions in parallel — each session counts independently toward rate limits.--work-type): 1=On-site, 2=Remote, 3=Hybrid--job-type): F=Full-time, P=Part-time, C=Contract, T=Temporary, I=Internship, V=Volunteer--experience): 1=Internship, 2=Entry level, 3=Associate, 4=Mid-Senior level, 5=Director--time-posted): r86400=Past 24 hours, r604800=Past week, r2592000=Past month--start, type: page-offset, start value: 0. Next page: increment by --count value. Termination: when count in response is 0, or start >= total, or start >= rows target.start=1000 maximum regardless of total.result count >= 1 and jobs[0].id is non-nulltotal shows a higher numberexperienceLevel may be null for many postings — companies do not always fill in this fieldsalary is null for most postings; LinkedIn only shows salary when the employer explicitly provides itsleep 1 between detail callsJSESSIONID cookie set at login--count 3 first to confirm the script runs correctly before scaling up.jsonl file line-by-line so the job can resume from a specific offset on failure{working-directory}/browser-act-skill-forge-memories/linkedin-job-search-linkedin-jobs-search.memory.md (working directory is determined by the Agent running the Skill, typically the project root or current working directory){YYYY-MM-DD}: {what happened} → {conclusion}