Staff Security Software Engineer

Design and govern how access to production systems is granted, with scalable RBAC/ABAC across infrastructure and products.

Build robust secrets management, credential lifecycle, encryption, and key-management patterns.

Define how agents and automated systems receive, scope, and lose authority.

Create auditability and forensic visibility for user and system actions.

Lead threat modeling across infrastructure, product, and research, and strengthen incident detection and response.

Make secure patterns easy and automatic for engineering teams, and drive enterprise security readiness.

One way the first 90 could unfold.

Days 1–30 — Immerse & Diagnose: Map the current access, secrets, and trust boundaries, and where the biggest risks and enterprise gaps are.

Days 30–60 — Ship & Validate: Ship a foundational system (identity/access or secrets management) that engineers actually adopt.

Days 60–90 — Scale & Systemize: Extend to agent permissioning and audit, and build toward enterprise security readiness.

You've built and operated security foundations in real production environments.

Excellent at writing code, reviewing infrastructure, and shipping systems.

You think in systems and trust boundaries, and understand that software can act with real authority.

Deep thought about how services, automations, or models are scoped, constrained, and observed.

High agency, and the ability to balance pragmatism with long-term rigor.