Founding Product Manager

Job description

We are building the world's decision infrastructure: the strategic twin of every industrial organization for complex combinatorial problems. We unlocked what wasn't possible before: mapping reality with its levers and constraints into a computer, then running n-dimensional optimization on critical value-chain decisions. We help Europe stay strong and the German Mittelstand make good decisions between market shifts, orders, machines and people. Founded by Dana (CEO) and Erik (CTO) from RWTH research, backed by a €2.8M round led by Vorwerk Ventures, with customers live on our optimization models. We move fast. We care. No patience for problems left unsolved. Your mission You own the product and the priorities behind it. The hard part of that job here is structural: our go-to-market runs vertically, one use case at a time, while the product has to stay general enough to serve the next customer without being rebuilt. You sit between Sales and Engineering and translate in both directions. Towards Sales: which use cases we can sell today, which we cannot, and what a demo is allowed to claim. Towards Engineering: which requirement is ready to be built, what it needs to be complete, and what we deliberately leave out. This is an early-stage role and we expect you to shape it rather than inherit it. We are extending the core of the application right now, which means your first decisions land while the product is still taking form. At the beginning, a meaningful part of your work will be spent on customer projects, close to the people whose decisions we model. That is where you see which patterns are worth turning into product. We will not sugarcoat it: short deadlines, wild workload, and a go to market with the product and its tech that is a day to day focus and iteration process. What you'll own The product roadmap and the reasoning behind it: what we build next, in which order, and what we decline. The boundary between standard product, configuration, and manual work for one customer. Requirements that engineering can build from: scope, acceptance criteria, and a clear statement of what is out. What we can credibly promise a customer, including where the product's limits currently are. Proofs of Value that you run yourself, and responsibility for individual accounts. Prototypes you build to test features with customers before we commit engineering time. How produc…