DevSecOps Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes: - Location: Onsite at a government site in Washington, DC metro area (maybe part of description) - 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 - Eligibility & Clearance Requirements (U.S. citizen, CBP suitability, clearance) - Your Mission (list of duties) - What You Bring to the Expedition (requirements/qualifications) - Why Explorers Stay (benefits: healthcare coverage, paid time off, teammates, opportunities, meaningful work) - How We Work (onsite, schedule depends, etc.) - About Via Logic (company description) - Possibly other sections like "Your Route Into Via Logic" (application instructions) - we should drop application instructions. - Repeated "Why Explorers Stay" appears twice; we should deduplicate. We must not include boilerplate like EEO, accessibility, fraud notice. We must not repeat job title as heading (the page already shows it). So we don't add a heading for job title. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. We need to prefer a few substantive sections over many thin ones. Thus we can combine some sections: maybe "About the role" could encompass mission and responsibilities. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which headings to include based on content. We have content for: - About the role: could be a brief description of the role (maybe the "Your Mission" and "What You Bring"). But we need to avoid duplication. Better to create sections: - Responsibilities (Your Mission) - Requirements / Qualifications (What You Bring to the Expedition + Eligibility & Clearance Requirements) - Benefits (Why Explorers Stay) - Pay (Compensation) - Schedule (How We Work mentions schedule depends, etc.) - Possibly "About the role" could be a short paragraph summarizing the role (maybe combine location, type, etc.) But we must not create sections with filler. So we need actual content. Let's extract specifics: 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. Eligibility & Clearance Requirements: - 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 (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 your experience. What You Bring to the Expedition (Requirements/Qualifications): - 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 (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. How We Work (Schedule/Work details): - 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. - (Later duplicate) Schedules depend on the assignment. Some teams work daytime Eastern Time hours; others may have shift or on-call requirements. We’ll discuss the schedule for a specific opening before moving forward. - When virtual meetings are part of the work, we expect active participation and use video when appropriate and permitted by the client environment. We can combine these into a Schedule section with details about schedule variability. About Via Logic (company description) maybe not required as a heading; but we could include as "About the company" but not in list of headings. The instruction only gave examples; we can include other headings if needed but better to stick to those. However we have substantive content about Via Logic; we could include as "About the role" maybe? But "About the role" is supposed to be about the role, not company. Could we include a section "About Via Logic"? Not in the list but maybe allowed. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive. So we can add other headings if needed. But we should prefer few substantive sections. The company description may be considered less essential; but we could incorporate into "About the role" or drop. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can omit About Via Logic to keep sections thin. Thus we will have sections: - Responsibilities (Your Mission) - Requirements (What You Bring + Eligibility & Clearance) - Benefits (Why Explorers Stay) - Pay (Compensation) - Schedule (How We Work) We might also include a short introductory paragraph about location and type before sections, maybe as a

  without heading. We must not repeat job title as heading. We must not include metadata like Job ID. We must output only HTML fragment. Let's craft:

  Location: Onsite at a government site in the Washington, DC metropolitan area. Type: Full-time, W-2.

  Then

  Responsibilities

  with
  • ... each duty. Then

    Requirements

    with
    • ... combine eligibility and qualifications. Then

      Benefits

      with
      • ... benefits. Then

        Pay

        with

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

        Then

        Schedule

        with

        ... schedule details. We need to ensure we preserve all substantive information: include location, type, eligibility details, etc. Let's list all details to include: 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. Eligibility & Clearance Requirements: - U.S. citizens. - Able to complete CBP suitability process and receive favorable determination before starting assignment (background investigation, credit history review). - Meet any additional clearance requirement for the specific opening; some assignments may require Secret or Top Secret clearance; specialized assignments may require SCI eligibility. We will confirm requirement as we match candidates to openings. Your Mission (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 your experience. What You Bring to the Expedition (Qualifications): - 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. - Ability to explain a finding, work with the team responsible for a fix, 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. - Specific platforms and tools vary by assignment. Why Explorers Stay (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. How We Work (Schedule/Work details): - 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. - Schedules depend on the assignment. Some teams work daytime Eastern Time hours; others may have shift or on-call requirements. We’ll discuss the schedule for a specific opening before moving forward. - When virtual meetings are part of the work, we expect active participation and use video when appropriate and permitted by the