At ERCOT, our diverse and dynamic work environment provides a platform on which employees can work together to build the future of the Texas power grid and wholesale market utilizing the latest technologies and resources. We encourage you to join our talented, dedicated workforce to develop world-class solutions for today and tomorrow's energy challenges while learning new skills and growing your career. ERCOT is committed to fostering inclusion at all levels of our company. It is the cornerstone of our corporate values of accountability, leadership, innovation, trust, and expertise. We know that individuals with a wide variety of talents, ideas, and experiences propel the innovation that drives our success. An inclusive and diverse workforce strengthens us and allows for a collaborative environment to solve the challenges that face our industry today and in the future. **JOB SUMMARY** The Senior Systems Reliability Engineer applies software engineering discipline to reliability problems - designing, building, and operating the systems that make production software measurable, scalable, and self-healing. This role treats operational challenges as engineering problems: when a process is manual, it gets automated; when a failure mode is unknown, it gets instrumented; when a system degrades, the degradation is understood before it recurs. At this level, the specialist owns SLO and error budget frameworks for assigned systems, architects the observability stack that the team relies on, leads engineering-driven incident response, and holds NERC/CIP compliance responsibility for assigned systems. This role partners directly with Software Engineers as a technical peer - participating in design reviews, influencing architecture decisions for reliability, and building the production readiness standards that govern how software ships. Advancement to Lead is based on demonstrated ability to define reliability engineering standards at the platform level, influencing practice across multiple teams and portfolios. **JOB DUTIES** + Performs complex reliability engineering work autonomously; recognized subject matter expert within the team and adjacent teams. + Designs and builds production software systems, reliability tooling, and automation frameworks; treats operational problems as engineering problems to be solved through code. + Owns SLO governance, error budget management, and observability architecture for assigned systems; leads engineering-driven incident response including failover scenarios. + Holds NERC/CIP compliance responsibility for assigned systems; formally mentors less experienced specialists; may coordinate team delivery and on-call activities. **ADDITIONAL JOB DUTIES** **Core Expectations** The following expectations apply at all Systems Reliability Specialist levels. Scope and independence expand with each level. + Engineer reliability solutions: when a process is manual and repeatable, automate it; when a failure mode is opaque, instrument it; when a system is fragile, redesign the failure boundary. + Define and own SLIs and SLOs for assigned systems; treat error budgets as a shared engineering contract with development teams, not an operations metric. + Respond to production incidents as an engineer: form a hypothesis, isolate the failure, resolve it, and close the loop with a post-mortem that addresses root cause. + Instrument systems so that on-call responders have sufficient telemetry to diagnose and act without tribal knowledge. + Participate in 24/7 on-call rotation; treat every alert as signal - either actionable or worth eliminating. + Write production-quality code: reliability tooling, automation frameworks, and operational software are held to the same engineering standards as application code. + Partner with development teams as a peer in design reviews; reliability is designed in, not bolted on after deployment. **Reliability Engineering** Senior specialists design and build the engineering systems that make production software reliable. This is software engineering applied to operational problems - the output is code, frameworks, and automated systems, not tickets and runbooks alone. + Design, build, and maintain reliability tooling: automated remediation systems, self-healing infrastructure components, and operational software that reduces human intervention in production. + Own SLO and error budget definitions for assigned systems; review error budget consumption with development teams and drive engineering decisions based on budget status. + Architect and implement chaos engineering programs: define failure injection scenarios, automate resilience tests, and validate recovery behavior against defined SLOs. + Build and maintain CI/CD reliability gates: automated canary analysis, progressive delivery validation, and rollback triggers based on SLI thresholds. + Design capacity planning models for assigned systems; build tooling to project resource needs and su