Senior Software Engineer - Clojure

<h1><span><strong id="docs-internal-guid-1af527c2-7fff-6fa8-2973-ef7a8ee0dcfa">Senior Software Engineer, Clojure at Ardoq</strong></span></h1><p><span><strong id="docs-internal-guid-1af527c2-7fff-6fa8-2973-ef7a8ee0dcfa"><em>Help turn Ardoq's living model of the enterprise into fast, reliable software that customers trust every day.</em></strong></span></p><h3><span><strong id="docs-internal-guid-1af527c2-7fff-6fa8-2973-ef7a8ee0dcfa">The Ardoq story</strong></span></h3><p><span>Ardoq is one of Norway's most exciting scale-ups, a truly global company built out of Oslo. We are a SaaS platform that helps organizations understand, manage, and evolve their complex digital landscape. By providing a dynamic, collaborative "digital twin" of their 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 (like 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><h3><span><strong id="docs-internal-guid-1af527c2-7fff-6fa8-2973-ef7a8ee0dcfa">About the role</strong></span></h3><p><span>Ardoq's platform runs on a proprietary graph foundation that turns fragmented enterprise data into a living, connected model, and a meaningful part of that platform is written in Clojure. As a Senior Software Engineer on the team, you'll take ownership of large, sometimes loosely defined areas of the codebase: designing new capabilities, hardening what's already there, and making sure the decisions you make today hold up as the platform scales. You'll think natively in immutable data structures and pure functions, while staying connected to what customers actually need from the platform.</span></p><p><span>At Ardoq, we value autonomy and psychological safety. In this role, you won't just follow a script; you will have the influence to shape your domain and the ownership to see your ideas through to execution.</span></p><h3><span><strong id="docs-internal-guid-1af527c2-7fff-6fa8-2973-ef7a8ee0dcfa">What you'll do</strong></span></h3><ul><li><p><span><strong>Own complex systems:</strong> Design, build, and improve services across large, sometimes loosely defined areas of the codebase, applying the same rigor to a quick fix as you would to a new capability.</span></p></li><li><p><span><strong>Pay down technical debt: </strong>Identify high-complexity debt before it becomes a customer problem, and architect solutions that keep it from coming back.</span></p></li><li><p><span><strong>Debug at the system level:</strong> Investigate problems that span multiple services and components, and use what you find to prevent them recurring.</span></p></li><li><p><span><strong>Raise the bar in code review: </strong>Give architecture-level feedback that improves not just the pull request in front of you, but the team's coding standards more broadly.</span></p></li><li><p><span><strong>Mentor and multiply: </strong>Share knowledge openly and help other engineers grow their functional programming craft and system thinking.</span></p></li></ul><h3><span><strong id="docs-internal-guid-1af527c2-7fff-6fa8-2973-ef7a8ee0dcfa">On a typical day, you will</strong></span></h3><p><span>Start at the REPL, tracing a data-shape mismatch that only shows up under real production load. You'll spend a chunk of the morning in a focused pairing session, working through a gnarly piece of state management with a teammate, favoring the simplest function that solves the problem over the cleverest one. By early afternoon, you're in a design conversation about how a new feature should fit into the existing data model, pushing back constructively when a proposed shortcut would create debt down the line. You close the day reviewing a colleague's pull request with the same care you'd want on your own, leaving feedback that helps them, and the team, get sharper.</span></p><h3><span><strong id="docs-internal-guid-1af527c2-7fff-6fa8-2973-ef7a8ee0dcfa">Who you are</strong></span></h3><p><span>We'r