Security Engineer, Full Stack

Job description

Job responsibilities

• Own security end-to-end across the whole stack — application code, cloud infrastructure (AWS/GCP), Kubernetes workloads, identity and authorization, and the factory-floor and operational-technology systems that produce…
• Scale security through automation . Build the agentic tooling and automation loops — AI-driven checks, paved-road patterns, self-enforcing guardrails — that let coverage grow with what you build rather than with…
• Dig into unfamiliar systems — new tech we're adopting and manufacturing systems few people understand — map how they actually work, identify where the real risk lies, and design controls that fit the way Hadrian builds.
• Turn compliance into engineering . Build the practical foundations for CMMC 2.0 / NIST 800-171 and the ITAR boundary as controls that hold up under audit — not paperwork beside the system.
• Respond when it matters . Investigate, contain, and drive incidents to resolution, then turn each one into a systemic fix and a better default.

Job requirements

• Ship the fix, not just the finding. You write code (Go, Python, or similar) and solve problems by building the guardrails and tooling — SDKs, CLIs, CI/CD checks, and patterns — that make it easy to do the right thing…
• 4+ years in security engineering, software engineering, or infrastructure/platform engineering, with real hands-on security ownership somewhere in there.
• Fluency with agentic systems . Familiarity with agentic loops and task delegation — building with or on LLM agents and automation
• You move fast and learn faster . You take an under-specified mission, decide where to start, make sound calls under uncertainty, and ramp on something unfamiliar quickly
• You weigh risk against innovation — and say so. You make the risk-aversion versus innovation trade-off explicit on real decisions, so the business chooses deliberately rather than defaulting to "no."
• A track record of deleting controls or process — retiring the checks that shouldn't exist and proving the automated replacement held.
• Genuine breadth and curiosity . You move between application security, cloud and Kubernetes security, identity/authorization, and networking — and you actively want to understand how a new layer works, down to the…