L'IA agentique d'entreprise.
À la française.
TL;DR: You are the first dedicated hire on the Idun Engine open-source core. You own the runtime that thousands of engineers will use to put LangGraph and Google ADK agents in production. Architecture decisions, API design, observability pipeline, plugin interfaces, OSS community — this is a founding-level engineering role with Paris-hybrid or EU-remote flexibility, €70–100k + significant equity (0.5–1.5%).
Idun Group builds the operating foundation for enterprise AI agents. Idun Engine is our GPL 3.0 open-source runtime: one pip install puts a LangGraph or Google ADK agent in production with a bundled chat UI, admin panel, trace viewer, guardrails, memory backends, MCP tool governance, and OIDC auth. It is the third path between LangSmith Deployment (vendor lock-in, per-node billing) and rolling your own FastAPI wrapper (three weeks of engineering glue). The Engine is used by enterprise clients across Europe and by independent developers building on the open-source layer.
Idun Engine v0.6 collapsed three services into a single wheel and deleted 151,820 lines of code. The surface is clean. The next 12 months are about making the runtime genuinely production-hardened, developer-friendly, and community-ready.
This is not a maintenance role. You are the technical owner of the Engine. You decide how the plugin interface evolves. You define the observability contract between the runtime and external trace backends. You architect the memory abstraction layer. You write the docs that let a developer in Amsterdam or Warsaw deploy a production-grade agent in an afternoon without reading source code.
The work has two surfaces. The first is internal: building the platform features that Idun's consulting practice deploys at clients (Airbus, LVMH, Schneider Electric — they run on Engine). The second is public: maintaining the OSS repo, triaging issues, reviewing external PRs, writing release notes that explain not just what changed but why. Both surfaces matter equally.
You will work closely with Geoffrey (CEO) and Yassin (CTO) on architecture decisions. As a founding engineer, your API choices will be load-bearing — they will be the patterns that ten future engineers build on top of.
- Own the core runtime loop — the FastAPI service layer, the agent execution model, streaming via AG-UI, and the configuration system that drives deployment from a single YAML file. - Design and implement the plugin and integration interface — the seam between the Engine's runtime and external frameworks (LangGraph, Google ADK, Haystack), tool servers (MCP), trace backends (Langfuse, Phoenix, LangSmith, GCP Trace), and memory backends (PostgreSQL, SQLite, Vertex AI). - Lead the observability pipeline: asyncpg COPY writer, OpenTelemetry span ingestion, the admin dashboard KPIs, and the trace viewer — so operators get a real production view, not a demo. - Drive the developer experience: CLI ergonomics (idun setup, idun serve, idun deploy), error messages that tell you what to fix, documentation that does not require reading source code. - Write, maintain, and evolve the public documentation (MkDocs-based) — quickstart, how-to guides, API reference, architecture explainer, migration guides between versions. - Triage GitHub issues, review external PRs, and manage the OSS release cadence — versioned releases with a clear changelog and semantic guarantees. - Contribute architectural context to consulting engagements when client deployments surface Engine limitations that feed back into the roadmap.