Product Manager, Product Layer of the CTRM System

Read this part first Most of this system is built by coding agents. Delivery capacity is not our constraint — deciding what should exist is. That is the whole of this role. You will not receive requirements. You will go and find out what a trader, an operator, an economist and a financier actually do, write the definition of each of those jobs yourself, and turn it into a working prototype of the system. You will own the backlog and the sprint scope for your layer: what is ready, what enters a sprint, what ships, what gets cut. And you will say no to the business when no is the right answer, and defend it in the demo, with the people who asked for it in the room. If that reads as too much authority for one person, it is not the job you are looking for. If it reads as the first product job in years that isn't ticket administration, keep going. The product We are building the system an international oil-products trader will run its business on: the full deal lifecycle from contract to settlement. Pricing against Platts and Argus formulas. Costs accumulating across a chain of vessels, rail, trucks and storage. Invoicing, inventory, losses, claims, hedging. The purpose of the whole thing is that anyone involved in a deal can reconstruct the P&L between any two points of the chain, at any moment, on an agreed basis. Real money moves on the numbers it produces. Correctness is the product. Today that business runs on spreadsheets, email and phone calls, plus six years of an atte