Director of Operational Transformation

We need to output HTML fragment with sections: About the role? The posting includes "Job Description" then description. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes responsibilities (Key Responsibilities with subpoints). Qualifications (Required, Preferred). Education & Experience. No explicit Benefits, Pay, Schedule. So we should not include those sections. Also we need About the role? The initial paragraph could be considered About the role. We'll create

About the role

with paragraph(s) summarizing the description (but must preserve all substantive info, not invent or summarize away detail). We cannot summarize away detail; we need to preserve all substantive information. However we can keep the original prose as paragraphs. The instruction: "Use

for prose." So we can put the description paragraphs as

. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO statement (Company Statement about equal employment). That's boilerplate; we should remove it. Also remove navigation etc. There's none. We need to preserve all substantive information: responsibilities list, qualifications required, preferred, education & experience. We'll format responsibilities as

• . The responsibilities have sub-bullets; we can keep them as list items. Possibly nested lists? The instruction says use
  • for any list of duties/requirements/benefits. It doesn't forbid nesting but we can keep flat list with each bullet as a line. However there are many bullet points; we can keep them as separate
  • . For sub-bullets under each main bullet, we could keep them as part of the same
  • text (including semicolons). That's okay. Similarly qualifications required and preferred: we can make two sections? The heading "Qualifications" could cover both required and preferred. Could also split into Required and Preferred subheadings but not required. We'll just have

    Qualifications

    and then

    for required? But we need to use

    • for any list of duties/requirements/benefits. Qualifications is a list of requirements, so we should use
      • . We'll separate required and preferred maybe as two
        with headings

        or . But we cannot create extra headings not specified; but we can use

        to label. Probably acceptable:

        Required:

        then
        • ... etc. Similarly for Preferred. Education & Experience: could be a section? Not among the prescribed headings but we could treat as part of Qualifications or separate. The instruction: "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could add Education & Experience as a heading if we want, but better to keep under Qualifications. However the content is substantive; we could include as

          Education & Experience

          but not in the list; but it's okay as it's a section heading. The instruction says use

          for section headings (e.g. ...). It doesn't forbid other headings, but to be safe we could incorporate into Qualifications. We must not include Pay/Benefits/Schedule sections because not present. We must remove boilerplate: the Company Statement about equal employment. Remove that. Now craft HTML. Start with

          About the role

          then a

          containing the initial paragraph(s) from Job Description: "The Director of Operational Transformation will lead the discovery, design, development, piloting, and adoption of technology-enabled process improvements across PSS Cross Country internal operations and selected customer-facing workflows. The role will serve as a bridge between business operations and technology, translating real-world processes into requirements for the Project Health Intelligence platform and other digital solutions. The position is expected to influence process design, operating practices, organizational interfaces, decision rights, metrics, and workflows when opportunities for improvement are identified. The role is not the accountable owner of the underlying business functions, organizational structures, staffing decisions, or operational results; those responsibilities remain with the appropriate functional leaders." Then

          Responsibilities

          then
          with each bullet. We need to capture all bullet points under Key Responsibilities: - Process Discovery, Design & Continuous Improvement - Develop a detailed understanding... - Document current-state processes... - Identify bottlenecks... - Develop future-state process recommendations... - Define the events, states, measures... - Establish repeatable methods... - Platform Requirements & Business-Technology Translation - Translate operational processes into clear business... - Develop and maintain process maps... - Serve as a primary liaison... - Translate operational concepts... - Help define what the platform must know... - Review designs and prototypes... - Platform Development, Piloting & Validation - Participate throughout the Project Health Intelligence platform lifecycle... - Help define how processes are represented within the platform... - Identify appropriate internal and external processes for pilot implementation... - Lead business-side testing and validation... - Identify defects... - Compare expected outcomes... - Adoption, Change Leadership & Cross-Functional Influence - Lead business adoption... - Work with functional leaders... - Develop training... - Monitor adoption... - Facilitate cross-functional discussions... - Use data and process evidence... - Support expansion... We'll make each top-level bullet as
          • containing the sub-bullets as separate sentences or maybe
            • inside? But instruction says use
              • for any list of duties/requirements/benefits. It doesn't forbid nested lists. Safer to keep flat list: each bullet as a separate
              • with the sub-points separated by semicolons. However that may lose structure but still preserve all info. Could also do nested
                inside
                • . That still uses
                  • for list items. I'd do nested to keep readability. Thus:

                    Responsibilities

                    • Process Discovery, Design & Continuous Improvement
                      • Develop a detailed understanding of assigned business and operational processes through direct observation, interviews, workshops, data analysis, and engagement with frontline employees and leaders.
                      • Document current-state processes, including workflows, handoffs, systems, data sources, constraints, exceptions, responsibilities, and decision points.
                      • Identify bottlenecks, rework, delays, capacity constraints, information gaps, control weaknesses, and other sources of process inefficiency.
                      • Develop future-state process recommendations where changes could improve visibility, consistency, decision-making, or overall process effectiveness.
                      • Define the events, states, measures, relationships, and leading indicators required to monitor process effectiveness and forecast future outcomes.
                      • Establish repeatable methods for evaluating, documenting, and improving additional internal or customer-facing processes over time.
                    • Platform Requirements & Business-Technology Translation
                      • Translate operational processes into clear business, functional, data, workflow, analytical, and user-experience requirements for technical teams.
                      • Develop and maintain process maps, business rules, use cases, user stories, data requirements, acceptance criteria, and exception scenarios.
                      • Serve as a primary liaison between business stakeholders and software development, data, AI, analytics, architecture, and IT teams.
                      • Translate operational concepts into requirements technical teams can implement and translate technical limitations or design alternatives into practical business terms.
                      • Help define what the platform must know to determine current state, identify emerging process risk, forecast future outcomes, simulate alternatives, and support recommended actions.
                      • Review designs and prototypes to ensure solutions accurately represent operational reality and business needs.
                    • Platform Development, Piloting & Validation
                      • Participate throughout the Project Health Intelligence platform lifecycle, from discovery and requirements through design, development, testing, deployment, and continuous improvement.
                      • Help define how processes are represented within the platform, including objects, events, states, relationships, measures, thresholds, business rules, and decision logic.
                      • Identify appropriate internal and external processes for pilot implementation and define pilot scope, success measures, test cases, baseline conditions, and acceptance criteria.
                      • Lead business-side testing and validation of platform outputs against actual operating conditions.
                      • Identify defects, incorrect assumptions, process gaps, and usability issues and work with technical teams to refine the solution.
                      • Compare expected outcomes with actual results and incorporate lessons learned into future platform and process improvements.
                    • Adoption, Change Leadership & Cross-Functional Influence
                      • Lead business adoption of new platform capabilities and related process improvements.
                      • Work with functional leaders to integrate new capabilities into existing management routines, workflows, and operating practices.
                      • Develop training, user guidance, standard work, and supporting documentation as needed.
                      • Monitor adoption and identify behavioral, organizational, process, or technical barriers to sustained use.
                      • Facilitate cross-functional discussions when improved outcomes may require changes to workflow, responsibilities, decision rights, handoffs, metrics, staffing models, or system usage.
                      • Use data and process evidence to influence functional leaders and stakeholders while respecting their ownership and accountability for the underlying operation.
                      • Support expansion of successful approaches across additional PSS Cross Country functions and approved customer-facing use cases.
                    Now Qualifications section. We have Required and Preferred bullet lists. We'll do:

                    Qualifications

                    Required:

                    • Significant experience managing, improving, or analyzing complex operational or business processes.
                    • Demonstrated ability to quickly learn unfamiliar processes and understand how work is actually performed.
                    • Strong process-mapping, workflow-analysis, analytical, and problem-solving skills.
                    • Experience working cross-functionally with operating leaders, frontline employees, and technical teams.
                    • Ability to translate business processes into clear requirements for technology teams.
                    • Strong written and verbal communication skills.
                    • Demonstrated ability to influence change without direct ownership of the affected organization or process.
                    • Experience leading pilots, implementations, process changes, or technology-enabled transformation initiatives.
                    • Ability to operate effectively in ambiguous environments and create structure where requirements are not clearly defined.

                    Preferred:

                    • Experience with continuous improvement, Lean, Six Sigma, value-stream mapping, operational excellence, or similar methodologies.
                    • Experience participating in software, digital-platform, ERP, workflow, or enterprise-system implementations.
                    • Experience developing business or functional requirements for developers.
                    • Familiarity with analytics, AI, process mining, forecasting, optimization, simulation, digital twins, or related technologies.
                    • Experience establishing KPIs, operational metrics, leading indicators, and business-performance measures.
                    • Experience working across multiple operating functions, business units, customers, or industries.
                    Education & Experience: Could be part of Qualifications but we have separate paragraph. We'll add another

                    maybe under