AI Engineer - Europe only
Talentuch
—
Jul 15, 2026
—
Jul 21, 2026
What this job asks for AI summary
An AI engineering role focused on building and productionizing the LLM layer of a platform, spanning multi-agent orchestration, hybrid retrieval systems combining knowledge graphs and vector search, and evaluation/observability tooling. The work bridges research prototypes and production backends, requiring solid Python engineering experience alongside hands-on familiarity with LLM APIs, agents, and retrieval-augmented generation pipelines.
Senior level · 4+ years · Remote
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 8,200 people nationally plausibly meet what this posting asks for (software developers). range 4,900–12,300
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
The title 'AI Engineer' carries no explicit seniority level, so advertised seniority is Unspecified; however, the 4+ years requirement and expectation of taking prototypes to production systems support a Senior classification.
The OpenAI/Anthropic API requirement includes the qualifier 'or comparable' — Anthropic API is listed as the named alternative; any comparable LLM provider API would also satisfy this gate.
Agent orchestration, tool use, structured outputs, and guardrails are described as core responsibilities but map to the same LLMs/OpenAI API skills rather than separate named technologies.
Hybrid retrieval architectures appear under 'Nice to have' as a distinct bullet alongside vector databases, so both are marked preferred even though retrieval is discussed in the role narrative — the narrative is context, not a gate.
No compensation, location, or employment type is stated in the posting.
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.