Walt Disney World Costuming Project Analyst Intern, Spring 2027

We need to output HTML fragment with sections: About the role (maybe "About The Role & Program" but we need heading

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to preserve all substantive info, remove boilerplate. We need to parse the posting. Sections: - About The Role & Program: includes description of company, internship details (full-time, location, dates). This is about the role. - What You Will Do: responsibilities. - Required Qualifications & Skills: includes required qualifications (list) and maybe also skills. - Preferred Qualifications: maybe part of qualifications. - Education: maybe part of qualifications. - Eligibility Requirements & Program Information: eligibility. - Additional Information: includes schedule, housing, transportation, etc. Also pay rate and benefits. We need to decide which sections to output based on actual content. We must not repeat job title as heading. We must not include Job ID etc. We must not include cookie/navigation/legal/EEO etc. The posting includes "Recommendation – Print This Role Description:" and note about printing, also "Select benefits may be provided..." etc. Those are substantive? The note about printing is maybe not essential but it's part of posting; but we can consider it boilerplate? It's not legal/EEO but it's a recommendation. Might be considered filler? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Recommendation – Print This Role Description:" is not exactly those but could be considered application instruction? It's encouraging to print for interview. Might be considered application instruction. Safer to omit. Also "Note that this role description will not be accessible once the posting is closed." That's also maybe not needed. We need to include Pay and Benefits sections if posting actually states them. Pay: "The pay rate for this role in Florida is $32.00 per hour." That's specific, so we need a Pay section. Benefits: "Select benefits may be provided as part of the compensation package, such as medical, financial, and/or other benefits, dependent on the level and position offered. To learn more about our benefits visit: https://jobs.disneycareers.com/benefits". That's substantive, so Benefits section. Schedule: The posting mentions "Able to have a consistent, reliable work schedule throughout the internship", "Fully available from Monday – Friday and occasional evenings and/or weekends depending on project needs". That's schedule info, so we can include Schedule section. We also have location and dates: "This internship is a full-time commitment located in the Orlando, FL area from January 2027– June 2027". That's part of About the role. We also have eligibility requirements: list. We also have education: "Junior or Senior year preferred...". We also have required qualifications & skills list. We also have preferred qualifications. We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine some: For example, "Qualifications" could include Required Qualifications & Skills, Preferred Qualifications, Education, Eligibility Requirements. But we need to follow instruction: Prefer a few substantive sections over many thin ones. So we could combine into sections: About the role, Responsibilities, Qualifications (including required, preferred, education, eligibility), Benefits, Pay, Schedule. But we must use headings exactly as listed? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings if we have content. It doesn't say we must use all; we should include a section only when posting has real, specific content for it. So we can choose which of those headings to use. We need to avoid thin sections. So maybe we combine Requirements and Qualifications into one "Qualifications" section. Skills could be part of Qualifications. But we have a separate "Skills" heading example; we could still use Skills if we have content. But we already have skills in required qualifications list. Could make a Skills section listing those skills. However that might be thin if we split. Better: Use sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Within Qualifications we can have sub-lists: Required Qualifications, Preferred Qualifications, Education, Eligibility Requirements. We need to use

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

  for prose. Thus: - About the role: prose paragraph(s) summarizing role description. - Responsibilities:

  • for each duty from "What You Will Do". - Qualifications: we can have multiple
    • lists under headings? But we cannot add extra headings besides

      . However we can still have

      for prose and

      • for lists. We could have a

        introducing then separate

        for each category with maybe a or something? But we cannot add extra headings; but we can still separate lists with

        headings? The instruction only says use

        for section headings; it doesn't forbid using other headings like

        or . But to be safe, we can just have one

        for all qualifications items, mixing required, preferred, education, eligibility. But that may lose distinction. However we must preserve ALL substantive information; not lose distinction but we can still convey via text within each
        • . Eg: "Required: Strong written and verbal communication skills". That's okay. Thus Qualifications section: a
          with each qualification as
          • . We'll include required, preferred, education, eligibility items. - Benefits:
            • for benefits: medical, financial, other benefits; also link to benefits page. - Pay:

              stating pay rate. - Schedule:

              or

              ? Schedule info: "Able to have a consistent, reliable work schedule throughout the internship", "Fully available from Monday – Friday and occasional evenings and/or weekends depending on project needs". Could be two
              • items. We also need to include location/dates maybe in About the role. Let's extract content. About the role & program: "The Walt Disney Company is the global leader in high-quality entertainment and innovative technology. Begin a career that delivers unparalleled creative content and experiences to audiences around the world! As a Costuming Project Analyst intern, you will handle project assignments autonomously to identify, develop, and analyze improvement opportunities that will increase efficiency in the Costuming organization! This internship is a full-time commitment located in the Orlando, FL area from January 2027– June 2027" We can make two paragraphs: first about company, second about role and details. Responsibilities (What You Will Do): - Provide consultative support by conducting analysis including layout optimization, workload planning, inventory forecasting, productivity studies, project management and other industrial engineering projects. - Recognize and implement process improvements that will reduce fiscal spending and/or increase operational efficiency. - Build relationships and interact with all levels of Cast Members from front-line cast to executives. We need to preserve all detail; keep as is. Qualifications & Skills (Required): List: - Strong written and verbal communication skills - Advanced analytical and project management capabilities - Ability to thrive in fast-paced environments and meet tight deadlines - Skilled at balancing multiple tasks while maintaining confidentiality - Quick learner with proven ability to master new software applications and analytical tools - Exceptional organizational skills with keen attention to detail - Demonstrated initiative and drive to achieve results - Knowledge of data analysis and visualization software such as Excel, Smartsheet, Tableau, Power Bi, SSRS, SQL, etc. - Candidates must have a valid U.S. Driver’s license Preferred Qualifications: - Proven knowledge and/or experience with Walt Disney Parks and Resorts - Strong critical thinking and problem-solving skills - Solid understanding of the project life cycle Education: - Junior or Senior year preferred - Major or previous coursework in Industrial Engineering, Project Management, or Supply Chain Management, Inventory Management, Data Science, or related field. Eligibility Requirements & Program Information: - Be enrolled in an accredited college/university pursuing a degree taking at least one class at time of application OR currently participating in a Disney College Program or Disney Internship. - Current Disney Interns, College, International, or Culinary Program Participants: You may only work for ONE consecutive year (12 months) in any combination of an internship and/or program. - Be at least 18 years of age - Possess unrestricted work authorization. Additional Information (schedule, housing, transportation, appearance): - Able to have a consistent, reliable work schedule throughout the internship - Fully available from Monday – Friday and occasional evenings and/or weekends depending on project needs for the duration of the internship - Able to provide own housing for the duration of the internship program in the Orlando, FL area - Able to provide reliable transportation to/from work with a personal vehicle, including travel to various locations across the Walt Disney World property throughout the day. - Be compliant with The Disney Look appearance guidelines. We also have limited housing opportunities note: "We provide limited housing opportunities for Florida Based Professional Interns through American Campus Communities, for more information click here". That's substantive; we could include in Additional Information or maybe in Benefits? It's about housing. Could be part of Additional Information but we don't have a heading for that; we could include in Schedule? Not exactly. Could be part of Additional Information but we don't have a heading for that; we could incorporate into Schedule or Benefits? Probably better to include in a separate section? But we don't have a heading for "Additional Information". We could put housing and transportation details under Schedule? Not ideal. Maybe we can create a section "Details" but not in allowed headings. However we could treat housing/transport as part of Schedule? Not really. Could be part of "About the role"? Might be okay to include in About the role as extra prose. But we must preserve ALL substantive information. So we need to include housing, transportation, appearance guidelines somewhere. We could add a

                under About the role after the initial description covering those details. Or we could create a separate section "Details" but not in allowed headings; but we could still use

                for a custom heading? The instruction says use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use

                for section headings (e.g. those). It might be okay to use other headings but they'd be non-standard. Safer to stick to those headings. So we need to fit housing/transport/appearance into one of those sections. Perhaps we can add them to Schedule? Not exactly schedule. Could add to Benefits? Not benefits. Could add to Qualifications? No. Maybe we can create a section "Details" but still use

                and treat it as a heading; the instruction didn't forbid other headings, just gave examples. It says "use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings when appropriate, but we could also use other headings if needed? The instruction: "Use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are those. To be safe, we could create a section "Additional Information" using

                as well, even though not in examples. The instruction didn't forbid; it just gave examples. I think it's okay. Thus we can have sections: About the role, Responsibilities, Qualifications, Benefits