Special Event Associate (Part Time, On Call)

We need to output HTML fragment with sections: About the role? The posting includes "Who We Are", "Position Overview", "Responsibilities", "Requirements And Skills", "Working Conditions and Schedule", "Inclusion, Diversity, Equity, and Accessibility (IDEA) at The Tech", "The Pay Range For This Role Is 23 - 23 USD per hour". Also maybe "Benefits"? Not present. So we include sections where there is content. We must not repeat job title as heading. Use

for section headings. Use

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

  for prose. We need to preserve all substantive info, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The IDEA section includes EEO statement; we need to remove boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the EEO statement (the long paragraph about non-discrimination) and the accommodation contact line? That is part of EEO. Probably remove that entire paragraph. Keep the IDEA heading? The heading "Inclusion, Diversity, Equity, and Accessibility (IDEA) at The Tech" is not boilerplate; it's a section describing their commitment. The content after that includes the EEO statement; we should remove that boilerplate but maybe keep the introductory sentence: "Our success is dependent on building teams that include people from different backgrounds and experiences who challenge each other’s assumptions with fresh perspectives. To that end, we look for a diverse pool of applicants including but not limited to those from historically marginalized groups — women, people with disabilities, people of color, people who are lesbian, gay, bisexual, transgender, and/or nonconforming, veterans, and people from different socioeconomic backgrounds." That's not boilerplate; it's substantive. Then the EEO statement is boilerplate; remove it. Also the accommodation contact line is part of EEO; remove. Also remove duplicated lines: maybe none. We need to include Pay section only if posting actually states them. It does: "The Pay Range For This Role Is 23 - 23 USD per hour". So we include a Pay section with that info. Schedule: we have Working Conditions and Schedule section includes schedule info. So we can include a Schedule section? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have a Schedule heading if there is schedule content. The Working Conditions and Schedule includes schedule info; we could either keep that as a section named "Working Conditions and Schedule" or split into Schedule and Working Conditions? The instruction says prefer a few substantive sections over many thin ones. So we could keep "Working Conditions and Schedule" as a heading (though not in the example list but allowed? The examples are not exhaustive; they said e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could use "Working Conditions and Schedule" as a heading, but maybe better to use "Schedule" and include schedule info there, and maybe "Working Conditions" could be omitted or merged. However we have substantive info about working conditions: onsite, variable hour on call, at least one weekend shift per week, flexible availability, significant periods of standing/walking, moving objects up to 35 pounds, indoor/outdoor. That's schedule and working conditions. Could combine into a single section "Working Conditions and Schedule". That seems fine. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  Who We Are

  maybe? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). "Who We Are" is not in list but could be considered "About the role"? Actually "About the role" is similar to Position Overview. But we have "Who We Are" describing the organization. Could we treat that as "About the role"? Not exactly. But we need to include all substantive info. 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 suggests those as examples. Safer to use those exact headings where applicable. We have content that maps: - About the role: could be Position Overview. - Responsibilities: we have Responsibilities section. - Requirements: we have Requirements And Skills. - Skills: could be combined with Requirements? But we have both; we could make a Skills section separate. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one section "Requirements and Skills". That's fine. - Benefits: none. - Pay: we have Pay. - Schedule: we have Working Conditions and Schedule. We also have "Who We Are" which could be considered "About the role"? Actually "About the role" is about the job, not the organization. But we could include an "About the organization" section maybe not required but we should preserve that info. The instruction says "include a section ONLY when the posting has real, specific content for it". So we need to include that info somewhere. Could we put it under a heading like "About the Tech Interactive"? Not in the list but we could still use

  for that heading. The instruction didn't forbid other headings; it just gave examples. So we can add a heading "Who We Are". That seems fine. Thus sections: - Who We Are - About the role (Position Overview) - Responsibilities - Requirements and Skills - Working Conditions and Schedule - Pay We need to use

  • for any list of duties/requirements/benefits. So for Responsibilities, we should list each duty as
  • . For Requirements and Skills, list each requirement/skill as
  • . For Working Conditions and Schedule, maybe not a list but could be prose; but we could list schedule items as
  • . However the instruction: "Use
    • for any list of duties/requirements/benefits". So if we present them as a list, we must use
      • . If we present as prose, we can use

        . We'll decide. Responsibilities: there are many bullet-like sentences. We'll make a

        with each responsibility as
        • . Requirements and Skills: also bullet-like; we can make a
          . Working Conditions and Schedule: we could make a

          describing. Pay:

          with the pay range. Now we need to strip boilerplate: remove the EEO statement and accommodation contact. Also remove duplicated lines? Not seeing duplicates. Also remove "Any applicant with a disability may contact The Tech Interactive to arrange for accommodations. Please contact the Tech at careers@thetech.org or call (408) 795-6248." That's boilerplate; remove. Also remove "The Tech will provide an equal opportunity in recruitment and employment to all individuals and will not discriminate on the basis of ..." that's EEO; remove. Now we need to preserve all other substantive info. Let's extract content. Who We Are paragraph: "Since opening in 1998, The Tech Interactive has been an integral part of the San Francisco Bay area and is proud to serve families and young people through hands-on activities, experimental labs, and design challenge experiences. Here at The Tech our mission is to inspire the innovator in everyone! We are a team of diverse individuals committed to creating learning experiences that empower young folks to innovate with creativity, curiosity, and compassion. We believe that technology is leading and transforming lives all over the world and we want to help develop the next generation of problem-solvers. If you join our team, we know you will have a fulfilling and rewarding role focused on giving back to our community, especially those that have been historically marginalized and underserved." We'll put that in

          . Position Overview: "The Event Associate provides support in the execution of a variety of events at The Tech Interactive. Examples include facility rentals, limited run IMAX showings, extended hours, and member and community events among others. This on-call, non-exempt (hourly) position reports to the Special Events Senior Manager and will be scheduled based on the event calendar. Flexible availability, primarily during evenings and weekends, is needed. Duties will vary depending on the event. You may help with visitor services duties such as ticket sales, concessions, IMAX console, store, and membership sales, or assisting guests with hands-on learning experiences during special events. This role will expose you to a variety of tasks required to run an event or special program." We'll put that in

          under heading About the role. Responsibilities list: - Coordinate logistics of an event with the Event Supervisor and execute the event setup and strike requirements. - On-site support contact for clients during events and maintain hands-on event support during the event. - Facilitate exhibit experiences and/or hand-on activities with guests of varying ages and knowledge levels using our signature Design Challenge Learning style of facilitation. - Assist with volunteer assignments and coordinate breaks as needed. - Handle ticket sales if applicable. - Perform other visitor services functions such as ticket taking, membership sales, or store sales if applicable to the event. - Assist with IMAX Theater duties including working concession stand, console, ushering, and cleaning. - Interact and communicate with guests and ensure superior service. - Participate in required and optional training sessions to build and maintain facilitation and engagement skills. - Maintain current knowledge about The Tech’s programs, IMAX films, exhibits, and other guest-related information. - Demonstrate The Tech’s mission and values, including values in diversity, equity, and inclusion in all aspects of the job. - Perform other duties as assigned. We'll make

          • for each. Requirements and Skills list: - One or more years of retail, sales, museum, and/or customer service experience preferred - Ability to work in a public setting, interact with guests, and follow safety protocols. - Excellent communication skills (verbal and written), as well as professional phone etiquette. - Ability to speak in public in front of groups. - Ability to learn new procedures and systems and thrives in an environment that may rotate multiple job stations in a shift - Outgoing, positive attitude and enthusiasm for working with the public and children. - Computer literate (Microsoft Windows, Microsoft Office, Google Suite, internet) We'll make
            • . Working Conditions and Schedule: we need to include schedule info: "This is an onsite position. This is a variable hour on call position, based on operational need. At least one-weekend shift per week is required. Flexible availability, including weekdays, weekends, evenings, and holidays. Significant periods of standing and walking within an assigned space. Walking around and interacting with guests is an essential part of this job. Significant periods of time in both an indoor and outdoor environment. Frequently moves objects up to 35 pounds." We'll put that in

              . Pay: "The Pay Range For This Role Is 23 - 23 USD per hour". We'll put that in

              . Now ensure we didn't include any boilerplate. Also remove "The Tech Interactive" at end of pay line? It's part of the line: "The Pay Range For This Role Is 23 - 23 USD per hour(The Tech Interactive)". Actually the original: "The Pay Range For This Role Is 23 - 23 USD per hour(The Tech Interactive)". There's no space before parentheses. We'll keep the pay range and maybe drop the "(The Tech Interactive)" as it's redundant? It's part of the line but not essential; we can keep it as part of the sentence: "The Pay Range For This Role Is 23 - 23 USD per hour." We'll omit the parentheses. Now produce HTML. We'll start