Location: EU
AI tooling changes weekly. Keeping up is hard. Turning it into something teams actually use in daily work is harder. That is the job.
You will work with the VP of Engineering and the Chief Architect to build and run the AI tooling that our engineering teams depend on. Agents, plugins, MCP servers, integrations, and the infrastructure around them.
Not a research role. Hands-on engineering and enablement.
You’ll work closely with the VP of Engineering and the Chief Architect, and you have real influence over how our engineering teams build software. This role is the start of a small AI platform team we are building over the next year.
Keep us current on what is actually worth using. Anthropic, OpenAI, Google, open source, the agentic ecosystem. Test things, form opinions, make recommendations backed by evidence.
Take AI from prototype to production. Set up agents, plugins, MCP servers, hooks, and integrations that run reliably. Get the operational side right: access, cost limits, audit trails.
Run the AI coding assistant stack. Install it, configure it, keep it updated, watch the costs, fix things before teams notice.
Build the shared infrastructure. MCP servers, agent configs, reusable prompts, custom tools. All version-controlled and documented.
Help teams actually use it. Pair with engineers on real work. Move them from "tried it once" to "this is how I work now."
Work with the Chief Architect on what good looks like. Code review standards, patterns, and tooling that makes them easy to follow.
Talk to engineers constantly. Find the friction, remove it, share what works.
A real software engineering background. You have shipped production code across more than one stack.
Actual experience using AI coding agents for real work. Claude Code, Cursor, Cline, Copilot, whatever. You know where they help and where they do not.
Production experience with AI features. Agents, RAG, MCP integrations, LLM-backed features that users depend on.
Comfort with agentic patterns: MCP, tool use, context management, prompt engineering, evaluation.
Curiosity. You follow releases, read the papers you need to, and try new tools quickly. You do this because you want to, not because someone told you to.
Solid infrastructure habits. Version control, scripts, reproducibility, observability.
You can talk to people. Senior engineers who are skeptical, juniors who are overwhelmed, and everyone in between.
Self-direction. The role does not come with a playbook.
Nice-to-haves:
Developer tooling or platform engineering experience
Azure, GitHub, modern CI/CD
Some exposure to .NET or TypeScript (our main stacks)
Background as a working developer before moving into enablement
Long-term engagement in a stable, growing SaaS company
Remote-first, async-friendly culture
High engineering and product standards
A team that values depth over hype: production quality over flashy prototypes
A culture that values personal growth as much as business outcomes
Flexible environment with a flat organizational structure
A global, diverse, and highly skilled team across Denmark, Ukraine, UK, Poland, Canada, Australia, USA, and more.
Sounds like a good match?
We look forward to your application! (please submit your English CV)
Auditdata is an equal opportunity employer that is committed to create diverse work environment free of discrimination and harassment. We make hiring decisions based on your experience and skills.