Security Engineer

Deepgram•,

39d•$150,000 - $245,000

About The Position

Deepgram is seeking a Security Engineer to build and automate the technical controls for its security program. The role involves managing security for a primarily bare-metal infrastructure with containerized workloads (Docker, Ansible, GitHub Actions) and some AWS usage. The company culture is high-trust and fast-moving, requiring controls to be delivered as code, reproducible, and self-auditing. The engineer will be responsible for host hardening, configuration management, vulnerability and patch management, penetration testing, container security, detection and response, CI/CD and supply chain security, and supporting SOC 2, PCI DSS, and ISO 27001 compliance. A key aspect of the role is the aggressive use of AI and agentic tooling to enhance efficiency and secure AI systems and adopted tools. This is a hands-on technical position, distinct from a GRC role, focusing on the implementation and evidence generation for security controls. The role reports to the Director of Information Security, and the company is open to hiring strong mid-level and senior candidates, calibrating title, scope, and compensation accordingly.

Requirements

Solid experience in security engineering or infrastructure engineering with a security focus — enough that you have owned controls in production, not just recommended them.
Deep Linux. You should be comfortable hardening, debugging, and reasoning about a large fleet of physical Linux hosts — users and sudo, SSH, systemd, kernel and package updates, host firewalls, and what a host-based agent is actually doing.
Ansible at fleet scale is required. You automate first and document second.
Strong scripting. Python and/or Go, plus real shell competence.
Production experience securing Docker containers and the pipelines that build them.
Hands-on experience securing GitHub and GitHub Actions: branch protection, CODEOWNERS, workflow permissions, secrets, and third-party action risk.
Experience running vulnerability and patch management as an ongoing program — including the unglamorous part, which is getting other teams to actually ship the fix.
Experience managing third-party penetration tests from the inside: scoping them well, and turning a report into closed engineering work rather than a PDF in a folder.
Hands-on involvement in at least one formal audit — ISO 27001, PCI DSS, or SOC 2 — as the engineer producing and defending evidence, not only as a reader of the report.
Comfortable using AI coding and agentic tools in daily work, and clear-eyed about their risks: prompt injection, secret leakage, and supply chain exposure.
Pragmatic. Controls that block shipping without a proportionate risk reduction get routed around, and we would rather you name the trade-off than pretend it does not exist.

Nice To Haves

Datacenter or colocation experience: network segmentation, out-of-band management (IPMI/BMC), physical and vendor controls.
Detection engineering or SIEM/HIDS ownership at scale (for example Wazuh, OSSEC, Elastic).
Secrets management with HashiCorp Vault.
AWS security (IAM, SCPs, VPC) and Terraform.
Kubernetes security.
Offensive security background: penetration testing or red teaming.
PCI DSS work inside a cardholder data environment.
Ownership of a secure SDLC program.
Experience with GPU infrastructure, ML platforms, or multi-tenant inference workloads.
Certifications such as OSCP, GIAC, CISSP, or AWS Security Specialty.

Responsibilities

Build, deploy, and maintain security controls across our bare-metal fleet and AWS footprint — access management, network segmentation and firewalling, encryption and secrets management, logging and detection coverage, endpoint security, and vulnerability management.
Own configuration management and host hardening as code with Ansible, so baselines are reproducible across hundreds of Linux hosts and drift is detectable rather than merely documented.
Secure containerized workloads: Docker image build pipelines, registry scanning, runtime hardening and detection, and secrets management.
Run vulnerability management end to end — discovery, prioritization by real exploitability rather than raw CVSS, driving remediation with engineering teams, and reporting on it.
Own patch and update management as a program: the server fleet, the endpoint fleet, base images, OS and package updates, firmware where it matters, and dependency upgrades. Set and hold patch SLAs, track exceptions, and automate the routine cases so they do not depend on anyone remembering.
Own the penetration testing lifecycle: scoping and vendor selection, scheduling, triaging findings into engineering work with real owners and dates, verifying fixes on retest, and producing the summary we can share with customers.
Write detections, tune out noise, and take part in incident response. Improve log, telemetry, and security-agent coverage where we are blind.
Run periodic log and access reviews as a standing control, and automate the collection so each cycle produces its own evidence rather than a scramble.
Automate compliance evidence collection for SOC 2, PCI DSS, and ISO 27001, and support audit fieldwork on technical questions — the GRC lead owns the auditor relationship and the narrative; you own the systems that make the evidence true and repeatable.
Harden GitHub Actions CI/CD and the software supply chain: dependency and secret scanning, action pinning, SBOM, artifact and image signing, least-privilege OIDC in place of long-lived credentials.
Apply AI and agentic tooling to security work — triage, evidence gathering, code review, detection engineering — and help secure how the rest of the company uses AI.
Provide the technical input behind customer-facing security work: questionnaire and architecture answers, penetration test summaries, and hardening guidance for customers running Deepgram self-hosted.