> Markdown version of [/jobs/ext/4607681-software-engineer-ii-cloud-security](https://www.wearedevelopers.com/jobs/ext/4607681-software-engineer-ii-cloud-security). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer II, Cloud Security - **Company:** Qualia - **Location:** Austin, TX, United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Artificial Intelligence, Amazon Web Services, Software System Penetration Testing, Microsoft Azure, Cloud Computing, Cloud Computing Security, Computer Networks, Software Design Documents, Python (Programming Language), MongoDB, Node.Js, Open Source Technology, Role-Based Access Control, Reliability Engineering, Red Team (Cyber Security), TypeScript, Okta, Grafana, Software Security, Amazon Virtual Private Cloud (VPC), Kubernetes, Production Code, Vertica, Terraform, Microservices - **Published:** November 6, 2026 - **Apply:** https://job-boards.greenhouse.io/qualia/jobs/8336735 ## About the Role * 6+ years in cloud security, infrastructure, SRE, or platform engineering, with at least 3 focused on securing production cloud environments * Deep hands-on AWS: IAM policy evaluation, Organizations, VPC and private connectivity, KMS, CloudTrail, GuardDuty or equivalent * Production Kubernetes security: RBAC, admission control, network policy, pod security, and how workloads authenticate to cloud APIs * Strong Terraform (or similar IaC) - you write and review modules, and you've built guardrails other teams depend on * You write production code. Go preferred; Python or TypeScript welcome if you're ready to work in Go * You can explain how an attacker moves from a leaked credential or a compromised pod to sensitive data, and how you'd detect each step * Clear, direct writing: findings an engineer wants to fix and design docs that hold up in review * Experience in fintech, real estate tech, or another regulated, high-liability domain (Optional) * Cloud penetration testing, red team, or DFIR experience (Optional) * Supply chain security: artifact signing, SBOMs, SLSA-style provenance in CI/CD (Optional) * Open source security tooling, published research, or conference talks (Optional) ## Description * Harden AWS. Design and implement account structure, IAM roles and permission boundaries, network segmentation, and KMS usage, all in Terraform and Go * Secure Kubernetes. Ship admission policies, RBAC, network policies, workload identity, and runtime controls; keep container images minimal and patched * Build guardrails engineers want. Write hardened, reusable IaC modules and CI policy checks that make the secure path the easy one * Engineer detections. Build and tune cloud detections on CloudTrail, Kubernetes audit logs, and runtime signal; write the Go services and pipelines behind them and feed InfoSec's SIEM * Kill standing access. Implement just-in-time access, short-lived credentials, and secrets management for humans, services, and CI * Run posture to zero. Build and run our in-house posture checks in Go across AWS accounts and container images; fix root causes in code and automate the fix where the class repeats * Respond. Investigate cloud alerts and take the infrastructure side of incidents, then close the gap so it doesn't recur * Review and teach. Review infrastructure PRs and design proposals; pair with SRE and product engineers to land fixes, * Kubernetes and a microservice architecture, defined in Terraform and our infrastructure-as-code monorepo * Okta for workforce identity and SSO into AWS * NodeJS / TypeScript services, MongoDB, and an internal ClickHouse + Grafana security telemetry pipeline * Go for internal security tooling and detection services We are a remote-first development organization that values flexibility in how our teams work. In addition to supporting fully remote roles, we have an office in Austin, with a hybrid option available for those who live nearby and prefer in-person collaboration. While this role is based in Austin, Texas, we're open to exploring remote possibilities for qualified candidates.