> Markdown version of [/jobs/ext/4208694-site-reliability-engineer](https://www.wearedevelopers.com/jobs/ext/4208694-site-reliability-engineer). 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).

---

# Site Reliability Engineer

- **Company:** Hadrian Inc.
- **Location:** Bodega Bay, CA, United States
- **Salary:** $175,000.0 - $285,000.0
- **Contract:** Permanent contract
- **Skills:** Microsoft Windows, Application Programming Interfaces (APIs), Apple Mac Systems, Bash Shell, Configuration Management, Python (Programming Language), Windows PowerShell, Ansible, Software Vulnerability Management, Pulumi, Workspace ONE, Infrastructure as Code (IaC), Microsoft InTune, Patch Management, Casper Suite, Puppet, Terraform
- **Published:** October 9, 2026
- **Apply:** https://www.thejobnetwork.com/job/f8909764-3c81-4068-b19e-2dc386558531/site-reliability-engineer-client-platform

## About the Role

* Ownership. You treat the fleet as a product, take incidents personally, and close the loop with automation rather than a runbook. Strong scripting in Python, Bash, and PowerShell.
 * Scalability. Hands-on experience with Infrastructure as Code (IaC) and configuration management: Ansible and Terraform (or equivalents like Chef, Salt, Puppet, Pulumi).
 * Device Management. Working knowledge of at least one major MDM (Fleet DM, Intune, Jamf, Workspace ONE) and its API surface.
 * Security Remediation. Practical experience with patch management, vulnerability remediation, and endpoint hardening on both macOS and Windows.

What Will Set You Apart

 * Strong computer science fundamentals. You can reason about systems from the operating system up, demonstrating durable and sustainable solutions.
 * Experience building self-healing or auto-remediation platforms (remote actions, osquery + response, custom agents). Exposure to OT (Operational Technology) systems.
 * Comfort operating in an SRE culture: SLOs, error budgets, and blameless postmortems applied to the end-user experience.