Product Manager, Interoperability

Job Summary

At project44, we believe in better.

We challenge the status quo because we know a better supply chain isn't just possible - it's essential. Better for our customers. Better for their business. Better for the world.

With our Decision Intelligence Platform,

Movement

, we're redefining how global supply chains operate. By transforming fragmented logistics data into real-time, AI-powered insights, we empower companies to connect instantly, see clearly, act decisively, and automate intelligently. Our Supply Chain AI enhances visibility, drives smarter execution, and unlocks next-gen applications that keep businesses moving forward.

Headquartered in Chicago, IL with a 2nd HQ in Bengaluru, India we are powered by a diverse global team that is tackling the toughest logistics challenges with innovation, urgency, and purpose.

If you're driven to solve meaningful problems, leverage AI to scale rapidly, drive impact daily, and be part of a high-performance team - we should talk.

AI at project44

We expect every project44 team member, regardless of role or function, to actively leverage AI in their day-to-day work. Whether you're building product, serving customers, managing people, or running operations, AI is a tool you're expected to use with intent, curiosity, and judgment. We don't expect everyone to be a data scientist. We do expect everyone to be an intelligent user of AI: able to identify where it adds value, direct it effectively, evaluate outputs critically, and govern it responsibly. We invest in our teams AI fluency because we believe it's a competitive advantage for every person at project44, not just our engineers.

Were hiring a Product Manager, Interoperability to define how project44 connects to the systems our customers, logistics service providers, and partners run - which systems we ingest data from, which systems we egress to, and the business rules that govern the workflow between them. This role owns the process design, not just the requirements handoff: mapping as-is and to-be workflows, defining the system-to-system data flow for each integration pattern, and setting the success metrics that determine whether a given interoperability solution actually works for the business, with the goal of creating packaged integration solutions that are ready to go to market, as well as decrease time to value for Project44 customers.

Responsibilities

• Understand project44 s ICP and their Supply Chain Systems of record, and our customers needs to integrate to those solutions. Additionally, understand adjacent solutions and data sources and how our customers use those to fuel their supply chain solutions.

• Define and document system-to-system workflows - which source systems we ingest from (Supply / Demand Planning, ERP, TMS/WMS, EDI/API feeds) and which destination systems we egress to (Supply Chain Planning systems, partner systems, cloud Datawarehouse systems), including sequencing the work and business rules

• Write business design documents, PRD s, design specs and any documentation necessary to communicate system integrations and data types need to support required workflows.

• Own business process design for interoperability: map as-is and to-be workflows for scenarios like order-to-cash, Transportation Planning and Execution, and Supply and Demand Planning lifecycles, exception handling, and translate them into structured system-to-system data flows

• Understand fundamentals of MCP interoperability and where it s used - and how system to system interoperability goals can be met between LLM s

• Define the success metrics and acceptance criteria for each workflow or integration pattern before build begins, and own whether those metrics are actually met post-launch

• Act as the source of truth for interoperability workflow definitions - what data moves, between which systems, under what conditions - resolving ambiguity before it reaches Engineering

• Run structured discovery with customers, partners, and internal stakeholders (Sales, Customer Success, Solutions Engineering) to capture current-state process gaps and target-state workflow designs

• Partner with Data/Platform Engineering to validate that workflow designs are compatible with cloud data warehouse ingestion and transformation patterns (Snowflake, Databricks)

• Prioritize and sequence workflow design work across the interoperability roadmap, balancing one-off customer requests against scalable, reusable process patterns

• Write clear, unambiguous workflow and requirements documentation that Engineering can build against without re-litigating the business process

  Qualifications

• 5-8 years in business process design, business/systems analysis, or product management with a focus on system-to-system integrations

• Demonstrated experience mapping and documenting business process workflows across multiple systems (process mapping, workflow diagrams, BPMN or equivalent)

• Strong fluency in API and MCP concepts and data transformation patterns - enough to define workflows credibly and partner with Engineering on feasibility; hands-on API build experience is not required

• Working familiarity with cloud data warehouse platforms (Snowflake, Databricks, or similar) and how data moves through ingestion, transformation, and egress

• Track record of defining success metrics and acceptance criteria for complex, cross-system initiatives - not just executing against metrics someone else set

• Excellent facilitation and stakeholder management skills; able to run structured discovery sessions with customers, partners, and internal teams and drive them to a decision

• Supply chain, logistics, or complex B2B SaaS platform experience is a plus, not required

  Success Metrics

• Documented, source-of-truth workflow definitions (ingress/egress maps) published for the top integration patterns across the interoperability portfolio

• A standard framework for defining success metrics and acceptance criteria adopted across all new interoperability initiatives

• Reduction in Engineering rework attributable to incomplete or ambiguous process definitions

• Positive feedback from Engineering, Solutions, and Customer Success on the clarity of workflow specs prior to build

  Work from Office Expectations

This role requires you to operate from office all 5 days in a week.

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.