Lead Product Manager, Templates & Hierarchy

What you'll do:

Nice to have:

• CMMS, EAM or industrial operations background
• Experience migrating customers off SAP PM or Maximo-class systems
• Our mission is to keep the physical world running. Factories, fleets, hospitals and campuses stay up because the people who maintain them have tools worth using. That is what we build.
• Compensation and benefits. Base pay is one part of the package. Depending on the role, compensation may also include commission, an annual bonus and equity. Benefits differ by country. For roles in the United States, Autodesk’s benefits are described at benefits.autodesk.com. For roles in Canada and other countries, the plan differs on health coverage, retirement and leave, and your recruiter will walk you through it.
• Belonging. We take pride in a culture where everyone can thrive. More at autodesk.com/company/global-belonging. More on where this is going: Autodesk CEO Andrew Anagnost on building the future of connected operations, and AOS SVP Stephen Hooper on welcoming MaintainX to Autodesk.

Qualifications

• 10+ years in product management, including 5+ years of platform or core-product work at an enterprise SaaS company — entity models, permissioning, configuration frameworks, the foundations other products are built on, not the features on top
• Deep systems thinking: you can hold a cascade/override policy or a hierarchy schema in your head, reason about cardinality and migration states, and argue the trade-offs with staff engineers as a peer
• A real discovery motion — you run design-partner sessions yourself and let evidence overrule opinion
• A track record sequencing multi-year foundational work while shipping customer-visible value every quarter

Responsibilities

• You'll own the Templating Service end to end, and as it matures, the redesign of the location and asset hierarchy underneath it.
• Own strategy, roadmap and execution for templates across assets, procedures, work orders and parts, taking the current design-partner alpha to GA adoption across multi-site enterprise accounts
• Consolidate three overlapping configuration systems into one registry, with a migration path and deprecation sequence that strands no customer mid-move
• Resolve the semantics this space is full of — update policies, publish and conflict flows, versioning, promoting existing records into templates — so teams building on top have settled rules
• Run the design-partner program yourself: recurring customer sessions and prototype-driven discovery, converted into roadmap
• Take the hierarchy redesign from spec to validated model — typed locations, N-level depth, functional positions that keep PM schedules alive through asset swaps — additive and non-breaking for customers on today's two-level structure
• 10+ years in product management, including 5+ years of platform or core-product work at an enterprise SaaS company — entity models, permissioning, configuration frameworks, the foundations other products are built on, not the features on top
• Deep systems thinking: you can hold a cascade/override policy or a hierarchy schema in your head, reason about cardinality and migration states, and argue the trade-offs with staff engineers as a peer
• A real discovery motion — you run design-partner sessions yourself and let evidence overrule opinion
• A track record sequencing multi-year foundational work while shipping customer-visible value every quarter