<h3><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">Product Engineer (ShiftX) at Ardoq</strong></span></h3><p><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">Build the collaborative process canvas. Think Figma, but for how your company actually works.</strong></span></p><h4><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">Our Story</strong></span></h4><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>ShiftX is a real-time, AI-native process modeling tool. You map workflows, customer journeys, and org processes in a visual canvas — with your whole team editing at once. We're replacing hours of static documentation with living models that connect to the systems and people behind them.</span></p><h4><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">About the Role</strong></span></h4><p><span>Two years ago ShiftX joined Ardoq (backed by EQT & One Peak). We’re still a small, focused team. The benefit of the acquisition: enterprise distribution and serious resources. The cultural reality: we still work like a startup.</span></p><p><span>In this role you’ll have real ownership over hard problems — autonomy to shape your domain and see your ideas through to execution.</span></p><h4><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">The Problems You’ll Work On</strong></span></h4><ul><li><p><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">Collaborative canvas at scale: </strong>Real-time multiplayer editing on process graphs with hundreds of nodes. Think Figma’s multiplayer model applied to structured graph data — performance, state sync, and conflict resolution all matter here.</span></p></li><li><p><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">AI-powered process generation: </strong>We’re building production-grade features that generate process maps from natural language and images. Not demos — real features that replace hours of manual modeling for our users.</span></p></li><li><p><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">Connecting process to architecture: </strong>ShiftX models live alongside Ardoq’s system and data architecture. Linking these layers opens up genuinely novel product territory that nobody has solved well yet.</span></p></li></ul><h4><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">How We Work</strong></span></h4><p><span>We build close to the user. That means engineers here regularly join customer calls, watch session recordings, and talk directly to the people using ShiftX — not to demo the product, but to understand where it breaks down or gets confusing. When you spot something in a recording that explains a bug report, or a customer mentions a workflow we’ve never considered, that feeds directly into what gets built next.</span></p><p><span>You won’t be handed a complete spec and told to implement it. You’ll be expected to care about whether your work actually solves the problem — and to go find out if it does.</span></p><h4><span><strong id="docs-internal-guid-80f06e4d-7fff-3448-9e9b-d211bf38368e">You’ll Fit If…</strong></span></h4><ul><li><p><span>You’ve shipped production TypeScript/React at a SaaS company and have strong opinions about how to do it well.</span></p></li><li><p><span>You think about UX, not just code correctness — you’ve caught yourself using your own product and noticing something feels off.</span></p></li><li><p><span>You’re comfortable owning a problem from spec to production without being handed a ticket.</span></p></li><li><p><span>You’re curious about how users actually work, and you’d rather jump on a 30-minute call with a customer than guess.</span></p></li>&l