CPQ Program & Platform Manager, Watertown SD

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections with real content. No job title heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove application instructions (How To Apply). Also remove duplicated lines. Keep all substantive info. We need to parse the job description. Key sections: - Position: CPQ Program & Platform Manager Location: Watertown, SD (maybe we can include location in a paragraph under About the role? Not a heading.) - About the role: description of role purpose. - Responsibilities: list of primary responsibilities (multiple bullet points). The description includes "Primary Responsibilities" with subheadings: CPQ Relaunch Program Leadership, Business Process, Requirements, and Solution Governance, Testing, Change Management, and Adoption, Post-Launch Platform Leadership, Stakeholder, Executive, and Vendor Coordination. We can combine these as bullet points under Responsibilities, or we could create separate sections? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include if content present. We have content for About the role (role purpose). Responsibilities (primary responsibilities). Requirements (maybe "Required Qualifications"). Qualifications (maybe "Preferred Qualifications"). Skills (maybe "Leadership Competencies"). Benefits (the "Why Join Us" includes benefits). Pay (not mentioned). Schedule (not mentioned). So we omit Pay and Schedule. We must not include placeholder text like "commensurate with experience". Not present. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep details like bullet points. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus: - About the role: prose paragraph(s) summarizing role purpose. Could be multiple paragraphs but we can combine. - Responsibilities: list of duties. Could be bullet points under each subheading? But we can just list bullet points for each responsibility item. However we need to preserve all detail; we could keep subheadings as part of bullet text? The instruction: use

  for section headings; we already have Responsibilities heading. Under it we can have

  • each duty. The duty text can be long sentences. We need to extract duties from the "Primary Responsibilities" section. Let's list them: Under CPQ Relaunch Program Leadership: - Serve as the business program lead for the CPQ relaunch and maintain the authoritative integrated project plan across workstreams, milestones, resources, dependencies, decisions, and deliverables. - Translate approved scope and objectives into execution plans, governance cadence, success measures, stage gates, acceptance criteria, and escalation paths. - Lead cross-functional planning and execution across Commercial Operations, Sales, Engineering, Product Management, Pricing, Finance, Operations, Inside Sales, IT, Quality, and external implementation partners. - Own project controls, including schedule, RAID log, decision log, action register, budget visibility, resource constraints, vendor commitments, scope changes, value tracking, and executive status reporting. - Frame decisions for sponsors and steering teams by clarifying options, business impacts, risks, tradeoffs, recommendations, and accountable decision owners. - Orchestrate business and technical dependencies across Salesforce, Oracle CPQ, Oracle EBS, product data, pricing data, document outputs, integrations, and downstream processes. - Lead cutover planning, launch readiness, go-live governance, hypercare, stabilization, and transition to steady-state support. Business Process, Requirements, and Solution Governance: - Own the business architecture and design integrity for the future-state quote-to-order experience and ensure requirements support Pre-Configured, CTO, and ETO pathways. - Lead discovery workshops and translate commercial, engineering, operational, financial, and customer needs into prioritized capabilities, process maps, requirements, user stories, and measurable acceptance criteria. - Validate that proposed designs support governed product structures, configuration rules, bills of material, pricing logic, approvals, guided selling, quote documents, revisions, and change-order processes. - Challenge solution proposals that create unnecessary complexity, weak controls, poor user experience, excessive maintenance, or misalignment with commercial strategy. - Maintain traceability from business need through design, testing, deployment, and realized outcome; secure approval from designated business and process owners. Testing, Change Management, and Adoption: - Create the business testing strategy and lead UAT planning, scenario coverage, test execution, defect triage, retesting, acceptance, and go-live exit criteria. - Ensure test scenarios cover configuration accuracy, pricing, approvals, documents, integrations, revisions, change orders, user roles, exception handling, and downstream transactions. - Lead stakeholder readiness, impact assessment, communications, training coordination, super-user development, SOP creation, and adoption measurement. - Partner with business leaders to resolve process noncompliance, unclear ownership, data gaps, and adoption barriers that threaten benefits realization. - Monitor post-launch usage, support themes, defects, process performance, and user feedback to drive corrective actions. Post-Launch Platform Leadership: - Serve as the day-to-day business platform owner and Commercial Operations administration lead for the CPQ ecosystem after launch. - Develop, maintain, and execute the multi-year CPQ roadmap in alignment with commercial strategy, product portfolio priorities, pricing governance, customer experience, operating capacity, and Quote-to-Cash initiatives. - Own and govern demand intake, business cases, backlog management, prioritization recommendations, release planning, and communication of approved priorities and tradeoffs. - Facilitate governance for product, configuration, pricing, approval, document, integration, and workflow changes; prepare recommendations and route decisions to designated accountable owners. - Establish and maintain approved ownership, standards, and controls for product models, attributes, rules, bills of material, pricing inputs, approval policies, templates, roles, and reference data. - Coordinate incident, defect, enhancement, and release management with IT and external partners, including service expectations, root-cause follow-up, regression testing, and deployment readiness. - Monitor platform health, adoption, data quality, process compliance, support demand, and KPI performance; convert insights into corrective actions and roadmap priorities. - Maintain system and process documentation, decision history, governance standards, release notes, training content, and business continuity plans. Stakeholder, Executive, and Vendor Coordination: - Build alignment among senior leaders, functional owners, subject-matter experts, end users, IT teams, and external implementation partners. - Prepare concise steering committee and executive communications focused on required decisions, progress against outcomes, risks, financial or operational impacts, and recovery actions. - Facilitate difficult cross-functional decisions through fact-based recommendations, documented tradeoffs, clear decision ownership, and established governance. - Manage external partner coordination, including scope alignment, deliverable quality, issue resolution, change control, and readiness expectations. Now Required Qualifications (under "Required Qualifications"): - Bachelor’s degree in Business, Engineering, Information Systems, Operations, Project Management, Supply Chain, Finance, or a related field, or equivalent combination of education and directly relevant experience. - Five or more years of progressive experience leading cross-functional business transformation, enterprise-system implementation, commercial operations, business systems, product ownership, or project/program management. - Five or more years of experience with CPQ, CRM, ERP, product configuration, pricing, Quote-to-Cash, or comparable enterprise commercial platforms. - Demonstrated ownership of project plans, scope, risks, dependencies, decisions, stakeholder governance, testing, change management, and implementation partner deliverables. - Experience translating complex business processes into structured requirements, user stories, process designs, acceptance criteria, and prioritized roadmaps. - Sound understanding of configurable products, product structures, option rules, bills of material, pricing models, approvals, quote documents, and order-management dependencies. - Experience leading UAT, defect triage, launch readiness, deployment, hypercare, and continuous-improvement activities. - Strong business judgment, analytical problem-solving, facilitation, negotiation, written communication, executive presentation, and influence-without-authority skills. Preferred Qualifications: - Experience with Oracle CPQ, Oracle EBS, Salesforce CRM, or closely related platforms. - Experience in heavy equipment, industrial manufacturing, or another complex Configure-to-Order / Engineer-to-Order environment. - Formal project-management or product-ownership certification such as PMP, PMI-ACP, Certified Scrum Product Owner, or equivalent. - Experience with pricing governance, product lifecycle management, engineering change, order integration, analytics, and commercial data governance. - Experience managing a multi-phase implementation with third-party systems integrators and distributed cross-functional teams. Leadership Competencies (maybe Skills section): - Enterprise perspective, commercial judgment, executive presence, disciplined execution, decision quality, risk management, vendor accountability, customer-centered process design, change leadership, and continuous improvement. Why Join Us (Benefits): - We are a global company defined by our Values: Integrity, Respect, Improvement, Servant Leadership, Courage, and Citizenship. - Safety is an absolute way of life, and we expect all team members to prioritize safety and commit to Zero Harm. - We are committed to creating an inclusive environment where every team member feels safe, supported, and valued. - We make a positive impact through innovative solutions, engaged people, and sustainable operations. - We offer competitive salaries, health insurance, life insurance, disability coverage, leave options, paid time off, company holidays, 401k matching, employee stock purchase plan, legal assistance, wellness programs, tuition reimbursement, and discount programs. - This description is non-exhaustive, and additional duties may be assigned in accordance with the role. - If you are interested in an open position but feel you may not meet all the listed qualifications, we still encourage you to apply. (But that's more like application encouragement; maybe we can keep as part of Benefits? It's not a benefit but could be considered. However instruction: remove application instructions. This line is about encouraging to apply; maybe considered application instruction. Safer to remove it. Also "If you are interested in an open position but feel you may not meet all the listed qualifications, we still encourage you to apply." appears twice; we should remove. Also we need to remove duplicated lines. There's a duplicate of that encouragement line earlier in the description (near the end). We'll remove. Also remove "About Terex:" paragraph at the end (starting with "About Terex: Terex Corporation is a global leader...") That's boilerplate? It's company description; maybe considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description may not be explicitly listed but could be considered boilerplate? It's not EEO etc. Might be okay to keep? However it's not directly about the role; it's generic company info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive? It's about Terex. Might be considered boilerplate but not explicitly listed. Safer to keep? However the instruction says "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Company description is not those. So we can keep it. But it's after the "How To Apply" section. The "How To Apply" we need to remove. So we will remove the How To Apply lines and the equal opportunity employer lines. Thus final HTML:

    About the role

    Terex Utilities is seeking a CPQ Program & Platform Manager to lead execution of a business-critical Configure, Price, Quote relaunch and serve as the long-term business platform owner for the Watertown, SD team. This role executes Commercial Operations strategy and leadership direction into enterprise execution across business process design, product modeling, configuration logic, pricing, integrations, testing, deployment, adoption, stabilization, and continuous improvement. During implementation, this position serves as the full-time Commercial Operations execution