IT Support IV, Manufacturing Operations (Onsite)

We need to output only HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also we must include a section only when posting has real specific content for it; no filler. We need to parse the posting. The posting includes: - Title: IT Support IV, Manufacturing Operations (Onsite) - Description: "Join Axon and be a Force for Good..." etc. This is about the role, mission, etc. Could be "About the role" or "About Axon". We need a heading for section about the role. Likely "About the role" or "About Axon". Use

About the role

then paragraphs. - "Your Impact" section: describes role responsibilities. Could be under "Responsibilities". We'll put that. - "What You'll Do" includes location, core hours, reports to, direct reports, then bullet list of duties. This is responsibilities. - "What You Bring" includes qualifications, requirements, skills, etc. We'll split into Requirements, Qualifications, Skills maybe. - "Benefits That Benefit You" includes benefits list. - Pay: Not explicitly mentioned. There's "Competitive salary" but not specific number. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It says "Competitive salary and 401k with employer match" etc. That's benefits. Pay not specific number, but "Competitive salary" is vague. 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. Since they say "Competitive salary" but not a number, is that considered filler? It's vague but still states they offer competitive salary. Might be considered stating pay exists but not amount. The instruction says not to create Pay section unless posting actually states them. It does state "Competitive salary". That is a statement about pay, albeit vague. Should we include Pay section? The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive salary, so we could include Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might combine Pay into Benefits? But Benefits section already includes benefits list. Pay could be separate. Schedule: They give Core Hours: 8:00 a.m.-4:00 p.m.; flexibility to cover 6:00 a.m.-2:00 p.m. or 10:00 a.m.-6:00 p.m. shifts as needed. That's schedule info. So we can include Schedule section. Benefits: They list benefits. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to avoid duplication and filler. Let's extract content. First, remove boilerplate lines: The repeated "The insights provided are generated by AI..." appears twice at start and after title. Also there are lines like "Don't meet every single requirement? That's ok." etc. That's not boilerplate but maybe part of encouragement; it's substantive? It's more about encouraging applicants; could be kept? It's not a duty/requirement/benefit. Might be considered fluff but still part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Don't meet every single requirement..." is not exactly those categories; it's more motivational. Might keep? It's not a duty/requirement/benefit but could be considered part of "About the role" or "Qualifications". Might be okay to keep as paragraph. Also "Important Notes" etc is legal boilerplate; should remove. Also "We are an equal opportunity employer..." etc is EEO boilerplate; remove. Also "Phishing alert:" etc is scam-warning; remove. Also "Important Notes" about job description not exhaustive etc is legal; remove. Also "We collect personal information..." etc is privacy; remove. Also "Axon's mission is to Protect Life..." etc is maybe mission statement but could be part of About the role. However it's also somewhat boilerplate but still about company mission. Might keep as part of About the role. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the specifics: location, core hours, reports to, direct reports, duties list, qualifications list, benefits list, etc. We'll need to format lists with

• . We'll need to decide which content goes under which heading. Let's extract sections: About the role / Company overview: The paragraph starting "Join Axon and be a Force for Good." up to "Here, you'll take ownership and drive real change. Constantly grow as you work hard for a mission that matters at a company where you matter." That's about Axon and role impact. Could be under "About the role". We'll keep that as paragraph(s). Your Impact: "As an IT Support IV, you will serve as a senior technical resource for Axon's manufacturing and warehouse operations at the Pinnacle Peak facility. You will help keep production, shipping, and logistics environments running by resolving complex endpoint and hardware issues, responding to manufacturing-critical incidents, and improving the tools and processes that support our employees and operations. This is a hands-on role with the opportunity to lead technical initiatives, mentor peers, and shape scalable IT support practices in a fast-paced environment where uptime matters." This is more about role responsibilities; could be part of Responsibilities. What You'll Do: includes location, core hours, reports to, direct reports, then bullet list of duties. We could combine "Your Impact" and "What You'll Do" under Responsibilities. But we need headings only when there is real specific content. We'll have: - About the role (company overview + mission) - Responsibilities (duties) - Requirements (maybe years of experience, etc) - Qualifications (education, certifications) - Skills (technical skills) - Benefits - Pay - Schedule We must avoid thin sections. Let's see if we have enough content for each. Requirements: "3-5 years of enterprise IT support experience, preferably in a manufacturing, warehouse, logistics, production, or similarly uptime-sensitive environment." That's a requirement. Qualifications: "Bachelor's degree in Information Technology, Computer Science, or a related field is preferred but not required." plus "Relevant certifications, such as Microsoft Certified: Modern Desktop Administrator, Jamf 300/400, CompTIA Security+, CompTIA CySA+, or equivalent, are a plus." plus "Scripting experience in PowerShell, Bash, or Python for automation and systems administration is a plus." plus "Experience troubleshooting enterprise audio/visual systems is preferred." These could be qualifications. Skills: "Advanced hands-on experience supporting endpoint-management and collaboration tools such as Jamf, Microsoft Intune/Autopilot, Tanium, Okta, Google Workspace, Zoom, Slack, ServiceNow, and Windows imaging or PXE environments." plus "Strong troubleshooting ability across industrial IT hardware, production workstations, printers, shipping stations, mobile devices, and related peripherals." plus "Working knowledge of ITSM or ITIL-based support practices, networking fundamentals-including DNS, DHCP, subnetting, and connectivity troubleshooting-and identity-management concepts such as SSO and MFA." plus "Demonstrated ability to manage high-pressure technical incidents with professionalism, prioritize production-impacting issues, communicate clearly with stakeholders, and work independently in a fast-paced environment." plus "Experience partnering cross-functionally to implement scalable IT solutions, improve processes, and support operational initiatives." These are skills. We could also include "Experience troubleshooting enterprise audio/visual systems is preferred." under Skills. Now Benefits: list: Competitive salary and 401k with employer match, Discretionary paid time off, Paid parental leave for all, Medical, Dental, Vision plans, Fitness Programs, Emotional & Mental Wellness support, Learning & Development programs, snacks in offices. Also note "Benefits listed herein may vary depending on the nature of your employment and the location where you work." That's a qualifier but we can keep. Pay: "Competitive salary" is mentioned in benefits but we could separate Pay: "Competitive salary". However that is vague; but it's still a statement about pay. Might be okay to include Pay section with that phrase. Schedule: "Core Hours: 8:00 a.m.-4:00 p.m.; flexibility to cover 6:00 a.m.-2:00 p.m. or 10:00 a.m.-6:00 p.m. shifts as needed." That's schedule. Now we need to remove boilerplate: The repeated AI insights lines, the "Don't meet every single requirement?" paragraph (maybe keep as encouragement but not required). The "Important Notes" and following legal/EEO/Phishing etc must be removed. Also remove duplicated lines: The AI insights line appears twice; we remove both. Also remove "Join Axon and be a Force for Good."? No that's substantive. Now we need to output only HTML fragment, no /, no markdown. We'll produce something like:

  About the role

  Join Axon and be a Force for Good. At Axon, we're on a mission to Protect Life. We're explorers, pursuing society's most critical safety and justice issues with our ecosystem of devices and cloud software. Like our products, we work better together. We connect with candor and care, seeking out diverse perspectives from our customers, communities and each other. Life at Axon is fast-paced, challenging and meaningful. Here, you'll take ownership and drive real change. Constantly grow as you work hard for a mission that matters at a company where you matter.

  Responsibilities

  As an IT Support IV, you will serve as a senior technical resource for Axon's manufacturing and warehouse operations at the Pinnacle Peak facility. You will help keep production, shipping, and logistics environments running by resolving complex endpoint and hardware issues, responding to manufacturing-critical incidents, and improving the tools and processes that support our employees and operations. This is a hands-on role with the opportunity to lead technical initiatives, mentor peers, and shape scalable IT support practices in a fast-paced environment where uptime matters.

  Location: Onsite at our Pinnacle Peak Warehouse in Phoenix, Arizona

  Core Hours: 8:00 a.m.-4:00 p.m.; flexibility to cover 6:00 a.m.-2:00 p.m. or 10:00 a.m.-6:00 p.m. shifts as needed

  Reports to: IT Support Manager

  Direct Reports: None

  • Serve as the senior escalation point for IT support issues across the Pinnacle Peak manufacturing and warehouse location, as well as remote sites as needed.
  • Diagnose and resolve complex hardware, software, and endpoint issues across Windows, macOS, mobile devices, production workstations, and specialized manufacturing peripherals.
  • Respond rapidly to production-critical incidents, prioritize manufacturing outages appropriately, and minimize operational downtime.
  • Deploy, image, configure, and lifecycle-manage manufacturing and warehouse devices using standardized endpoint-management and imaging processes.
  • Support production, warehouse, and shipping operations