Principal Engineer, Security Products — Cryptography and Key Lifecycle Management

Weights & Biases Weights & Biases · Data AI · New York, NY · Technology

CoreWeave is seeking a Staff or Principal Engineer for their Security Products team to lead the technical direction and implementation of encryption and key lifecycle management. This role involves designing and evolving key lifecycle management, encryption control planes, algorithm/library selection, and systems integrations to protect AI workloads and data on their cloud platform, particularly for regulated customers. The position blends hands-on system design and coding with cross-team technical leadership and roadmap shaping.

What you'd actually do

  1. Lead the design and evolution of encryption and key lifecycle management products.
  2. Manage encryption and cryptography technology development for services within our Cloud Platform, particularly those for high security and highly regulated customers.
  3. Design and build deep integrations between our Cloud Platform and external key sources (eg, HashiCorp Vault, AWS KMS, HSMs).
  4. Collaborate with other product engineering teams to support the safe use of multicloud key management technology.
  5. Partner with IAM to define unified authorization patterns and policy models for key management APIs with consistent semantics across the resource hierarchy.

Skills

Required

  • 8+ years of experience building and operating distributed backend systems in production
  • ownership of reliability and security outcomes for critical services
  • Deep experience with encryption at rest and key management systems
  • envelope encryption patterns
  • key hierarchies
  • secure key lifecycle management
  • Hands-on experience integrating with at least one major KMS or secrets manager (e.g., AWS KMS, HashiCorp Vault, Azure Key Vault, GCP KMS, HSMs)
  • designing APIs and workflows around those systems
  • Strong proficiency in a systems programming language such as Go (preferred) or Rust
  • experience building networked services (gRPC / REST) in a Linux / Kubernetes environment
  • Solid understanding of applied cryptography concepts relevant to data‑at‑rest protection (AES‑GCM/CTR, key wrapping, KDFs, randomness requirements, envelope encryption, and key separation)
  • ability to reason about threat models and failure modes with Security partners
  • Experience designing and operating multi‑tenant services with strong isolation and authorization semantics across customers and internal tenants
  • Demonstrated track record of leading cross‑team technical initiatives
  • driving projects from problem statement through rollout, alignment, and operational readiness
  • Strong operational experience defining SLIs / SLOs
  • building dashboards and alerts
  • partnering with SRE / Production Engineering on incident response and post‑incident improvement
  • Excellent written and verbal communication skills
  • ability to produce clear, opinionated design docs that influence Senior Engineers, PMs, and Security stakeholders through context setting and sound technical judgment

Nice to have

  • Prior experience designing or implementing remote or externalized key management for cloud storage, databases, or filesystems (e.g., BYOK/BYOKMS, customer‑managed keys, envelope encryption for S3‑like object storage)
  • Experience with hardware‑backed key management (HSMs) and cryptographic compliance regimes (FIPS 140‑2/3, PCI, HIPAA, FedRAMP Moderate+, or similar) and how they shape system design
  • Familiarity with IAM policy models (RBAC / ABAC, OpenFGA, OPA/Rego, etc.) and how to integrate fine‑grained authorization into security‑sensitive APIs
  • Experience extending encryption and key management across multiple storage domains (object storage, block/file storage, databases, control plane state like etcd) in a coherent way
  • Background working in security‑sensitive or regulated environments where auditability, segregation of duties, and key custody requirements are critical
  • Contributions to open source cryptography, security tooling, or KMS/client libraries
  • Previous US/NATO federal cryptographic security experience is ideal but not necessary

What the JD emphasized

  • highly regulated customers
  • regulated environments
  • regulated and security‑sensitive workloads
  • security‑sensitive or regulated environments
  • cryptographic compliance regimes
  • security‑sensitive AI workloads