Senior Staff Engineer Anywhere Cloud Cloudera Object Store

Job description

**Business Area:** Engineering **Seniority Level:** Mid-Senior level **The Technical Surface** You wont touch all of this every day, but you should be comfortable picking up any of it when the system needs you to. **Youll work across:** - Rust: Async I/O with tokio, io\\_uring buffer rings, zero-copy. - Java: Existing Apache Ozone codebase contribute upstream fixes, and maintain the stable contract between Java metadata services and the Rust data plane. - Go: Kubernetes operator built on controller-runtime, CRDs, reconcilers for StatefulSets/Deployments/PVs, init container orchestration, status conditions, and event reporting. - Kubernetes: Persistent volumes and storage classes, pod topology and anti-affinity, Istio ambient mesh for mTLS, NetworkPolicies, node maintenance flows, rolling upgrades, ResourceQuotas. - Distributed Systems: Erasure coding (RS-3-2, RS-6-3, RS-10-4), Ratis consensus, container replication, block deletion at scale, scrubber and reconciliation, online/offline EC reconstruction. **What Youll Actually Do** **As a Builder** - Own end-to-end implementation of major features from design spec through merged code to production validation. - Contribute upstream to Apache Ozone for shared components. - Build the Kubernetes-native test suite, S3 conformance, EC fault injection via pod eviction, decommission and maintenance mode flows, and bit rot detection. **As a Force Multiplier** - Mentor engineers across the Rust, Go, and Java parts of the stack. The team has deep individual expertise but needs someone who can connect the dots between layers. - Run rigorous technical reviews. We dont approve PRs that pass tests but skip invariant verification. We dont ship features without articulated failure modes. You will set this bar. - Make and document architectural decisions. Not every choice has a "right" answer what matters is that the rationale survives the engineer who made it. - Push back on scope creep, hidden complexity, and "lets add it just in case" thinking. Three similar lines of code beats a premature abstraction. **What You Bring** **Required** - 8+ years building production distributed systems, with at least 3 years at the Staff level (or equivalent). Youve owned systems through architecture, implementation, on-call, and customer escalations. - Deep expertise in at least two of: Rust, Go, Java. You dont need to be world-class in all three on day one, but youve shipped non-trivial code in multiple languages and arent religious about which language solves a given problem. - Strong storage or distributed systems background. You understand consensus protocols (Raft, Paxos), erasure coding tradeoffs (latency vs. durability vs. storage overhead), the cost of fsync, and why "exactly once" is a lie. - Production Kubernetes experience. Youve written operators, debugged controller reconciliation loops, traced networking issues across CNI/Istio, and understand the gap between kubectl apply succeeded and "the system actually works." - Track record of technical leadership. Design specs youve authored that others built from, architectural decisions that survived contact with reality, and PR feedback that measurably improved code. - Comfort with ambiguity. You make progress when the spec isnt clear, upstream behavior is undocumented, and the team disagrees on the approach. **Strongly Preferred** - Apache Ozone or HDFS experience: Direct contribution to either project, or operations experience at scale (PB+). If youve debugged a Ratis pipeline issue or chased down a container replication anomaly, we want to talk. - S3 protocol experience: Youve implemented an S3-compatible server, written a SigV4 signer/verifier from scratch, or operated S3-compatible storage in production at scale. - Performance engineering: Profiling with perf/dhat/flamegraphs, understanding memory allocator behavior, or experience with io\\_uring, RDMA, or other modern I/O frameworks. - Open source contributions: Apache projects, Rust ecosystem crates (tokio, hyper, tonic), Kubernetes (kubebuilder, controller-runtime), or storage systems (RocksDB, Ceph, MinIO). - Multi-cloud / Kubernetes distribution experience: Youve shipped software for EKS, GKE, AKS, OpenShift, and on-prem K8s without special-casing each one. **You may also have:** - Erasure coding internals: ISA-L, Jerasure, or equivalent. You know what a Reed-Solomon generator matrix looks like and why CPU vectorization matters for stripe reconstruction throughput. - Network protocol design: Youve designed a wire protocol that survived real workloads. You know the difference between "gRPC streaming" and "actually achieving low latency over gRPC streaming." - Istio / service mesh expertise: Youve debugged mTLS handshake failures, written EnvoyFilters, and understand the cost of an L7 proxy hop in the data path. Disclaimer : This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.