Skills required in ADEM job vacancies

Open data API in a single place

Provided by Agence pour le développement de l'emploi

Get early access to Skills required in ADEM job vacancies API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
2024.09.04
Available languages
English
Keywords
job, competences, work, skills, travail, emploi
Quality scoring

Dataset description

This dataset contains data on the skill requirements identified in each job vacancy that was brought to ADEM’s database between 2015 and now. Employers in Luxembourg are legally obliged to transfer their open job vacancies to ADEM. Each row of the dataset corresponds to a vacancy-skill combination: for example, if vacancy_id=”123” and skill=”work in teams”, this means that our algorithm identified the skill of working in teams in the description of vacancy “123”. If the column skill is empty for a given vacancy, this means that no skill requirement could be identified for that vacancy. Skills are identified through an algorithm that automatically reads the job vacancy description and classifies the skill requirements based on fuzzy text matching, given a set of keywords corresponding to each skill requirement. Identified skills are structured according to the ESCO framework, based on the metadata made available (see https://esco.ec.europa.eu/en/classification/skill_main). Most other variables (number of advertised job positions, canton of work location, occupation, economic sector) are based on information declared by the employers transferring the vacancy to ADEM; the month and year refer to the time of publication. The methodology used to perform and evaluate the skill identification is described in the paper "Evaluating ESCO Skill Classifiers", available in the Journal of the International Association for Official Statistics (https://doi.org/10.1177/18747655251395229) or open source on the SSRN repository (https://doi.org/10.13140/RG.2.2.13502.55366). **Variable ** Vacancy _id: Dataset-specific Id of the vacancy Skill: ESCO preferred label for the skill (see https://esco.ec.europa.eu/en/classification/skill_main) Skill_uri: ESCO id for the skill (see https://esco.ec.europa.eu/en/classification/skill_main) Positions: open positions advertised in the vacancy (e.g. if a company opens a vacancy to recruit 7 accountants, then positions = 7) Month: month of publication of the vacancy Year: year of publication of the vacancy Canton: Canton in which the advertised job would be located Occupation _code: ROME occupational code that best fits the vacancy (see https://rome.adem.etat.lu/index_base.html and https://www.franceoeuvre.fr/employer/your-recruitments/le-rome-et-les-fiches-metiers.html) Occupation _label: ROME occupational code label for the vacancy (see https://rome.adem.etat.lu/index_base.html and https://www.franceoeuvre.fr/employer/your-recruitments/le-rome-et-les-fiches-metiers.html) NACE_code: NACE economic sector code that best fits the vacancy (see https://statistiques.public.lu/dam-assets/catalogue-publications/nace/nace-2.pdf) NACE_label: NACE economic sector code label for the vacancy (see https://statistiques.public.lu/dam-assets/catalogue-publications/nace/nace-2.pdf)
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks