Product Engineer (m/f/d)

Job description

At Stackgini we are building the AI operating system for Autonomous Enterprise IT. IT landscapes of large enterprises have never been under more pressure. Thousands of applications to govern. Major transformations to manage. Growing regulatory complexity on one side, business units shipping AI prototypes in days on the other. And in the middle: enterprise IT teams still managing and collecting tech demands manually, managing the complexity of highly integrated processes and systems. Stackgini changes this fundamentally. Stackgini's system understands its customers' enterprise tech landscape from the ground up, from technical configuration to application documentation, from individual IT demands to dependencies across the entire tech portfolio, with the depth of knowledge of a senior IT expert and the speed of a machine. If you had unlimited budget, you would hire a dedicated IT expert for every IT demand. With Stackgini, this is now possible. Some of the largest organizations in this world trust Stackgini including DAX-40 and Fortune-500 customers like Siemens Healthineers or REWE. We're a small, talent-dense team of >10, building what we believe will change how the world's largest companies operate. We are growing fast, and the people joining now are the ones who set the standard - for the product, the culture, and our category. Stackgini will be the place where you will do the most meaningful work of your career. Tasks The role A Product Engineer at Stackgini owns features end to end. You take a customer problem, scope it with Product & CSM, design the solution, build it across the stack, ship it, and stay close to it after release. Recent examples: Product Engineers shipped Decisions and Approvals (a feature for routing IT requests through multi-step approval workflows), built evaluation infrastructure to benchmark agent recommendations against expert baselines, and agentic IT solutions research with our inhouse developed agent tool-use. You are close to users. You join customer calls, run user tests, read support context, and you use that input to decide what should exist and how it should behave. The person building the feature is expected to shape the feature. We have more good ideas than hands. For most reasonable feature ideas the question is not whether we build them, but when. Product Engineers are the people who turn that prioritization into ship…