Technical Product Manager

IMC is building the next generation of trader facing tools, and we are looking for a Product Manager to help lead that effort. Technology sits at the heart of how we trade, and these applications are not support systems. They are the primary interface traders use all day, every day, to see the market, make decisions, and execute.

This role sits directly at the intersection of trading and engineering. You will help reimagine how our tools work from the ground up, shaping workflows, visualizations, and interactions where speed and clarity matter. In many cases, a single click or extra second can be the difference between capturing an opportunity or missing it. Your work will have immediate and measurable impact on trading performance.

You will play a central role in a major reinvestment in our trading platform, with real ownership, high visibility, and the chance to define how traders interact with the market at IMC for years to come.

Your Core Responsibilities:

• Partner closely with traders to understand daily workflows, decision making, and trading patterns
• Work with engineering teams to design, build, and iterate on high performance GUIs
• Translate trader insights and business needs into clear product goals, priorities, and requirements
• Own initiatives end to end, from problem definition and scoping through delivery, iteration, and adoption with development teams
• Obsess over workflow efficiency, recognizing that every click, keystroke, and visual element matters
• Identify opportunities to share common patterns and tools across desks, but also decide when it makes sense to deviate
• Communicate product direction, priorities, risks, and progress clearly to trading, engineering, and related teams
• Surface dependencies and risks early, see them before they become blockers

Your Skills and Experience:

• Experience owning and driving complex products that are the central focus of a user’s daily work
• Background in trading, financial markets, trading systems, or closely related domains is ideal but not required
• Strong intuition for how users interact with tools under time pressure, and how design choices affect decision making
• Enough technical depth to work effectively with engineers and reason about systems, data flows, and tradeoffs
• Demonstrated ability to turn ambiguous problems into clear direction and execution
• Clear and effective communicator across disciplines