Principal Product Manager, PPL Technology

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve substantive info. We need to parse the posting. Key content: - Intro paragraph about PI-SD, role description: "People Insights & Solution Design (PI-SD) owns the technology portfolio for People & Places (PPL)..." etc. That's about the role. - Responsibilities: list bullet points after "Responsibilities". Those are many bullet points. - Requirements/Qualifications/Skills: The posting mentions "genuine learning agility, not just product experience", "look around corners", etc. Might be considered requirements. Also "Build new domain and technical fluency quickly". There's no explicit list of qualifications like years experience, but we can infer. We need to preserve all substantive info; we shouldn't invent. So we can include a section "Requirements" with bullet points derived from statements about needed traits: genuine learning agility, ability to surface risks, set direction with minimal oversight, pace limited by organization not judgment, etc. Also "Build new domain and technical fluency quickly". Also "Apply vendor capture test", "Use AI directly". Might be considered skills. But we must not create sections with filler like "commensurate with experience". We have actual content. Benefits: There's a Benefits section: "From health and financial benefits to time away and everyday wellness, we give Autodeskers the best, so they can do their best work. Learn more about our benefits in the U.S. by visiting https://benefits.autodesk.com/". That's substantive. Pay: There's Salary transparency: "Salary is one part of Autodesk’s competitive compensation package. For U.S.-based roles, we expect a starting base salary between $142,425 and $259,050. Offers are based on the candidate’s experience and geographic location, and may exceed this range. In addition to base salaries, our compensation package may include annual cash bonuses, commissions for sales roles, stock grants, and a comprehensive benefits package." That's substantive. Schedule: Not mentioned. No schedule info. So we should not include Schedule. Also there is "Learn More About Autodesk" etc which is boilerplate? It's descriptive about company; might be considered not required but could be considered part of About the role? It's more general company info. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Learn More About Autodesk" is not exactly boilerplate but could be considered generic marketing. Might be okay to keep as part of About the role? But we already have an About the role section from the earlier paragraphs. The "Learn More About Autodesk" could be considered extra but not required. However we need to preserve ALL substantive information; is that substantive? It's about company culture, maybe not directly about the role. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't say remove company overview. But to be safe, we could include it as part of About the role or maybe a separate section "About Autodesk". However the allowed headings are limited to those listed; we cannot add arbitrary headings. So we could incorporate that info into About the role section as prose. Similarly "In-Person Onboarding and Identity Verification" is a note; could be included maybe as a short p under About the role or maybe as a separate note but not a heading. We'll include as a short p. Now we need to output only HTML fragment, no /, no markdown fences. We'll structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Benefits

...

Pay

...

We need to ensure we don't include sections with filler. All have content. Now extract precise content. About the role: combine paragraphs before Responsibilities. Original text before "Responsibilities": "Job Requisition ID # 26WD100184 People Insights & Solution Design (PI-SD) owns the technology portfolio for People & Places (PPL), the HR and workplace organization supporting nearly 15,000 Autodesk employees worldwide. PI-SD builds the experience and intelligence layer above Workday and other systems of record, so the logic and insight generated by Autodesk's people and workplace data stay owned by Autodesk, not captured by vendors. Today, too much of that experience is fragmented across disconnected tools. We're moving PPL from that fragmented ecosystem to one seamless experience and intelligence layer, and we need Senior Product Managers to own that shift for an assigned domain, from problem definition through delivery, adoption, and ongoing optimization. You will work directly with engineering, experience design teams, PPL Centers of Excellence leaders, and senior leaders to translate ambiguous employee and business problems into product strategy, requirements and measurable outcomes for your domain customers. This role calls for genuine learning agility, not just product experience. The domains, tools, and skills it requires will keep shifting, especially as AI reshapes what a product team can own directly, and we need people who treat that as fuel, not friction. We're looking for product managers who look around corners: who surface risks and opportunities before they become executive escalations, who set direction and make significant calls with minimal oversight, and whose pace is limited by the organization, not by their own judgment or execution." We should exclude the Job Requisition ID line. So start after that. Thus About the role paragraph(s) will be the rest. We can combine into one

maybe multiple

but we can just put all in one

. Now Responsibilities: list bullet points after "Responsibilities". Let's extract them exactly. The text after "Responsibilities" (starting at "Own product strategy and roadmap..."): "Own product strategy and roadmap for an assigned PPL domain portfolio, for example Talent Acquisition, Talent Management, Compensation & Rewards, Employee Support & Services, Workplace & Travel Experience, or PI-SD's AI-enabled products, applying build versus buy principles and the six-dimension evaluation framework used across the PPL portfolio Own visibility across every tool, vendor, and contract in your domain, and drive renewal, divestment, and consolidation decisions backed by business cases through the quarterly PPL leadership technology review Translate ambiguous employee and business problems into clear product requirements, user stories, and acceptance criteria Own the experience and intelligence layer for your domain, keeping Workday and other systems of record as infrastructure while PPL owns the logic built on top of them Partner with ESE engineering teams daily through build and delivery, acting as the accountable product voice from requirements through launch Apply the vendor capture test to every AI capability in your domain: is it trained on data Autodesk owns and controls, or does it represent vendor capture of Autodesk's logic? Use AI directly in your own research, analysis, prioritization, and execution Build trust and alignment across technical and business stakeholders, and drive decisions without relying on direct authority Drive adoption of what you build, including bringing stakeholders who previously owned their own tech decisions through the transition to a centralized model with trust intact Define and own the KPIs for your domain, connecting product-level metrics to the broader PPL talent strategy, and build the dashboards and leading indicators that make performance visible before problems compound Identify portfolio risks, redundancies, and opportunities early, and bring recommendations, not open questions, to leadership before they surface as escalations Build new domain and technical fluency quickly as the portfolio and tools evolve, rather than waiting for structured training" We need each as

. Now Requirements: we need to extract statements about what they look for. From the About the role we have: "This role calls for genuine learning agility, not just product experience." "The domains, tools, and skills it requires will keep shifting, especially as AI reshapes what a product team can own directly, and we need people who treat that as fuel, not friction." "We're looking for product managers who look around corners: who surface risks and opportunities before they become executive escalations, who set direction and make significant calls with minimal oversight, and whose pace is limited by the organization, not by their own judgment or execution." Also from Responsibilities we have "Build new domain and technical fluency quickly as the portfolio and tools evolve, rather than waiting for structured training" which could be a requirement. Also "Apply the vendor capture test to every AI capability in your domain: is it trained on data Autodesk owns and controls, or does it represent vendor capture of Autodesk's logic? Use AI directly in your own research, analysis, prioritization, and execution" could be skill. Thus we can create Requirements bullet list: - Genuine learning agility (not just product experience) - Ability to treat shifting domains, tools, and skills (especially AI-driven changes) as fuel, not friction - Skill in looking around corners: surfacing risks and opportunities before they become executive escalations - Setting direction and making significant calls with minimal oversight - Pace limited by organizational constraints, not personal judgment or execution - Ability to build new domain and technical fluency quickly as the portfolio and tools evolve - Capability to apply the vendor capture test to AI capabilities and use AI directly in research, analysis, prioritization, and execution We should avoid inventing; these are derived from text. Now Benefits: we have paragraph: "From health and financial benefits to time away and everyday wellness, we give Autodeskers the best, so they can do their best work. Learn more about our benefits in the U.S. by visiting https://benefits.autodesk.com/" We'll put that in

. Pay: we have paragraph: "Salary is one part of Autodesk’s competitive compensation package. For U.S.-based roles, we expect a starting base salary between $142,425 and $259,050. Offers are based on the candidate’s experience and geographic location, and may exceed this range. In addition to base salaries, our compensation package may include annual cash bonuses, commissions for sales roles, stock grants, and a comprehensive benefits package." We'll put that in

. Now also there is "In-Person Onboarding and Identity Verification This role may require in-person onboarding and/or in-person ID verification." Could be included as a short p under About the role or maybe as a separate note but not a heading. We'll add after About the role maybe as a separate

but still under About the role? Could be its own

after the about role paragraph. We'll include it as a separate

after the about role paragraph but still within the About the role section? Since we cannot add extra headings, we can just add another

after the first

within the same section. That's fine. Now ensure we don't include any boilerplate like EEO, etc. We removed those. Now output HTML. Let's craft. We'll start with

About the role

People Insights & Solution Design (PI-SD) owns the technology portfolio for People & Places (PPL), the HR and workplace organization supporting nearly 15,000 Autodesk employees worldwide. PI-SD builds the experience and intelligence layer above Workday and other systems of record, so the logic and insight generated by Autodesk's people and workplace data stay owned by Autodesk, not captured by vendors. Today, too much of that experience is fragmented across disconnected tools. We're moving PPL from that fragmented ecosystem to one seamless experience and intelligence layer, and we need Senior Product Managers to