Seasonal Technical Support Analyst

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, EEO, etc. Keep substantive info. We need to parse the posting. Key sections: - Role Overview: description of role: "The Tech Support Analyst – Seasonal provides hands-on technical support for PC, Mac, mobile, and networked systems across Fanatics Commerce's enterprise environment, working under general supervision within established procedures to resolve a wide range of hardware, software, and connectivity issues. This role operates in a fast-paced, often warehouse-based setting, requiring the ability to manage multiple priorities, maintain confidentiality, and communicate clearly with users at all levels. The Tech Support Analyst – Seasonal delivers business and fan impact through BOLD leadership and execution excellence, leveraging data, automation, and AI-enabled insights." That could go under "About the role" heading. - How Will You Drive Impact: includes subsections: Team & Leadership Impact, Fan & Customer Impact, Innovation & Problem Solving, Ownership & Execution, AI & DIGITAL CAPABILITY. These are responsibilities. Could be under "Responsibilities". We need to list bullet points. - Required Qualifications: includes CAPABILITIES & EXPERIENCE YOU BRING (list of qualifications) and Education. Could be under "Requirements" or "Qualifications". We need to decide which headings to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple like About the role, Responsibilities, Requirements, Qualifications, Skills. We need to avoid thin sections. Probably combine Requirements and Qualifications? But they are distinct: Requirements could be experience/education; Qualifications could be capabilities. However we can put both under "Requirements" and "Qualifications" if content exists. - Skills: maybe list specific technical skills: Windows OS, Mac OS, MS Office, Google Workspace, Zoom, Cisco AnyConnect, Box, Adobe Creative Cloud, networking concepts TCP/IP, DNS, LAN, WAN, VPN, Android/iOS device management, SOTI MobiControl, ITSM platforms ServiceNow, Cat6 cabling, communication, analytical, calm, ability to lift 60 lbs, travel, warehouse. - Benefits, Pay, Schedule: not mentioned in posting. So we should NOT include those sections. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract details. About the role paragraph: we have the role overview. Responsibilities: we need to capture bullet points from the subsections. Let's list them: Team & Leadership Impact (Build Championship Teams): - Collaborate cross-functionally with end users, peers, and higher-level support tiers to diagnose and escalate technical issues with clear, detailed documentation. - Champion positive and collaborative working relationships across the user base, maintaining professionalism with demanding customers and upper management alike. - Contribute to a shared knowledge base by assisting in the creation and maintenance of self-service end-user support documentation. Fan & Customer Impact (Obsessed with Fans): - Provide responsive, high-quality technical support to end users, ensuring minimal disruption to day-to-day operations and a consistently positive support experience. - Deliver clear direction and instruction on computer applications, empowering users to resolve basic issues independently where possible. - Maintain a strong dedication to customer service, responding to last-minute requests with accuracy and composure. - Handle all interactions with discretion, safeguarding confidential data and sensitive system access. Innovation & Problem Solving (Limitless Entrepreneurial Spirit): - Diagnose and resolve complex hardware, software, network, VPN, Wi-Fi, and LAN/WAN connectivity issues, applying structured troubleshooting methodologies. - Support Android and Apple iOS device management, including operating system reinstallation and use of ADB tools where required. - Identify and document technical issues in sufficient detail to enable efficient escalation and resolution by higher support levels. - Apply working knowledge of TCP/IP, DNS, and Active Directory to address network and user access problems systematically. Ownership & Execution (Determined & Relentless Mindset): - Manage end-to-end PC provisioning, including hardware setup, software installation, and peripheral configuration for end users. - Maintain, repair, and troubleshoot printers (network and standalone), handheld scanners, label printers, and other ruggedized warehouse equipment. - Adhere to all standard operating procedures for computer networking and information systems as established by Fanatics, including safety regulations when using ladders or power industrial equipment. - Demonstrate consistent follow-through to ensure problems are fully resolved, with the ability to work independently with minimal direction when required. AI & DIGITAL CAPABILITY: - Apply AI and technology to improve efficiency, quality, and outcomes. - Use data and digital tools to inform decisions and enhance performance. - Demonstrate curiosity and adaptability in adopting new technologies and ways of working. - Contribute to a culture of innovation and continuous improvement. We can combine these bullet points under Responsibilities. Requirements: maybe education and experience? The posting includes "Required Qualifications" with subheading CAPABILITIES & EXPERIENCE YOU BRING and Education. Could treat CAPABILITIES & EXPERIENCE as Requirements, and Education as Qualifications? Or vice versa. Let's decide: Requirements: Experience: One to three years of experience in a technical support role, with demonstrated ability to troubleshoot and resolve PC, Mac, and peripheral hardware and software issues. Education: High school diploma or equivalent with 3 years of related work experience required; or a college or associate degree with 2 years of related work experience. Qualifications: The list of capabilities: strong working knowledge of Windows OS, Mac OS, MS Office, Google Workspace, hands-on experience supporting additional tools such as Zoom, Cisco AnyConnect, Box, and Adobe Creative Cloud. Solid understanding of networking concepts including TCP/IP, DNS, LAN, WAN, and VPN, with ability to diagnose and articulate connectivity issues clearly. Experience operating and supporting Android and Apple iOS devices, including mobile device management platforms such as SOTI MobiControl. Proficiency with ITSM platforms, with experience in ServiceNow preferred; familiarity with running and terminating Cat6 network cabling is a plus. Excellent verbal and written communication skills, strong analytical ability, and a calm, composed approach when supporting demanding users or fast-moving operational environments. Physical ability to lift computer equipment including monitors and printers up to 60 lbs., and willingness to travel occasionally to remote locations and work within warehouse environments. Skills: maybe we can extract specific technical skills list: Windows OS, Mac OS, MS Office, Google Workspace, Zoom, Cisco AnyConnect, Box, Adobe Creative Cloud, TCP/IP, DNS, LAN, WAN, VPN, Active Directory, Android/iOS device management, ADB tools, SOTI MobiControl, ServiceNow, Cat6 cabling, communication, analytical, calm, lift 60 lbs, travel, warehouse. But we already have many of those in Qualifications. To avoid duplication, we could treat Qualifications as the capabilities list, and Skills as maybe soft skills? However the instruction says we can have Skills section. We need to avoid thin sections. If we put Skills, we need substantive content. We could list specific technical skills: Windows OS, Mac OS, MS Office, Google Workspace, Zoom, Cisco AnyConnect, Box, Adobe Creative Cloud, TCP/IP, DNS, LAN, WAN, VPN, Active Directory, Android/iOS, ADB, SOTI MobiControl, ServiceNow, Cat6 cabling. That's substantive. But then Qualifications could be experience and education. However the posting lumps capabilities under "Required Qualifications". So maybe better: Requirements = experience + education; Qualifications = capabilities list; Skills = maybe not needed. But we need to avoid thin sections. If we make Skills empty or thin, we shouldn't include it. So we can omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications. Check if we have content for each. About the role: we have paragraph. Responsibilities: we have bullet points. Requirements: experience (1-3 years) and education (HS diploma or equivalent with 3 years related work experience; or college/associate degree with 2 years related work experience). Also maybe mention work location? That's not a requirement but location. Could be included in About the role? Might be separate but we can include location in About the role or maybe as a separate "Work Location" but not a heading we have. Since we don't have a heading for location, we could fold it into About the role paragraph: "On-site: Your work location will be onsite in Waxahachie, TX." That's substantive. We'll add that to About the role. Qualifications: capabilities list (Windows OS, Mac OS, MS Office, Google Workspace, Zoom, Cisco AnyConnect, Box, Adobe Creative Cloud, networking concepts TCP/IP, DNS, LAN, WAN, VPN, Active Directory, Android/iOS device management, SOTI MobiControl, ITSM platforms ServiceNow preferred, Cat6 cabling plus, communication, analytical, calm, lift 60 lbs, travel, warehouse). That's substantive. We must not repeat job title. No mention of Job ID. We must not include boilerplate like "At Fanatics, we bring our BOLD Leadership Principles...". That's part of About the role? Actually that appears earlier in the description before Role Overview. It's generic company description. Might be considered boilerplate? It's not navigation/legal/EEO but it's generic marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The BOLD Leadership Principles statement is not exactly boilerplate but could be considered part of company overview. However it's substantive? It's repeated later in About Us and About The Team. Might be considered duplicated. Safer to remove that generic statement. The Role Overview already includes mention of BOLD leadership and execution excellence. So we can drop the earlier BOLD Leadership Principles line. Also the "About Us" and "About The Team" sections are likely boilerplate; we should remove them. The instruction says remove duplicated lines. So we will omit those sections. Thus final HTML:

About the role

The Tech Support Analyst – Seasonal provides hands-on technical support for PC, Mac, mobile, and networked systems across Fanatics Commerce's enterprise environment, working under general supervision within established procedures to resolve a wide range of hardware, software, and connectivity issues. This role operates in a fast-paced, often warehouse-based setting, requiring the ability to manage multiple priorities, maintain confidentiality, and communicate clearly with users at all levels. The Tech Support Analyst – Seasonal delivers business and fan impact through BOLD leadership and execution excellence, leveraging data, automation, and AI-enabled insights. On-site: Your work location will be onsite in Waxahachie, TX.

Responsibilities

• Collaborate cross-functionally with end users, peers, and higher-level support tiers to diagnose and escalate technical issues with clear, detailed documentation.
• Champion positive and collaborative working relationships across the user base, maintaining professionalism with demanding customers and upper management alike.
• Contribute to a shared knowledge base by assisting in the creation and maintenance of self-service end-user support documentation.
• Provide responsive, high-quality technical support to end users, ensuring minimal disruption to day-to-day operations and a consistently positive support experience.
• Deliver clear direction and instruction on computer applications, empowering users to resolve basic issues independently where possible.
• Maintain a strong dedication to customer service, responding to last-minute requests with accuracy and composure.
• Handle all interactions with discretion, safeguarding confidential data and sensitive system access.
• Diagnose and resolve complex hardware, software, network, VPN, Wi-Fi, and