Can AI Replace Your Applicant Tracking System? An Honest Assessment for 2026

What unconscious bias really does in hiring, what candidates think about it, what AI can structurally do better – and why the EU AI Act is not an obstacle but the decisive quality filter. With figures from our study of 1,044 job seekers.

We all believe we assess applications rationally. We read the CV, check the qualifications, look for fit – and then decide whether someone is invited to an interview or not.

The research says otherwise.

In a large-scale field experiment in Germany, published by the IZA Institute of Labor Economics, an applicant with a Turkish-sounding name and a headscarf had to send out 4.5 times as many applications on average as an identically qualified applicant with a German name in order to receive the same number of interview invitations. Identical profile. Same education. Same work experience. Different treatment.

Findings like this have been replicated for decades across Europe and beyond. Despite equal treatment legislation, despite awareness training, despite a declared commitment to diversity and equal opportunity. The conclusion is not "recruiters are biased". It is: people are biased, and recruiters are people.

And candidates already know it

Research shows that bias exists. Our own study shows that candidates feel it, too. For "Applying as a Slot Machine", the market research institute Bilendi surveyed 1,044 job seekers on our behalf in July 2026 – all of whom had applied for a job within the previous twelve months. Instead of agreement scales, we asked them to choose between sharply contrasting statements.

The result: 57% assume that hiring decisions are shaped by prejudice – regarding age, gender or origin, for example. 61% say a recruiter's personal sympathy has a very strong influence on who gets through. Among the hiring managers involved, 64% believe this. And almost one in two (46%) experience their own application as a game of chance: often arbitrary and hard to follow.

This contradicts the self-image of many HR departments, which describe their selection as structured, objective and criteria-based. Whether that perception is accurate in any individual case is secondary. Those who believe gut feeling decides in the end apply half-heartedly – or not at all.

This is exactly where a question comes in that is gaining importance in the discussion around AI in recruiting and the EU AI Act: what does a "non-discriminatory hiring process" actually mean – and what can AI contribute to it?

What bias in recruiting actually means

"Bias" is one of the overused words of our time. In recruiting, it means something specific: systematic distortions in how candidates are evaluated that have nothing to do with their professional suitability – and that may constitute discrimination under equal treatment law. The main forms have been documented for decades:

• ‍Halo effect: One striking positive trait – attractiveness, eloquence, a well-known company on the CV – outshines the perception of all other traits. Studies from the 1970s and 1990s (Schuler & Berger; Marlowe, Schneider & Nelson) consistently show that attractive candidates are invited to interviews more often despite identical qualifications. Recruiters are practically never aware of this.‍
• Affinity bias (or "similar-to-me"): Someone from the same city, the same university, with similar hobbies – comes across as more likeable and therefore, unconsciously, more competent. This is the psychological basis behind the much-invoked "culture fit", which sometimes becomes a polite cover for affinity bias.‍
• Name bias: The IZA field experiment is just one example of many. The name on an application systematically changes the probability of being invited – even when the recruiter is convinced they only look at qualifications.‍
• Confirmation bias: Once an initial hypothesis is formed, the brain interprets everything that follows as confirmation. Contradicting evidence is filtered out or reinterpreted.

These mechanisms are not character flaws of individual recruiters. They are properties of the human brain – heuristics we use to process complex information quickly. They activate stereotypes without us noticing.

Notably, those who suspect these mechanisms most are the ones with the most experience: among job seekers over 60, 64% assume prejudice in selection, compared with 55% among 18- to 29-year-olds. University graduates are more sceptical (60%) than people without a degree (53%). The more hiring processes someone has been through, the less they believe in objective assessment.

Why training and anonymised applications alone are not enough

The obvious reflex is: "Then we need to train our recruiters better." Well-intentioned, but empirically a weak strategy.

The reason: bias is largely unconscious. The Implicit Association Test (IAT), used in thousands of variants since 1998, reliably shows that people unconsciously link stereotypes to certain groups – even when they sincerely believe they discriminate against no one. Training that explains the halo effect changes remarkably little. Knowing about a heuristic does not switch it off.

Anonymised applications – leaving out photo, name and date of birth in the first screening round – are a good first step, but not a complete one. As soon as the personal interview begins, every relevant characteristic is back in the room and the heuristics kick in. Anonymised applications reduce bias in pre-selection but do not replace consistent evaluation across the entire process.

Then there is the volume problem. A recruiter reviewing 50 applications a week has less than two minutes per CV on average. At 200 applications, it's seconds. Under that kind of time pressure, the brain falls back almost automatically on heuristics – exactly the shortcuts that produce discrimination in the first place. In other words: the larger the application volume, the stronger the tendency towards unconscious bias. Precisely in the settings where objective assessment matters most, it is hardest to achieve.

Candidates feel that time pressure directly: 59% find it hard to reach employers during the process when questions come up. Where there is no time for questions, there is no time for methodical evaluation either.

What AI can structurally do better

Here is the point that is often overlooked – including in the public debate on AI in recruiting, which likes to focus on risks: a properly built AI has structural properties that can systematically reduce human bias. Not because it is "more neutral" than people, but because it is consistent.

• ‍Consistency: An AI evaluates every application against the same criteria, in the same order, with the same attention. It does not tire, is not influenced by the previous application, does not have a bad day. Application number 1 and application number 200 get the same treatment – something that demonstrably does not hold in human-led processes.‍
• Structured evaluation: Recruiting research has long shown that structured interviews and standardised scoring grids almost double the predictive power for actual job performance compared with unstructured conversations – and massively reduce bias effects. An AI runs structured processes by nature: that is its default mode, not a training recommendation someone might remember.‍
• Auditability: A human decision is hard to review after the fact. Why wasn't this candidate invited? "Gut feeling" is an honest answer in practice, but a risky one legally. An AI, by contrast, can log every step: criteria applied, score calculated, recommendation given. That is what makes patterns of discrimination visible in the first place – and therefore correctable.‍
• Scalability of fairness: Reducing bias is not only a question of will but of capacity. With ten applications, a recruiter might force themselves to work methodically. With two hundred, that gets hard. A well-built AI maintains its methodology at any volume.‍
• Acceptance on the candidate side: A common counter-argument is that candidates don't want AI in the process. The data says otherwise. 54% of job seekers would leave pre-selection to an AI if it decides on verifiable criteria whether they get an interview with their future manager – the classic review of documents by recruiters comes in behind. And 32% name a process free of human prejudice as one of the three most important features of an ideal hiring process. Those who suspect gut feeling in the process trust transparent criteria more than the person at the desk.

The important caveat: AI is not automatically fair

At this point, honesty is required – this is not a statement about all recruiting AIs, but about what AI can fundamentally do when it is deliberately built for it.

The counter-story is well known: from 2014, Amazon developed an internal AI tool for sorting CVs and had to shut it down because it systematically rated female applicants for tech positions lower. The reason was banal: the model was trained on historical hiring data dominated by men – and learned that "male" correlates with "successfully hired". Exactly what the AI was supposed to prevent, it replicated.

The lesson is not that AI is unsuitable. The lesson is that design is decisive. An AI trained unfiltered on historical data replicates the distortions in that data. An AI trained on curated, representative data, whose evaluation criteria are job-relevant and verifiable, and whose live results are continuously monitored for patterns of discrimination, can do the opposite: it makes evaluations more objective, not more subjective.

Candidates draw a clear line here as well. Given the choice, 56% opt for a classic process with human decisions throughout, even if it takes four to ten weeks. 44% would prefer a largely AI-driven process that reaches a decision in 24 to 48 hours – provided a human decides at the end. So AI is welcome at the pre-selection stage. For now, people should decide. Exactly this division of labour is the architecture the following section is about.

This is exactly what the EU AI Act demands

This brings in a reading of the EU AI Act that usually gets lost in compliance discussions. The AI Act is not primarily a hurdle for AI in recruiting – it is a quality filter for the right kind of AI in recruiting.

A note on timing: with the Digital Omnibus Regulation adopted in summer 2026, the EU postponed the application of the core high-risk requirements for Annex III systems – which include recruiting software – to 2 December 2027. That changes nothing about the requirements themselves. Anyone choosing a system today that will need retrofitting in 2027 is buying a problem with advance notice.

What the AI Act requires of high-risk systems – and recruiting is one of them – are precisely the properties that separate a bias-replicating system from a bias-reducing one:

• ‍Data quality and data governance: Training and test data must be curated so that distortions are detectable and controllable. This is exactly the measure Amazon did not take.‍
• Bias monitoring in live operation: Not only the training data but also ongoing results are monitored for systematic deviations. If certain groups are treated differently, it becomes visible – before it becomes a scandal.‍
• Explainability: Every recommendation must be traceably justified. No "match: 73%", but understandable criteria. That makes bias something to discuss rather than guess at.‍
• Human oversight: AI prepares, humans decide. This separation not only protects candidates but also prevents AI bias from flowing uncorrected into a final decision.‍
• Documentation: Every decision is logged. Bias analysis becomes a continuous possibility rather than a one-off audit.

Put differently: anyone looking for a recruiting AI that hires more fairly than people is automatically looking for a recruiting AI that meets the AI Act. The two go together. The AI Act sorts out the tools that replicate discrimination – and leaves those that actively support equal opportunity.

What this means for HR leaders

Anyone who wants to hire more fairly in 2026 than a few years ago has better levers than ever before. Three points make the difference in practice.

1. The honest acknowledgement that human evaluation alone is not a solution. "We pay attention to fairness" is not enough – the data shows that good intentions barely influence the brain's heuristics. Structured processes and consistent criteria are the precondition for a genuinely non-discriminatory hiring process.
2. An AI built for recruiting – not a generalist tool with an HR module bolted on, not a homegrown solution. A specialised recruiting AI brings the decisive properties out of the box: consistent evaluation across all applications, continuous bias monitoring in live operation, traceable justification for every recommendation. Generalist tools inherit the distortions of their training data. Homegrown solutions have to build this architecture first – an effort that is rarely realistic alongside day-to-day business.
3. The clarity that people decide – and can now do so better than before. In a purely human pre-selection, there is often nothing tangible left at the end about why someone was rejected. A specialised recruiting AI turns this around: the recruiter sees every recommendation with its justification and can accept, adjust or reject it. What they gain is not less control – it is informed control, on a data basis that can later be explained and documented.

Our customer VD Mayr, a Munich-based security services company with around 600 hires a year, shows what this looks like in practice. Around half of the applicants for sports events have an international background. In the live interview, Paul checks whether German is available at B2 level – and nothing else. Origin and accent play no role. Self-assessed language skills often differ considerably from actual competence; the structured check makes them comparable, with the same criteria for every application.

One last thought

The most important insight from decades of bias research is not that recruiters are unfair. It is that fairness in recruiting is a question of architecture, not of character. Structured processes, consistent criteria, documented decisions, continuous monitoring – these are the tools with which discrimination can be systematically reduced.

That architecture is exactly what a well-built recruiting AI delivers. And it is exactly what the EU AI Act demands of high-risk systems. Both pull in the same direction – and both work towards a goal that is in every company's interest anyway: better, fairer and verifiably traceable hiring decisions that carry diversity as more than a slogan.

At Paul's job, we have put exactly this logic at the centre of our product: recruiting AI that treats the AI Act not as an afterthought but as a design principle – and candidates as the benchmark. What they want, we have compiled in "Applying as a Slot Machine". The full study is available free of charge.

And if you want to see what fair, AI-Act-compliant recruiting actually feels like: get in touch, we'll show you.

‍

There is now a fairly standard implementation pattern behind many so-called “AI agents”: the model receives context, decides whether to invoke a tool, observes the tool result, and repeats until it decides the task is complete. OpenAI’s Agents SDK describes this explicitly as an agent loop, and Anthropic distinguishes these model-directed systems from workflows, where execution paths are predefined in code.

That distinction is important for production systems, because “agentic” and “autonomous” are not interchangeable. A system can use LLM-based routing, reasoning, decomposition, and synthesis while still keeping control flow, state transitions, and side effects outside model-directed execution.

That is the architecture we chose for recruiting automation.

Instead of pursuing a fully autonomous agent, we chose to build a workflow-governed agent system: a multi-stage architecture in which specialized LLM calls perform bounded cognitive tasks, while orchestration, sequencing, and mutation of system state remain code-controlled. This design is closer to what Berkeley AI Research describes as a compound AI system than to a single autonomous agent.

Architecture overview

Our runtime is organized into three stages:

1. parallel classification
2. domain execution
3. response synthesis

Each stage uses LLMs differently, and each stage has a narrow contract.

1) Parallel classification layer

The first layer performs concurrent inference across several specialized classifiers: safety, jailbreak detection, language identification, retrieval eligibility, intent routing, and workflow classification.

This layer is best understood as a combination of routing and parallelization in Anthropic’s workflow taxonomy. The model helps classify the request, but it does not dynamically construct arbitrary downstream plans. The available execution paths are predefined, typed, and enforced by code.

Two engineering properties matter here:

Latency isolation. Since these classifiers run concurrently, end-to-end latency is closer to the slowest classifier than to the sum of all classifier runtimes.

Error isolation. Each classifier has a narrow prompt surface and a single responsibility, which makes failures easier to detect, evaluate, and retrain than a monolithic orchestration prompt.

2) Domain execution layer

After classification, a code-level dispatcher selects the relevant domain handlers.

This layer reflects our clearest design choice: keeping execution bounded rather than model-directed. The model is not deciding, step by step, which tool to call next in an open loop. Instead, execution follows a constrained graph:

• read-only operations may fan out in parallel
• state-mutating operations execute sequentially
• side effects are performed through code-governed handlers
• outputs are written into typed data structures rather than appended to an unconstrained reasoning transcript

This makes execution semantics more explicit and easier to inspect. The system does not rely on the model to remember hidden state, infer permissible transitions, or decide whether certain checks are required.

For recruiting workflows, that matters because the runtime is not just answering questions. It is also participating in a stateful business process: collecting required information, validating completion criteria, applying stage logic, and triggering downstream actions.

3) Response synthesis layer

The final stage takes structured outputs from prior stages and renders a user-facing response.

This stage is intentionally separated from execution. Its role is linguistic, not operational: translate workflow state into a clear conversational response; adapt tone and phrasing; preserve multilingual quality; and explain next steps.

It does not:

• choose new execution paths
• mutate workflow state
• reinterpret transition rules
• bypass required process steps

That separation of concerns is one of the main advantages of the architecture. It allows the system to benefit from LLM fluency without giving the response model authority over control flow.

Why we did not use a fully autonomous agent loop

The main reason is that for the kinds of recruiting workflows we care about, unconstrained model-directed execution introduces the wrong tradeoffs.

1) Process fidelity is more important than conversational initiative

In a general assistant, initiative can be a feature. In recruiting, it can become a defect.

A screening flow often contains required questions, specific evaluation steps, mandatory disclosures, and deterministic transition conditions. A fully autonomous agent may infer that a question is redundant because the candidate already mentioned something adjacent to it. That may be conversationally efficient, but it can violate standardization requirements or downstream scoring assumptions.

A workflow-governed system is designed to reduce that class of error: the model may adapt how a step is communicated, but not whether the step exists.

2) Stateful execution is easier to reason about in code than in prompt state

State-heavy processes degrade quickly when too much execution logic is delegated to conversational context. In a long-running agent loop, the system must continually preserve and reinterpret latent state across turns and tool results.

By contrast, a typed workflow architecture externalizes state:

• progress is explicit
• transition conditions are explicit
• side effects are explicit
• failure recovery is explicit

That makes the system easier to test, easier to audit, and easier to modify.

3) Reliability still drops sharply in realistic enterprise tasks

Recent benchmark evidence suggests that realistic multi-step enterprise execution remains difficult for frontier systems. In EnterpriseOps-Gym, a March 2026 benchmark covering 1,150 expert-curated tasks across eight enterprise domains, the best reported model reached 37.4% success. That result highlights the gap between impressive local agent behaviors and dependable end-to-end task completion in production-style environments.

The lesson is not that agentic techniques are useless. It is that long-horizon model-directed execution introduces many failure surfaces at once: decomposition, action choice, parameter selection, result interpretation, policy adherence, and state consistency.

Our architecture narrows that error surface by assigning different responsibilities to different components and keeping the most sensitive parts of execution outside autonomous control.

Why this matters specifically in recruiting

Recruiting automation differs from general-purpose assistance in one important way: the conversational participant is not the only stakeholder.

The recruiter, employer, or process owner defines:

• required steps
• evaluation criteria
• transition rules
• compliance boundaries
• acceptable automation behavior

The candidate interacts with the system, but does not define its operating semantics.

That makes recruiting an example of process-governed automation, not pure user-driven assistance.

In that setting, giving the model broad autonomy can create a mismatch between conversational optimization and process correctness. A model may optimize for brevity, empathy, or local coherence while violating requirements that matter to the actual system owner.

A workflow-governed agent system resolves that by separating:

• what must happen — encoded in workflow logic
• how it is communicated — handled by LLMs

Safety and compliance are easier to enforce structurally

Another reason we preferred workflow control is that safety checks can be mandatory pipeline steps rather than optional model decisions.

Moderation, jailbreak detection, policy classification, and scope validation all run because the runtime executes them — not because the model chooses to. That can make prompt injection less effective, since the model does not own the decision of whether protective checks run.

This is particularly relevant in hiring. Under the EU AI Act, AI systems used for recruitment or selection of natural persons are explicitly classified as high-risk in Annex III, and the main obligations for those systems apply from 2 August 2026. In a high-risk context, system properties like traceability, human oversight, and technical documentation become architectural concerns, not just policy aspirations.

A workflow-based architecture helps because it produces explicit intermediate artifacts:

• classifier outputs
• selected execution path
• collected structured data
• triggered rules
• resulting state transition

That is closer to an auditable system record than a free-form interleaving of reasoning and tool traces.

Tradeoffs

This architecture is intentionally less flexible than a fully autonomous agent.

It cannot improvise arbitrary new capabilities outside the defined execution graph. If a capability is not represented in the workflow, the system will not invent it. That is a limitation, but in a regulated, stateful, business-process domain, it is often the right limitation.

The upside is stronger guarantees around:

• process fidelity
• state consistency
• safety enforcement
• auditability
• operational predictability

For recruiting automation, we have found those properties more valuable than unconstrained model autonomy.

Conclusion

We did not reject agentic techniques. We use them extensively — for routing, classification, synthesis, and bounded decision-making. What we rejected was fully autonomous control over execution.

The result is an architecture where LLMs contribute intelligence inside narrow interfaces, while code retains authority over workflow structure, state mutation, and side effects. For recruiting automation, that has been a better engineering fit for us than a single autonomous agent loop.

Yesterday, OpenAI introduced a new feature for ChatGPT: Instant Checkout. Users in the USA can now buy products from Etsy or over a million Shopify retailers directly in chat — without detours via shopping carts or external sites. With Stripe as a technical basis, this creates an agentical protocol for commerce that seamlessly integrates checkout, payment and fulfillment into a conversation.

That sounds like e-commerce at first. But anyone who looks deeper realizes that this is exactly the paradigm shift that we are also experiencing in recruiting.

From click to conversation

In classic online retail, customers click through catalogs, shopping carts and checkout funnels. Now everything happens in a conversation with an AI that presents products, answers questions and finalizes the purchase.

Recruiting was similar for a long time:

• Search job ad
• Open form
• Enter data
• dispatching
• waiting

Today, the process is also shifting here: Agentic AI makes it possible for applicants to apply directly via chat. Whether via WhatsApp, SMS or other messengers — the application becomes a fluid dialogue.

Recruiting = Commerce

The parallel is striking:

• Product data in retail corresponds to job data in recruiting.
• Checkout in e-commerce is the same as an application.
• Fulfillment (shipping, delivery) corresponds to the onboarding phase.

Just as ChatGPT only conveys information between buyer and retailer during checkout, recruiting AI conveys the relevant data between applicant and employer.

The result: less friction, more speed and the candidate experience that applicants expect today.

Agentic AI in applicant management

Instant Checkout creates an open standard for commerce that allows secure, powerful and easy-to-integrate payments in chat. We transfer exactly this idea to applicant management:

• Dialogue instead of a funnel: Applicants upload documents, answer questions, prove qualifications — all in chat.
• Agentic processes: AI understands the context, checks requirements in real time (e.g. language level, certificate of conduct), coordinates appointments and ensures that all stakeholders remain informed.
• Security and data protection: Just like with a payment token, the applicant only shares the data that is necessary — and remains in control at all times.

Agent readiness for recruiting

Instant Checkout creates a new field in e-commerce: agent readiness. Retailers must structure product data so that AI agents can understand and use it correctly.

The same applies to recruiting:

• Clean job data: clear role profiles, requirements, start dates, working hours.
• Machine-readable documents: contracts, proofs, certificates.
• Transparent processes: interview slots, feedback logic, feedback rules.

Only companies that prepare their recruiting data in such a way that agentic AI can work with it will benefit from this development in the future.

Conclusion: Instant recruiting is the next stage of evolution

What we are observing in retail is the blueprint for recruiting: away from click paths and towards intent-driven conversations with AI agents.

Just as ChatGPT completes the buying process in chat, applicant management will soon work like this:

• Find jobs
• Apply directly in chat
• Screening, interview, contract — all in one stream

The result: Recruiting in 60 minutes instead of 60 days.

Companies that start making their processes agent-enabled today secure the decisive advantage: find and hire the right employees faster — before the competition does.

In June 2025, McKinsey released the new CEO Playbook Seizing the Agentic AI Advantage. The report confirms what many of us have long been observing in practice: Generative AI is widely used, but so far it has barely had any noticeable impact on company performance.

McKinsey calls that Gen-AI paradox: Almost 80% of companies are already using AI, but a similar number report that they see no measurable effect on their results.

The reason is simple. To date, most companies have relied on horizontal use cases — chatbots, copilots, text summaries. These are easy to introduce, but only provide diffuse, superficial benefits. Real impact comes from vertical use cases — i.e. AI that is deeply embedded in a company's core processes. That's where agents come in.

‍

The change: From assistants to agents

As McKinsey describes, real added value is only created when processes are automated end-to-end. Agents differ from simple co-pilots because they:

• Understanding goals and breaking them down into subtasks
• Interact with people and systems
• Execute workflows independently
• Adapt in real time as conditions change

This is not just an increase in efficiency — it is a transformation of the way we work.

‍

Recruiting as a prime example

At Paul's Job, we experience this every day. Recruiting is one of the most complex communicative processes in any organization. A single setting includes:

• Candidates who submit documents, answer questions, coordinate appointments
• Recruiters who pre-check, check documents, clarify availabilities
• Hiring managers who make decisions
• Assistants or coordinators who manage calendars and processes

If this process is run manually, it consumes enormous time and management capacity. In industries such as nursing, facility management or retail — where service performance depends directly on sufficient personnel — this has serious consequences:

• Vacancies remain vacant.
• Companies can serve fewer customers or patients.
• Competitors win candidates simply because they are faster.

‍

What happens when you automate recruiting

Now let's imagine an end-to-end recruiting agent. Candidates apply directly via WhatsApp or SMS. Paul, the AI agent, guides them through the process:

• Collects documents (driver's license, language certificates, work permits)
• Checks requirements (language level via voice message, availability, certificates)
• Automatically coordinates interviews with hiring managers
• Prepare contracts as soon as all criteria are met

The result: From initial contact to a signed contract in less than 60 minutes.

This is not a chatbot that is docked to old processes. This is a process that has been rethought from the ground up around agents — exactly the vertical deployment that McKinsey identifies as the missing piece of the puzzle of today's AI strategies.

‍

Why this is particularly important for service industries

In labor-intensive companies, faster recruiting is not just an HR indicator — it directly determines performance:

• Care services with more nurses can serve more patients.
• Retailers and logisticians can staff branches and warehouses more reliably.
• Security and facility firms can fulfill contracts on time, without expensive delays.

Recruiting speed is a strategic competitive advantage, especially in times of skill and labor shortages.

‍

The bigger lesson for CEOs

The McKinsey playbook concludes with a clear message: The experimental phase is over. CEOs must have the courage to fundamentally rethink processes with agents. That means:

• Embed agents into core workflows, not just as an add-on
• Redesign processes to utilize the strengths of agents — parallel operations, real-time customization, scalability
• Create governance to ensure trust, security, and acceptance

Recruiting shows what that can look like: From weeks of communication to hiring in less than an hour. It's not a gimmick, it's process innovation.

‍

conclusion

The Gen AI paradox cannot be solved with additional co-pilots or chatbots. The solution is when companies select a few, highly relevant processes, redesign them end-to-end — and let agents take over.

Recruiting is an excellent example. Anyone who automates here not only gains efficiency, but also real competitiveness. That is the real strength of Agentic AI.

‍

For us, customer proximity doesn't just mean video calls — sometimes it also means being on site live. In September, Yannick was invited to visit our customer VD Mayr.

It started in the office: Yannick visited the recruiting team, looked at their processes and gathered lots of impressions. Particularly exciting: He was able to attend an application day, get to know applicants and talk to them briefly. The highlight: All applicants who appeared that day were recruited, selected and invited completely autonomously by Paul. A real proof point moment for us — to see how our agent really makes the difference in everyday life.

The feedback from candidates was consistently positive: They found the application process via WhatsApp with Paul easy and uncomplicated. That is exactly our goal — to remove hurdles, bring in speed, but still provide an appreciative candidate experience.

And because a successful day also deserves a good end: In the evening, we went to the stadium together with VD Mayr — Bayern versus Chelsea. Football, exciting conversations and a cool evening with customers who have become real partners.

For us, it was a good example of how close we stay with our customers and applicants — not just in theory, but directly in practice.

‍

Be honest: We hear this question all the time. Will AI replace recruiters?

Our answer is clear: No.

But — the role is fundamentally changing.

With Paul, we can already see how much work is being done by recruiters. Communicating with applicants, collecting documents, coordinating interviews, checking basic requirements — an AI agent can do all of this faster, smarter and more consistently.

What does that mean for recruiters? It creates space for the tasks that really matter:

• Build the right teams.
• Strategically support specialist areas.
• Build stronger applicant engagement (almost like HR marketing).
• And very important: managing AI.

Because AI doesn't run on autopilot. With Paul, there is always a human-in-the-loop. Paul suggests decisions — such as whether a candidate fits the profile — but the last word lies with the person. Recruiters thus become AI managers: They review, control and refine what the system does.

Yes, the job profile is changing. But that is exactly where the opportunity lies: better decisions, higher quality and more time for what recruiting really means — the human side.

So no — AI doesn't replace recruiters. But it makes them better, faster and more effective than ever before.

‍