GoOpti B.V. cerca: Head of AI Engineering (Architecture & Agents) a Da remoto. <h2>Help 350,000 travellers a year move across…
Azienda: GoOpti B.V. · Sede: Da remoto (Regno Unito) · Modalità: da remoto · Contratto: Full-time
<h2>Help 350,000 travellers a year move across Europe</h2><p></p><p><em>Location: Remote (CET) with two days/month on-site or Ljubljana, Slovenia · Full-time</em></p><p><em>Reports to: CEO, working daily with the dev team and CTO · Start February 2027</em></p><p><em>Salary: €75,000 - 100,000 gross per year + bonus and equity (TBC)</em></p><p></p><p></p><p>GoOpti is a door-to-door shared-transfer marketplace connecting cities and airports across Europe. Behind every booking sits real-time search, dynamic pricing, vehicle occupancy optimisation, franchise and partner settlement, and customer care in several languages and countries.</p><p>We have decided to become an AI-native company. Not a chatbot bolted onto the website - a business where agents do real work in every department, safely, measurably, and connected to the systems that actually run the company.</p><p></p><p>We are looking for the person who designs that foundation and ships the first agents on top of it. You will be our first senior AI hire, with a direct line to the CEO and CTO and an open mandate to shape how we do this.</p><p></p><h3> The role</h3><p>You will do two things at once:</p><p>1. Architect the agent platform - how agents are orchestrated, how they reach our internal systems and data, how they handle context and memory, how we monitor them and where a person stays in the loop. An architecture that makes the tenth agent a week of work, not a new project.</p><p>2. Build and ship - hands on the code, connecting AI to our Java backend, our APIs and our databases, and getting the first autonomous agents into daily use.</p><p></p><h3>What you'll own</h3><p><strong>The Company Brain</strong></p><p>Bring together bookings, prices, trips and franchise results from our data warehouse with our business rules (fares, refunds, franchise terms) and our working knowledge - MS Teams, email, customer-care conversations, complaints, Git - into one machine-readable knowledge layer that agents can query, that flags contradictions and keeps itself up to date.</p><p><strong>Agent platform architecture</strong></p><ul><li>Tool / MCP layer over our booking, pricing, planning, analytics and financesystems</li><li>Orchestration and hand-off between agents, short- and long-term memory, context management</li><li>Observability, tracing and evaluations for non-deterministic systems</li><li>Human-in-the-loop checkpoints and permissioning — a person approves anything touching price or customers</li></ul><p></p><p><strong>The autonomous agents</strong> - start where impact is highest, prove it, expand:</p><ul><li>Marketing - content, SEO/AEO and AI-readable answer pages across our markets</li><li>Development - agents supporting our engineering workflow, from triage to merge requests</li><li>Finance - agents supporting cashflow forecasting, reporting and clearing/refund reconciliation</li><li>Customer care - booking changes handled end to end by our customer-care chatbots (live today, built on OpenAI)</li><li>Pricing & planning - assistants that capture and apply the knowledge of our pricing and planning experts</li><li>Sales (fast follow) - lead handling and B2B partner support</li></ul><p></p><p><strong>Self-improving loops & token economics</strong></p><p>When an agent fails, a supervisor agent diagnoses why, drafts the code fix or policy change, tests it in a sandbox and opens a merge request for a person to approve. Own the model and token budget, choose models per task, run evaluations, and report cost per booking.</p><p></p><p><strong>Intake, priorities & people</strong></p><p>Run a weekly intake of problems from department heads — at most two builds per department at once, </p><p>each with an owner, a measure and a go/no-go gate. Lead one or two contract AI developers, work alongside our backend team, and teach managers how to write a good spec for an agent.</p><p></p><h3>What success looks like</h3><ul><li> By 31 March 2027 - the platform foundation in place; three agent skills in daily use; baselines set; a supervisor agent learning from every conversation our chatbots hand to a person; our pricing and planning knowledge captured in the Brain.</li><li>By 30 June 2027 - at least two skills live in every department; improvement loops running in customer care, complaints and planning.</li><li>By 30 September 2027 - the summer peak handled with office headcount flat; an AI-native review of the whole company.</li></ul><p>How we'll measure it: hours freed per week · share of customer conversations resolved without a person · revenue per employee · token cost per booking · fixes merged from loops. Targets are set together from the baselines.</p><p></p><p><strong>What you'll connect AI to</strong></p><ul><li>Backend: Java core marketplace and micro services; new services in **Java** (REST, Hibernate/Panache, REST clients); legacy JRuby/Rails storefront being migrated to React</li><li>APIs: internal REST services, partner and aggregator APIs, payment and fraud screening integrations</li><li>Data: MySQL (operational + analytics databases), PostgreSQL, Redis, DynamoDB clickstream, a new BI warehouse</li><li>Infrastructure: AWS (EKS), Docker, Kubernetes / Helm, GitHub Actions CI/CD, New Relic</li></ul>
<h3>What we're looking for</h3><ul><li>6+ years building backend or data systems, including 2+ years shipping LLM-based systems in production - tool use, retrieval, evaluations, agents. You have hit context limits, tool-calling failures, runaway costs and silent regressions, and you have opinions about each.</li><li>Strong backend engineering - you are comfortable in a large Java codebase, design clean REST APIs and integrate with existing services. Python or TypeScript for AI tooling.</li><li>Solid data modelling - SQL you can reason about seriously (MySQL / PostgreSQL)</li><li>Architecture thinking - you can argue for and against an approach, write the decision down, and design for scale, security and GDPR from day one.</li><li>Pragmatism - a record of building practical things fast in a small company with real, existing systems.</li><li>Communication - you explain trade-offs to non-technical managers and know when to say no. Fluent English.</li></ul><p><strong>Nice to have</strong></p><ul><li>Building MCP servers and multi-agent orchestration in production</li><li>Experience with LLM observability / eval tooling and model routing across providers (OpenAI, Anthropic, open models)</li><li>Travel, mobility or marketplace experience; routing or operations research</li></ul><p></p>
<h3>What we offer</h3><ul><li>€75,000 - 100,000 gross a year, plus [bonus and equity - to confirm]</li><li>A genuinely open mandate: you shape the AI architecture of the whole company, not one feature</li><li>Direct access to the people whose problems you're solving - and leadership that has already committed to the goal</li><li>A business with real complexity: pricing, fleet optimisation, multi-country operations, partner settlement - agents with something worth doing</li><li>Visible impact: your work moves people across Europe every day</li><li>Budget for models, tools and evaluations</li><li>25+ days of vacation, team buildings and in-person meetups</li></ul><p></p><p>If you want to build an AI-native company for real - with production systems, real customers and real money on the line - we'd love to hear from you.</p><p>Apply now with your CV and a short note on one (biggest) LLM system you shipped to production: what broke, and what you changed.</p><p></p>
© 2026 JobMule