Skip to content
ApplySignals Get early access

Fresh job postings from employer career sites, ready for your pipeline.

We read the career sites employers publish on their applicant tracking systems and turn every posting into a clean record: where it is, how it is worked, what level it is, its ISCO code, and the requirements the ad actually states. You pay only for the jobs you take.

Get early access See every field

kestrel-freight.example/careers, read on 24 Oct

Senior Backend Engineer (Hybrid)

Kestrel Freight GmbH, Berlin, Germany

You will build the services that route 40,000 shipments a day. You have 5+ years of backend experience in Java or Kotlin, and you have run production services on AWS.

German is a plus. Three days a week in our Kreuzberg office.

Salary: EUR 75,000 - 90,000 per year. Questions? Call [phone removed].

work_arrangement
hybrid
location.country
DE
classification
senior, engineering, ISCO 251
skills_required_any
java or kotlin
skills_required
aws
min_experience_months
60, overall
languages (preferred)
de
salary
75,000 to 90,000 EUR a year
An illustrative posting and the fields its record carries. Every requirement keeps the exact quote it came from, and phone numbers and emails are removed before delivery.

Coverage today

Counting live postings…

What every record holds

One record per posting, keyed by a stable id that never changes while the posting lives. Fields we cannot read from the posting stay empty instead of being guessed.

Where and how

  • City, state and ISO country code, plus the location text as the employer wrote it
  • Remote, hybrid or on-site, read from the title, the location or the ATS's own field
  • Full time, part time, contract, temporary or internship

The role

  • Seniority, published only when the title states it
  • Job family and the ISCO-08 minor group (3 digits) with its label
  • Department and team when the employer lists them

Requirements

  • Required and preferred skills, with "Java or Kotlin" kept as alternatives
  • Minimum experience in months, by scope: overall, role, skill or industry
  • Education, certifications, languages and industries, each with its source quote

Pay and source

  • Salary range, currency and period, exactly as published
  • Company, its career site, the ATS and the ATS's own job id
  • The posting URL and the apply link

Text and freshness

  • The full description as plain text with its line breaks
  • When we first saw the posting, when the employer dated it, and when its board last confirmed it

Read the full field reference

How to get the data

  1. 1

    Open ApplySignals on Apify

    Sign in with your Apify account; there is nothing else to set up.

  2. 2

    Choose what you need

    Filter by keywords, country, ATS, work arrangement, seniority, ISCO group, skills or the date a posting was first seen.

  3. 3

    Run it and take the dataset

    Download JSON, CSV or Excel, or read the dataset through the Apify API. Schedule the run to collect new postings every day.

You pay per job returned, through your Apify account, and the current price is on the Apify listing. On Apify's free plan you get up to 100 sample jobs a day with short descriptions, so you can check the fields before you buy.

Need volume or a direct API key? Write to hello@applysignals.com.

Kept current, kept clean

Each record says when it was confirmed

verified_at is the last successful check of the employer's board that still listed the posting. New postings usually reach the dataset within an hour of that check.

Closed postings leave

When a posting disappears from its board, it leaves the dataset once the board's next successful check confirms it is gone, or after 24 hours. Asking for a removed id returns only its status.

Contact details are stripped

Email addresses and phone numbers in descriptions and quotes are replaced before delivery. Salary ranges, dates and reference numbers stay.

Removal on request

Employers and people named in a posting can ask us to take it out. See how to send a takedown request.

Questions

Where do the postings come from?

From public career sites that employers run on applicant tracking systems such as Greenhouse, Lever or Workday. We read the same pages job seekers see, so every record links to the employer's own posting.

How are the requirements extracted?

A language model reads each description and lists what it asks for, quoting the sentence each requirement comes from. Output that fails validation is not published. The record names the model and the extraction date.

Can I get only new postings?

Yes. Filter on the date a posting was first seen, for example the last 24 hours, and schedule the run daily.

Are descriptions complete?

Paid runs get the full text we store, up to 25,000 characters. A longer description is cut at that point and its record says so.