Senior Principal Software Engineer (Go)

Required

• Technical Skills & Experience
• Advanced Go (Golang) Proficiency: 3+ years of professional experience writing production-grade Go code, with a deep understanding of concurrency patterns (goroutines, channels) and profiling.
• Kubernetes Internals & Operator Pattern: Strong hands-on experience using the controller-runtime library, client-go, Operator SDK, or Kubebuilder to build custom controllers and operators.
• Cloud-Native Infrastructure Automation: Experience building and managing infrastructure declaratively, ideally with control-plane-based provisioning tools like Crossplane.
• GitOps & Continuous Delivery: Proficiency with GitOps workflows and continuous delivery practices, using tools like Flux, Helm, and Kustomize to manage infrastructure lifecycles.
• Soft Skills & Engineering Mindset
• Systems Thinker: Ability to view physical hardware and hyperscale clouds not as static targets, but as endpoints controlled by software APIs.
• Collaboration & Communication: Strong capability to bridge the gap between pure application developers and traditional infrastructure engineers, speaking comfortably to both.
• Ruthless Solver of Race Conditions: An investigative mindset capable of debugging complex, asynchronous distributed systems where resources depend on sequential, timed events.
• Extreme Ownership: A proven track record of acting as a technical steward for a product or subsystem, where you care as much about the operational metrics, edge-case failures, and technical debt of the system as you do about delivering new features.
• Defensive Engineering Mindset: An engineering approach that assumes distributed systems will fail asynchronously. You naturally build deep observability, robust error handling, self-healing reconcile loops, and fallback mechanisms into your Go controllers.
• Traceability and Documentation: A commitment to maintaining clear architectural records (ADRs), comprehensive unit/integration test suites, and clear API documentation, ensuring that your subsystem can be safely maintained by other engineers.