Lead Tech Project Mgr

We need to output HTML fragment with sections: About the role? Actually we have Department Description, Team Description, What You’ll Do, Required Qualifications & Skills, Preferred Qualifications, Required Education, Pay info (hiring range). Also maybe Benefits? Not explicit benefits beyond mention of bonus and long-term incentive units and medical etc. The posting says: "A bonus and/or long-term incentive units may be provided as part of the compensation package, in addition to the full range of medical, financial, and/or other benefits, dependent on the level and position offered." That's generic; we should not create Benefits section unless specific content. It's vague; better not create Benefits section. Pay section: we have hiring range. So we can create a Pay section with that info. Schedule not mentioned, so omit. We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections with real content. Use appropriate headings: maybe "About the role" for Department Description + Team Description? Could combine. Or we could have "About the team" etc. But instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We have: - Department Description: could be "About the role" or maybe "About the team". But we can use "About the role" to describe the role and context. - Team Description: maybe also part of About the role. - What You’ll Do: Responsibilities. - Required Qualifications & Skills: Requirements/Qualifications/Skills. Could split: Requirements (maybe required qualifications) and Skills (maybe required skills). But we can combine into one section "Requirements" or "Qualifications". Since they said use headings like Requirements, Qualifications, Skills. We need to decide. We have Required Qualifications & Skills (list). Then Preferred Qualifications (list). Then Required Education. We could have:

About the role

with department + team description.

Responsibilities

with What You’ll Do.

Requirements

with Required Qualifications & Skills (maybe split into required qualifications and skills). Could also have

Qualifications

for Required Qualifications & Skills and

Skills

for same? Might be redundant. Better to follow instruction: use headings for sections that exist. We can have: - About the role - Responsibilities - Requirements (covers required qualifications) - Preferred Qualifications (maybe as a separate heading? Not in list but we can still use

Preferred Qualifications

though not in examples; but they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't forbid other headings, but they said use

for section headings (e.g. those). Likely we should stick to those examples; but we can also add other headings if needed. Safer to stick to those. So we need to map content to those headings. We have Required Qualifications & Skills -> could go under Requirements and Skills. Could split: Requirements (experience, education, etc.) and Skills (specific skills). But we have both qualifications and skills mixed. Could put all under Requirements. Preferred Qualifications: could go under Qualifications? Actually Qualifications heading could cover both required and preferred? But we need to avoid filler. Maybe we create a section "Qualifications" for required qualifications, and another "Skills" for required skills? But we don't have separate. Alternative: Use "Requirements" for required qualifications & skills, and "Preferred Qualifications" as a separate heading (though not in examples). The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive. So we can add other headings like Preferred Qualifications. That seems fine. Thus sections: - About the role (Department Description + Team Description) - Responsibilities (What You’ll Do) - Requirements (Required Qualifications & Skills) - Preferred Qualifications (Preferred Qualifications) - Education (Required Education) maybe under Requirements? Could be its own heading "Education" but not in examples. Could put under Requirements. But we have separate line "Required Education". Could include under Requirements as a bullet. - Pay (hiring range) We should not include Benefits as it's vague. Now we need to output HTML fragment only, no markdown. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need
  • . For required qualifications list, also
    • . For preferred qualifications list, also
      • . For education maybe just a

        . We need to preserve all substantive information, not invent or summarize away detail. So we need to keep all bullet points exactly as given. Let's extract content. Department Description: "At Disney Experiences Technology, we design and deliver more than 400 digital and physical products that bring Disney stories to life in unexpected ways. From theme parks and resorts to cruise ships and beyond, our global team of technologists, designers, and innovators creates seamless, immersive experiences that delight millions of Guests and Cast Members around the world." Team Description: "We are seeking a detail-oriented and proactive Lead Technical Project Manager to oversee and drive complex cross-functional technical initiatives from initiation through delivery. In this role, you will work closely with engineering, product, design, and business stakeholders to ensure projects are delivered on time, within scope, and aligned with technical and business goals. You will apply project management principles, practices, and techniques to lead and control project schedule, scope, quality, cost and performance risks independently, for multiple complex technology projects. You will also provide leadership to other project managers and ensure the successful delivery of high-impact technical programs aligned with business objectives." We can combine into About the role section. Responsibilities (What You’ll Do): List: - Plan, manage, and execute multiple technical projects and programs across teams throughout the full project lifecycle. - Collaborate with engineering teams to translate technical requirements into project plans - Define project scope, goals, timelines, milestones, and deliverables - Track progress, manage dependencies, and mitigate risks and issues and serve as the primary escalation point for project risks, issues, and dependencies - Partner with engineering, product, architecture, and business leaders to define technical roadmaps and delivery plans - Facilitate project meetings, stand-ups, retrospectives, and stakeholder updates - Coordinate communication between technical and non-technical stakeholders - Manage project documentation, schedules, and status reports - Ensure adherence to Agile, Scrum, or Waterfall methodologies as appropriate - Mentor and guide Technical Project Managers and project teams - Drive alignment across stakeholders and ensure clear communication at all levels - Own project planning, execution, and delivery for complex, high-visibility initiatives - Manage budgets, resources, timelines, and delivery metrics - Facilitate executive-level status reporting and decision-making - Ensure projects adhere to Agile, Scrum, or hybrid delivery methodologies - Demonstrated ability to drive complex forecasts & capacity plans and to effectively communicate risks and dependencies to leaders and business partners. Note: The last bullet seems like a qualification but it's under What You’ll Do; we keep it. Required Qualifications & Skills: List: - 7+ years of project management experience, including leading technical projects - Proven experience managing large-scale, cross-functional technical initiatives - Strong understanding of software development lifecycles (SDLC) - Technical background in software development, infrastructure, or systems architecture - Experience working with engineering and technical teams - Proficiency with project management tools (e.g., Jira, Confluence, Clarity) - Strong organizational, communication, and leadership skills - Demonstrated ability to lead and influence without direct authority - Excellent communication, leadership, and problem-solving skills Preferred Qualifications: List: - Experience in a Lead or Program Management role - Technical background in data and analytics, and tools like Snowflake, Java, and Cortex - Experience managing AI-based projects - PMP, PgMP, CSM, SAFe, or similar certifications - Experience working in Agile/Scrum and hybrid environments - Experience managing globally distributed cross-functional teams Required Education: - Bachelor’s degree in computer science, Information Technology, or a related field. Pay info: "The hiring range for this position in Orlando, FL is $148,300 - $190,800 per year. The base pay actually offered will take into account internal equity and also may vary depending on the candidate’s geographic region, job-related knowledge, skills, and experience among other factors. A bonus and/or long-term incentive units may be provided as part of the compensation package, in addition to the full range of medical, financial, and/or other benefits, dependent on the level and position offered." We need to include Pay section with that info. Should we include the whole paragraph? Yes, preserve all substantive information. However we should avoid boilerplate like "The base pay actually offered will take into account internal equity..." that's still substantive. Keep it. We should not include Benefits section because it's vague; but the pay paragraph mentions bonus and long-term incentive units and medical etc. That's still part of compensation. Could we create a Benefits section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state bonus and long-term incentive units and medical etc. So we could create a Benefits section for those? But they said Pay/Schedule/Benefits sections only if posting actually states them. The posting does state compensation package includes bonus and/or long-term incentive units, plus medical, financial, other benefits. So we could create a Benefits section with that detail. However the Pay section already includes base pay range. The benefits info is also in same paragraph. Could we split: Pay section for base pay range, Benefits section for bonus etc. That seems appropriate. Thus:

        Pay

        The hiring range for this position in Orlando, FL is $148,300 - $190,800 per year. The base pay actually offered will take into account internal equity and also may vary depending on the candidate’s geographic region, job-related knowledge, skills, and experience among other factors.

        Benefits

        A bonus and/or long-term incentive units may be provided as part of the compensation package, in addition to the full range of medical, financial, and/or other benefits, dependent on the level and position offered.

        We should not create Schedule section. Now we need to output only HTML fragment. Let's craft. We'll start with

        About the role

        ... combine department and team description into one paragraph? Could be two paragraphs. Use

        for prose. We'll put both sentences in one

        maybe separated by space. Then Responsibilities:

        Responsibilities

        • ... each bullet. Then Requirements:

          Requirements

          • ... required qualifications list. Then Preferred Qualifications:

            Preferred Qualifications

            • ... list. Then Education: Could be under Requirements but we have separate. Could make

              Education

              Bachelor’s degree in computer science, Information Technology, or a related field.

              Then Pay: as above. Then Benefits: as above. Check that we didn't miss any substantive info: The bullet about "Demonstrated ability to drive complex forecasts & capacity plans and to effectively communicate risks and dependencies to leaders and business partners." was under What You’ll Do; we included it as a responsibility bullet. Check that we didn't duplicate any lines. Now ensure we didn't include any boilerplate like EEO etc. Not present. Now output.