Salt Lake City - MIT Engineer III

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Les Olson IT" (company description) then "Position Summary", then "What You'll Do", then "What You Bring", then "Technical Expertise", then "Preferred Experience", then "Preferred Certifications", then "Success In This Role". We need to use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we must map content to appropriate headings. The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings when appropriate. But we need to include a section only when posting has real, specific content for it. So we need to decide which sections apply. We have company description: could be "About the role"? Actually "About the role" is about the job, not company. But we have "About Les Olson IT" which is company overview. Could map to "About the role"? Might be okay but better to use "About the role" for role description. However we have "Position Summary". That could be "About the role". Use that. Responsibilities: "What You'll Do" is responsibilities. Requirements: "What You Bring" could be requirements (experience). Also "Technical Expertise" could be skills/qualifications. Qualifications: maybe "Preferred Experience" and "Preferred Certifications" could be qualifications. Skills: maybe "Technical Expertise" is skills. Benefits, Pay, Schedule: not present, so we should NOT include those sections. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information, not invent or summarize away detail. Use

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

  for prose. We need to parse the content into lists where appropriate. Let's extract sections: - About the role (Position Summary): The Engineer 3 serves as a senior technical resource within the Managed IT Services organization, responsible for complex engineering, solution design, technical leadership, automation, and operational improvement initiatives. This role supports on-premises, cloud, and hybrid customer environments while serving as a Tier 3 escalation point for complex technical issues. Engineer 3 team members are expected to look beyond individual incidents and identify systemic issues, recurring trends, and opportunities for automation that improve customer outcomes while reducing support demand, operational complexity, and organizational risk. Successful candidates are experienced technical consultants who can design solutions, lead projects, mentor engineers, and drive continuous improvement across the Managed IT Services organization. That's prose; we can put in

  . - Responsibilities (What You'll Do): It has bullet-like sentences each starting with a verb. We can turn each line into

• . The text includes multiple paragraphs grouped by categories: Infrastructure, Cloud & Hybrid Engineering; Security & Identity; Automation & Operational Efficiency; Service Optimization & Problem Management; Technical Leadership & Consulting. Each category has a heading (bold?) but we can treat each bullet as list item. We'll produce a
  with items for each sentence. Let's list them: Infrastructure, Cloud & Hybrid Engineering: - Design, deploy, support, and troubleshoot complex on-premises, cloud, and hybrid IT environments. - Design, implement, and maintain Windows Server environments utilizing current Microsoft-supported server platforms. - Design and support Active Directory and Microsoft Entra ID environments, including hybrid identity solutions. - Administer and support Microsoft 365, Google Workspace, and cloud productivity platforms. - Design, deploy, and maintain virtualization environments utilizing VMware and Hyper-V technologies. - Configure and support Azure infrastructure and cloud services. - Design and support enterprise storage, backup, disaster recovery, and business continuity solutions. - Troubleshoot advanced networking issues involving TCP/IP, DNS, DHCP, routing, switching, VPN, VLAN, and WAN technologies. - Support server, storage, virtualization, identity, and cloud infrastructure across diverse customer environments. Security & Identity: - Design and implement security best practices across customer environments. - Configure and support Microsoft Defender, endpoint security, identity protection, Conditional Access, MFA, and related security technologies. - Conduct security reviews and participate in remediation planning for identified risks and vulnerabilities. - Assist customers with security modernization initiatives and security-focused projects. - Ensure engineering solutions align with organizational and industry security best practices. Automation & Operational Efficiency: - Develop scripts, workflows, and automation utilizing PowerShell and other automation platforms. - Identify repetitive operational tasks and implement automation solutions that improve efficiency and consistency. - Design scalable solutions that reduce manual effort and improve service delivery. - Evaluate and implement tools, workflows, and integrations that improve operational effectiveness. - Leverage AI-assisted technologies, automation platforms, and modern engineering practices to improve customer and business outcomes. Service Optimization & Problem Management: - Analyze recurring incidents, service requests, and operational challenges across customer environments. - Perform root cause analysis to identify underlying causes of recurring issues. - Design and implement preventative solutions that reduce ticket volume and improve service stability. - Partner with Service Desk, Engineering, Security, and Operations teams to eliminate recurring sources of support demand. - Identify trends across customer environments and recommend improvements, standards, and automation opportunities. - Contribute to operational maturity initiatives that improve consistency, reliability, and scalability throughout the organization. Technical Leadership & Consulting: - Serve as a Tier 3 escalation resource for complex technical issues. - Lead infrastructure modernization, cloud adoption, security, migration, and transformation projects. - Mentor Engineer 1 and Engineer 2 team members through technical guidance, coaching, and knowledge sharing. - Participate in technical reviews, architecture discussions, and solution design activities. - Assist with developing and maintaining engineering standards, best practices, and deployment methodologies. - Serve as a trusted technical advisor for customers, helping align technology decisions with business objectives. - Contribute to strategic technology discussions and long-term infrastructure planning. We'll put all these as
  • under a single
    or maybe separate
    per category? The instruction: use
    • for any list of duties/requirements/benefits. Could be one list. We'll just make one
      with all items. - Requirements (What You Bring): list of bullet points. What You Bring: - 8+ years of Information Technology experience with extensive hands-on infrastructure, cloud, and systems engineering experience. - Strong customer-facing consulting and communication skills. - Experience supporting and designing on-premises, cloud, and hybrid environments. - Experience leading complex technical projects and initiatives. - Demonstrated ability to mentor and develop technical team members. - Strong analytical and problem-solving skills. - Proven ability to identify operational inefficiencies and create sustainable technical solutions. We'll make
      . - Skills (Technical Expertise): list. Technical Expertise: - Advanced Knowledge Of Microsoft 365 - Microsoft Entra ID - Active Directory - Azure cloud services - VMware and/or Hyper-V - Windows Server platforms - Google Workspace - Exchange Online - SharePoint Online - Microsoft Teams - Microsoft Intune - Backup and disaster recovery platforms - Identity and access management - Security and endpoint protection technologies - LAN/WAN networking - VPN technologies - Enterprise storage solutions - PowerShell scripting and automation We'll make
      . - Qualifications (Preferred Experience): list. Preferred Experience: - Hybrid cloud environments - Azure infrastructure - Security frameworks and best practices - Process automation and systems integration - Managed Services environments - AI-assisted operational tools and automation platforms We'll make
      . - Qualifications (Preferred Certifications): list. Preferred Certifications: - Microsoft Certified: Azure Administrator (AZ-104) - Microsoft 365 Administrator (MS-102) - Microsoft Certified Security Certifications (SC-200, SC-300, or equivalent) - VMware Certified Professional (VCP) - CompTIA Security+ - Relevant cloud, networking, virtualization, or security certifications We'll make
      . - Success In This Role: could be considered "Qualifications" or maybe "Skills"? It's more about success criteria. Could be a separate section like "Success In This Role" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could map Success In This Role to "Qualifications" or maybe "Skills". But we already have Qualifications for preferred experience/certs. We could combine success criteria into Qualifications as additional bullet points. However we must not invent or summarize away detail; we can include them as part of Qualifications. Alternatively we could create a section "Qualifications" and include both preferred experience/certs and success criteria. That seems okay. We must not create sections with filler text. All sections we create must have substantive content. Thus final HTML:

      About the role

      ...position summary...

      Responsibilities

      • ... each duty ...
      ...

      Requirements

      • ... each requirement ...
      ...

      Skills

      • ... each technical expertise ...
      ...

      Qualifications

      • ... preferred experience ...
      • ... preferred certifications ...
      • ... success criteria ...
      ...
      We need to include success criteria items as list items under Qualifications. Success In This Role bullet points: - A Successful Engineer 3 Solves complex technical problems. - Identifies and eliminates recurring issues. - Automates repetitive work. - Improves standards and operational efficiency. - Serves as a trusted advisor to customers and peers. - Mentors less experienced engineers. - Drives modernization across on-premises, cloud, and hybrid environments. - Most importantly, Engineer 3 team members are expected to look beyond the immediate incident and identify the underlying problem around the problem, implementing scalable solutions that prevent future issues and improve the overall customer experience. We'll include each as
      • . Now ensure we preserve all substantive information: we included company description? Actually we omitted "About Les Olson IT" company overview. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." The company overview is not a heading; we could include it as a paragraph under About the role? But About the role is supposed to be about the role, not company. However we could include company overview as a short paragraph before the About the role section? The instruction says we can fold minor metadata into a short

        or drop it. Company overview is not minor metadata; it's substantive about the company. But we don't have a heading for "About the company". The allowed headings list does not include "About the company". However we could treat it as part of "About the role" maybe? But that would be mixing. The instruction says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive? It says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should not create a heading for company overview. We could include the company overview as a short

        before the first heading, as minor metadata? It's not minor but maybe acceptable as a preamble. The instruction: "fold minor metadata into a short

        or drop it." Company overview might be considered minor metadata? It's about the company, not the job. Might be okay to include as a short

        before sections. Thus we will output:

        Les Olson IT is one of the fastest-growing and most capable technology service providers in the West. We do I