Principal Engineer - Release Engineering

You'll lead change across product teams through influence, not authority. You'll make the paved path the default, enforce standards at the pipeline gate, own migrations yourself with tooling rather than tickets, and make the safe path the faster one. You'll use leadership support for deprecations when the data justifies it.

Requirements:

• 8+ years building and operating production systems, with Staff-level scope: org-wide technical direction and at least one cross-team migration driven to completion.
• You've driven a technical decision through teams that didn't report to you, against real resistance.
• You've built an internal platform other teams adopted, and can explain why they adopted it.
• Deep experience designing and running CD at scale (Spinnaker, Argo CD/Rollouts, Harness or an in-house equivalent), including its failure modes.
• Deep Kubernetes knowledge: rollouts, apply and patch behaviour, and failure handling.
• Strong backend engineering in Go, Java/Kotlin or Python, and comfort working in large codebases you didn't write, including open-source tools.
• Sound judgment on the trade-off between speed and safety, defensible with data to engineers and executives.

Nice to have:

• Contributions to Spinnaker or similar open-source projects.
• Knowledge of statistical canary analysis and deployment validation techniques.
• Experience with workflow orchestration engines such as Temporal.
• Familiarity with hermetic builds and remote caching tools such as Bazel.
• Understanding of software supply chain security standards and tools, including SLSA and Sigstore.
• Experience delivering software solutions under audit and compliance requirements, particularly in finance or other regulated industries.