Stand out for this role — generate a tailored resume and cover letter in about a minute.
Better Collective in Copenhagen, Denmark, seeks a hands-on AI Engineer to build and productionize AI-driven publishing workflows.
You will turn ideas into working software, test quickly, and collaborate with QA, product, editorial, and production teams to validate model outputs. Strong Python, TypeScript, LLMs, and API/agentic tooling experience are required.
We are looking for a hands-on AI Engineer to build, test, and improve AI-driven solutions for the publishing business.
This is a practical technical role. We are not looking for someone who only talks about AI strategy, builds simple no-code automations, or experiments with visual app builders. We are looking for someone who can turn ideas into working software, test things quickly, and help move useful AI solutions toward production.
The ideal candidate is technically strong, curious, independent, and comfortable working with emerging AI technologies. You should be familiar with LLMs, APIs, agentic workflows, and frameworks such as LangChain, LangGraph, LlamaIndex, or similar tools.
You should also be comfortable using modern agentic coding tools such as Codex, Cursor, Claude Code, GitHub Copilot, or similar systems as part of your development workflow.
This is not a no-code or low-code automation role.
Experience with tools such as Make, Zapier, Lovable, Bolt, or similar platforms can be useful, but it is not enough for this position on its own. We are looking for someone who can code, debug, integrate APIs, design AI-powered workflows, evaluate outputs, and build systems that can become reliable production tools.
You should be comfortable working directly with code and using AI as part of a serious engineering workflow.
Candidates must document something they have personally built where the final project or pipeline uses AI.
As part of the final application process, candidates must present a small project, prototype, workflow, pipeline, or technical solution they have built. The final result must actively use AI, such as an LLM, AI API, agentic workflow, retrieval system, automation pipeline, model-based classification, content generation flow, or similar AI-driven component.
The documentation should clearly show:
Projects built only with no-code or low-code tools will not meet this requirement unless there is also clear technical implementation, coding, API integration, or system design involved.
This requirement is intended to demonstrate hands-on ability, technical curiosity, independent execution, and comfort with using AI in real project work.