Senior Security Engineer, Docker Desktop

Responsibilities

• Partner with engineering and product teams throughout the development lifecycle to identify security risks early, from design review through code review and release.
• Conduct threat modeling and security design reviews for new and evolving product features, with particular focus on authentication, authorization, and container runtime security.
• Serve as the team's primary liaison to the organization's security group, attending security syncs, relaying guidance, and translating central policy into practical engineering decisions.
• Act as the first point of contact for incoming vulnerability reports and CVEs: validate severity, reproduce issues, coordinate disclosure timelines, and drive remediation with the relevant engineers.
• Review Go code with a security mindset, identifying classes of issues such as privilege escalation, insecure defaults, injection risks, and improper credential handling.
• Contribute security-focused improvements directly to the codebase where appropriate.
• Develop and maintain internal security documentation, guidelines, and runbooks for the team.
• Stay current on the Linux security landscape as it pertains to containers: namespaces, cgroups, seccomp, AppArmor, capabilities, and the evolving OCI ecosystem.
• This role may require participation in an on-call rotation to provide support outside of standard business hours, including evenings, weekends, and holidays, as needed.

Qualifications

• 6+ years of experience in security engineering, application security, or a closely related discipline, with a track record at senior or staff level.
• Bachelor’s degree in Computer Science, Engineering, or a related field, or equivalent practical experience.
• Strong proficiency in Go, with the ability to review and contribute to production-grade code.
• Deep understanding of Linux fundamentals relevant to container security: namespaces, cgroups, capabilities, seccomp profiles, AppArmor/SELinux, rootless containers, and privilege boundaries.
• Solid grasp of OCI specifications and container runtime security (e.g. runc, containerd, BuildKit).
• Hands-on experience with identity and access management concepts: OAuth 2.0, OIDC, token handling, and auth flows in desktop or cloud-adjacent contexts.
• Experience performing security design reviews, threat modeling, and participating in secure development workflows.
• Familiarity with vulnerability management processes: CVE triage, CVSS scoring, coordinated disclosure, and working with external reporters.
• Strong written and verbal communication skills; comfortable bridging the gap between a dedicated security team and a product engineering team.

What to ExpectFirst 30 DaysYou will onboard into the team and get hands-on with the Docker Desktop codebase, architecture, and development workflow. You will meet your counterparts in the central security organization and learn how vulnerability reports are currently handled. The goal is to listen, ask questions, and build a clear picture of the product's current security posture, not to change anything yet.

First 90 DaysYou will be an active participant in design and code reviews, bringing a security lens to features in flight. You will have taken ownership of the vulnerability intake process, handling your first end-to-end triage cycles with minimal guidance. You will have a working relationship with the engineers on the team and a growing sense of where the most meaningful security investments should be made.

One Year Outlook (First Year)You will be the team's trusted authority on product security. You will have driven meaningful improvements to how the team approaches security across the development lifecycle, whether that's better threat modeling practices, improved auth flows, stronger container isolation defaults, or reduced time-to-remediation for reported issues. you will be a known presence in the broader security organization, and your work will be directly visible in the security and resilience of a product used by millions of developers every day.

Docker considers visa sponsorship on a case-by-case basis based on business needs.