Expert: Interactive Coding, Site Reliability Engineering (Contract, Remote)
Patronus AI, Inc.
United States
14 days ago
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Apply on www.indeed.com
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Contract type
Permanent contract
Employment type
Full-time (> 32 hours)
Experience level
Experienced
Experience required
3 years minimum
Compensation
$312,000
Working hours
Regular working hours
Job source
Tech stack
Artificial Intelligence
Bash Shell
Bioinformatics
Continuous Integration
Python (Programming Language)
Reliability Engineering
Large Language Models
AI Coding Agents
Terraform
Splunk
New Relic (SaaS)
Job 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.
Requirements
- 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.
Benefits & conditions
- All solutions, write-ups and reviews are your own work. LLM-generated code or text is not permitted.
- Scenarios and solutions must be original. Nothing may be copied from published or easily searchable sources.
- Never include code, configuration, runbooks or incident details from a current or former employer or client, or anything covered by an NDA. All systems and scenarios are fictional, and all work is your own.
- Quality is judged on correctness, clarity of reasoning and reviewer agreement, not on speed or volume.
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Apply on www.indeed.com
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Good distractions
Loading talks and stories from around this roleβ¦