Infrastructure Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate. We need to parse the posting: It includes Duties (with percentages), Skills (required, preferred, software, licenses), Schedule Notes, Education, Required Work Experience, Partial Onsite schedule, Team Name, Standard Hours, Required Technologies, Nice To Have, Day to Day, Soft Skills, The Team, Interview. We need to map to sections: About the role (maybe from Day to Day or description), Responsibilities (duties), Requirements (education, experience, certifications), Qualifications (maybe similar), Skills (required/preferred), Benefits (none given), Pay (none), Schedule (schedule notes, partial onsite, standard hours). We must not create sections with filler like "not specified". So only include sections where we have content. We have schedule notes: "IS - Credit Check Required / No Subcontractors Required". Also "Partial Onsite - Tuesday, Wednesday, Thursday onsite and as needed." and "Standard Hours: 8:00 AM – 5:00 PM". So schedule section can contain that. We have no explicit Benefits or Pay. So we omit those sections. We have "Team Name: Network Change". Could be part of About the role or The Team. We'll include About the role summarizing role purpose. We have Duties with percentages. We'll put under Responsibilities as list. We have Skills: Required Skills and Abilities, Required Software and Other Tools, Preferred Skills and Abilities, Preferred Software and Other Tools, Preferred Licenses and Certificate, Required Licenses and Certificates. We'll combine into Skills section with sublists maybe. We have Education, Required Work Experience, maybe also Required Technologies, Nice To Have, Day to Day, Soft Skills, The Team, Interview. Those could go under Requirements or Qualifications. We need to decide. We have sections: Requirements (education, experience, certifications). Qualifications maybe similar but we can combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. But we can also just use Requirements for education/experience/certifications, and Qualifications for maybe required technologies, nice to have, day to day, soft skills, team, interview. However we must not create sections with filler. We'll include only those with content. Let's extract: About the role: Could be from "Day to Day: This role is responsible for managing the most complex, project-driven work within the Deployment Management Methodology (DMM) framework." plus maybe "The Team: The Network Change Team is responsible..." We'll combine. Responsibilities: Duties list with percentages. Requirements: Education, Required Work Experience, Required Licenses and Certificates (C2 certification), maybe also Required Technologies? But Required Technologies could be under Qualifications. Qualifications: Preferred Skills, Preferred Software, Preferred Licenses, Nice To Have, Required Technologies, Soft Skills, The Team, Interview. Skills: Required Skills and Abilities, Required Software and Other Tools. But note that Required Skills and Abilities overlap with Skills section. We'll put Required Skills and Abilities under Skills. Preferred Skills and Abilities maybe under Qualifications. Let's structure:

About the role

... (combined description)

Responsibilities

• ... each duty with percentages

Requirements

• Education: Bachelor's degree in Computer Science, Information Technology or other job related degree. or 4 years of job related work experience or 2 years of job related experience plus an associate's degree in Computer Science, Information Technology or other job related degree
• Required Work Experience: 8 years of hands-on experience building or supporting IT infrastructure (servers and/or networks).
• Required Licenses and Certificates: C2 certification required by DOD (TRICARE)

Qualifications

• Required Technologies: Hands-on experience building and support IT infrastructure (servers and networks). Application design experience. Cisco ACI and GitHub experience for Software Defined Networks.
• Nice To Have: Skilled in multiple disciplines of Windows Server, RHEL, OpenShift, BIGIP, Cisco, Telephony systems, IBM/Hitachi SAN/NAS storage.
• Preferred Skills and Abilities: Skilled in multiple disciplines of Windows Server, AIX, SUN Solaris, BIGIP, Juniper, Cisco, Telephony systems, EMC/IBM/Hitachi SAN/NAS storage.
• Preferred Software and Other Tools: Expert-level proficiency for Visio.
• Preferred Licenses and Certificate: MCSE, CCDA or CCDP.
• Soft Skills: Attention to detail, ability to effectively communicate with peers and partner IT teams, ability to pivot to multiple tasks, strong troubleshooting skills.
• The Team: The Network Change Team is responsible for making the changes required to facilitate all connectivity for the entire Client Organization. This team plays a crucial role in ensuring the security, efficiency, and reliability of the organization's network infrastructure. We are a collaborative team that is focused on providing support to our customers to ensure the business applications they support are available and operational.
• Interview: One interview On-Site Management Interview (up to 90 minutes)

Skills

• Required Skills and Abilities: In-depth knowledge of server technology and associated operating systems (Windows Server, AIX, Linux, and/or Sun). In-depth knowledge of network technologies and TCP/IP.
• Required Software and Other Tools: Microsoft Office and Visio.

Schedule

• IS - Credit Check Required / No Subcontractors Required
• Partial Onsite - Tuesday, Wednesday, Thursday onsite and as needed.
• Standard Hours: 8:00 AM – 5:00 PM

We must not include Benefits or Pay. Check for any duplicated lines: Ensure we didn't repeat. Check that we preserved all substantive info: Let's verify. Original Duties: includes percentages and details. We captured each bullet. We need to ensure we didn't lose any detail: The Duties bullet list: - Responsible for project driven work within the framework of Deployment Management Methodology (DMM). Assesses customer requirements and approved technical solutions developed by the solutions team, determines infrastructure changes (for both server and network) required to deploy the solution, and creates detailed deployment specification documents to be used by deployment teams for making infrastructure change. Incorporates guidance from other areas such as Architecture, Security and Operations. 35% - Assesses and determines server specifications to meet project requirements, including number and size of non-host (distributed) servers, storage specifications, security membership, operating systems, etc. Produces project deliverables/documentation in the form of detailed "build " specifications. Routinely designs and specifies server infrastructure requiring expertise in a single operating system platform. 35% - Assesses and determines network design specifications to meet project requirements, including all connectivity, network equipment, network placement, data center placement, IP address assignments, and firewall rules. Produces project deliverables/documentation in the form of detailed "build " specifications and network diagrams. 20% - Assesses existing network infrastructure and produces detailed network diagrams to meet special requests (not deployment projects) such as responding to requests associated with a security compliance audits. 5% - Performs non-project technical consultation with Customers, Client Advocates, or Application Owners. 5% - Provides Network/IP address assignments for non-project requests. 5% We need to include each bullet with its percentage. We'll embed percentages inside bullet. Now About the role: We used Day to Day and The Team. Also maybe include "Team Name: Network Change". We'll incorporate. Let's craft About the role paragraph: "This role is responsible for managing the most complex, project-driven work within the Deployment Management Methodology (DMM) framework. Key responsibilities include assessing customer requirements, evaluating approved technical solutions from the solutions team, and determining necessary infrastructure changes for both servers and networks. The role involves creating detailed deployment specification documents for use by deployment teams and incorporating guidance from Architecture, Security, and Operations teams. The Network Change Team facilitates all connectivity for the client organization, ensuring security, efficiency, and reliability of the network infrastructure." We should not invent info; we are summarizing but preserving meaning. The instruction says do NOT invent or summarize away detail. Summarizing may be considered summarizing away detail? It says "do NOT invent or summarize away detail". That suggests we should not omit details; we should preserve all substantive information. Summarizing may lose detail. Better to keep the exact sentences from Day to Day and The Team without summarizing. So we can directly include those sentences. Thus About the role can contain the Day to Day sentence and The Team sentence, plus maybe Team Name. Let's do:

This role is responsible for managing the most complex, project-driven work within the Deployment Management Methodology (DMM) framework. Key responsibilities include assessing customer requirements, evaluating approved technical solutions from the solutions team, and determining necessary infrastructure changes for both servers and networks. The role involves creating detailed deployment specification documents for use by deployment teams and incorporating guidance from Architecture, Security, and Operations teams.

The Network Change Team is responsible for making the changes required to facilitate all connectivity for the entire Client Organization. This team plays a crucial role in ensuring the security, efficiency, and reliability of the organization's network infrastructure. We are a collaborative team that is focused on providing support to our customers to ensure the business applications they support are available and operational.

That's directly from the text. Now Responsibilities: list each duty with percentages. We'll produce

• ... 35%
etc. Now Requirements: Education, Required Work Experience, Required Licenses and Certificates. We need to include Education exactly: "Bachelor's degree in Computer Science, Information Technology or other job related degree. or 4 years of job related work experience or 2 years of job related experience plus an associate's degree in Computer Science, Information Technology or other job related degree". Keep as is. Required Work Experience: "8 years of hands-on experience building or supporting IT infrastructure (servers and/or networks)." Required Licenses and Certificates: ""C2 " certification required by DOD (TRICARE)" (note there are spaces and quotes). We'll keep exactly: "C2 certification required by DOD (TRICARE)" maybe preserve quotes? The original: ""C2 " certification required by DOD (TRICARE)". We'll output as is. Now Qualifications: include Required Technologies, Nice To Have, Preferred Skills and Abilities, Preferred Software and Other Tools, Preferred Licenses and Certificate, Soft Skills, The Team, Interview. But we already used The Team in About the role; we might duplicate. To avoid duplication, we could omit The Team from Qualifications and keep only in About the role. However we already used The Team sentences there. So we should not repeat. Let's check if we used The Team sentences in About the role: yes we included both sentences. So we should not repeat The Team in Qualifications. Thus Qualifications will contain: Required Technologies, Nice To Have, Preferred Skills and Abilities, Preferred Software and Other Tools, Preferred Licenses and Certificate, Soft Skills, Interview. Check if any other info: "Team Name: Network Change" not yet used. Could add to About the role or Qualifications. We'll add to About the role as a sentence: "Team Name: Network Change." But that's minor metadata; we can fold into short p. We'll add a short p: "