Sr. DevOps Engineer - TS/SCI

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - Intro paragraph: "Senior DevOps Engineer – TS/SCI Xcelerate Solutions has an exciting opening for you, our next TS/SCI cleared Senior DevOps Software Engineer to play a critical role on the DOMEX Technology Platform (DTP) Program where we support our client’s mission to centralize and standardize Tasking, Collection, Processing, Exploitation and Dissemination (TCPED) of Open Source Intelligence (OSINT) across the DoD and IC enterprise. We integrate off the shelf and newly development software to sustain and enhance the TCPED platform. We leverage cloud-based computing, artificial intelligence (Al), machine learning (ML) and cross-domain transfer systems to provide cutting edge data exploitation, enrichment, triage, and analytics capabilities to Defense and Intelligence Community members. DTP advances the state of the art in mission-focused big data analytics tools and micro-service development spanning the breadth of Agile sprints to multiyear research and development cycles. While most work is conducted on-site at our client location in Bethesda, MD, we offer a flexible schedule and, occasionally, some tasks may be performed remotely. As a Senior DevOps Engineer you will lead an DevOps team responsible for the design, deployment, and maintenance of a full stack containerized microservices architecture as well as technical systems administration, installation, and configuration. You will participate in fostering a DevOps culture, building strong cross functional collaboration with systems engineering, architecture, development, security, operations, and integration teams, in a dynamic and fast paced environment. Come join our award-winning organization and work with some of the most talented and brightest minds in the GovCon industry." That's about the role. - Clearance: TS/SCI - Location: Bethesda, MD These are metadata; we can put in a short

maybe under About the role or separate? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a paragraph with Clearance and Location. - Responsibilities: list bullet points. - Minimum Requirements: list bullet points. - Preferred Qualification: bullet points. - About Xcelerate Solutions: description. - EEO etc: boilerplate to remove. - Pay Transparency Notice: maybe we can include as a short paragraph? It's about pay transparency but not actual pay amount. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does not state actual pay, schedule, benefits. It mentions flexible schedule, occasional remote. That's schedule info. It says "we offer a flexible schedule and, occasionally, some tasks may be performed remotely." That's schedule info. So we can include a Schedule section with that statement. Benefits? Not mentioned. Pay? Not mentioned. So we should not create Pay or Benefits sections. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include those with real content. So we will have About the role, Responsibilities, Requirements (maybe combine Minimum Requirements and Preferred Qualification?), Qualifications (maybe Preferred Qualification?), Skills (maybe list specific technical skills?), Schedule (flexible schedule). Benefits and Pay omitted. We need to decide how to split content. We have Minimum Requirements (education, experience, clearance, certifications, etc.) That's Requirements. Preferred Qualification: maybe Qualifications. Skills: we could list technical skills like Kubernetes, Helm, etc. But those are already in Requirements/Preferred. Could create a Skills section summarizing technical proficiencies. However we must not invent content; we can extract from the posting: "Experienced with container/container orchestration, specifically Kubernetes and troubleshooting experience with: Ingress/Gateway API, Helm chart design/build, Pod disruption budgets, Affinity/anti-affinity rules, Familiarity with external-secrets, ArgoCD, cert-manager, eck (elastic search)". Also "GitLab pipeline development experience including: Integration of GitLab CI/CD components, Integration of GitLab Code Quality reports, Integration of GitLab Code Coverage/Test reports". Also "Knowledgeable in navigating Linux OS, specifically: Knowledgeable about sysctls for K8s environments, FApolicyd and SELinux experience". Also "Comfortable with Elastic Search, Logstash, Kibana". Also "Experience as a Product Owner or a similar role in an Agile software development team: Demonstrated ability to break down complex problems into actionable steps. Experience managing and prioritizing product backlogs effectively. Strong understanding of Agile methodologies. Experience with facilitating scrum for the team (Planning, Retrospective, Grooming & Review/Demo). Excellent communication skills (verbal and written) to articulate technical and non-technical concepts to diverse audiences. Proven ability to work cross-functionally with engineering, design, and project management teams. Demonstrated ability to manage expectations and maintain strong relationships with stakeholders." Also Preferred Qualification: "Experience with development, i.e. Bash, PowerShell, SALT, Python, Groovy, Java, etc. Experience on a production/ enterprise system Experience with any of the following technologies: Kafka or other message passing systems (AMQP, JMS) Kubernetes monitoring, e.g., Prometheus/ Graphana GPU-based Kubernetes SALT for deployment automation Nexus" Thus we can create Skills section summarizing these technical skills. But we must not duplicate content; we can still include them in Skills but also they appear in Requirements/Preferred. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. However we can keep them in Requirements and Preferred and not create Skills if it would be redundant. But we need to decide which sections to include. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But they have headings: Requirements, Qualifications, Skills. We could have Requirements (including minimum requirements) and Qualifications (preferred). Skills could be omitted if covered. But we need to follow the instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if we have content. It's okay to omit some. Thus we will produce:

About the role

with paragraph(s) summarizing the role description. Then a

for metadata: Clearance and Location. Then

Responsibilities

with

• list. Then

  Requirements

  with
  • list of minimum requirements. Then

    Qualifications

    with
    • list of preferred qualifications. Then

      Schedule

      with

      about flexible schedule and occasional remote. We will not include Benefits, Pay. We must not include boilerplate like EEO, Pay Transparency Notice? The Pay Transparency Notice is about pay but not actual pay; we can drop it as it's not specific pay/benefits. It's a notice; we can drop. Now we need to ensure we preserve all substantive information. Let's extract. About the role paragraph: we can keep the two paragraphs (intro and role description). Could combine into one

      but we can split. Metadata: Clearance: TS/SCI; Location: Bethesda, MD. Responsibilities list: - Deploy, triage and maintain a production big data pipeline using a microservice architecture running on Kubernetes, Elasticsearch backend, and Kafka messaging. - Enhance, improve, and maintain CI/CD and DevOps scripts and processes to facilitate faster development, quicker error detection and resilient deployments. - Design, develop, and support scalable, redundant infrastructure to include physical and virtualized environments. - Use Helm to configure Kubernetes deployments to support new feature requirements. - Collaborate with System Engineers to design solutions for new features and requirements. - Provide technical input to systems engineering documentation and diagrams/models working in coordination/collaboration with SE team members and Architect team. - Own and prioritize the Agile team backlog, ensuring work aligns with business priorities and delivers maximum value. - Break down features, prioritize work, and ensure requirements are clear and actionable. - Support SAFe Program Increment (PI) planning and execution, including creating and managing work items and project documentation. - Participate in Agile ceremonies, including sprint planning, daily standups, reviews, and retrospectives. - Monitor sprint and program progress, helping resolve dependencies, risks, and impediments that impact delivery. - Review and accept completed work to ensure it meets business requirements and quality standards. - Collaborate with stakeholders, developers, and leadership to communicate priorities, progress, and product goals. That's all. Minimum Requirements list: - BS in Engineering, Computer Science, Systems Engineering, or related field or equivalent experience with 12+ years in software development, system engineering or related field. - 10+ years of experience with Master’s degree. - Active TS/SCI security clearance with the ability to obtain and maintain a Polygraph. - Current DoD 8570.01M IAT Level II (or higher) certification, such as Security+, CySA+, SSCP, CCNA Security, or CISSP (or Associate). - Ability to obtain Privileged User Account (PUA) certification. - Experienced with container/container orchestration, specifically Kubernetes and troubleshooting experience with: - Ingress/Gateway API - Helm chart design/build - Pod disruption budgets - Affinity/anti-affinity rules - Familiarity with external-secrets, ArgoCD, cert-manager, eck (elastic search) - GitLab pipeline development experience including: - Integration of GitLab CI/CD components - Integration of GitLab Code Quality reports - Integration of GitLab Code Coverage/Test reports - Knowledgeable in navigating Linux OS, specifically: - Knowledgeable about sysctls for K8s environments - FApolicyd and SELinux experience - Comfortable with Elastic Search, Logstash, Kibana - Experience as a Product Owner or a similar role in an Agile software development team: - Demonstrated ability to break down complex problems into actionable steps. - Experience managing and prioritizing product backlogs effectively. - Strong understanding of Agile methodologies. - Experience with facilitating scrum for the team (Planning, Retrospective, Grooming & Review/Demo). - Excellent communication skills (verbal and written) to articulate technical and non-technical concepts to diverse audiences. - Proven ability to work cross-functionally with engineering, design, and project management teams. - Demonstrated ability to manage expectations and maintain strong relationships with stakeholders. We need to format as list items; nested lists okay? Probably we can keep as

      • with sub-items as
        inside. Preferred Qualification list: - Experience with development, i.e. Bash, PowerShell, SALT, Python, Groovy, Java, etc. - Experience on a production/enterprise system - Experience with any of the following technologies: - Kafka or other message passing systems (AMQP, JMS) - Kubernetes monitoring, e.g., Prometheus/Graphana - GPU-based Kubernetes - SALT for deployment automation - Nexus Schedule: "While most work is conducted on-site at our client location in Bethesda, MD, we offer a flexible schedule and, occasionally, some tasks may be performed remotely." We already have location in metadata; but schedule section can mention flexible schedule and occasional remote. Now About Xcelerate Solutions description: Should we include? It's about the company; could be part of About the role? The instruction: "About the role" heading is for role description; company description maybe not needed but could be included as part of