Differentiation from Other Providers
Many systems on the market rely on generic AI models trained on broad text corpora (e.g., Wikipedia, Common Crawl). These models are generally not specialized for the context of job profiles, career paths, or industry-specific requirements. Our architecture differs in the following ways:- Proprietary model development: complete control over architecture, training, evaluation, and integration
- Specialized training focus: targeted training on German-language labor market and HR data
- Contextual knowledge about requirements, career paths, and specific companies
- Hosting and data storage in the EU in accordance with GDPR and the requirements of the EU AI Act
Company-Specific Context
A key distinguishing feature of our model is that it not only considers general industry characteristics or company sizes, but also integrates specific companies as contextual elements. This means: When our model sees a role, a skill, or a degree, it evaluates these not in isolation, but in conjunction with the employer – both for previous positions in the CV and for potential future roles.Contextual Interpretation: An Example
The skill “Kubernetes” is a common requirement in technical roles – but its significance varies greatly depending on the company and task context:- In a cloud-native tech company like “Google Cloud” or “Hetzner,” Kubernetes is typically a core component of productive system architectures. Here, the skill indicates deep experience in container orchestration, CI/CD pipelines, and infrastructure-as-code.
- At a mid-sized industrial company with a modern IT department (e.g., “Trumpf” or “Krones”), the same skill usually points to the ability to modernize existing on-prem or hybrid infrastructures and transition them into DevOps processes – often with a stronger focus on automation and stability.
- In a consulting role at companies like “Capgemini” or “Zühlke,” Kubernetes expertise often indicates breadth of project and technology experience – such as the ability to introduce Kubernetes into various client systems, document it, and transfer knowledge.
Training Data and Model Size
The model was trained in three phases:- Pretraining on general German and English text sources (including Wikipedia, public documents)
- Model-specific training on several million profiles from the German-speaking region in three stages of increasing difficulty
Number of parameters: several hundred million
Insights on Requirement Profiles
Through training on structured and unstructured HR data, the model has developed a detailed understanding of job requirements across various industries, company sizes – and specific employers. It recognizes, among other things:- Which skills are typical or required for certain roles
- Which software solutions are commonly used in specific industries and roles
- Which industry experience is often required
- Which educational paths and qualifications are common for certain positions
- Which certifications are considered relevant (e.g., PMP, CFA, ITIL)
- In which roles language skills, willingness to travel, or leadership experience are required
Insights on Career Paths
In addition to analyzing requirement profiles, the model was trained to recognize typical career paths in the DACH region. It can identify relationships and patterns, such as:- Which career steps typically follow one another (e.g., clerk → team leader → department head)
- From which industries or types of companies candidates move into certain roles
- Which universities or educational institutions correlate with certain employer groups
- How long specialists or managers typically stay in certain positions or companies
- Which positions serve as typical preparation for certain roles
Data Protection & Compliance
All training data comes either from publicly accessible sources or has been contractually approved for use. Data processing takes place entirely within the EU. The models are hosted in certified data centers. Our system architecture is designed to meet the requirements of the GDPR as well as the upcoming EU AI Act – including traceability of model decisions (audit trails) and transparency regarding data sources.Frequently Asked Questions
How does the model differ from classic keyword search systems?
How does the model differ from classic keyword search systems?
While classic systems rely on the mere presence of search terms, our model recognizes relationships between terms, roles, skills, and employer context.
It evaluates information not in isolation, but in its respective usage context.
It evaluates information not in isolation, but in its respective usage context.
Which languages does the model understand?
Which languages does the model understand?
The model is geared towards German-language content, but can also correctly process English terms and mixed forms – a typical scenario in many CVs.
Which roles are particularly well covered?
Which roles are particularly well covered?
The focus is on specialist and management positions, especially in commercial, technical, finance-related, and consulting environments.
Is the model being further developed?
Is the model being further developed?
Yes. The architecture allows the model base to be continuously developed and new data sources or requirements to be incorporated.
At the same time, traceability is maintained – a key criterion when dealing with AI in the recruiting context.
At the same time, traceability is maintained – a key criterion when dealing with AI in the recruiting context.