Applied Operations Research Engineer

Hi, I'm Erik, CTO at Circonomit. We build the decision platform industrial companies use to plan their production. The toughest challenges we're facing:

• A model that answers for one site has to keep answering across twelve, over more periods and harder constraints. And a hundred customers have to solve at once without noticing each other.
• Our engineers, and eventually our customers, should build and extend models without you in the room. That means deciding where the abstraction belongs and what the modeling vocabulary has to cover.
• When the honest answer is "impossible", the planner still needs something usable: which rules collide, and what it would cost to bend one.

I need someone to own the engine our models run on: decide how it gets built, build it, keep it running.

Our models decide what gets produced when, on which machine, and at what stock level. The engine sits between the mathematics that makes the answer correct and the product that has to make it usable by people who are not mathematicians.

We came out of RWTH research, raised €2.8M with Vorwerk Ventures, and have customers running on our models today. Small team, Cologne office.

• You have modeled and shipped combinatorial optimization in industry (MILP, CP, or both), with models that ran on messy data and real users.
• Recent, substantial hands-on experience writing and operating production Python: tests, types, review, measurement before optimization. You know how numerics go wrong where a model meets a solver: scaling, tolerances, integrality.
• You know where solvers reach their limits, CP-SAT and Gurobi included, and can say which technique bought you what: warm starts, rolling horizon, relax-and-fix, aggregation, or a heuristic.
• Experience running optimization workloads in production, not only in notebooks: cancellation, timeouts, and parallel solves included.
• You can name the modeling or solver decision that will decide whether something holds up at scale, before it is built.
• The ability to make technical decisions independently and explain the trade-offs.
• You want to understand the customer's problem and their data, not only the mathematics.
• German at C1 level or above, and fluent English. Team communication is in German; code and documentation are in English.
• Existing work visa for Germany.

You should enjoy turning ambiguous customer problems into models that hold up, rather than waiting for a specification. Priorities change as we learn from customers, and we make scope and trade-offs explicit together.

• Ownership. The engine every customer model runs on: modeling language, compiler, solver integration.
• Architectural influence. You'll own how modeling and solving evolve here, and make those trade-offs directly with the team.
• Leverage. You do not build one model for one customer. You build what every model here is built with.
• Real-world impact. Customers plan their production on our models today.
• Direct collaboration. Small team, no org chart. We work directly together. Weekly feedback, both ways.
• Compensation. Competitive salary plus a VSOP package reflecting your contribution and development in the role.
• Hybrid work. We work from our Cologne office, with one to two home-office days per week. You don't need to live in Cologne, but you do need to be able to work from the office on the remaining days.
• Your setup and everyday extras. Hardware of your choice · AI tooling budget · sports membership · Deutschland-Ticket.

Process: A 20-minute call, a technical conversation with me and one of our engineers, a three-hour challenge with a 45-minute walkthrough, then a conversation with the team. Two to three weeks overall, with feedback within days.