Sr. Project Manager, IT

We need to output HTML fragment with sections: About the role (already present), Responsibilities (What You'll Do), Requirements (Required Qualifications), Preferred Qualifications maybe as Skills? Actually we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We have About the role content. Responsibilities: "What You'll Do" includes bullet points. Requirements: "Required Qualifications" includes bullet points. Preferred Qualifications: maybe treat as Skills? Could be "Preferred Qualifications" as Skills section. Benefits: "Why Join TD SYNNEX?" and "What's In It For You?" includes benefits. Pay: Salary Range Requirement includes salary range. Schedule: none. So we will not include Schedule. We must not repeat job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement at end; we should remove that. Also remove "Don't meet every single requirement? Apply anyway." etc. Also remove "We are an equal opportunity employer..." etc. Also remove "At Shyft Global Services..." repeated? We'll keep some parts that are substantive: "Why Join TD SYNNEX?" and "What's In It For You?" but need to strip application encouragement and EEO. We need to keep the content about benefits: "Elective Benefits: Our programs are tailored to your country to best accommodate your lifestyle." etc. Also "Grow Your Career:", "Elevate Your Personal Well-Being:", "Diversity, Equity & Inclusion:", "Make the Most of our Global Organization:", "Connect with Your Community:". We need to keep Salary Range Requirement paragraph. We need to keep "About The Role" paragraph. We need to keep "What You'll Do" bullet points. We need to keep "Required Qualifications" bullet points. We need to keep "Preferred Qualifications" bullet points. We need to keep "Success Traits We're Looking For" maybe as Skills? Actually that could be under Skills or Qualifications. The instruction says we can have Skills section. We could put Success Traits under Skills. But we already have Preferred Qualifications; maybe we treat Success Traits as Skills. However we need to avoid thin sections. Could combine Preferred Qualifications and Success Traits into a Skills section? But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have About the role (done). Responsibilities (What You'll Do). Requirements (Required Qualifications). Qualifications (maybe Preferred Qualifications?). Skills (Success Traits). Benefits (Why Join TD SYNNEX? + What's In It For You?). Pay (Salary Range Requirement). Schedule omitted. We must not create empty sections. So we need to ensure each heading has content. Let's extract content. About The Role paragraph: "TD SYNNEX is seeking a highly experienced Senior Project Manager, IT to lead large-scale, strategic technology initiatives that drive business transformation and operational excellence. In this role, you will serve as the central leader responsible for planning, coordinating, and delivering complex cross-functional projects with significant organizational impact. As a trusted partner to executive stakeholders, business leaders, and technical teams, you will guide projects from initiation through execution, ensuring alignment with business objectives, timelines, budgets, and expected outcomes. This position is ideal for a strategic thinker who thrives in dynamic environments, enjoys influencing without direct authority, and is passionate about delivering measurable results. With project portfolios typically exceeding $2 million in budget or financial impact, this role offers the opportunity to make a visible contribution to enterprise-wide initiatives while advancing your leadership and project management expertise." That's prose. Responsibilities: Under "What You'll Do" there are subheadings: Project Leadership & Delivery, Stakeholder & Executive Engagement, Change Management & Business Impact, Team Collaboration. Each has bullet points. We need to output a list (

  • ) for duties. We could combine all bullet points into a single list, or separate lists per subheading? The instruction: use
    • for any list of duties/requirements/benefits. It doesn't forbid multiple lists. We'll likely create a
      with
      • items for each bullet point. We'll keep the subheadings maybe as

        or ? Not required. We could keep subheadings as

        ...

        then list. But we must not invent headings; we can keep them as prose. Simpler: after

        Responsibilities

        , we can put a

        describing that responsibilities include... then a

        with each bullet. Let's extract bullet points: Project Leadership & Delivery: - Lead large, complex, and strategic IT projects from planning through successful implementation. - Define project objectives, scope, success metrics, deliverables, timelines, and resource requirements. - Develop and maintain detailed project plans, including milestones, dependencies, risk mitigation strategies, and budget tracking. - Monitor project progress and proactively address issues, risks, and roadblocks to ensure successful outcomes. Stakeholder & Executive Engagement: - Serve as the primary point of contact for project-related communications. - Establish and facilitate project governance, steering committees, and executive status reviews. - Build strong relationships across business and technology teams to drive collaboration and alignment. - Communicate project updates, risks, dependencies, and achievements to stakeholders at all levels of the organization. Change Management & Business Impact: - Lead communication, training, and organizational change management activities that support project adoption and success. - Partner with subject matter experts to ensure technical requirements are accurately captured and executed. - Drive business outcomes by ensuring projects deliver measurable value and align with strategic objectives. Team Collaboration: - Foster a high-performing and collaborative project environment. - Coordinate cross-functional teams and influence stakeholders to achieve shared goals. - Promote accountability, transparency, and continuous improvement throughout the project lifecycle. We'll list each as
        • . Requirements: Under "Required Qualifications" bullet points: - Bachelor's degree in Computer Science, Information Technology, Business, or a related field. - Minimum of 7 years of project management experience leading large-scale, transformational, and cross-functional initiatives. - Proven success managing projects with significant budgets, financial impact, and enterprise-level visibility. - Experience managing stakeholders across multiple departments, including senior leadership and executive teams. - Strong knowledge of project management methodologies, tools, and best practices. - Advanced proficiency with project management software such as Microsoft Project and related planning tools. - Experience with budget management, financial forecasting, and ROI analysis. - Excellent communication, presentation, facilitation, and relationship-building skills. Preferred Qualifications bullet points: - PMP certification or equivalent project management certification. - Experience in IT transformation, digital transformation, or enterprise technology initiatives. - Experience with Lean, Six Sigma, Agile, or continuous improvement methodologies. - Leadership experience in matrixed or global environments. Success Traits bullet points: - Professionals Who Think strategically while managing day-to-day execution. - Adapt quickly in fast-paced and evolving environments. - Solve problems with confidence and sound judgment. - Build trust and influence across diverse teams. - Balance competing priorities while maintaining attention to detail. - Demonstrate integrity, professionalism, and accountability in every interaction. We need to map these to sections: Qualifications (maybe Preferred Qualifications) and Skills (Success Traits). Let's decide:

          Qualifications

          will contain Preferred Qualifications list.

          Skills

          will contain Success Traits list. But we also have Required Qualifications under Requirements. Now Benefits: Under "Why Join TD SYNNEX?" and "What's In It For You?" we need to extract benefits points. "Why Join TD SYNNEX?" paragraph: "At TD SYNNEX, we believe our people drive our success. You'll join a collaborative, inclusive, and innovation-focused environment where your ideas and leadership can make a meaningful impact. We Are Committed To Supporting Professional Growth Through Challenging, high-visibility projectsOpportunities to collaborate with senior leadersCareer development and continuous learningA culture built on teamwork, accountability, and innovationFlexible and inclusive work practices that empower diverse perspectives" It seems missing spaces but we can keep as is. Then bullet list under "What's In It For You?": - Elective Benefits: Our programs are tailored to your country to best accommodate your lifestyle. - Grow Your Career: Accelerate your path to success (and keep up with the future) with formal programs on leadership and professional development, and many more on-demand courses. - Elevate Your Personal Well-Being: Boost your financial, physical, and mental well-being through seminars, events, and our global Life Empowerment Assistance Program. - Diversity, Equity & Inclusion: It's not just a phrase to us; valuing every voice is how we succeed. Join us in celebrating our global diversity through inclusive education, meaningful peer-to-peer conversations, and equitable growth and development opportunities. - Make the Most of our Global Organization: Network with other new co-workers within your first 30 days through our onboarding program. - Connect with Your Community: Participate in internal, peer-led inclusive communities and activities, including business resource groups, local volunteering events, and more environmental and social initiatives. We need to output these as
          • . Pay: Salary Range Requirement paragraph: "Actual annual compensation offered for this exempt role will be a minimum annual salary of $105,000 based on several variables including length and depth of work experience, education, and skills/achievements, and will be mutually agreed upon at the time of offer." We need to output as

            . Now we must remove boilerplate: EEO statement, "Don't meet every single requirement? Apply anyway.", "We are an equal opportunity employer..." etc. Also remove "At Shyft Global Services, a TD SYNNEX Company, our values guide everything we do: Together, We Own It, We Dare to Go, We Grow and Win, and above all, We Do the Right Thing." That's also boilerplate? It's values statement; maybe considered substantive? It's not a benefit but could be considered part of culture. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The values statement might be considered boilerplate but not explicitly listed. However it's somewhat generic; but it's part of the posting. I'd keep it? Might be considered fluff. Safer to remove? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Values statement not those. Could keep. But we already have Benefits section covering culture; maybe we can keep values as part of Benefits? However we already have Benefits list; we could add a paragraph about values. But to keep it simple, we could omit values statement as it's not explicitly requested. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The values statement is substantive? It's describing company values. Might be considered substantive. But we already have Benefits section that includes culture aspects. I'd keep it as a

            under Benefits maybe. However we must not create thin sections; we already have Benefits with list; adding a paragraph is fine. But we need to decide: keep or remove? I'd keep it as a brief paragraph after the list. Now we need to output only HTML fragment, no /, no markdown. Let's structure:

            About the role

            ...

            Responsibilities

            What You'll Do:

            • ...
            ...
            But we might not need the "What You'll Do:" line; we can just start list. Better:

            Responsibilities

            ...
            with each bullet. But we need to preserve the subheadings? Could