Infrastructure Engineer

We need to output only HTML fragment, no html/body tags. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. Let's parse. Job title: Infrastructure Engineer (not used as heading). Location: Onsite - National Business Park, Maryland. Should be folded into short

or drop. Probably include location in a

. We have description: "Nightwing provides technically advanced..." That's about the company; could be "About the role" maybe? Actually "About the role" heading should contain description of role. The first paragraph describes Nightwing capabilities; then "Nightwing is seeking an experienced Infrastructure Engineer to design, build, and maintain the backbone..." That's role description. So we can put that in About the role. Responsibilities: list of bullet points after "Responsibilities". Those are specific duties. Use

• . Requirements: maybe "Minimum Qualifications". That's qualifications. Could be Requirements heading. Use
  . Preferred Qualifications: could be Qualifications heading? Actually we have Minimum Qualifications and Preferred Qualifications. Could combine into Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we can have Requirements (minimum) and Qualifications (preferred) maybe. Or we could have Requirements for minimum, Qualifications for preferred. Or we could have Skills for specific skills. But we have many skill mentions. We also have "Why Join Us At Nightwing" which is like Benefits? Actually it's about company culture; could be Benefits? But Benefits heading should be for benefits like insurance, 401k, PTO. The posting includes "Nightwing offers medical, vision and dental insurance coverage in addition to a 401k plan, PTO, Holidays, and additional insurances." That's benefits. Also "Why Join Us" includes innovative environment, collaborative teams, opportunities to grow, mission-driven impact. That could be considered Benefits? But maybe we treat that as a separate section like "About the company" but not in allowed headings. Could fold into Benefits? Might be okay to include as Benefits? However Benefits heading should be for benefits like insurance etc. The "Why Join Us" is more about culture; we could put under a heading like "About the role"? Not ideal. Perhaps we can omit "Why Join Us" as it's not strictly required but it's substantive. The instruction: Prefer a few substantive sections over many thin ones. We could combine "Why Join Us" into Benefits? Might be okay. Pay: Salary range is given: $99,000-$206,000. Also note "commensurate with experience" but we should not include filler like "commensurate with experience" as heading content? Actually we can include the salary range and note that it's commensurate; but we should avoid placeholder like "commensurate with experience" as a heading? The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we cannot have a Pay section with just that phrase; but we have actual numbers, so we can include Pay section with the range and maybe note that it's commensurate. That's okay. Schedule: Not mentioned; no schedule info. So we should not create Schedule section. Skills: Could be a section for specific skills like Linux, networking, DevSecOps, etc. But we already have many in Responsibilities and Qualifications. Might be thin. Better to not create Skills unless we have distinct list. We could combine skills into Responsibilities or Qualifications. Thus sections: About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred qualifications), Benefits, Pay. We need to ensure we don't repeat job title as heading. Use

  for each. We need to wrap content in appropriate tags:

  for prose,

  • for lists. We must preserve all substantive information; do not invent or summarize away detail. Let's extract content. About the role: Should include description of Nightwing and role. Let's combine: "Nightwing provides technically advanced full-spectrum cyber, data operations, systems integration and intelligence mission support services to meet our customers’ most demanding challenges. Our capabilities include cyber space operations, cyber defense and resiliency, vulnerability research, ubiquitous technical surveillance, data intelligence, lifecycle mission enablement, and software modernization. Nightwing brings disruptive technologies, agility, and competitive offerings to customers in the intelligence community, defense, civil, and commercial markets. Nightwing is seeking an experienced Infrastructure Engineer to design, build, and maintain the backbone of our advanced systems infrastructure. As a key member of our team, you’ll take ownership of planning, configuring, and sustaining systems that enable scalable and efficient operations. From orchestrating container architectures like Kubernetes and Rancher, to implementing robust virtualization solutions, you will be instrumental in ensuring high availability, security, and adaptability across our network and software stack." That's a lot; we can keep as prose. Location: "Location: Onsite - National Business Park, Maryland." Could be a short

    . Responsibilities list: bullet points from "Architect, deploy, and maintain containerized environments..." to "Provide technical guidance for infrastructure scalability, capacity planning, and risk mitigation in virtualized environments." Let's capture each: - Architect, deploy, and maintain containerized environments using technologies such as Kubernetes, Proxmox, and Rancher. - Design and implement scalable virtualization solutions using Citrix clients, enabling seamless system operations and multi-user environments. - Manage logging, monitoring, and observability systems, such as the ELK stack (ElasticSearch, Logstash, Kibana), for real-time performance optimization and troubleshooting. - Plan and configure network software stacks that integrate microservices and distributed systems for secure and scalable operations. - Develop and maintain automation scripts using languages like Python, Bash, or Terraform for configuration management and provisioning. - Optimize infrastructure performance to support heavy workloads, improve fault tolerance, and minimize downtime. - Collaborate with development and operations teams to integrate infrastructure solutions into agile deployment pipelines. - Ensure compliance with robust security policies and practices, leveraging DevSecOps workflows and tools like Git, Ansible, and CI/CD systems. - Provide technical guidance for infrastructure scalability, capacity planning, and risk mitigation in virtualized environments. That's 9 bullets. Requirements (Minimum Qualifications): list: - Bachelor’s degree in a STEM field (Science, Technology, Engineering, Mathematics) or equivalent experience. - At least 5 years of hands-on experience in infrastructure engineering or related roles. - Proven experience designing, deploying, and maintaining Kubernetes clusters and container orchestration systems. - Solid understanding of virtualization technologies and protocols, including expertise in Citrix environments. - Proficiency with monitoring and observability tools (e.g., ELK Stack, Prometheus, Grafana). - Strong knowledge of Linux-based systems and network administration, with the ability to optimize performance and troubleshoot issues. - Hands-on experience with infrastructure automation tools and writing scripts (e.g., Python, Bash, Terraform). - Familiarity with DevSecOps practices, CI/CD workflows, and version control systems like Git. - Ability to lead the planning and execution of scalable, virtualized systems while maintaining operational efficiency. Qualifications (Preferred Qualifications): list: - Experience working with Proxmox and Rancher for container and virtualization management. - Familiarity with managing virtualization environments for multi-user desktops and remote clients. - Knowledge of distributed systems architecture and event-driven frameworks. - Strong understanding of networking protocols, firewalls, and security configurations. - Previous experience designing infrastructure for high-load systems or large-scale environments. - Certification in infrastructure-related technologies or tools (e.g., Kubernetes Certified Administrator). Benefits: from "Nightwing offers medical, vision and dental insurance coverage in addition to a 401k plan, PTO, Holidays, and additional insurances." Also maybe include "Why Join Us" points? Could incorporate as benefits? But we already have benefits; we could add a separate section for "Why Join Us" but not allowed heading. Could incorporate into Benefits as additional points: innovative environment, collaborative teams, opportunities to grow, mission-driven impact. However those are not typical benefits but could be included. The instruction: Prefer a few substantive sections over many thin ones. So we could expand Benefits to include those cultural points. Let's include them as bullet points under Benefits. Thus Benefits bullets: - Medical, vision, and dental insurance coverage - 401k plan - PTO and Holidays - Additional insurances - Innovative environment: work on cutting-edge technologies and tackle meaningful challenges that push the limits of scalability and reliability. - Collaborative teams: join a group of skilled engineers who thrive on solving tough problems together and continuously sharing knowledge. - Opportunities to grow: expand your skillset with access to enterprise-grade tools and learn from industry experts. - Mission-driven impact: build infrastructure that supports national security operations and real-world success. Pay: Salary range: $99,000-$206,000, commensurate with qualifications, years of relevant experience, demonstrated level of expertise. Also note compensation determined based on these factors to ensure alignment with skills, responsibilities, and market standards. We should not include filler like "commensurate with experience" as heading but we can include in prose. Thus Pay section:

    The salary associated with this position is $99,000‑$206,000, commensurate with the selected candidate’s qualifications, years of relevant experience, and demonstrated level of expertise. Compensation will be determined based on these factors to ensure alignment with skills, responsibilities, and market standards.

    We should not repeat the salary line twice; there is duplicate in posting; we include once. We should not include EEO boilerplate. Now construct HTML fragment. We'll start with location

    maybe. Structure:

    Location: Onsite - National Business Park, Maryland

    About the role

    ... (prose)

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Qualifications

    • ...
    ...

    Benefits

    • ...
    ...

    Pay

    ...

    Make sure no extra whitespace issues. Let's craft the About the role prose exactly as we captured. Check for any repeated lines: we must preserve all substantive information; we included the Nightwing capabilities and role description. Did we miss any? The posting also says: "Ideal candidate is a highly skilled Infrastructure Engineer with deep expertise in containerization, virtualization, and automation. These individuals find maximum job satisfaction in being both a systems thinker and a hands-on builder, capable of designing, deploying, and optimizing scalable, secure, and resilient infrastructure within complex environments. Candidate will work in a fast-paced, mission-critical settings and bring a strong foundation in Linux systems, networking, and distributed architectures, combined with modern DevSecOps practices." This is more about ideal candidate; could be part of About the role or Requirements. Since we already have Requirements and Qualifications, we could incorporate this into About the role as additional description. But we might be missing some details if we omit. The instruction: Preserve ALL substantive information. So we need to include that paragraph somewhere. Could add to About the role after the initial description. Or we could add to Requirements as a summary but it's not a requirement per se. Better to add to About the role. Thus About the role prose will be longer: combine the initial Nightwing capabilities, role description, and ideal candidate paragraph. Let's craft: "Nightwing provides technically advanced full-spectrum cyber, data operations, systems integration and intelligence mission support services to meet our customers’ most demanding challenges. Our