Senior Lead Network Engineer

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 need to parse the posting. First, job title: Senior Network Engineer (but we do not repeat as heading). Employment Type: Full Time, Department: Information Technology. We need to extract sections. Let's read the posting: "Senior Network EngineerEmployment Type: Full TimeDepartment: Information Technology CGS is seeking an experienced Senior Lead Network Engineer to join a team focused on the evaluation, enhancement, and maintenance of a large-scale network project that includes both wired and wireless network infrastructure and related hardware & software. The project's objectives are to evaluate the current setup of existing disparate networks and design & implement a network infrastructure that encompasses the wireless, wired, and software network requirements. The project will also include consultation regarding hardware and software necessary to facilitate the proper support for this encompassing infrastructure, and the associated systems testing, vulnerability assessments, and quality assurance needed to implement the new setup. This Network Engineer will interface with state and local governmental personnel, internal stakeholders, subject matter experts, and vendor(s) who will provide development services. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities. Skills and attributes for success:- Operate and manage NPS network infrastructure;- Improve infrastructure monitoring and reporting capabilities based on the deployment of network management software;- Develop, maintain and deliver infrastructure documentation relating to the network infrastructure within the NPS environment;- Review current best practices and provide recommendations for architecture, design, management and operation of the network infrastructure;- Administration of the Cloudpath (or equivalent) onboarding process, monitoring and troubleshooting of wireless network health, maintenance of wireless network infrastructure, implementation of network security patches and software/firmware updates, from 0800 to 1700 PST, Monday-Friday;- Assess the NPS network infrastructure and make recommendations on improvement and optimization;- Define and conduct testing procedures for new infrastructure projects;- Implement technology solutions within the NPS network environment;- Provide design guidance on network solutions within NPS infrastructure projects;- Provide informal training and knowledge transfer to NPS resources on best practices and theory of operation relating to network products. Qualifications:- Bachelor’s Degree from an accredited college or university in Engineering, Computer Science, Business, Information systems or a related discipline.- Strong documentation skills including updating JIRA Tickets, Wiki Pages and Network Diagrams- Ability to communicate with end users, cross-organizational staff and technical assistance center.- CWNA Certification or equivalent- BCNE Certification or equivalent- Experience utilizing (RF) site survey tools such as Ekahau, RF Scanners and Wireshark packet capture software- Strong knowledge of layer 2 switching and layer 3 routing protocols; including VLANs, 802.1w, OSPF and VRRP- Strong knowledge of network security including; 802.1x, MAC Authentication, ACLs, RADIUS and Certificate of Authority (CA)- Strong knowledge of troubleshooting RF and LAN issues- Working knowledge of LINUX, MS Server 2013, VMware, etc.- A Master’s Degree in Engineering, Computer Science, Business, Information systems or a related discipline- At least 3 years experience with disaster recovery plan creation / implementation testing or projects - Experience with penetration testing, vulnerability assessment, and vulnerability testing- Experience with cyber threat information collection and analysis- Working knowledge of Agile/SCUM project management methodologies- Additional Industry certifications/licences Our Commitment:Contact Government Services (CGS) strives to simplify and enhance government bureaucracy through the optimization of human, technical, and financial resources. We combine cutting-edge technology with world-class personnel to deliver customized solutions that fit our client’s specific needs. We are committed to solving the most challenging and dynamic problems. For the past seven years, we’ve been growing our government-contracting portfolio, and along the way, we’ve created valuable partnerships by demonstrating a commitment to honesty, professionalism, and quality work.Here at CGS we value honesty through hard work and self-awareness, professionalism in all we do, and to deliver the best quality to our consumers mending those relations for years to come. We care about our employees. Therefore, we offer a comprehensive benefits package.- Health, Dental, and Vision- Life Insurance- 401k- Flexible Spending Account (Health, Dependent Care, and Commuter)- Paid Time Off and Observance of State/Federal Holidays Contact Government Services, LLC is an Equal Opportunity Employer. Applicants will be considered without regard to their race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or status as a protected veteran. Join our team and become part of government innovation!Explore additional job opportunities with CGS on our Job Board:https://cgsfederal.com/join-our-team/For more information about CGS please visit: https://www.cgsfederal.com or contact:Email: [email protected] #CJ$80,000 - $200,000 a yearWe may use artificial intelligence (AI) tools to support parts of the hiring process, such as reviewing applications, analyzing resumes, or assessing responses and identifying potential inconsistencies or verification signals in application materials based on available information. These tools assist our recruitment team but do not replace human judgment. Final hiring decisions are ultimately made by humans. If you would like more information about how your data is processed, please contact us." We need to remove boilerplate: EEO, contact info, AI note, etc. Also remove duplicated lines, navigation, legal, etc. We need to preserve substantive info. We need sections: About the role (maybe the introductory paragraph), Responsibilities (list of duties), Requirements (maybe qualifications?), Skills (maybe skills and attributes), Benefits, Pay, Schedule. We need to decide what content belongs where. The posting includes: - Intro: "CGS is seeking an experienced Senior Lead Network Engineer to join a team focused on the evaluation, enhancement, and maintenance of a large-scale network project that includes both wired and wireless network infrastructure and related hardware & software. The project's objectives are to evaluate the current setup of existing disparate networks and design & implement a network infrastructure that encompasses the wireless, wired, and software network requirements. The project will also include consultation regarding hardware and software necessary to facilitate the proper support for this encompassing infrastructure, and the associated systems testing, vulnerability assessments, and quality assurance needed to implement the new setup. This Network Engineer will interface with state and local governmental personnel, internal stakeholders, subject matter experts, and vendor(s) who will provide development services. CGS brings motivated, highly skilled, and creative people together to solve the government’s most dynamic problems with cutting-edge technology. To carry out our mission, we are seeking candidates who are excited to contribute to government innovation, appreciate collaboration, and can anticipate the needs of others. Here at CGS, we offer an environment in which our employees feel supported, and we encourage professional growth through various learning opportunities." That could be About the role. Then "Skills and attributes for success:" list of bullet points (starting with Operate and manage NPS network infrastructure; etc). Those could be Responsibilities or Skills. Then "Qualifications:" list of bullet points (starting with Bachelor’s Degree...). Those could be Qualifications. Then "Our Commitment:" paragraph about CGS mission etc. Could be About the company but not needed. Then benefits list: "- Health, Dental, and Vision- Life Insurance- 401k- Flexible Spending Account (Health, Dependent Care, and Commuter)- Paid Time Off and Observance of State/Federal Holidays". That is Benefits. Pay: "#CJ$80,000 - $200,000 a year". That's Pay. Schedule: There's mention "from 0800 to 1700 PST, Monday-Friday;" within one bullet point under Skills and attributes for success. That indicates schedule: 8am-5pm PST Monday-Friday. So we can extract schedule. We need to avoid repeating job title as heading. We need to not include placeholders like "commensurate with experience". Not present. We need to output only HTML fragment. We need to use

for section headings. We need to use

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

  for prose. We need to decide which sections to include. Potential sections: - About the role (intro paragraph) - Responsibilities (maybe the skills and attributes list? Actually those are duties/responsibilities) - Requirements (maybe qualifications) - Skills (maybe separate from responsibilities? But we have both skills and qualifications. Could combine qualifications as Requirements, and skills as Skills. But we need to avoid thin sections. Let's see content. Responsibilities list: The bullet points under "Skills and attributes for success:" are actually responsibilities/duties. They include operating network, improving monitoring, documentation, reviewing best practices, administration of Cloudpath, assessing infrastructure, define testing, implement solutions, provide design guidance, provide training. Those are responsibilities. Qualifications list: Bachelor's degree, documentation skills, communication ability, CWNA, BCNE, experience with RF site survey tools, knowledge of layer 2/3, network security, troubleshooting RF/LAN, working knowledge of LINUX/MS Server/VMware, Master's degree, 3 years disaster recovery, penetration testing, cyber threat info, Agile/SCUM, additional certifications. That's qualifications. Skills: Could be overlapping; but we could treat the qualifications as Requirements, and maybe we don't need a separate Skills section. However the instruction says we can have Skills section if posting has real specific content for it. The posting includes "Skills and attributes for success:" which is a list of skills/attributes. That could be considered Skills section. But we already used that list for Responsibilities. However we could split: Responsibilities could be the duties (like operate, improve, develop, review, administration, assess, define, implement, provide design guidance, provide training). Skills could be the technical skills like knowledge of protocols, certifications, tools, etc. But the bullet list includes both. Better to follow the posting: They have a "Skills and attributes for success:" list. That could be considered Skills section. Then Qualifications separate. Thus we can have: - About the role (intro paragraph) - Responsibilities (maybe we could extract from the Skills and attributes list? But that list is labeled Skills and attributes for success. Might be better to treat as Skills. However we need Responsibilities section if there are duties listed elsewhere. The posting does not have a separate "Responsibilities" heading; but we can infer responsibilities from the Skills and attributes list. However the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which headings to include based on content. We have content for About the role (intro). We have content for Skills (the list). We have content for Qualifications (the list). We have Benefits (list). We have Pay (salary range). We have Schedule (8am-5pm PST Mon-Fri). We may not have a distinct Responsibilities section separate from Skills; but we could treat the Skills list as Responsibilities. However we already have Skills heading; we could also have Responsibilities heading with same list? That would duplicate. Better to assign the list to either Responsibilities or Skills, not both. Given the posting explicitly says "Skills and attributes for success:" we should map that to Skills section. Then we need Responsibilities maybe from other parts? The intro includes some responsibilities like "interface with state and local governmental personnel..." but that's more about role. Could treat that as About the role. Thus we may omit Responsibilities section if no distinct responsibilities beyond skills. But the instruction says "Prefer a few substantive sections over