Software Engineering MTS - Security Automation (Cloud Security)

TL;DR

Software Engineering MTS - Security Automation (Cloud Security): Responsible for ensuring the high-velocity platform remains impenetrable by translating compliance frameworks and corporate data policies into automated, programmatic rules. Focus on validating infrastructure deployed by developers for security and compliance before it reaches production.

Location: New York, NY; San Francisco, CA

Company

hirify.global is a company.

What you will do

• Write, test, and maintain rules that evaluate developer Pull Requests to ensure they meet data classification standards.
• Maintain and update the knowledge base and rule sets used by AI-augmented GitOps agents.
• Implement programmatic boundaries to restrict unauthorized regions, mandate encryption, and enforce a strict "Private-by-Default" network posture.
• Ensure operational and audit telemetry is aggregated into centralized, tamper-proof storage, and monitor aggregated threat detection dashboards to resolve anomalies.

Requirements

• Bachelor's degree in Computer Science, Computer Engineering, Software Engineering or relevant work experience
• 4+ years of experience in cloud security, DevSecOps, or security automation engineering.
• Hands-on experience writing and deploying Policy-as-Code (e.g., Open Policy Agent, Rego, Sentinel).
• Deep understanding of enterprise cloud security constructs, centralized policy enforcement, and KMS cryptography.
• Familiarity with translating rigorous compliance frameworks (e.g., NIST SP 800-53, FedRAMP, SOC2) into automated technical controls.
• Strong scripting skills (Python, bash) for developing automated security remediation lambda functions.

Culture & Benefits

• Treating internal developers as primary customers and prioritizing their velocity and user experience.
• Eradicating manual toil and "ticket-ops" via GitOps and AI-augmented workflows.
• Believing that security should be "shifted left" and built into the code, not bolted on as an afterthought.
• Engineering for failure, prioritizing self-healing systems, and maintaining a 99.999% availability standard.
• Relying on telemetry, centralized logging, and ChatOps to proactively identify and resolve issues.