L'IA agentique d'entreprise.
À la française.
TL;DR: You own the technical side of every deal Idun closes — from first call to signed contract. RFP responses, scoping workshops, solution architecture, technical demos. You have a strong engineering background and genuine commercial acumen. You know the difference between a real fit and a stretch, and you tell the truth about both. Paris-based, hybrid, €70–95k base + variable + equity.
Idun Group builds the operating foundation for enterprise AI agents. We deploy agents in production at large European enterprises using Idun Engine (open source, GPL 3.0) and Idun Platform (our proprietary governance and observability control plane). Our clients are engineering-driven organisations in aerospace, luxury goods, industrials, and financial services — the kinds of organisations that have already run a proof of concept and now need to understand whether this can go to production at scale.
Idun's inbound leads arrive technically sophisticated. They have tried LangChain, read the LangGraph docs, and sometimes already have a prototype running. What they need to know is: can Idun get this into production on their infrastructure, within their compliance constraints, on a realistic budget and timeline? Can Idun Platform actually handle their access-control requirements? What does the EU AI Act mean for their deployment?
The AI Solutions Architect is the person who answers those questions credibly and turns qualified interest into a signed statement of work. You are the technical face of Idun during the sales cycle.
This is not a traditional sales-engineer role. The clients are senior engineers and CTOs. The conversations are peer-level technical discussions, not presentations of a product brochure. You will run scoping workshops that produce real architecture diagrams, real component inventories, and real cost models. You will write RFP responses that differentiate Idun from systems integrators who are re-selling generic AI toolkits. You will build reference demos on the Idun Platform that show — not tell — what production deployment looks like.
After the contract is signed, you own the handoff to the consulting team. That means writing a scoping document detailed enough that the first day of the engagement starts with clarity, not re-discovery.
- Lead the technical scoping for all inbound opportunities — initial discovery calls, architecture workshops, written proposals, and formal RFP/RFI responses. - Build and maintain a library of reference architectures and demo environments on the Idun Platform for the three to four most common enterprise use cases (document QA, multi-agent workflow, compliance monitoring, customer-facing assistant). - Write technically credible proposals that are honest about what Idun does and does not do, and that explain why our approach is better for the client's specific context. - Present technical architectures and platform capabilities to CTO, CIO, and VP Engineering audiences — clearly, without overselling, with an accurate picture of complexity. - Define qualification criteria and apply them consistently: flag deals where the fit is poor early, before the consulting team commits time to a bad engagement. - Own the deal handoff — write the scoping document that bridges pre-sales to the consulting engagement, so the client team hits the ground running. - Contribute to Idun's public technical positioning — architecture comparisons, platform capability documentation, and the kind of credible technical content that generates warm inbound.