> Markdown version of [/jobs/ext/3949833-systems-resilience-engineer-hybrid-cloud-storage](https://www.wearedevelopers.com/jobs/ext/3949833-systems-resilience-engineer-hybrid-cloud-storage). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Systems Resilience Engineer - Hybrid Cloud Storage - **Company:** Qumulo, Inc. - **Location:** Seattle, WA, United States - **Experience:** Experienced - **Salary:** $140,000 - $210,000 - **Contract:** Permanent contract - **Skills:** Amazon Web Services, Amazon S3, Systems Engineering, Automation of Tests, Microsoft Azure, Ubuntu (Operating System), Cloud Computing, Cloud Storage, Computer Programming, Linux, Distributed File Systems, Python (Programming Language), Ansible, Prometheus, Software Systems, Cloud Platform System, Grafana, HybridCloud, Firewalls (Computer Science), Kubernetes, Low Latency, Influxdb, Data Analytics, Data Management, Hardware Infrastructure, Terraform, Jenkins - **Published:** October 27, 2026 - **Apply:** https://www.careerbuilder.com/job-details/systems-resilience-engineer-hybrid-cloud-storage-seattle-wa--2d012c87-e4d5-459a-aaf4-a133a078cbca ## About the Role Hybrid Cloud, Cloud Storage, Systems Engineering, Cloud Computing, Data Management, Test Design, Systems Engineering, Test Automation, Acceptance Testing, Testing, * 3+ years building and operating automated testing, validation, and/or certification for complex software systems * Strong programming ability in C. Experience with Qumulo's distributed file system, or parallel filesystems, would be a major plus * A real breaker's instinct. You go looking for edge cases and ask "what happens if I do this?" before anyone asks you to * A track record of building tests yourself, not just running test plans handed to you * Hands-on experience across both on-premises infrastructure and cloud (AWS, GCP, or Azure), with a real grasp of where each one's limits are * Working fluency in Linux (we run Ubuntu) and Python * A data-driven approach to deciding what to test and how often * Experience with orchestration tools (Ansible, Terraform), containers, and Kubernetes * Solid understanding of networks (routing, firewalls, security inspection devices, switch configuration) a plus * Storage (IOPS, Latency, read/write patterns) or protocol experience (NFS, SMB, S3, ) a strong plus ## Description Qumulo's cloud data platform manages exabytes of the world's most demanding data, unifying files, objects, and every workload across edge, core, and cloud. About the Role: You'll be one of the first hires on a team with a single mandate: find out how Qumulo breaks before our customers do. The platform manages exabytes of data for more than 1,100 customers across on-prem and every major cloud, and these are mission-critical workloads where a missed edge case becomes a customer's bad day. This is a Systems Resilience Engineer role for the engineer who thinks like a breaker. You'll put on the customer's hat, work out how a feature will really get used, and design the tests that push it past its limits across hardware and cloud. You'll automate the testing our principal engineers run by hand today, and decide what gets tested, how often, and why. You'll help build this function from the ground up, including where we set the quality bar and which builds are good enough to ship. As a Systems Resilience Engineer at Qumulo you will: * Design and operationalize testing for new features: work out how customers will actually use them, how to scale-test them, and how to break them * Automate the manual, repetitive testing our principal engineers run by hand today, using Python and our in-house frameworks on Jenkins and Argo * Build a data-driven plan for which tests run, how often, and why, plus the framework to schedule and rerun them * Troubleshoot build and test failures across VM instances and Qumulo-qualified hardware, from compile-time errors to integration failures * Read cluster output and C error logs to tell a test problem from an infrastructure problem from a real bug * Set up monitoring and alerting so problems surface early (we use OpenMetrics, Grafana, InfluxDB, and Prometheus alongside home-grown tooling) * Help set the quality bar for releases, including a real say in what ships * Take part in an on-call rotation for the systems your team owns