End User Computing Analyst

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have description, duties & responsibilities, essential functions, skills, qualifications, job type & location, pay and benefits, workplace type, application deadline, about TEKsystems (boilerplate). We need to remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions (deadline maybe considered application instruction? The instruction says remove application instructions. The "Application Deadline" is likely an application instruction; we should drop it. Also "Job Type & Location" maybe we keep location? The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

or drop it. Job type & location could be considered minor metadata; but location is relevant. Could include in a short paragraph under About the role? Probably better to include location in a paragraph under About the role or as a separate short p. However we must not create sections for Schedule unless posting actually states schedule. It says Workplace Type: fully onsite. That's schedule? Not exactly schedule but location. Could include in a paragraph. We need sections: About the role (maybe a brief summary). Responsibilities (duties). Requirements (maybe qualifications). Qualifications (maybe separate). Skills (list). Benefits (list). Pay (range). Schedule? Not given explicit schedule like hours; we have fully onsite but not schedule. So we should not create Schedule section. We must not repeat job title as heading. The job title is not given explicitly but we can ignore. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all duties, responsibilities, essential functions, skills, qualifications, benefits, pay, location, workplace type. We need to format using

for section headings. Use

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

  for prose. We need to decide which content goes where. Let's extract: Description: "Provide Tier 2 end-user technical support by troubleshooting, tracking, resolving, and communicating technology issues. This role supports break/fix activities, IMAC (Install, Move, Add, Change) requests, endpoint device support, and IT asset management processes to ensure a reliable and efficient user computing environment." That's a prose summary; could go under About the role. Duties & Responsibilities bullet list (multiple sentences). We'll put under Responsibilities as

  • . Essential Functions list similar to duties; might be redundant. We could combine or keep but avoid duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we combine we might lose some nuance but still preserve. However essential functions list is similar to duties; we could merge them but ensure we keep all points. Let's list each unique point. Duties & Responsibilities points: - Troubleshoot, document, track, and resolve hardware, software, and connectivity issues within the end-user environment. - Provide break/fix support for desktops, laptops, tablets, mobile devices, printers, and related peripherals. - Fulfill installation, move, add, and change (IMAC) requests for end-user technology equipment. - Provide Tier 2 technical support and serve as an escalation point for complex user issues. - Configure, deploy, maintain, and troubleshoot endpoint devices and software applications. - Support Microsoft 365 applications, Outlook, Active Directory, and enterprise desktop technologies. - Assist with software deployments, device refreshes, and workstation migrations. - Support IT asset lifecycle processes including inventory tracking, deployment, recovery, and disposal. - Escalate issues when appropriate and collaborate with other IT teams to ensure timely resolution. - Maintain accurate incident, service request, and asset documentation. - Deliver exceptional customer service while supporting users in high-pressure situations. Essential Functions points (some overlap): - Provide break/fix support for end-user devices and applications. - Support IMAC activities and endpoint deployments. - Manage and support IT asset management processes. - Deliver Tier 2 support for desktops, laptops, tablets, mobile devices, and printers. - Troubleshoot and resolve hardware, software, and access-related issues. - Maintain asset and support documentation. These are largely covered. To preserve all, we could keep both lists but note duplication. Might be okay to keep both as separate
    under Responsibilities? But that would be repetitive. The instruction: "Prefer a few substantive sections over many thin ones." So we should combine into one Responsibilities section, merging unique points, ensuring we don't lose any. Let's create a combined list that includes all points from both, removing exact duplicates. Let's compile unique items: 1. Troubleshoot, document, track, and resolve hardware, software, and connectivity issues within the end-user environment. 2. Provide break/fix support for desktops, laptops, tablets, mobile devices, printers, and related peripherals. 3. Fulfill installation, move, add, and change (IMAC) requests for end-user technology equipment. 4. Provide Tier 2 technical support and serve as an escalation point for complex user issues. 5. Configure, deploy, maintain, and troubleshoot endpoint devices and software applications. 6. Support Microsoft 365 applications, Outlook, Active Directory, and enterprise desktop technologies. 7. Assist with software deployments, device refreshes, and workstation migrations. 8. Support IT asset lifecycle processes including inventory tracking, deployment, recovery, and disposal. 9. Escalate issues when appropriate and collaborate with other IT teams to ensure timely resolution. 10. Maintain accurate incident, service request, and asset documentation. 11. Deliver exceptional customer service while supporting users in high-pressure situations. 12. Support IMAC activities and endpoint deployments. (similar to #3 and #5? but we can keep as separate nuance) 13. Manage and support IT asset management processes. (similar to #8) 14. Deliver Tier 2 support for desktops, laptops, tablets, mobile devices, and printers. (similar to #2 and #4) 15. Troubleshoot and resolve hardware, software, and access-related issues. (similar to #1) Given duplication, we can keep a concise list that covers all aspects without repeating same idea. The instruction says preserve ALL substantive information; does that mean we must keep each sentence? Likely yes, we should not omit any substantive detail. However if we combine and still convey same meaning, it's okay. But to be safe, we could keep both lists but under same section, maybe separate headings? But we cannot create extra headings besides the allowed ones. Could we use

    to separate? We could put both lists as separate

    under Responsibilities, but that would be repetitive but still preserve all info. The instruction: "Prefer a few substantive sections over many thin ones." Having two lists under same section is okay. Thus we can output Responsibilities with two
    blocks: one for Duties & Responsibilities, one for Essential Functions. That preserves all. Now Requirements vs Qualifications: The posting has "Qualifications" section with Experience, Knowledge, Skills & Abilities. Also there is a "Skills" list separate. So we can have: - Requirements: maybe experience requirements? Could be under Qualifications. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes under Requirements vs Qualifications. Usually Requirements are the mandatory experience/education; Qualifications could be preferred or additional. The posting has "Experience 3+ years..." under Qualifications heading. Also "Knowledge, Skills & Abilities". So we could treat that as Qualifications. Requirements could be maybe none? But we must include a section only when posting has real specific content. If we don't have distinct Requirements content, we should omit Requirements section. However we have "Experience 3+ years..." etc. That's under Qualifications. So we can put that under Qualifications. The separate "Skills" list is under Skills heading. Thus we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Possibly also Workplace Type (location) could be included in About the role as a paragraph. We must not include Schedule as no schedule info. Now extract content: About the role: description paragraph plus location and workplace type. Description: "Provide Tier 2 end-user technical support by troubleshooting, tracking, resolving, and communicating technology issues. This role supports break/fix activities, IMAC (Install, Move, Add, Change) requests, endpoint device support, and IT asset management processes to ensure a reliable and efficient user computing environment." Location: "This is a Contract to Hire position based out of Merrill, WI." Also "Workplace Type: This is a fully onsite position in Merrill,WI." We can combine: "This is a Contract to Hire position based out of Merrill, WI. The role is fully onsite." We'll put as

    . Now Responsibilities: two

    blocks. First
    for Duties & Responsibilities (list as above). Second
    for Essential Functions. We need to ensure we don't miss any point. Let's list Duties & Responsibilities exactly as given: - Troubleshoot, document, track, and resolve hardware, software, and connectivity issues within the end-user environment. - Provide break/fix support for desktops, laptops, tablets, mobile devices, printers, and related peripherals. - Fulfill installation, move, add, and change (IMAC) requests for end-user technology equipment. - Provide Tier 2 technical support and serve as an escalation point for complex user issues. - Configure, deploy, maintain, and troubleshoot endpoint devices and software applications. - Support Microsoft 365 applications, Outlook, Active Directory, and enterprise desktop technologies. - Assist with software deployments, device refreshes, and workstation migrations. - Support IT asset lifecycle processes including inventory tracking, deployment, recovery, and disposal. - Escalate issues when appropriate and collaborate with other IT teams to ensure timely resolution. - Maintain accurate incident, service request, and asset documentation. - Deliver exceptional customer service while supporting users in high-pressure situations. Essential Functions list: - Provide break/fix support for end-user devices and applications. - Support IMAC activities and endpoint deployments. - Manage and support IT asset management processes. - Deliver Tier 2 support for desktops, laptops, tablets, mobile devices, and printers. - Troubleshoot and resolve hardware, software, and access-related issues. - Maintain asset and support documentation. We'll keep both. Now Qualifications: includes Experience, Knowledge, Skills & Abilities. We need to preserve all details. Experience: "Experience 3+ years of endpoint computing, desktop support, or technical support experience. Experience supporting enterprise end-user environments. Insurance industry experience preferred." Knowledge, Skills & Abilities bullet list: - Knowledge of Microsoft 365 and Office applications. - Knowledge of endpoint support and desktop administration practices. - Understanding of IT asset management processes and lifecycle management. - Strong troubleshooting and problem-solving skills. - Strong customer service and communication skills. - Ability to prioritize, manage, and escalate issues appropriately. - Strong collaboration, teamwork, and knowledge-sharing abilities. - Ability to adapt quickly to new technologies and changing priorities. - Strong organizational and documentation skills. - Ability to learn internal systems, processes, policies, and technologies with minimal supervision. We'll put under Qualifications as
    . Now Skills: list of skills given: "Windows 10/11, SCCM, Microsoft 365, Outlook, Active Directory, Desktop Support, Tier 2 Support, Endpoint Management, Hardware Troubleshooting, Software Deployment, Incident Management, Service Request Management, IT Asset Management, Help Desk Support, Technical Support, Customer Service, Printer Support, Laptop Support, Device Configuration, Documentation, Problem Solving" We'll put as
    • each item separated by commas? Better to split into individual li. Now Benefits: list from Pay And