Staff Platform Product Manager, Movement

project44•Chicago, IL

1d•$165,000 - $240,000•Hybrid

About The Position

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. 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 team's AI fluency because we believe it's a competitive advantage for every person at project44, not just our engineers. 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. In-office Commitment: Our office is where ideas spark, connections thrive, and innovation comes alive. We are looking for candidates who are enthusiastic and committed to joining our team on-site, in our beautiful headquarters four days a week. Together, we’re building something extraordinarily learn, grow, and thrive in our fast-paced, transformative environment. About the role Movement is the platform underneath everything project44 ships: visibility, analytics, AI agents, and a growing set of modules (Appointment Manager, Yard, Last Mile) being migrated onto it as a shared foundation. We're hiring a Senior Platform Product Manager to own both halves of that foundation: the technical platform capabilities that power Movement — identity and access, Collaborative Visibility, Search — and the user experience built on top of them. This is the connective tissue that makes Movement feel like one coherent product instead of a collection of features — the experience layer every persona depends on, the analytics customers see every day, and the security guarantees enterprise customers require before they'll trust us with sensitive freight data. You'll sit at the intersection of Product, Design, Engineering, and Security — partnering closely with the pillar PMs who own individual modes and modules, while owning the platform primitives all of them build on. The role is deliberately dual-track: deep technical partnership with Engineering on the capabilities beneath the surface, and close partnership with Product Design on the experience above it.

Requirements

6+ years of product management experience, with meaningful time owning platform, identity/access, or infrastructure-adjacent surfaces — not only customer-facing features
Working knowledge of IAM concepts (roles, permissions, tenancy, authorization) deep enough to have real trade-off conversations with engineering
Range across both technical platform work and user experience — credible with engineering on data models, APIs, and search performance, and a real partner to Design on UX vision and prototypes
A track record of shipping analytics or reporting products, ideally including vendor or build-vs-buy decisions for embedded BI
Experience designing for multiple personas within one product, with the configurability-vs-complexity trade-off made explicit rather than assumed
Comfort operating in ambiguity — this charter has been informally covered by several people, and you'll need to define its edges as much as execute inside them
Clear, direct writing — PRDs and briefs a busy exec can read in five minutes and act on
Enterprise B2B SaaS experience; supply chain, logistics, or another data-intensive vertical platform is a strong plus

Nice To Haves

Experience integrating an acquired company's users and data onto a unified platform and permissions model
Familiarity with freight/logistics security requirements (cargo visibility restrictions, data-sharing constraints) or equivalent regulated-data experience
Experience evaluating or migrating embedded analytics/BI vendors

Responsibilities

Own the product vision for how Movement's core experience evolves — the Overview dashboard, navigation, and shared UI patterns that other modules inherit as they migrate onto the platform
Partner directly with Product Design on UX vision and prototypes, translating design principles into a sequenced, buildable roadmap
Arbitrate platform-level UX trade-offs across pillar teams so Movement doesn't fragment into inconsistent experiences as more products move onto it
Own the web, responsive, and mobile app strategy for Movement — deciding what belongs on web versus mobile, how responsive breakpoints serve users, and driving that plan through to implementation with Design and Engineering
Own the roadmap for Movement's IAM layer: tenant and user permissioning, Access Groups, role definitions, and the unified authorization model that lets us bring new products and acquisitions onto one identity system instead of bespoke ones
Define and prioritize new permission models (e.g., restricted-visibility roles for security-sensitive customers) in partnership with Engineering and Security
Be the product point of contact for IAM scoping on new acquisitions and partner integrations
Own the product roadmap for Collaborative Visibility — how shippers, carriers, and partners share shipment data across tenant boundaries, and what each party is permitted to see
Own Search as a platform capability: a consistent, performant way to find shipments, orders, locations, and documents across every module on Movement
Work directly with platform engineering on the technical trade-offs behind these capabilities — data models, APIs, and performance — and translate them into a sequenced roadmap the pillar teams can build against
Take Movement from a one-size-fits-all Overview to persona-aware experiences for operators/planners, managers, and executives, building on validated discovery already in hand
Define what's configurable versus persona-default, and how personalization scales without fragmenting the core platform
Partner with Data/Analytics to use behavioral data — not just stated preference — to keep refining personas post-launch
Own the platform-level strategy for analytics embedded in Movement: the shared infrastructure and experience layer, distinct from the mode-specific analytics content pillar PMs already own
Lead build-vs-buy and vendor decisions for embedded analytics/BI
Define self-service and platform-value reporting that cuts manual reporting work for Customer Success and gives customers direct visibility into adoption and ROI
Own security and data-exposure requirements across Movement's UI and APIs — field-level redaction, need-to-know access patterns, and audit logging for regulated or security-sensitive customers
Partner with Security/Privacy and Engineering to turn customer security requirements into shippable, testable product requirements rather than one-off exceptions
Represent Product in compliance-adjacent conversations (e.g., SOC 2, customer security reviews) where platform behavior is in scope
Be the accountable owner that Sales, CX, Support, and Engineering escalate to on platform-level Movement questions
Represent Platform in quarterly planning, RICE-based prioritization, and roadmap reviews alongside pillar PMs
Write clear PRDs, product briefs, and decision docs — this org runs on Confluence and Jira Product Discovery as the system of record, not Slack threads
In your first 90 days, expect to: get current on the two or three enterprise-committed platform requests already in flight, ship (or make the call not to ship) the first phase of persona-based experiences, and stand up a clear owner-of-record model for embedded analytics — including a recommendation on our current BI vendor relationship.