<h1><span><strong id="docs-internal-guid-93172ef9-7fff-30e6-430e-bbc8496d03a4">Data Engineer (Mid/Senior) at Ardoq</strong></span></h1><h5><span><strong id="docs-internal-guid-93172ef9-7fff-30e6-430e-bbc8496d03a4">Building the data foundation that turns enterprise complexity into connected intelligence.</strong></span></h5><p><span><strong id="docs-internal-guid-93172ef9-7fff-30e6-430e-bbc8496d03a4">The Ardoq Story</strong></span></p><p><span>Ardoq is one of Norway's most exciting scale-ups - a truly global company built out of Oslo. We are the AI-powered Enterprise Architecture platform that helps organizations understand, manage, and evolve their complex digital landscape. By providing a dynamic, collaborative digital twin of the business, we connect systems, people, and processes to drive better decision-making and accelerate digital transformation.</span></p><p><span>Today, we help some of the world's most complex organizations - including ExxonMobil and British Telecom - gain clarity in a changing world. We are backed by leading global tech investors, including EQT and One Peak, giving us the stability of a mature company with the speed and soul of a startup.</span></p><p><span><strong id="docs-internal-guid-93172ef9-7fff-30e6-430e-bbc8496d03a4">About the Role</strong></span></p><p><span>We're looking for a mid-to-senior Data Engineer to join our centralized data team of 5 in Oslo. Together with the team this role owns the data solutions that the rest of the company can trust and use, from pipelines and models to the platform they run on. You'll operate across large, loosely scoped problems, and you'll get to a solution by iterating with the people who'll actually use what you build, not by shipping to a fixed spec<strong id="docs-internal-guid-93172ef9-7fff-30e6-430e-bbc8496d03a4"><br></strong></span></p><p><span><strong id="docs-internal-guid-93172ef9-7fff-30e6-430e-bbc8496d03a4">What You'll Do</strong></span></p><ul><li><p><span>Partner directly with Product, Customer Success, Finance, and other business stakeholders to understand what they actually need from the data - then build the pipeline, model, or solution that gets them there, not just superficially what they might have asked for.</span></p></li><li><p><span>Design and implement scalable data pipelines that power analytics and business decision-making</span></p></li><li><p><span>Build and maintain alerting to monitor pipeline health, and diagnose and resolve failures within a reasonable time when they happen</span></p></li><li><p><span>Improve data models, ingestion logic, and processing frameworks for performance and long-term maintainability.</span></p></li><li><p><span>Automate away the maintenance you can, rather than manually fixing the same issue every time it resurfaces</span></p></li><li><p><span>Manage a mix of ad-hoc and planned engineering work, balancing competing priorities while keeping stakeholders informed on timelines and progress</span></p></li><li><p><span>Be on the forefront of Data and AI, using AI as a core component of your work— you'll use it to build, test, and actually automate.</span></p></li><li><p><span>Contribute to architectural decisions for Ardoq's data platform, including the trade-offs (speed vs. rigor, cost vs. flexibility) that have real business consequences, and be able to translate these tradeoffs for a less tech-savvy audience</span></p></li></ul><p><strong id="docs-internal-guid-93172ef9-7fff-30e6-430e-bbc8496d03a4"><br></strong></p><p><span><strong id="docs-internal-guid-93172ef9-7fff-30e6-430e-bbc8496d03a4">On a Typical Day, You Will<br><br></strong>Review & action the AI agent replies from yesterday, check & add your thoughts on Slack - and then join the team stand-up to flag blockers and state current work. From there, you might dig into a failing pipeline, trace it to a schema change the source team shipped without warning, patch it, and then work with them to add a check that catches the next one before it breaks anything. PR review is a regular part of the day too - checking a teammate's pipeline changes, their documentation and their tests before merging. Some afternoons bring an urgent ad-hoc request, like pulling together a very spec