SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Stratus is a ~50-person, Series B software company building MEP (mechanical, electrical, plumbing) contractor software that digitizes and automates workflows from design through fabrication to installation. The Senior Site Reliability Engineer reports to the Senior Director of Platform Engineering and owns how Stratus behaves in production—where downtime means work stops on job sites, not just a degraded user experience.
This is a hands-on engineering role with a production mandate. You will define what "reliable" means in measurable terms, instrument systems to observe reliability, and close the loop from production signals back into engineering priorities. You will write code, tune queries, build alerting, run load tests, and lead incidents. Success is measured on customer-visible availability and latency, not tickets closed.
Key responsibilities include: defining and owning service level indicators, objectives, and error budgets for customer-facing services; building production observability across the stack (AKS on Azure, Prometheus, Loki, Tempo, Grafana, Istio, Flux); establishing incident response practice with on-call rotations, severity definitions, and blameless post-mortems; setting recovery standards and verifying them through regular exercises; leading performance and capacity engineering (query tuning, index design, connection pooling, capacity modeling); working with load testing (k6) to set latency thresholds tied to SLOs; driving production readiness reviews for new services; tracking post-mortem action items to verified production change; contributing to business continuity and disaster recovery planning; coaching engineering pods on instrumenting and operating their own services; and writing tooling, automation, and instrumentation code.
You will work across every engineering pod, with platform and security functions, and with customer-facing teams. The role is ideal for someone comfortable stating reliability numbers out loud and defending them, and drawn to building a reliability practice from the ground up rather than maintaining an existing one.
REQUIREMENTS:
- 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 tools; you have instrumented real systems and built alerting that pages on customer impact rather than 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
- 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
