Cloud Security Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Key info:
- 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), meet any additional clearance requirement; some assignments may require Secret or Top Secret clearance, specialized may require SCI eligibility.
- Your Mission: bullet list of duties.
- What You Bring to the Expedition: qualifications/experience.
- 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 (should be removed)
- About Via Logic: company description (could be considered "About the role"? Actually it's about company; maybe we can include as a section like "About Via Logic" but not required headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
We need to avoid repeating job title as heading (not present). Remove boilerplate: EEO, accessibility, recruiting fraud notice, etc. Also remove application instructions ("Your Route Into Via Logic", "Tell us what you have secured...").
We need to preserve all substantive information.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to include a section only when posting has real specific content for it. So we need to decide which sections to include.
Potential sections:
- About the role: could include description of role, mission, maybe "Your Mission". Could be "About the role" heading.
- Responsibilities: list of duties (Your Mission bullet points). Could be under Responsibilities.
- Requirements: eligibility & clearance requirements (US citizenship, CBP suitability, clearance). Also maybe experience requirement.
- Qualifications: "What You Bring to the Expedition" (experience, skills). Could be Qualifications.
- Skills: maybe list of specific skills (cloud platform, IAC, scripting, CI/CD, container security, cloud networking, security automation). Could be Skills.
- Benefits: "Why Explorers Stay" (healthcare coverage, paid time off, teammates, opportunities, meaningful work). Also maybe "How We Work" includes schedule etc.
- Pay: compensation range.
- Schedule: schedule depends on opening, extended hours or on-call expectations discussed, virtual meetings expectations.
We need to avoid filler like "commensurate with experience" etc. We have actual compensation range.
We need to ensure we don't create sections with placeholder text.
Let's extract content.
**About the role** (maybe combine location, type, mission). Could be a paragraph: "Full-time, W-2 position onsite at a government site in the Washington, DC metropolitan area. Work may focus on identity and access, secure cloud configuration, network controls, monitoring, automation, or resolving cloud security findings."
**Responsibilities** (Your Mission bullet points):
- 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** (Eligibility & Clearance Requirements + maybe experience baseline):
- U.S. citizenship.
- Ability to complete the CBP suitability process and receive a favorable determination before starting (includes background investigation and review of credit history).
- 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** (What You Bring to the Expedition):
- 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.
- Specific platforms and tools vary by assignment; you do not need to have used every item listed here.
**Skills** (maybe combine with qualifications? But we can separate: list of technical skills: cloud platform, IAM, networking, logging, security services, IaC, scripting, CI/CD, container security, cloud networking, security automation). However we already listed many in qualifications. Might be redundant. Better to keep Qualifications as experience, and Skills as technical abilities. But we can also merge. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one section called "Qualifications & Skills". But headings list includes both; we can choose to include only those with content. We could include Qualifications and Skills separate if we have distinct content. Let's see: Qualifications: experience years, ability to work onsite, etc. Skills: hands-on experience with cloud platform, IaC, scripting, CI/CD, container security, cloud networking, security automation. There's overlap but we can separate.
**Benefits** (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.
**Pay**: Compensation: $80,000–$130,000 annually, depending on experience and assignment.
**Schedule**: 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.
We should not include "About Via Logic" as it's not in headings list; but we could include as a paragraph under maybe "About the role"? However 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 says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should stick to those.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to ensure we don't include empty sections. All have content.
Now format:
About the role
Full-time, W-2 position onsite at a government site in the Washington, DC metropolitan area. Work may focus on identity and access, secure cloud configuration, network controls, monitoring, automation, or resolving cloud security findings.
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
- U.S. citizenship.
- Ability to complete the CBP suitability process and receive a favorable determination before starting (includes background investigation and review of credit history).
- 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
- 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.
But we also need to include experience years? Already in Requirements. Qualifications could focus on the "What You Bring" items besides experience and clearance. Let's list:
- 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.
- Experience with infrastructure as code, scripting, CI/CD, container security, cloud networking, or security automation is welcome.
- Specific platforms and tools vary by assignment; you do not need to have used every item listed here.
We could also include ability to work with engineers etc. Already in Qualifications.
Let's decide: Qualifications: list of experience/skills beyond baseline.
Thus:
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.
- Experience with infrastructure as code, scripting, CI/CD, container security, cloud networking, or security automation is welcome.
- Specific platforms and tools vary by assignment; you do not need to have used every item listed here.
Now Skills: maybe we can list technical skill areas: cloud platform services, IAM, networking, logging, security services, IaC, scripting, CI/CD, container security, cloud networking, security automation. But that duplicates qualifications. Perhaps we can omit Skills section to avoid thin sections. But we have content for Skills; we could combine Qualifications and Skills into one section, but we already have Qualifications with many items. The instruction: Prefer a few substantive sections over many thin ones. So maybe we should not include Skills if it's thin. However we have distinct skill list; but we could incorporate into Qualifications. Let's see if we can make Qualifications substantive enough.
Qualifications currently has 6
- for any list of duties/requirements/benefits. Use
for prose. We need to include a section only when posting has real specific content for it. So we need to decide which sections to include. Potential sections: - About the role: could include description of role, mission, maybe "Your Mission". Could be "About the role" heading. - Responsibilities: list of duties (Your Mission bullet points). Could be under Responsibilities. - Requirements: eligibility & clearance requirements (US citizenship, CBP suitability, clearance). Also maybe experience requirement. - Qualifications: "What You Bring to the Expedition" (experience, skills). Could be Qualifications. - Skills: maybe list of specific skills (cloud platform, IAC, scripting, CI/CD, container security, cloud networking, security automation). Could be Skills. - Benefits: "Why Explorers Stay" (healthcare coverage, paid time off, teammates, opportunities, meaningful work). Also maybe "How We Work" includes schedule etc. - Pay: compensation range. - Schedule: schedule depends on opening, extended hours or on-call expectations discussed, virtual meetings expectations. We need to avoid filler like "commensurate with experience" etc. We have actual compensation range. We need to ensure we don't create sections with placeholder text. Let's extract content. **About the role** (maybe combine location, type, mission). Could be a paragraph: "Full-time, W-2 position onsite at a government site in the Washington, DC metropolitan area. Work may focus on identity and access, secure cloud configuration, network controls, monitoring, automation, or resolving cloud security findings." **Responsibilities** (Your Mission bullet points): - 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** (Eligibility & Clearance Requirements + maybe experience baseline): - U.S. citizenship. - Ability to complete the CBP suitability process and receive a favorable determination before starting (includes background investigation and review of credit history). - 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** (What You Bring to the Expedition): - 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. - Specific platforms and tools vary by assignment; you do not need to have used every item listed here. **Skills** (maybe combine with qualifications? But we can separate: list of technical skills: cloud platform, IAM, networking, logging, security services, IaC, scripting, CI/CD, container security, cloud networking, security automation). However we already listed many in qualifications. Might be redundant. Better to keep Qualifications as experience, and Skills as technical abilities. But we can also merge. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one section called "Qualifications & Skills". But headings list includes both; we can choose to include only those with content. We could include Qualifications and Skills separate if we have distinct content. Let's see: Qualifications: experience years, ability to work onsite, etc. Skills: hands-on experience with cloud platform, IaC, scripting, CI/CD, container security, cloud networking, security automation. There's overlap but we can separate. **Benefits** (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. **Pay**: Compensation: $80,000–$130,000 annually, depending on experience and assignment. **Schedule**: 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. We should not include "About Via Logic" as it's not in headings list; but we could include as a paragraph under maybe "About the role"? However 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 says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should stick to those. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to ensure we don't include empty sections. All have content. Now format:
About the role
Full-time, W-2 position onsite at a government site in the Washington, DC metropolitan area. Work may focus on identity and access, secure cloud configuration, network controls, monitoring, automation, or resolving cloud security findings.
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
- U.S. citizenship.
- Ability to complete the CBP suitability process and receive a favorable determination before starting (includes background investigation and review of credit history).
- 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
- 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.
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.
- Experience with infrastructure as code, scripting, CI/CD, container security, cloud networking, or security automation is welcome.
- Specific platforms and tools vary by assignment; you do not need to have used every item listed here.