Staff AI Engineer, Developer Productivity

Our mission at Oura is to empower every person to own their inner potential. Our award-winning products help our global community gain a deeper knowledge of their readiness, activity, and sleep quality by using their Oura Ring and its connected app. We've helped millions of people understand and improve their health by providing daily insights and practical steps to inspire healthy lifestyles. Empowering the world starts with living our values and empowering our team. As a quickly growing company focused on helping people live healthier and happier lives, we ensure that our team members have what they need to do their best work — both in and out of the office. About the role Oura is rebuilding how it builds software. Every engineer has agentic tooling, and our own pipeline already takes a well-formed ticket to a reviewed, tested commit stack. It runs interactively, headless, and on a cloud sandbox fleet, with its own evals and tracing. We are looking for engineers who use AI as a fundamental building block of both the products we ship and the way we build them. That is a strong start on one stage of the lifecycle. The next step is the whole loop. As a Staff Engineer on the AI Transformation team, you will architect and own the system that turns agentic development from something power users do into the way hundreds of engineers across iOS, Android, backend and AI services ship every day. That means spec and intake, planning, implementation, review, testing, CI/CD, release, observability and incident follow-up, each with agents doing real work and humans keeping judgment where it matters. This is a fast-moving, LLM-forward team. We prioritize rapid prototyping, iterative loops and AI-native development, with the speed of a startup and the reach of a product used by millions of members. You can work hybrid from our offices in Helsinki, Oulu or Tampere. You will build the pipeline, measure it, and make it trustworthy enough that teams choose it. Success is measured in validated changes reaching members faster and safer: time to a trustworthy signal, escaped defects, cost per merged change, and how many squads run on the paved path because it is better, not because they were told to. What you will do You don't need to do all of these on day one, but these are the kinds of problems you'll own: Set the technical direction for the agentic pipeline: Make our existing ticket-to-PR pipeline dependable infrastructure. Own its architecture, including agent orchestration, context management and tool calling, and improve its reliability, throughput, cost and developer experience across mobile, backend and web repositories. Run it unattended where the risk allows. Close the loop across the SDLC: Extend agentic workflows beyond code generation into spec quality checks, test generation, automated review, CI failure triage and repair, release verification, and post-deploy signals, so the system improves from what happens after merge. Prototype fast, then harden: G