Karriere.at Jobs Scraper
Pricing
Pay per usage
Karriere.at Jobs Scraper
Extract job listings from Austria's leading job board. Scrape Karriere.at for titles, companies, salaries & requirements. Perfect for job market analysis, recruitment automation & competitive intelligence. Fast, reliable data extraction.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Shahid Irfan
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Extract job listings from Karriere.at with titles, companies, locations, salary details, employment types, and optional full descriptions. This actor is built for recruiting research, market monitoring, job data pipelines, and lead generation workflows that need clean structured output.
Features
- Keyword and location search — Collect jobs by keyword, location, or both.
- Direct URL input — Start from a Karriere.at search URL when you already have the exact filtered search page.
- Real pagination support — Continues through additional result pages until the requested number of jobs is collected.
- Optional detail enrichment — Adds full descriptions and extra structured job fields when enabled.
- Clean dataset output — Omits empty and null values from dataset items.
Use Cases
Recruitment Research
Track openings for specific roles and cities to understand demand, salary trends, and employer activity.
Market Intelligence
Monitor hiring activity across companies and regions to detect growth patterns and changing labor demand.
Job Data Pipelines
Export structured job data into dashboards, spreadsheets, databases, and downstream automation flows.
Sales Prospecting
Identify companies actively hiring relevant roles and build targeted lead lists for outreach.
Input Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
startUrl | String | No | — | Karriere.at search URL to start from |
url | String | No | — | Alternative search URL input used when startUrl is empty |
keyword | String | No | software engineer | Search keyword for jobs |
location | String | No | Wien | Location filter for jobs |
collectDetails | Boolean | No | true | Enrich items with full job description and extra details |
results_wanted | Integer | No | 20 | Maximum number of jobs to collect |
max_pages | Integer | No | 10 | Safety cap on pages to visit |
proxyConfiguration | Object | No | optional | Proxy settings for more reliable collection |
Output Data
Each dataset item can contain:
| Field | Type | Description |
|---|---|---|
id | String | Karriere.at job ID |
url | String | Job detail URL |
title | String | Job title |
company | String | Company name |
company_id | String | Company identifier |
company_slug | String | Company slug |
company_url | String | Company profile URL |
company_logo_url | String | Company logo URL |
company_employees | String | Reported employee range |
company_location | String | Main company location |
company_website | String | Company website when available |
location | String | Primary location |
locations | Array | All extracted locations |
location_slugs | Array | Extracted location slugs |
salary | String | Human-readable salary text |
salary_min | Number | Numeric salary minimum when available |
salary_currency | String | Salary currency |
salary_period | String | Salary period such as month or year |
employment_types | Array | Employment types for the role |
date_posted | String | Relative publication text |
posted_at | String | Structured posting timestamp |
is_home_office | Boolean | Whether home office is signaled |
is_active | Boolean | Whether the listing is active |
is_smart_apply_job | Boolean | Whether the job supports Smart Apply |
is_direct_apply | Boolean | Whether direct apply is available |
description_html | String | Full description in HTML |
description_text | String | Plain-text description |
snippet | String | Listing snippet |
source | String | Source platform name |
Usage Examples
Basic Keyword Search
{"keyword": "software engineer","location": "Wien","results_wanted": 20}
Search By URL
{"url": "https://www.karriere.at/jobs?keywords=data&locations=graz","results_wanted": 30,"max_pages": 5}
Listing-Only Collection
{"keyword": "marketing","location": "Linz","collectDetails": false,"results_wanted": 15}
Sample Output
{"id": "10010845","url": "https://www.karriere.at/jobs/10010845","title": "Junior Software Support & Application Engineer","company": "RailNetEurope","company_id": "119456","location": "Wien","salary": "ab 47.000 € jährlich","salary_min": 47000,"salary_currency": "EUR","employment_types": ["Full Time"],"date_posted": "30.3.2026","posted_at": "2026-03-30T00:00:00+02:00","description_text": "RailNetEurope (RNE) is an association of European Infrastructure Managers...","source": "karriere.at"}
Tips for Best Results
Use Specific Searches
Use focused keywords and locations to reduce noise and get more relevant results.
Start Small First
Test with results_wanted: 20 before increasing volume for production runs.
Use URL Input For Exact Filters
If you already have a Karriere.at search page with the right filters applied, pass it through startUrl or url.
Disable Details For Faster Runs
Set collectDetails to false when you only need listing-level data.
Proxy Configuration
{"proxyConfiguration": {"useApifyProxy": true,"apifyProxyGroups": ["RESIDENTIAL"]}}
Integrations
- Google Sheets — Export job data for analysis
- Airtable — Build searchable hiring databases
- Slack — Send run notifications to your team
- Webhooks — Forward results to your own endpoints
- Make — Automate enrichment and delivery workflows
- Zapier — Connect job datasets to other business tools
Export Formats
- JSON — For APIs and developers
- CSV — For spreadsheets and BI tools
- Excel — For business reporting
- XML — For custom integrations
Frequently Asked Questions
Can I use a search URL instead of keywords?
Yes. You can provide startUrl or url and the actor will use that search page directly.
Does the actor collect more than the first page?
Yes. The actor follows the site pagination flow and keeps loading more pages until it reaches results_wanted, max_pages, or no more pages are available.
Can I collect only listing data?
Yes. Set collectDetails to false if you do not need full descriptions.
Why are some fields missing from certain items?
Some jobs do not expose every field. Empty and null values are omitted from the final dataset.
Will user-provided input override defaults?
Yes. Runtime input always takes priority over defaults and prefill values.
Support
If you encounter issues or want a feature improvement, use the support channel for your deployment environment or open an issue in the project repository.
Resources
Legal Notice
This actor is intended for legitimate data collection and research. Users are responsible for ensuring their use complies with website terms of service and applicable laws. Respect privacy requirements, robots.txt where relevant, and reasonable rate limits when collecting data.