Senior IT Support Technician - OKC

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Rockforce" description, then "Position Summary", "Core Responsibilities", "Onboarding, Offboarding & Endpoint Support", "Hardware Provisioning, Deployment & Inventory", "Identity, Security & Basic Network Support", "Documentation & Team Contribution", "Required Qualifications", "Preferred Qualifications", "Success in This Role", "The role is hybrid...". Also there is EEO boilerplate to remove. Also "Job Posted by ApplicantPro" maybe minor metadata; we can drop or put in short p. We must not repeat job title as heading. Use

for section headings. Use

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

  for prose. We need to include sections only when posting has real specific content. We have many sections. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details as they appear, but format as HTML. We need to decide which headings to use: The posting has headings: About Rockforce, Position Summary, Core Responsibilities, Onboarding, Offboarding & Endpoint Support, Hardware Provisioning, Deployment & Inventory, Identity, Security & Basic Network Support, Documentation & Team Contribution, Required Qualifications, Preferred Qualifications, Success in This Role, The role is hybrid... maybe we can treat "The role is hybrid..." as part of Success in This Role or separate Schedule? Actually schedule: "The role is hybrid, with 2-4 days in-office in OKC, Oklahoma". That's schedule info. So we could create a Schedule section with that sentence. But rule: include a section ONLY when posting has real, specific content for it. It does have schedule content. So we can add a Schedule section with that sentence. Also Pay/Benefits: not mentioned, so omit. Thus sections: About Rockforce (maybe we treat as About the role? Actually heading "About Rockforce" is company overview. Could be "About the role"? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? Probably we should map to those standard headings where possible. But we can also use other headings if they match content? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings. But we can also use other headings if they fit? Safer to use those standard headings. However the posting has sections like "Core Responsibilities" which maps to Responsibilities. "Required Qualifications" maps to Requirements/Qualifications. "Preferred Qualifications" maybe also Qualifications. "Success in This Role" maybe Skills? Not exactly. "Onboarding, Offboarding & Endpoint Support" could be part of Responsibilities. "Hardware Provisioning..." also Responsibilities. "Identity, Security & Basic Network Support" also Responsibilities. "Documentation & Team Contribution" also Responsibilities. So we could consolidate many into Responsibilities. But instruction: Prefer a few substantive sections over many thin ones. So we should combine similar content into fewer sections. Thus we could have sections: About the role (company overview), Responsibilities (combining all duty paragraphs), Requirements (Required Qualifications), Preferred Qualifications maybe as part of Requirements or separate Skills? Could be Skills. But we have "Preferred Qualifications" separate; we could treat as Skills section. Or we could include under Requirements as "Preferred". But instruction: use headings like Skills. So we could have Skills section for preferred qualifications. Schedule: hybrid info. We must not repeat job title as heading. The job title is Senior IT Support Technician; we should not use that as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: EEO, HIRING PRACTICES, etc. We must preserve all substantive information: need to keep details from each paragraph. Thus we need to extract substantive content from each section and place into appropriate sections. Let's parse content: About Rockforce paragraph: "RockForce provides World-Class Workforce & Production Solutions for Live Events. Our comprehensive strategic services are geared for the industry's unique needs from start to strike. RockForce provides production resources for tours, concerts, festivals, sporting events, live broadcasts, award shows, and corporate activations world-wide. Our teams bring decades of unmatched experience and expertise executing the most demanding and high-profile events for the biggest names in sports and entertainment. From Workforce Deployment, Rigging, streamlined Payroll Services, & Production Management - We Set the Stage for the Greatest Moments in Live Events. RockForce Operations has Workforce Divisions throughout the U.S. providing Union and Non-Union Stagehands for venues, broadcasting, and on-site productions with a commitment to safety, precision, and excellence. Every team member is thoroughly trained and supported by a leadership team with decades of hands-on experience in live event labor." That's substantive. Position Summary: "RockForce is seeking a Senior IT Support Technician to provide experienced frontline technology support across the organization. This role will own day-to-day employee support requests, workstation readiness, onboarding and offboarding tasks, Microsoft 365 support, device enrollment and compliance, hardware and peripheral troubleshooting, and basic network support. The successful candidate will combine strong technical troubleshooting with dependable customer service, disciplined ticket ownership, clear documentation, and a security-first mindset." That's also substantive; could be part of About the role or Responsibilities. We'll include in Responsibilities maybe. Core Responsibilities bullet list (actually sentences separated by periods). Let's extract each duty: - Serve as a primary point of contact for employee technology support and take ownership of requests through resolution or appropriate escalation. - Troubleshoot Windows laptops and desktops, mobile devices, printers, peripherals, conference-room technology, and common business applications. - Support Microsoft 365 services including Outlook, Teams, OneDrive, SharePoint, authentication, and common user-access issues. - Provide in-person and remote support while keeping employees informed of status and next steps. - Maintain accurate and useful ticket notes, resolution details, and follow-up documentation. Onboarding, Offboarding & Endpoint Support: - Prepare and configure company devices for new employees using RockForce standards and approved software. - Assist with user onboarding, initial sign-in, MFA setup, Microsoft 365 access, and required business applications. - Execute offboarding steps promptly, including account-access changes, equipment recovery, and documentation of completed actions. - Assist with Microsoft Intune enrollment, device compliance, patching, software deployment, and remediation of noncompliant endpoints. - Maintain accurate hardware and device inventory records and identify equipment requiring repair, replacement, or retirement. Hardware Provisioning, Deployment & Inventory: - Prepare, image, configure, and provision laptops, desktops, and related equipment according to RockForce standards before deployment. - Install required operating-system updates, business applications, security tools, Microsoft Intune enrollment, and approved configuration policies, and verify that devices are functional and compliant before release. - Package and ship computers, peripherals, and replacement equipment to remote employees and RockForce locations, and coordinate device swaps when required. - Receive and process returned equipment, including inspection, secure handling, reimaging, repair coordination, redeployment, or retirement as appropriate. - Maintain accurate asset records, including assigned user, serial number, location, deployment status, and lifecycle information. - Maintain a small on-hand inventory of deployable computers, common peripherals, and replacement equipment so urgent employee needs can be addressed without unnecessary delay. - Coordinate with RockForce hardware and IT service vendors for procurement, vendor-led provisioning, repair, warranty service, and larger-scale deployments while retaining the ability to prepare devices internally when needed. Identity, Security & Basic Network Support: - Handle password resets, MFA enrollment, user-account troubleshooting, and approved access requests according to established procedures. - Recognize and promptly escalate suspected phishing, malware, account compromise, unauthorized access, lost devices, or other potential security incidents. - Support the RockForce requirement that devices accessing company data be properly managed and compliant with approved endpoint-management controls. - Troubleshoot basic wired and wireless connectivity, Wi-Fi, DHCP, DNS, VPN, printers, and office-network issues, escalating advanced problems as needed. - Follow least-privilege, approval, confidentiality, and security requirements in all support activities. Documentation & Team Contribution: - Create and maintain clear documentation for recurring support tasks, common fixes, onboarding/offboarding procedures, and device standards. - Identify repetitive support problems that can be reduced through standardization, training, documentation, or automation. - Share knowledge with other support staff and help maintain consistent service practices across locations. - Participate in IT process improvement, asset-management, security-awareness, and operational-readiness initiatives. Required Qualifications: - Professional experience in desktop support, help desk, field support, or a similar IT support role. - Strong troubleshooting skills with Windows endpoints and common business technology. - Working knowledge of Microsoft 365 and user-account support. - Understanding of MFA, permissions, endpoint management, and basic identity and access concepts. - Basic networking knowledge including TCP/IP, Wi-Fi, DHCP, DNS, and VPN troubleshooting. - Strong customer-service, communication, organization, documentation, and follow-through skills. - Ability to handle confidential information responsibly and recognize when an issue may have security implications. Preferred Qualifications: - Experience with Microsoft Intune, Microsoft Entra ID, Microsoft Defender, or comparable endpoint and identity platforms. - Experience with Ubiquiti / UniFi networking or other managed network environments. - Experience supporting multiple offices, distributed users, IT asset-management systems, or ticketing/service-management platforms. - Relevant Microsoft, CompTIA, or comparable industry certifications. Success in This Role: - Employees receive timely, professional support and know the status of their requests. - New employees receive properly configured, secure devices and departing employees are offboarded consistently. - Endpoints remain accurately inventoried, properly managed, and compliant with RockForce standards, with a small ready-to-deploy hardware stock maintained for urgent needs. - Routine issues are resolved at Tier 1 while complex or security-sensitive problems are escalated promptly and with useful documentation. - Recurring support demand decreases over time through better documentation, standardization, and process improvement. The role is hybrid, with 2-4 days in-office in OKC, Oklahoma. Now we need to output HTML with sections: About the role (maybe combine About Rockforce and Position Summary?), Responsibilities (all duty bullets), Requirements (Required Qualifications), Skills (Preferred Qualifications), Schedule (hybrid info). Possibly also a section for Success in This Role? Could be part of Responsibilities or maybe a separate "Outcomes" but not in list. Since we prefer few substantive sections, we could incorporate Success in This Role into Responsibilities or maybe a separate "Outcomes" but not required. Better to keep as part of Responsibilities? It describes expected outcomes, not duties. Could be a separate section "Expectations" but not in examples. Might be okay to add a section "Success in This Role" as a heading, but instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings, but says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; but we could also use others if needed. However to be safe, we can map Success in This Role to Responsibilities or maybe a separate "Outcomes" but not listed. I'd incorporate into Responsibilities as a bullet list of expected outcomes. Thus sections: - About the role: combine About Rockforce and Position Summary? Actually Position Summary is about the role; we can include both. - Responsibilities: all duty bullet points from Core Responsibilities, Onboarding..., Hardware..., Identity..., Documentation...,