Senior Principal Software Engineer - Crypto

Oracle Oracle · Enterprise · Nashville, TN +1

Senior Principal Software Engineer for Oracle's Crypto organization's KMS team. This role focuses on the architecture and operational maturity of a Tier 0 key management service, protecting customer and internal keys on HSM-backed infrastructure. Responsibilities include defining architecture, leading technical strategy, partnering with cross-functional teams, driving operational excellence, and evaluating responsible AI opportunities within a highly secure and regulated environment.

What you'd actually do

  1. Define and drive the short- and long-term architecture for OCI KMS across HSM-backed key management, service software, distributed systems, and regional reliability.
  2. Lead technical strategy for a Tier 0 service where durability, recoverability, and operational rigor are fundamental product requirements.
  3. Partner with security, hardware/platform, SRE, product, and dependent OCI service teams to reduce systemic risk and improve service resilience.
  4. Drive operational excellence through observability, incident learning, SLO discipline, failure-mode analysis, and pragmatic engineering execution.
  5. Evaluate and shape responsible AI opportunities for KMS while preserving security boundaries, customer trust, and compliance expectations.

Skills

Required

  • Experience leading architecture for large-scale cloud infrastructure, distributed systems, or security-critical services at senior IC level.
  • Strong background in service reliability, operational excellence, incident response, and production ownership for high-availability systems.
  • Working knowledge of cryptography, key management, HSM-backed systems, secrets management, identity, or adjacent cloud security domains.
  • Ability to reason about stateful distributed systems, data durability, dependency isolation, regional failure modes, and recovery design.
  • Demonstrated ability to influence cross-functional technical direction across engineering, security, SRE, and product stakeholders.

Nice to have

  • Sound judgment on AI/ML adoption in regulated or security-sensitive infrastructure environments

What the JD emphasized

  • Tier 0 key management service
  • HSM-backed infrastructure
  • security-critical service
  • security boundaries
  • customer trust
  • compliance expectations
  • regulated or security-sensitive infrastructure environments