About the role
The Senior PM will own one or more product modules end-to-end for Hub and Depot Operations, Execution at Customer Stop, Returns and Reverse Logistics, Multi-Trip Shifts, or Workforce and Auth, from scoping with domain PMs, through workflow design with UX, to release readiness with the engineering pod and customer-onboarding teams. The role partners with the Principal PM on overall app vision and runs its modules independently.
Responsibilities:
- Own a slice of the mobile app: scope it, write the spec, drive design partnership, shepherd it through engineering, and land it in tenant rollouts.
- Author mobile workflow specs (Delivery / Pickup / Hub and Depot / Returns) and the matching epic + story tickets in Jira.
- Coordinate with domain PMs (Execution, Hub Ops, Workforce, Order Management) to translate entity specs and design decisions into driver-facing scenarios.
- Partner with UX on gap closure and with the mobile engineering pod on sequencing and delivery.
- Own one or more enterprise tenant rollouts, translating customer requirements into product changes vs. tenant config, and holding the line on what is product-grade vs. one-off.
- Uphold platform defaults: client-agnostic architecture, point-of-use permissions, plain-language UX, and no over-engineered enterprise theatre.
Requirements:
- 6+ years in product management, including 3+ years on enterprise SaaS or platform products. Mobile app PM experience is a strong plus.
- Shipped in domain-heavy, multi-team environments, comfortable reading entity specs, sequence diagrams, and engineering RFCs, not just user stories.
- Spec author. Can write a 3,000-word workflow doc that engineering, design, and customer success can all build from.
- Strong opinions about driver/operator UX have shipped for low-context, high-pressure mobile users (delivery, field service, frontline ops, warehousing).
- Jira-as-source-of-truth discipline: every scope decision is a ticket, every blocker is a link, and every spec gap is a child story.
- Bias toward plain language, concrete examples, and decision-by-tradeoff over decision-by-framework.
Nice to have:
- Logistics / last-mile / supply-chain domain background.
- Multi-tenant SaaS scoping experience (what's product vs. what's tenant config).
- Comfort with domain-driven teams (DDD, event sourcing, entity-first specs).