> Markdown version of [/jobs/ext/4188704-site-reliability-engineer](https://www.wearedevelopers.com/jobs/ext/4188704-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:** Stratus Technologies - **Location:** United States (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** ASP.NET, .NET Framework, Artificial Intelligence, Amazon Web Services, Microsoft Azure, C Sharp (Programming Language), Profiling, Software Debugging, Fault Tolerance, Apache JMeter, Python (Programming Language), Message Broker, MongoDB, Prometheus, Runbook, SignalR, TypeScript, WebSocket, Backup and Restore, Azure Service Bus, Performance Testing, Real Time Systems, Istio, Grafana, Gatling, Database Performance, Kubernetes, Sentry, Apache Kafka, Pagerduty, Golang - **Published:** October 4, 2026 - **Apply:** https://www.builtincolorado.com/job/senior-site-reliability-engineer/11505093?handler=ApplyRedirect ## About the Role * 6+ years of professional engineering experience, with at least 3+ years in a dedicated SRE or production engineering role at a B2B SaaS company. * Demonstrated ownership of SLOs and error budgets in production - you have defined them, measured them, argued about them with product leadership, and changed engineering behavior with them. * Deep, practical observability skills with Prometheus, Loki, Tempo, and Grafana or comparable: you have instrumented real systems and built alerting that pages on customer impact rather than on CPU. * Hands-on incident command experience at meaningful severity, including building on-call and escalation practice from the ground up. * Strong database performance skills - query profiling, index design, connection pooling, and diagnosing saturation under load. MongoDB experience strongly preferred; comparable document or relational depth acceptable. * Production Kubernetes experience (AKS preferred) sufficient to debug a live problem - pod scheduling, resource limits, networking, and service mesh behavior (Istio preferred). * Solid coding ability in at least one general-purpose language (Go, Python, C#, or TypeScript); willingness to work in a C#/.NET codebase. * Experience with load and performance testing tooling (k6, JMeter, Gatling, or comparable) and with turning results into engineering priority. * Production experience on Azure or AWS, with real understanding of the failure modes of managed services. * Fluency with AI-assisted engineering tooling and a track record of designing AI-leveraged workflows for your team - this is a graded expectation at every level at Stratus. * Excellent written communication: you write post-mortems, runbooks, and reliability reports that executives and engineers both read and act on. * Judgment and steadiness under pressure, and the credibility to tell engineering and product leadership something they do not want to hear. NICE TO HAVE: * Experience establishing or maturing an SRE practice - defining the discipline, not inheriting it. * Experience with Sentry or comparable application error-monitoring platforms. * Experience operating event-driven and real-time systems - message brokers (Azure Service Bus, Kafka) and websocket or push layers (SignalR or comparable). * Experience operating MongoDB Atlas at production scale, including replica set topology and Atlas performance tooling. * Experience with durable workflow orchestration (Temporal or comparable). * Background in multi-region or multi-zone architecture and DR design against stated recovery objectives. * Experience with incident.io, PagerDuty, or comparable incident management platforms. * Familiarity with DORA metrics and with reliability work inside SOC 2 or NIST 800-171 scope. * Experience with legacy monolith reliability - improving the operational behavior of an ASP.NET or comparable application you cannot rewrite. * Domain interest in MEP, BIM, AEC, or construction technology. * Prior experience in a Series B / growth-stage company navigating the transition from product-market fit to scale. ## Description * Define and own service level indicators, objectives, and error budgets for customer-facing services; build the measurement pipeline that makes them trustworthy and publish availability and latency against target on a regular cadence. * Build and own production observability: instrumentation standards, dashboards, and actionable alerting on our stack - AKS on Azure, Prometheus, Loki, Tempo, and Grafana, with Istio as the service mesh and Flux for GitOps - extending coverage across every environment. * Establish and run incident response practice - on-call rotation and paging paths, severity definitions, per-system incident ownership, escalation into and out of customer support, and blameless post-mortems in incident.io. * Set the recovery standard: define what rollback and recovery must demonstrate, and verify through regular exercise that every service meets it. * Lead performance and capacity engineering: query and index tuning, connection-pool sizing, capacity modeling against real load, and designing for graceful degradation under partial failure. * Work with the existing team that runs our k6 load, stress, spike, and soak testing against a production-like environment; help set per-endpoint latency thresholds tied to our SLOs and make the results a gate on delivery. * Drive production readiness: review new services and significant changes against readiness criteria covering instrumentation, alerting, failure modes, resource limits, and rollback before they ship. * Close the loop on remediation: track post-mortem action items through to verified production change. * Contribute to business continuity and disaster recovery planning, including backup and restore validation, failover design, and recovery objectives. * Partner with engineering pods to push reliability ownership outward - coach teams on instrumenting and operating their own services. * Write code: tooling, automation, instrumentation libraries, and fixes in the production codebase.