Cloud Security 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. Let's parse the posting. Key info: - Title: Start Your Adventure at Via Logic (but we don't repeat title as heading) - 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 center on identity and access, secure cloud configuration, network controls, monitoring, automation, or resolving cloud security findings. The broad experience and compensation ranges reflect the different openings; we will explore where your strengths fit best. - Eligibility & Clearance Requirements: Must be US citizens, able to complete CBP suitability process, background investigation, credit history review. Meet any additional clearance requirement; some assignments may require Secret or Top Secret clearance, specialized may require SCI eligibility. We will confirm requirement as we match candidates. - Your Mission: bullet list of duties. - What You Bring to the Expedition: experience requirements. - Why Explorers Stay: benefits (healthcare coverage and paid time off, teammates, opportunities, meaningful work) - How We Work: onsite, schedule depends, extended hours or on-call expectations discussed, virtual meetings expectations. - Your Route Into Via Logic: application instruction (we should remove application instructions) - About Via Logic: company description. - Equal Opportunity Employer, Accessibility & Accommodations, Recruiting Fraud Notice: boilerplate to remove. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop sections like Equal Opportunity Employer, Accessibility & Accommodations, Recruiting Fraud Notice. Also drop "Your Route Into Via Logic" (application instructions). Also drop "About Via Logic"? That's company description, not boilerplate; could be considered part of "About the role"? Might be okay to keep as a section maybe "About the company". But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. However we can include "About the role" as a heading for overview. The posting includes "Your Mission" (responsibilities), "What You Bring to the Expedition" (requirements/qualifications/skills), "Why Explorers Stay" (benefits), "How We Work" (schedule maybe). Also we have compensation and eligibility/clearance requirements. We need to decide which sections to include: - About the role: could include location, type, brief overview. - Responsibilities: from "Your Mission". - Requirements: from eligibility & clearance plus experience? Could combine. - Qualifications: maybe from "What You Bring to the Expedition". - Skills: maybe from same. - Benefits: from "Why Explorers Stay". - Pay: compensation range. - Schedule: from "How We Work" (schedule depends, extended hours, on-call). We must not create sections with filler like "commensurate with experience". We have actual content. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like US citizenship, CBP suitability, background investigation, credit history, possible Secret/Top Secret/SCI, etc. We need to use

for section headings. Use

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

  for prose. We must output only HTML fragment, no /, no markdown fences. Let's craft. First, maybe a short paragraph for About the role: location, type, full-time W-2, onsite at government site in DC metro area. Then Responsibilities: list items from "Your Mission". Those are: - Implement and improve security controls across cloud services and workloads. - Support identity and access, network protections, logging, monitoring, and secure configuration in cloud environments. - Investigate misconfigurations, vulnerabilities, and security findings; partner with platform and application teams to fix the underlying issues. - Help automate security checks, guardrails, and repeatable response or remediation tasks. - Support cloud security assessments, incident response, and clear documentation of changes and technical decisions. - Bring your experience to related DevSecOps, security engineering, or modernization work when the assignment calls for it. We'll put each as

• . Requirements: maybe combine eligibility & clearance and experience. But we need to avoid duplication. Could have a Requirements section with bullet list: - U.S. citizenship. - Ability to complete CBP suitability process and receive favorable determination (background investigation and credit history review). - Meet any additional clearance requirement for the specific opening (possible Secret, Top Secret, or SCI eligibility). - Approximately 1–5 years of relevant experience in cloud engineering, cloud security, infrastructure security, or related technical field. - Hands-on experience with a major cloud platform and some of its identity, networking, logging, or security services. - Experience identifying or fixing security gaps in cloud resources, access, configurations, or workloads. - Ability to work with engineers and system owners to put practical controls in place and explain why they matter. - Ability to work onsite in the Washington, DC metropolitan area. - Experience with infrastructure as code, scripting, CI/CD, container security, cloud networking, or security automation is welcome. But note that some of these are more like qualifications/skills. However we can split into Requirements (clearance, citizenship, experience) and Qualifications/Skills (the rest). But we must not create thin sections; better to combine into Requirements and Qualifications maybe. Qualifications: maybe the hands-on experience etc. Skills: maybe the specific technical skills list. But we can also have just Requirements and Qualifications and Skills as separate if they have content. Let's see: The posting includes "What You Bring to the Expedition" which includes experience, hands-on experience, experience identifying/fixing gaps, ability to work with engineers, ability to work onsite, experience with IaC, scripting, CI/CD, container security, cloud networking, or security automation is welcome. That's a mix of qualifications and skills. We could treat "What You Bring to the Expedition" as Qualifications (experience) and Skills (technical). But we need to avoid duplication. Simplify: Have sections: - About the role (overview) - Responsibilities (Your Mission) - Requirements (Eligibility & Clearance + experience years) - Qualifications (What You Bring to the Expedition - experience depth) - Skills (Technical skills list) - Benefits (Why Explorers Stay) - Pay (Compensation) - Schedule (How We Work) Check each for real content. About the role: we have location, type, full-time W-2, onsite at government site in DC metro area. Also mention multiple openings at different levels, work may center on identity and access, secure cloud config, network controls, monitoring, automation, or resolving cloud security findings. That's more like responsibilities but could be in About the role. We'll keep brief. Responsibilities: list from Your Mission. Requirements: include US citizenship, CBP suitability, clearance possibilities, 1-5 years experience. Qualifications: maybe include hands-on experience with major cloud platform, experience identifying/fixing gaps, ability to work with engineers, ability to work onsite. Skills: include experience with IaC, scripting, CI/CD, container security, cloud networking, security automation. Benefits: healthcare coverage and paid time off, teammates sharing knowledge, opportunities to deepen specialty, meaningful work protecting systems. Pay: $80,000–$130,000 annually, depending on experience and assignment. Schedule: onsite at government site in DC metro area; schedules depend on opening; discuss extended hours or on-call expectations before moving forward; virtual meetings expectations. We must not include boilerplate like "Equal Opportunity Employer". Good. Now produce HTML. We'll need to wrap each section in

  heading then content. For lists, use

  • . For prose, use

    . Let's craft. About the role:

    Onsite, full-time W-2 position at a government site in the Washington, DC metropolitan area. Via Logic is hiring for multiple openings at different experience levels; work may focus on identity and access, secure cloud configuration, network controls, monitoring, automation, or resolving cloud security findings.

    Responsibilities:

    Responsibilities

    • Implement and improve security controls across cloud services and workloads.
    • Support identity and access, network protections, logging, monitoring, and secure configuration in cloud environments.
    • Investigate misconfigurations, vulnerabilities, and security findings; partner with platform and application teams to fix the underlying issues.
    • Help automate security checks, guardrails, and repeatable response or remediation tasks.
    • Support cloud security assessments, incident response, and clear documentation of changes and technical decisions.
    • Bring your experience to related DevSecOps, security engineering, or modernization work when the assignment calls for it.
    Requirements:

    Requirements

    • U.S. citizenship.
    • Ability to complete the CBP suitability process and receive a favorable determination (background investigation and credit history review).
    • Meet any additional clearance requirement for the specific opening; some assignments may require Secret or Top Secret clearance, and specialized assignments may require SCI eligibility.
    • Approximately 1–5 years of relevant experience in cloud engineering, cloud security, infrastructure security, or a related technical field.
    Qualifications:

    Qualifications

    • Hands‑on experience with a major cloud platform and some of its identity, networking, logging, or security services.
    • Experience identifying or fixing security gaps in cloud resources, access, configurations, or workloads.
    • Ability to work with engineers and system owners to put practical controls in place and explain why they matter.
    • Ability to work onsite in the Washington, DC metropolitan area.
    Skills:

    Skills

    • Experience with infrastructure as code, scripting, CI/CD, container security, cloud networking, or security automation is welcome.
    Benefits:

    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:

    Pay

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

    Schedule:

    Schedule

    Onsite at a government site in the Washington, DC metropolitan area; schedules depend on the specific opening. Extended hours or on‑call expectations will be discussed before moving forward with an assignment. When virtual meetings are part of the work, active participation and video use are expected when appropriate and permitted by the customer environment.

    Check we didn't include any boilerplate. We omitted "Your Mission" heading, we used Responsibilities. We omitted "What You Bring to the Expedition" split into Qualifications and Skills. We omitted "Why Explorers Stay" turned into Benefits. We omitted "How We Work" turned into Schedule. We omitted "About Via Logic". We omitted eligibility & clearance details included in Requirements. We