AV Specialist | View Boston

We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually we have "THE ROLE: AV Specialist". The page already shows job title, so we should not repeat job title as heading. We need sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only when posting has real specific content. We need to parse content. The posting includes: - THE ROLE: AV Specialist (title) - LOCATION: View Boston | Boston, MA - About Legends Global (company description) - The Role (description of duties) - What You’ll Do (key Responsibilities & Outcomes) (list of duties) - What You Bring (qualifications & Experience) (education/experience, skills) - Compensation (salary up to $60k, benefits) - WORKING CONDITIONS (Location: On Site at View Boston) - PHYSICAL DEMANDS (description) - NOTE etc (boilerplate) - Equal Opportunity etc (boilerplate to remove) We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove NOTE, PHYSICAL DEMANDS? Physical demands might be considered substantive? It's about ability to lift etc. Could be part of Requirements/Qualifications. But we can include as part of Requirements maybe. However guidelines: Prefer few substantive sections over many thin ones. We can combine. We need sections: About the role (maybe company overview?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have: - About Legends Global: company description. Could be "About the role" or "About the company"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe describing role). But we have a separate "The Role" description. We could treat that as About the role. - Responsibilities: from "What You’ll Do (key Responsibilities & Outcomes)" list. - Requirements: maybe education/experience from "What You Bring (qualifications & Experience)" includes Education and/or Experience. - Qualifications: maybe same as Requirements? Could split but better to avoid thin sections. Could combine Education/Experience under Requirements, and Skills under Skills. - Skills: list of technical skills. - Benefits: from Compensation: "generous benefits package that includes medical, dental, vision, life and disability insurance, paid vacation, and 401k plan." - Pay: "Competitive salary of up to $60,000 commensurate with experience". However "commensurate with experience" is placeholder? It's not a specific number but it's a range up to $60k. The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary up to $60k commensurate with experience. That's somewhat placeholder but still gives a max. It's not "not specified". It's a specific max. I think we can include Pay section with that sentence. - Schedule: Not explicitly stated. There's "Flexible availability includes nights, weekends, and holidays." That's about schedule. Could be considered schedule. The posting mentions flexible availability includes nights, weekends, holidays. That's schedule info. So we can include Schedule section with that. - Location: Already given but we might not need separate section; could be part of About the role or maybe we drop. We must not repeat job title as heading. So no h3 for "AV Specialist". We'll output sections as needed. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from responsibilities, qualifications, skills, benefits, pay, schedule. We must not include boilerplate like Equal Opportunity, NOTE, PHYSICAL DEMANDS? Physical demands includes ability to lift etc. That's substantive; maybe we can include under Requirements or Skills? But we could add a separate section? Not in allowed headings list. Could incorporate into Requirements or Skills. Since we have limited headings, we can put physical demands under Requirements (maybe as bullet). But we must not lose that info. Thus we need to extract bullets. Let's parse responsibilities list: - Provide setup and support of multiple point-of-sale systems for View Boston Observatory facility. - Provide excellent desktop support services to internal staff. - Work with vendors and service providers to resolve issues and implement changes. - Must be able to communicate productively and professionally across all managerial levels. - Provide level 1 & 2 support for all point-of-sale system problems and escalate with inside and outside service providers when necessary. - Provides AV Support and Event Support for View Boston Observatory. - Serves as View Boston building wide point of contact on IT related matters. - Conduct Observatory walk-through to ensure all systems are operational prior to and during all events. - Replacement of defective hardware before, during and after events. - Diagnoses of software, firmware, & hardware errors and breakage, and execution of solutions. - Work with external vendors in support of proprietary systems. - Tracking RMAs of all equipment inbound and outbound for repairs. - Maintains a thorough knowledge of the organization and adheres to all standards and practices. - Perform other duties as assigned by Venue Technology Manager. We need to keep all. Qualifications/Education: - Education and/or Experience: Bachelor’s degree in Computer Information Systems or related field (equivalent experience considered). - 1–3+ years of IT/AV support or related technical experience. Skills and Abilities list: - Flexible availability includes nights, weekends, and holidays. - Working knowledge of PC hardware setup and troubleshooting. - Strong understanding of networking fundamentals, including TCP/IP and VLANs. - Experience with wireless LAN environments and related security protocols. - Proficiency with Microsoft Windows and macOS operating systems, Office suites, and basic server/network concepts. - Familiarity with virtualized environments (server and desktop). - Experience configuring, operating, and troubleshooting audiovisual (AV) systems, including: Video switchers, displays, projectors, LED walls, and digital signage systems. Audio consoles, amplifiers, microphones (wired and wireless), speakers, and DSPs. Streaming and conferencing platforms (Zoom Rooms, Teams Rooms, or equivalent). HDMI/SDI/DisplayPort signal routing, extenders, and network-based AV systems (AV over IP). Knowledge of Crestron, Extron, AMX, Q-SYS, or similar control system platforms (programming not required, operational familiarity preferred). - Skilled in performing system walk-throughs, live-event support, and real-time troubleshooting under time-sensitive conditions. - Understanding of IT security concepts, including password management and secure network practices. - Ability to move fast and act on assigned duties. - Ability to walk, stand, or sit for extended periods of time. - Ability to reach, bend, stoop, wipe, push and pull. - Ability to lift and carry items weighing 10-30 pounds, and up to 50 pounds. Compensation: - Competitive salary of up to $60,000 commensurate with experience, and a generous benefits package that includes medical, dental, vision, life and disability insurance, paid vacation, and 401k plan. Working Conditions: - Location: On Site at View Boston (Boston, MA) We could include location maybe in About the role or as a short p. Schedule: Flexible availability includes nights, weekends, and holidays. Now we need to output HTML fragment with h3 headings and appropriate content. We should not include duplicate lines. We need to decide sections: - About the role: maybe combine company description and role overview. Could use the "About Legends Global" paragraph and "The Role" brief description? The "The Role" section says: "Assist with event space set-up, including furniture placement and equipment distribution based on the specific catering clientele's needs for each event." That's a short description. We'll include that. Thus About the role section will contain:

Legends Global is the premier partner to the world’s greatest live events, venues, and brands. We deliver a fully integrated suite of premium services through a white-label model that keeps our partners front and center — from feasibility and project development to sales, partnerships, hospitality, merchandise, venue management, and world-class content and booking. With a global network of more than 450 venues, hosting 20,000 events and welcoming 165 million guests annually, Legends Global brings unmatched scale, expertise, and connectivity to help our partners grow. The Legends Global Way guides how we operate: Align, Scale, Connect, Team, Win — shared success, repeatable systems, connected solutions, unstoppable teams, and wins that are earned every day.

Assist with event space set-up, including furniture placement and equipment distribution based on the specific catering clientele's needs for each event.

That seems good. - Responsibilities: h3 Responsibilities then ul li list of duties. - Requirements: h3 Requirements then maybe include education/experience and physical demands? Could separate Qualifications and Skills but we have limited headings. Could do Requirements for education/experience, Qualifications for skills? But we have both Requirements and Qualifications as allowed headings. We could split: Requirements for education/experience, Qualifications for skills and abilities. However we also have Skills heading allowed. So we could have Requirements (education/experience), Qualifications (maybe core qualifications?), Skills (technical skills). But to avoid thin sections, we need to see if we have enough content for each. We have education/experience (2 bullets). That's small but still substantive. Could be Requirements. We have skills list (many bullets). That's substantial; could be Skills. We have also "Flexible availability includes nights, weekends, and holidays." which is schedule; could be Schedule. We have physical demands (lifting etc.) maybe could be part of Requirements or Qualifications. We have Benefits and Pay. Thus we can have sections: About the role, Responsibilities, Requirements (education/experience), Skills (technical skills), Benefits, Pay, Schedule. We might also include Qualifications? But we already have Skills covering technical skills; Qualifications could be used for other qualifications like ability to communicate, etc. But we could incorporate those into Skills or Requirements. Given the instruction to prefer few substantive sections over many thin ones, we might combine education/experience and physical demands into Requirements, and put all skills (including communication, flexibility, etc.) into Skills. Then we have Benefits, Pay, Schedule. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Check if any section would be empty or filler. - About the role: we have content. - Responsibilities: we have list. - Requirements: we have education/experience (Bachelor's degree, 1-3+ years IT/AV support) plus physical demands (ability to lift etc.) and maybe ability to walk, stand etc. That's substantive. - Skills: we have technical skills list (PC hardware, networking, wireless LAN, Windows/macOS, virtualization, AV systems, conferencing platforms, signal routing, control systems, walk-through, IT security, ability to move fast, etc.) plus maybe communication ability? Actually communication is in responsibilities. We'll keep it there. - Benefits: we have medical, dental, vision, life and disability insurance, paid vacation, 401k. - Pay: competitive salary up to $60k commensurate with experience. - Schedule: Flexible availability includes nights, weekends, and holidays. We must not include placeholder text like "commensurate with experience" in Pay heading? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The Pay section would have the sentence