Senior Site Reliability Engineer

Responsibilities Take an architect-approved design and turn it into production code that ships through GitOps + the CICD release pipeline. Build and operate one or more bounded contexts of the NeoCloud SRE platform. Own 1-2 of various services including collection, alert, correlation, and SLO frameworks. Implement fault-prediction and remediation workflows. Manage hardware lifecycle and data center operations. Develop services for identity, secrets, tenant configuration, and customer bridging. Requirements 7+ years of production software engineering experience, including 2 or more years operating what you built (real on‑call experience, not just shipping code). Production‑depth mastery of at least one systems‑grade language—Go (preferred), Rust, or Java. Proficiency in Python for tooling and SDK work. Strong grasp of at‑least‑once vs. exactly‑once trade‑offs, idempotency, back‑pressure, leader election, consistent hashing, gossip, and fan‑out. Experience at production scale with Prometheus, VictoriaMetrics, Mimir, Thanos, Loki, Elasticsearch, Tempo, Jaeger, or OpenTelemetry. Hands‑on experience with Argo, Flux, Helm, Kustomize, Cosign signing, signed‑bundle promotion, and blast‑radius‑aware rollouts. Proven experience writing a controller or CRD handling real production traffic, with a deep understanding of watch‑cache mechanics, leader election, and reconcile loops. Experience executing end‑to‑end mTLS bootstrap with certificate rotation. Hands‑on experience with HashiCorp Vault or cloud KMS (AWS KMS / GCP KMS). Ability to read a Prometheus query plan, build a recording‑rule strategy, and write SQL that joins per‑tenant telemetry against analytics‑lake tables. Rigorous approach to unit, integration, contract, chaos, and soak testing. Ability to author clear design docs that align with existing platform architecture, create runbooks optimized for 3 AM on‑call responses, and write intent‑driven PR descriptions. #J-18808-Ljbffr