Senior / Staff DevSecOps Engineer
Quick Summary
policies, tooling, rotation, and developer workflows that make doing the right thing easy. Lead security incident response: detection, containment, root cause analysis, and durable remediation.
America is under sustained cyber attack. Our adversaries infiltrate our networks, steal our IP, and degrade the digital infrastructure that modern life runs on. They’ve learned—correctly—that those attacks rarely produce consequences.
Twenty was founded to change that, by making our adversaries think twice before they attack us. Our vision is American and allied primacy in cyberspace—a future where they cannot contest us, deterrence is assured, and the free world remains secure.
Founded in 2024, Twenty Technologies (www.twenty.io) industrializes offensive cyber operations for the U.S. and its allies. Headquartered in Arlington, Virginia, Twenty has raised $168M from Khosla Ventures, Accel, Caffeinated Capital, Friends & Family Capital, Point72 Ventures, General Catalyst, and In-Q-Tel.
Mission | On Site | Full Time | U.S. Citizenship Required / No Active Clearance Required
You'll build and own the security infrastructure that keeps Twenty's engineering systems safe without slowing engineers down. This role spans runtime security, access control, secrets management, compliance, and CI/CD hardening — but it's equally about making security the path of least resistance. You'll embed with our engineering teams, design secure-by-default foundations, and build the tooling and automation that lets developers move fast without cutting corners. You'll report directly to the VP of Engineering and operate as a shared function across our product teams.
Responsibilities
~1 min read- →
Own runtime security and vulnerability management across cloud and container environments, including triage, prioritization, and remediation tracking.
- →
Design and enforce identity and access management (IAM) across AWS and internal systems — least-privilege by default.
- →
Own secrets and credentials management: policies, tooling, rotation, and developer workflows that make doing the right thing easy.
- →
Lead security incident response: detection, containment, root cause analysis, and durable remediation.
- →
Manage AWS Organization structure, account boundaries, SCPs, and guardrails.
- →
Harden and maintain CI/CD pipelines, embedding security scanning and policy enforcement into the software delivery lifecycle.
- →
Drive compliance efforts — own the evidence, controls, and remediation work to meet and maintain relevant frameworks.
- →
Build and maintain secure-by-default templates for repos, pipelines, and infrastructure modules.
- →
Reduce friction through automation: certificate issuance, secrets access, policy-as-code, and developer-facing tooling.
- →
Produce lightweight, practical security guidance that engineers actually use.
- →
Shape the direction of the DSO function as it scales, and contribute to hiring and team-building as we grow.
You believe security should be a force multiplier for engineering, not a gatekeeper.
You take ownership end-to-end: from identifying a risk to designing the control to shipping the fix.
You bring high judgment to tradeoffs — you know when to enforce hard controls and when friction kills adoption.
You communicate clearly with both engineers and non-technical stakeholders, and you translate risk into plain language.
You prefer automation over policy: if an engineer has to do something manually to stay secure, you see that as a bug.
You hold a high bar for reliability and auditability in the systems you build.
You're self-directed and thrive in an environment where the function is new and you're defining it.
Requirements
~2 min read8+ years in DevSecOps, platform security, or a closely related security engineering role.
Deep hands-on experience with AWS — IAM, SCPs, Organizations, security services (GuardDuty, Security Hub, CloudTrail, etc.).
Strong IaC experience with Terraform; you've used it to enforce security controls, not just provision infrastructure — and you've layered in policy-as-code tooling (e.g., OPA, Checkov, tfsec) or continuous compliance checks (e.g., AWS Config Rules) to catch drift and misconfigurations.
Experience owning secrets management end-to-end in a production engineering environment.
Proven track record designing and hardening CI/CD pipelines (we use GitHub Actions).
Hands-on experience with container security, including image scanning and runtime controls.
Experience leading or meaningfully contributing to a compliance program; CMMC Level 2 (or NIST SP 800-171) experience strongly preferred.
You've run incident response — you've been on call, you've led the post-mortem, and you've shipped the fix.
Strong communication skills and the ability to drive security adoption through enablement, not mandates.
Due to U.S. government contract and security requirements, this role is limited to U.S. citizens. Some positions may also require eligibility to obtain and maintain a U.S. Government security clearance. Any active clearance requirement will be listed in the role description.
Twenty is an equal opportunity employer. We consider all qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, veteran status, disability, or any other protected status, consistent with applicable law.
If you need a reasonable accommodation during the hiring process, let us know and we will work with you.
Nice to Have
~1 min readExperience growing a DSO or security engineering function — expanding scope, tooling, and team.
Familiarity with observability tooling and using it for security signal (we use the LGTM stack).
Background in configuration management tooling (Ansible or similar).
Experience with developer-facing security platforms or internal tooling that improved engineering workflows.
Interest in growing into a lead or manager role as the team scales.
Cloud: AWS (primary), Terraform for IaC, Ansible for configuration management
Containers: Docker, Docker Compose
CI/CD: GitHub Actions
Vulnerability scanning: Trivy
Observability: Grafana, Loki, Tempo, Mimir (LGTM stack)
Alerting / on-call: PagerDuty
Languages in use across engineering: Go, TypeScript/Node, React, Python
This role requires eligibility to obtain and maintain a U.S. Government security clearance. This role may involve work in a controlled environment.
Location & Eligibility
Listing Details
- Posted
- April 15, 2026
- First seen
- September 26, 2026
- Last seen
- September 26, 2026
Posting Health
- Days active
- 0
- Repost count
- 0
- Trust Level
- 30%
- Scored at
- September 26, 2026
Signal breakdown
Browse Similar Jobs
Stay ahead of the market
Get the latest job openings, salary trends, and hiring insights delivered to your inbox every week.
No spam. Unsubscribe at any time.