> Markdown version of [/jobs/ext/4587644-expert-interactive-coding-site-reliability-engineering-contract-remote](https://www.wearedevelopers.com/jobs/ext/4587644-expert-interactive-coding-site-reliability-engineering-contract-remote). 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). --- # Expert: Interactive Coding, Site Reliability Engineering (Contract, Remote) - **Company:** Patronus AI, Inc. - **Location:** United States (Remote available) - **Experience:** Experienced - **Salary:** $312,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Bash Shell, Bioinformatics, Continuous Integration, Python (Programming Language), Reliability Engineering, Large Language Models, AI Coding Agents, Terraform, Splunk, New Relic (SaaS) - **Published:** November 5, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=0787d4eef197aa77 ## About the Role * 3+ years running production systems in at least one of the areas above, including time on an on-call rotation within the last two years. You did the work yourself; managing the team is not enough. * Hands-on with Kubernetes, Prometheus and Grafana (or Datadog or New Relic), a log stack such as Loki, ELK or Splunk, infrastructure as code such as Terraform and Helm, and a CI/CD system. * Comfortable in Python, Go or Bash and at reading unfamiliar codebases. * Able to explain your reasoning out loud while you work, in clear professional English. * Reliable availability for scheduled live sessions and the habit of showing the evidence behind every conclusion. Nice to have * Experience writing runbooks, post-mortems, SLO definitions or incident training material. * Familiarity with how AI coding agents fail on operations work. ## Description * Incident response and on-call. Engineers on a production rotation who triage alerts, read metrics, logs and traces, find root cause, mitigate, roll back and write the post-mortem. Typical titles: Site Reliability Engineer, Production Engineer, On-Call Engineer, Platform Engineer. * Platform and infrastructure. Engineers who own clusters, deploy pipelines and infrastructure as code: Kubernetes, Helm, Terraform, CI/CD, networking and capacity. Typical titles: Infrastructure Engineer, DevOps Engineer, Platform Engineer, Cloud Engineer. * Observability. Engineers who build and tune the monitoring itself: Prometheus and PromQL, Grafana dashboards and alert rules, Loki or ELK, OpenTelemetry tracing, SLOs and error budgets. Typical titles: Observability Engineer, Monitoring Engineer, Site Reliability Engineer (Observability). What you'll do * Work through incident, debugging and infrastructure-change scenarios live with a researcher: reading dashboards and logs, writing PromQL and LogQL, fixing Helm and Kubernetes configuration, rolling back bad deploys and writing post-mortems. * Explain your reasoning as you work, including the fixes you considered and rejected. * Review scenarios we have drafted and say plainly what is unrealistic, too easy or underspecified. * Help write the acceptance criteria for each scenario, including the tempting wrong moves an engineer under pressure might make. * Write short notes after each session on how you approached the problem and what you verified. * Work in reviewer feedback within agreed turnaround times, and flag guideline gaps or edge cases you run into.