Product Engineer (m/f/d)

About 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. 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 shipped product quickly, without lowering the bar. The AI work AI is core to our product, but we don't run agents for everything. We use them where they create real value. For that we built our own LLM harness from hard-earned production experience: maximum freedom for the model, without compromising on enterprise control, governance or EU data residency. What this means for you: you work hands-on with these new technologies, you run evals instead of trusting demos, and you know how to put this stuff into production reliably. Agent output gets benchmarked against expert-curated baselines, and failure modes get named, measured and fixed. If you are obsessed with how AI systems behave, fail and improve, this is the place for you. How we ship Small teams of 2 to 3 engineers around a topic. We deploy continuously to production. We use AI tools heavily, and you have freedom in which ones (e.g. Cursor, Claude, Codex). Around that we run a strong operating system: clear ticket context, focused branches, AI review before human review, screenshots or videos for product changes, manual product testing before release, production verification after. The engineer who ships a change owns it in production. If something breaks, you lead the fix.