Security Engineer III

Veeam Software is hiring a Security Engineer III to own threat detection and response across its cloud estate and build the security data lake that supports those efforts. The role designs detection pipelines and automations, hardens Azure and AWS environments, delivers cloud security controls as code, and improves detection coverage and tooling.

Responsibilities:

• Design and build our security data lake: decide what telemetry we ingest from Azure, AWS, SaaS, and endpoint sources, how it's normalized and retained, and what it costs, so that detection engineers and incident responders can answer questions in minutes instead of days
• Write, tune, and version-control detections as code. Own the full lifecycle: hypothesis, query, test, deploy through CI/CD, measure false-positive rate, and retire what stops earning its keep
• Build the response side with the detections. Automate triage and enrichment, wire runbooks into the tooling, and cut mean-time-to-detect and mean-time-to-respond on the alert classes that matter most
• Hands on hardening our Azure and AWS environments: identity and RBAC boundaries, network egress, key and secret handling, logging coverage, and public-exposure control across multiple tenants and accounts
• Deliver cloud security controls as Terraform. Anything you fix once should land in the modules and pipelines so it stays fixed, in every environment, without a human remembering
• Turn cloud security posture findings into a prioritized, owned, and closing queue. Partner with the teams that own the resources and make remediation the path of least resistance
• Run detection coverage assessments against a recognized threat framework, find the gaps that matter for our platform and threat model, and close them
• Set direction on detection and cloud security tooling: what to adopt, what to retire, and what we build ourselves

Requirements:

• 5+ years in security engineering, cloud operations, or detection engineering, with recent hands-on ownership of production cloud security work
• Production Terraform experience. You've written and maintained modules other teams consume, and you know why a security control belongs in code rather than in a runbook
• Real operational depth in both Azure and AWS: identity models, logging and audit sources, network boundaries, and where each provider's defaults leave you exposed
• Demonstrated detection building. You've written detections against real telemetry, tuned them against real false positives, and can explain a specific rule you shipped and how you validated it
• Strong cloud security fundamentals: RBAC and least privilege, secret and key management, egress control, and public-exposure prevention
• Fluency in at least one query language for security data (KQL, SQL, or equivalent) and the judgment to know when a query problem is actually a data-model problem
• Scripting and automation ability in Python or a comparable language, enough to build and maintain tooling rather than only configure vendor products
• A track record of shipping production code or infrastructure you can point to. This is a hands-on building role, not an advisory one
• Microsoft Sentinel at production scale: analytics rules, automation rules, ingestion cost management, and multi-workspace design
• Wiz experience, including turning posture and attack-path findings into an owned remediation workflow
• Incident response experience in a cloud environment, on-call or as an investigator
• Security data lake or SIEM migration experience, including cost and retention tradeoffs
• Kubernetes and container security exposure (AKS, EKS) and runtime detection for containerized workloads
• Familiarity with regulated-industry audit expectations (SOC 2 Type 2, ISO 27001, FedRAMP, HITRUST) and what auditors want from logging and monitoring controls
• Relevant certifications (Azure or AWS security specialty, GCIA, GCDA, or similar)