DevSecOps Engineer

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, legal, scam warning, duplicated lines, application instructions. Also remove duplicated "Why Explorers Stay" etc. We need to preserve substantive info. Let's parse posting: - Start Your Adventure at Via Logic Location: Onsite at a government site in the Washington, DC metropolitan area - Type: Full-time, W-2 - Compensation: $80,000–$130,000 annually, depending on experience and assignment - Experience: Approximately 1–5 years of relevant experience; we are hiring at multiple levels - One posting, several possible routes. Via Logic is hiring for multiple openings at different experience levels. Your work may focus on secure delivery pipelines, application security, infrastructure automation, container security, or a blend of these areas. The broad experience and compensation ranges reflect the different openings; we will explore where your strengths fit best. - Eligibility & Clearance Requirements: These openings support CBP work. Applicants must: Be U.S. citizens. Be able to complete the CBP suitability process and receive a favorable determination before starting the assignment. The process includes a background investigation and review of credit history. Meet any additional clearance requirement for the specific opening. Some assignments may require a Secret or Top Secret clearance, and specialized assignments may require SCI eligibility. We will confirm the requirement as we match candidates to openings. - Your Mission: Build and improve security checks in development, build, and deployment workflows. Configure and use code, dependency, container, and infrastructure scanning tools; help teams understand findings and follow fixes through to completion. Partner with developers, platform engineers, and security teams to make secure practices part of everyday delivery. Automate repeatable security and infrastructure tasks, including work with infrastructure as code where applicable. Troubleshoot pipeline or security-tool issues and document changes so other teams can maintain them. Contribute to application security, cloud controls, centralized logging, or broader security improvements based on the assignment and your experience. - What You Bring to the Expedition: Approximately 1–5 years of relevant experience in DevOps, DevSecOps, software engineering, application security, or a related technical field. We will consider the depth of your work alongside your years of experience. Hands-on experience with CI/CD, scripting or automation, and at least one type of security testing or vulnerability remediation. Familiarity with some of the following: source control, infrastructure as code, containers, cloud services, code or dependency scanning, and application security practices. The ability to explain a finding, work with the team responsible for a fix, and balance security with reliable delivery. The ability to work onsite in the Washington, DC metropolitan area. Experience with cloud security, enterprise logging, or security modernization is welcome, especially when you have built or configured the underlying tools and workflows. Specific platforms and tools vary by assignment. - Why Explorers Stay: Healthcare coverage and paid time off that give you room to take care of life outside work. Teammates who share knowledge, pitch in, and help each other grow. Opportunities to deepen your specialty and explore adjacent areas of cybersecurity as new assignments open up. Meaningful work protecting systems that support a federal mission. - How We Work: These roles work onsite at a government site in the Washington, DC metropolitan area. The specific site depends on the assignment. You will work with Via Logic teammates, government partners, and other technical teams using tools approved for your work environment. Schedules depend on the opening. We will discuss any extended hours or on-call expectations before moving forward with a specific assignment. When virtual meetings are part of the work, we expect active participation and use video when appropriate and permitted by the customer environment. - Your Route Into Via Logic: Tell us what you have built, automated, or secured. We are hiring for multiple openings at different levels through this posting, and a few clear sentences are often enough to show us where your experience may fit. If your strengths lean toward application security, cloud security, or logging and automation, we want to hear about that too. - About Via Logic: Via Logic LLC is an information technology partner supporting mission-driven work across DevSecOps, cloud engineering, cybersecurity, data science, and national security analytics for federal and commercial clients. Our teams help modernize complex systems through automation, secure engineering practices, cloud-native technologies, and scalable infrastructure solutions that support real-world impact. But beyond the work itself, we care deeply about how we work. We believe great teams are built through collaboration, curiosity, accountability, and trust. Whether you're supporting customer missions, strengthening business operations, or leading expeditions of your own, Via Logic is a place where Explorers are encouraged to grow, contribute, and continuously evolve. - Then repeated sections: Equal Opportunity Employer, Accessibility & Accommodations, Recruiting Fraud Notice – these are boilerplate to remove. We need to produce sections: maybe About the role (could be "About the role" or "About Via Logic"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings where appropriate. We have: - About the role: could be description of role (Your Mission, What You Bring, etc). But we need to decide sections. We have content for: - Responsibilities: "Your Mission" bullet list. - Requirements/Qualifications: "What You Bring to the Expedition" (experience, skills). - Skills: maybe list of specific tools/experience. - Benefits: "Why Explorers Stay" (healthcare coverage, paid time off, teammates, opportunities, meaningful work). - Pay: Compensation range. - Schedule: "How We Work" includes schedule info. - About the role: maybe a summary paragraph about the role (the opening paragraphs about multiple openings, focus areas). Could be "About the role" heading. We must not create sections with filler like "commensurate with experience". We have actual content for Pay: $80,000–$130,000 annually, depending on experience and assignment. That's specific, so include Pay section. Schedule: we have "Schedules depend on the opening. We will discuss any extended hours or on-call expectations before moving forward with a specific assignment." Also later: "Schedules depend on the assignment. Some teams work daytime Eastern Time hours; others may have shift or on-call requirements." That's specific enough to include Schedule. Benefits: "Why Explorers Stay" includes healthcare coverage and paid time off, teammates, opportunities, meaningful work. That's specific. Responsibilities: "Your Mission" list. Requirements/Qualifications: "What You Bring to the Expedition" includes experience, hands-on experience, familiarity, ability to explain, ability to work onsite, etc. Skills: maybe we can extract specific skills: CI/CD, scripting or automation, security testing/vulnerability remediation, source control, infrastructure as code, containers, cloud services, code or dependency scanning, application security practices, cloud security, enterprise logging, security modernization. Could be a list. But we must not repeat content unnecessarily. Could combine Requirements and Skills? The instruction says prefer a few substantive sections over many thin ones. So we could have sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly Skills could be part of Requirements. We need to avoid duplication: The "What You Bring" includes experience and skills. We'll put that under Requirements (or Qualifications). We'll also include a brief About the role summarizing the multiple openings and focus areas. We must not include boilerplate like Equal Opportunity etc. We must not include duplicated lines: there are duplicated "Why Explorers Stay" and "How We Work" sections repeated later; we should include only once. We must not include application instructions like "Tell us what you have built..." that's actually part of "Your Route Into Via Logic". That's substantive? It's a call to action but maybe considered application instruction. The instruction says remove application instructions. That line is basically asking candidates to tell us what they have built... That's akin to application instruction. So we should omit that section. Also "Your Route Into Via Logic" is basically application instruction; we should drop. Also "About Via Logic" is company description; could be considered "About the role"? Might be okay to include as "About the role" or maybe separate "About the company". But the instruction only lists certain headings; we can include "About the role" heading and put the description of the role and maybe company info there. However we should not include fluff like "Via Logic LLC is an information technology partner..." That's company description, not role. Might be okay to include under About the role as context. But we need to see if it's substantive. It's about the company; could be considered relevant. We'll include a brief paragraph under About the role. We must not include headings with filler text. So we will only output sections we have content for. Let's craft HTML:

About the role

Via Logic is hiring for multiple openings at different experience levels supporting CBP work in the Washington, DC metropolitan area. Work may focus on secure delivery pipelines, application security, infrastructure automation, container security, or a blend of these areas. The role involves building and improving security checks in development, build, and deployment workflows, partnering with developers and security teams, and automating security and infrastructure tasks.

Responsibilities

• Build and improve security checks in development, build, and deployment workflows.
• Configure and use code, dependency, container, and infrastructure scanning tools; help teams understand findings and follow fixes through to completion.
• Partner with developers, platform engineers, and security teams to make secure practices part of everyday delivery.
• Automate repeatable security and infrastructure tasks, including work with infrastructure as code where applicable.
• Troubleshoot pipeline or security-tool issues and document changes so other teams can maintain them.
• Contribute to application security, cloud controls, centralized logging, or broader security improvements based on the assignment and experience.

Requirements

• Approximately 1–5 years of relevant experience in DevOps, DevSecOps, software engineering, application security, or a related technical field.
• Hands‑on experience with CI/CD, scripting or automation, and at least one type of security testing or vulnerability remediation.
• Familiarity with source control, infrastructure as code, containers, cloud services, code or dependency scanning, and application security practices.
• Ability to explain findings, work with the responsible team to implement fixes, and balance security with reliable delivery.
• Ability to work onsite in the Washington, DC metropolitan area.
• Experience with cloud security, enterprise logging, or security modernization is welcome, especially when you have built or configured the underlying tools and workflows.

Benefits

• Healthcare coverage and paid time off that give you room to take care of life outside work.
• Teammates who share knowledge, pitch in, and help each other grow.
• Opportunities to deepen your specialty and explore adjacent areas of cybersecurity as new assignments open up.
• Meaningful work protecting systems that support a federal mission.

Pay

$80,000–$130,000 annually, depending on experience and assignment.

Schedule

Schedules depend on the assignment; some teams work daytime Eastern Time hours while others may have shift or on‑call requirements. Extended hours or on‑call expectations will be discussed before moving forward with a specific assignment.

We need to ensure we didn't include any boiler