Cloud Security Engineer
Via Logic LLC · Ashburn, VA · 2 wk ago
On-siteEngineering$80k–$130k/yrFull-time
We need to output HTML fragment with sections: headings using for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, accessibility, fraud notice, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions.
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; 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: 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: bullet list of duties:
- 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.
- What You Bring to the Expedition: bullet list:
- Approximately 1–5 years of relevant experience in cloud engineering, cloud security, infrastructure security, or a related technical field. We will consider the depth of your work alongside your years of experience.
- 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.
- The ability to work with engineers and system owners to put practical controls in place and explain why they matter.
- The 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.
- Why Explorers Stay: bullet list:
- 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: paragraph:
- 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: paragraph: Tell us what you have secured, configured, or improved in a cloud environment. We are hiring for multiple openings at different levels through this posting, and a few clear sentences can tell us a lot. If your experience also reaches into DevSecOps, network security, or broader security engineering, we want to hear about that too.
- About Via Logic: paragraph describing company.
- Then we have EEO etc which we must remove.
We need to decide sections: About the role (maybe "About the role" corresponds to description of role? Could be "Your Mission" as Responsibilities. "What You Bring to the Expedition" as Requirements/Qualifications/Skills. "Why Explorers Stay" as Benefits. "How We Work" could cover Schedule (maybe mention schedules depend on opening). Also we have Compensation info: Pay section.
We must not create sections with placeholder text. So we need to include Pay section because compensation is given. Schedule section: we have some info about schedules depend on opening, discuss extended hours or on-call expectations. That's specific enough? It's not a specific schedule but mentions schedules depend on opening and we will discuss extended hours or on-call expectations. That's somewhat specific but not a concrete schedule. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedules depend on opening and we will discuss any extended hours or on-call expectations. That's still stating something about schedule. So we can include Schedule section with that info.
Benefits: we have "Why Explorers Stay" which includes healthcare coverage, paid time off, teammates, opportunities, meaningful work. That's benefits.
Thus sections: About the role (maybe a brief intro), Responsibilities (Your Mission), Requirements (What You Bring to the Expedition), Skills (maybe combine with Requirements? Could separate but we have overlapping. Could put Requirements as experience and qualifications, Skills as technical skills. But we risk thin sections. Better to have few substantive sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also "About Via Logic" as company info but not required heading? Could be part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (intro about role and company), Responsibilities (Your Mission), Requirements (What You Bring), Benefits (Why Explorers Stay), Pay (Compensation), Schedule (How We Work schedule part). Also maybe include "About Via Logic" as part of About the role.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information. So we need to include all points from each section.
Let's craft HTML:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, accessibility, fraud notice, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions.
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; 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: 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: bullet list of duties:
- 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.
- What You Bring to the Expedition: bullet list:
- Approximately 1–5 years of relevant experience in cloud engineering, cloud security, infrastructure security, or a related technical field. We will consider the depth of your work alongside your years of experience.
- 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.
- The ability to work with engineers and system owners to put practical controls in place and explain why they matter.
- The 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.
- Why Explorers Stay: bullet list:
- 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: paragraph:
- 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: paragraph: Tell us what you have secured, configured, or improved in a cloud environment. We are hiring for multiple openings at different levels through this posting, and a few clear sentences can tell us a lot. If your experience also reaches into DevSecOps, network security, or broader security engineering, we want to hear about that too.
- About Via Logic: paragraph describing company.
- Then we have EEO etc which we must remove.
We need to decide sections: About the role (maybe "About the role" corresponds to description of role? Could be "Your Mission" as Responsibilities. "What You Bring to the Expedition" as Requirements/Qualifications/Skills. "Why Explorers Stay" as Benefits. "How We Work" could cover Schedule (maybe mention schedules depend on opening). Also we have Compensation info: Pay section.
We must not create sections with placeholder text. So we need to include Pay section because compensation is given. Schedule section: we have some info about schedules depend on opening, discuss extended hours or on-call expectations. That's specific enough? It's not a specific schedule but mentions schedules depend on opening and we will discuss extended hours or on-call expectations. That's somewhat specific but not a concrete schedule. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedules depend on opening and we will discuss any extended hours or on-call expectations. That's still stating something about schedule. So we can include Schedule section with that info.
Benefits: we have "Why Explorers Stay" which includes healthcare coverage, paid time off, teammates, opportunities, meaningful work. That's benefits.
Thus sections: About the role (maybe a brief intro), Responsibilities (Your Mission), Requirements (What You Bring to the Expedition), Skills (maybe combine with Requirements? Could separate but we have overlapping. Could put Requirements as experience and qualifications, Skills as technical skills. But we risk thin sections. Better to have few substantive sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also "About Via Logic" as company info but not required heading? Could be part of About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role (intro about role and company), Responsibilities (Your Mission), Requirements (What You Bring), Benefits (Why Explorers Stay), Pay (Compensation), Schedule (How We Work schedule part). Also maybe include "About Via Logic" as part of About the role.
We must not repeat job title as heading. No Job ID.
We must preserve all substantive information. So we need to include all points from each section.
Let's craft HTML:
About the role
Via Logic is hiring for multiple openings at different experience levels to support CBP work at a government site in the Washington, DC metropolitan area. Your work may focus on identity and access, secure cloud configuration, network controls, monitoring, automation, or resolving cloud security findings. The role is full-time, W-2, onsite.
But we need to include eligibility & clearance requirements: U.S. citizenship, CBP suitability process, background investigation, credit history review, additional clearance (Secret/Top Secret, SCI). That could be part of Requirements. Responsibilities: list from Your Mission. Requirements: combine experience, education? Not given. Include: Approximately 1–5 years of relevant experience in cloud engineering, cloud security, infrastructure security, or related field; depth of work considered alongside years. 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 welcome. Specific platforms/tools vary; you do not need to have used every item listed. Also eligibility: U.S. citizen, able to complete CBP suitability process, meet clearance requirements (Secret/Top Secret, SCI). We'll include that. Skills: maybe we can separate technical skills from eligibility. But we can combine into Requirements. Benefits: Healthcare coverage and paid time off; teammates who share knowledge; opportunities to deepen specialty and explore adjacent areas; 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 opening; will discuss any extended hours or on-call expectations before moving forward with a specific assignment. Also note onsite work, virtual meetings expect active participation and use video when appropriate and permitted. We also have "How We Work" paragraph about working onsite, with teammates, using tools approved, schedules depend, virtual meetings. We'll incorporate that into Schedule section. We also have "Your Route Into Via Logic" and "About Via Logic". Those could be part of About the role or maybe a separate section "About Via Logic". But we can include them in About the role paragraph. We must not include boilerplate like EEO, accessibility, fraud notice. So we omit those. Now produce HTML fragment only. Let's craft:About the role
Via Logic is hiring for multiple openings at different experience levels to support CBP work at a government site in the Washington, DC metropolitan area. Your work may focus on identity and access, secure cloud configuration, network controls, monitoring, automation, or resolving cloud security findings. The role is full-time, W-2, onsite. 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, helping modernize complex systems through automation, secure engineering practices, cloud‑native technologies, and scalable infrastructure solutions.
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
- Approximately 1–5 years of relevant experience in cloud engineering, cloud security, infrastructure security, or a related technical field; depth of work considered alongside years of experience.
- 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.
- U.S. citizenship required.
- Must be able to complete the CBP suitability process (background investigation and credit‑history review) and receive a favorable determination before starting.
- Must 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.
Benefits
- Healthcare coverage and paid time off that give you room to take care of life outside work.