IT Senior Operations Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Hensel Phelps" then "Job Description". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real, specific content. We have content: About Hensel Phelps description (company overview) maybe treat as "About the role"? Actually "About Hensel Phelps" is company description, not role. Could be considered "About the role"? Might be better to have a section "About the role" containing the Hensel Phelps description? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We have: - Job Description: description of role responsibilities (list). That's Responsibilities. - Key Responsibilities: list of duties. - Qualifications: list of qualifications. - Physical Requirements: maybe not a standard heading; could be omitted or put under Requirements? But we only include sections when real specific content. Physical Requirements is specific; but not in list of allowed headings. We could maybe put under Requirements? But better to follow allowed headings: we have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications section already. We have Responsibilities (Key Responsibilities). We have Benefits. We have Pay (Compensation Data). We have maybe Skills? Could extract from Qualifications some skills but we already have Qualifications. Could combine Qualifications and Skills? But we should not invent sections. If we have both Qualifications and Skills content, we could separate. The posting includes many technical skills under Qualifications. Could treat those as Skills section. But we already have Qualifications (education, experience). Might split: Qualifications for education/experience, Skills for technical skills. However the instruction says prefer a few substantive sections over many thin ones. So maybe combine into Qualifications (includes education, experience, skills). But we have a separate "Qualifications" heading in the posting; we can keep that as

Qualifications

. Then we could have

Responsibilities

for Key Responsibilities. For company overview, we could use

About the role

containing the Hensel Phelps description. Benefits:

Benefits

. Pay:

Pay

with compensation data. Schedule: not provided, so omit. We must not include boilerplate like EEO, etc. We need to preserve all substantive information. So we need to include the Hensel Phelps overview text, the job description paragraph, the list of responsibilities (the bullet list), qualifications list, physical requirements? The physical requirements are substantive; we need to include them somewhere. Since we don't have a specific heading for physical requirements, we could include under Qualifications or maybe under Requirements. The allowed heading "Requirements" could encompass physical requirements and maybe other requirements like certifications, driver's license. So we can make a

Requirements

section that includes physical requirements, certifications, driver's license, etc. But we already have Qualifications heading used for education/experience etc. Might be overlapping. Let's think: The posting has "Qualifications" section with bullet list of abilities, knowledge, etc. Then after that there is "Physical Requirements". Then "Education". Then "Compensation Data". Then "Benefits". Then EEO. We could treat: - About the role: company overview. - Responsibilities: Key Responsibilities list. - Requirements: Physical Requirements + Certifications + Driver's license + maybe Education? But Education is separate. - Qualifications: maybe the bullet list of technical skills and abilities. But we have both Qualifications and Requirements as allowed headings. We could assign: - Requirements: Physical Requirements, Certifications (ITIL preferred), Valid driver's licence. - Qualifications: Education (College diploma or university degree...), plus the bullet list of abilities/knowledge/experience. But the bullet list under "Qualifications" in the posting includes many items like "Ability to lead a team...", "Extensive hands-on technical knowledge...", etc. Those are qualifications indeed. So we can put them under Qualifications. Education is also a qualification but we could keep under Qualifications as well. Thus we can have:

About the role

with Hensel Phelps overview.

Responsibilities

with the paragraph "The Senior IT Operations Engineer’s role is to supervise..." plus the list of responsibilities (the bullet list after Key Responsibilities). Actually the posting includes a paragraph then "Key Responsibilities" then a list. We'll combine.

Requirements

with Physical Requirements text, plus Certifications in ITIL preferred, Valid drivers licence.

Qualifications

with Education bullet and the bullet list of abilities/knowledge/experience (the long list). Might be large but okay.

Benefits

with benefits description.

Pay

with compensation data. We must not include schedule. We must not repeat job title. We must not include boilerplate. We must output only HTML fragment. We need to use

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

  for prose. Thus for each section, we need to decide if content is prose or list. About the role: prose (multiple sentences). Use

  . Responsibilities: we have a paragraph describing role then a list of responsibilities. Could do

  for the intro paragraph then

  • for each bullet. Requirements: Physical Requirements is prose (multiple sentences). Then Certifications and Driver's licence could be list items. Could do

    for Physical Requirements then

    • for Certifications and Driver's licence. Qualifications: Education is a sentence; then the bullet list of abilities etc. Could do

      for Education then

      • for each bullet. Benefits: prose description; could be

        . Pay: prose with compensation data; could be

        . We must preserve all substantive information. Ensure we don't miss any details. Let's extract text precisely. About Hensel Phelps: "At Hensel Phelps, we don’t just build projects—we build careers, communities, and a culture of excellence. As an employee-owned company, every person here plays a vital role in shaping our success and future. Guided by our core values of Ownership, Integrity, Builder mindset, Diversity, and Community, we combine cutting-edge technology with hands-on expertise to deliver landmark projects across the nation. When you join Hensel Phelps, you join a team that values your growth, empowers your ideas, and invests in your journey. Together, we create an environment where innovation thrives, safety is paramount, and every individual has the opportunity to make a lasting impact." Job Description paragraph: "The Senior IT Operations Engineer’s role is to supervise the design, build, and implementation of network systems across the operational region. This includes planning, developing, installing, configuring, maintaining, supporting, and optimizing all local and wide area network connections, project servers, associated software, and communication links. Senior IT Operations Engineers are also responsible for providing desktop support to end users in our regional office and at regional project locations. This person will also maintain proper end user configuration, IT hardware inventory, licensing, and PC/end user onboarding and offboarding of all IT equipment, including PC setup, troubleshooting, and security controls." Key Responsibilities list (each bullet): - Collaborate with executive management and department leaders to assess near- and long-term IT capacity needs - Create and maintain documentation as it relates to IT configuration, processes, and service records - Develop, implement, and maintain policies, procedures, and associated training plans for IT administration, usage, and disaster recovery - Lead in the development and implementation of policies for network asset management, including maintenance of network component inventory, related documentation, and technical specifications information - Lead in the development and implementation of policies for end user devices such as: desktop, laptop and mobile - Conduct research on IT products, services, protocols, and standards to remain abreast of developments in the technology industry - Oversee new and existing equipment, hardware, and software upgrades - Interact and negotiate with vendors, outsourcers, and contractors for IT products and services - Plan and implement any improvement, modification, or replacement of IT infrastructure components - Plan and manage budgeting for IT hardware and software procurement - Lead in the development and implementation of policies, procedures, and associated training for IT resource administration, appropriate use, and disaster recovery - Establish connectivity and uptime service level agreements - Supervise daily IT operations to ensure smooth and reliable function for fulfilling business objectives and processes - Monitor network performance and troubleshoot problem areas as needed - Oversee installation, configuration, maintenance, and troubleshooting of end-user workstation hardware, software, and peripheral devices - Ensure network connectivity of all servers, workstations, telephony equipment, fax machines, and other network appliances - Manage servers, including database, e-mail, print, and backup servers and their associated operating systems and software - Practice network asset management, including maintenance of network component inventory and related documentation and technical specifications information - Monitor and test network performance and provide network performance statistics and reports - Participate in managing all network security solutions - Perform server and security audits, and system backups and recovery - Manage and/or provide guidance to junior members of the team. Qualifications bullet list (under "Qualifications"): - Ability to lead a team of IT Engineers and projects - Extensive hands-on technical knowledge of network systems, protocols, and standards - Strong knowledge and experience with Microsoft Azure Active Directory Services, Windows Server OS, Office 365, VMware and virtualization technologies - Hands-on experience and current knowledge of network management and analysis tools such as Cisco technologies like Secure Endpoint, Umbrella, NAM, AnyConnect - Extensive client/server and operating system experience including imaging tools such as Microsoft Deployment Tool (MDT) server management - Experience working in a switched and routed environment - Hardware, software, and network connection troubleshooting experience - Working technical knowledge of current network hardware - Skilled at installing/configuring firewalls, switches, routers, wireless bridges, etc - Knowledge of security software, firewalls, intrusion detection systems, and other network security measures - Knowledge of current CMMC standardization and policies a plus - Knowledge of applicable data privacy practices and laws - Construction industry software knowledge in products such as, Autodesk-BIM Modeling, scheduling tools Asta & Oracle P6, Bluebeam PDF, Onscreen Takeoff a plus - Good working knowledge of Microsoft software including SharePoint, Azure, Exchange, Intune, and Teams - Telephony knowledge of Poly, Crestron, and AMX room AV systems a plus - Strong interpersonal, written, and oral communication skills - Able to conduct research into networking issues and products as required - Ability to present ideas in user-friendly language - Highly self-motivated and directed, with keen attention to detail - Proven analytical and problem-solving abilities - Able to effectively prioritize tasks in a high-pressure environment - Strong customer service orientation - Experience leading a team-oriented, collaborative environment. - Certifications in ITIL preferred - Valid drivers licence Note: The last two bullets are actually certifications and driver's licence, but they appear in the Qualifications list. However we might want to move them to Requirements. But we can keep them in Qualifications; but then we would duplicate if we also have Requirements section. Better to follow the posting: they are under Qualifications. So we keep them there. Then we might not need a separate Requirements section; we could put Physical Requirements under Requirements. But we still have Certifications and Driver's licence in Qualifications; that's okay. Thus we can have: - About the role: company overview. - Responsibilities: role description paragraph + list. - Requirements: Physical Requirements only (maybe also include any other requirements not covered elsewhere).