> Markdown version of [/jobs/ext/3988973-site-reliability-engineer](https://www.wearedevelopers.com/jobs/ext/3988973-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:** VelvetGold Technologies Limited Liability Company - **Location:** Chicago, IL, United States - **Experience:** Expert - **Salary:** $130,000.0 - **Contract:** Permanent contract - **Skills:** Amazon Web Services, Microsoft Azure, Bash Shell, Continuous Integration, DevOps, Domain Name System (DNS), Fault Tolerance, Python (Programming Language), Linux System Administration, Networking Basics, Reliability Engineering, Site Reliability Engineering Practices, Ansible, Prometheus, Runbook, TCP/IP, Datadog, Data Logging, Pulumi, Scripting, Transport Layer Security, Load Balancing, Cloud Platform System, Grafana, Kubernetes, Infrastructure Automation Frameworks, Low Latency, Drift Detection, Terraform, Software Version Control - **Published:** October 28, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=d70f29e18efd387b ## About the Role * 5+ years in site reliability, DevOps, or production systems engineering, with direct on-call experience for production services * Strong Linux systems administration and scripting proficiency (Python, Bash, or Go), with all code maintained under version control * Production experience with a major cloud platform (AWS, Azure, or GCP), including compute, networking, and managed-service tradeoffs * Hands-on Kubernetes production experience covering cluster operations, workload reliability, and upgrade planning * Practical SLO, SLI, or error-budget experience, including a documented instance in which error-budget analysis informed a release or staffing decision * Demonstrated observability capability: constructing dashboards and alerting from first principles and identifying actionable signals during incident conditions * Incident management experience, including authored postmortems with remediation carried through completion * Networking fundamentals: TCP/IP, DNS, TLS, load balancing, and latency diagnostics * Clear written communication; postmortems, runbooks, and capacity plans are principal deliverables of this position * Ability to work on-site or hybrid in Chicago, IL, and to carry a share of the on-call rotation, * Resilience or chaos engineering experience (Gremlin, LitmusChaos, or equivalent fault-injection tooling) * Go or Python development beyond scripting, for internal tooling and agents * Observability stack administration (Prometheus/Alertmanager, Grafana, OpenTelemetry collectors) * Infrastructure automation at scale (Terraform modules, Ansible, or Pulumi across multiple environments) * Experience in a regulated or high-availability domain: fintech, healthcare, trading, or logistics * Experience establishing SRE practices in an organization transitioning from traditional operations ## Description * Define and instrument SLIs and SLOs for production services in partnership with development teams, and manage error budgets as a formal input to release decisions * Build and maintain observability systems : metrics, logging, and tracing (Prometheus, Grafana, Datadog, OpenTelemetry, or current stack equivalents), with alerting aligned to error budgets rather than raw thresholds * Serve as an on-call engineer for incident response: triage, mitigation, stakeholder communication, and written post-incident review leading to root-cause determination and assigned remediation * Automate operational runbooks and recurring tasks, with a stated objective of reducing toil quarter over quarter rather than accommodating it * Improve deployment reliability through CI/CD pipeline health, progressive rollout and rollback capability, and change-failure reduction in partnership with development teams * Manage infrastructure-as-code (Terraform) across environments with drift detection and review-based change control * Conduct load, stress, and resilience testing to validate capacity assumptions before production traffic does * Support capacity planning, including growth modeling, cost-per-request analysis, and documented scaling thresholds * Maintain backup and recovery procedures, including scheduled restore exercises measured against stated recovery objectives * Participate in architecture reviews from a reliability perspective: failure modes, dependency risk, and graceful degradation