Site Reliability Engineering Leader

Responsibilities:

• Infrastructure, built properly: Infrastructure as code for all of FanOS (Terraform on AWS). They write the core modules and set the patterns others follow. AWS account structure, access control, secrets, emergency-access (break-glass) process. Cloud cost per tenant and overall hosting margin
• CI/CD and change management: Build and deployment pipelines for every FanOS service. They design the pipeline templates and write the hard parts themselves. - Safe releases across many tenants: staged rollouts, feature flags, automatic rollback, release gates for tests, code quality and security scans. - Change process that keeps engineers shipping fast and keeps production stable. -Track delivery health: deploy frequency, lead time, change failure rate, time to restore.
• Observability: Metrics, logs and traces across all services, with one place to see platform health. -Per-tenant visibility: which client is affected, how badly, and why. - Alerting tuned to customer impact, so on-call engineers get paged for real problems and not noise. - Dashboards that show leadership availability and performance against targets.
• Reliability and incident management: Availability targets (SLOs) per service and per tenant, built on the observability above. On-call rotation, severity levels, incident command, post-incident reviews. -They act as incident commander on major outages until the team can
• Business continuity and disaster recovery: Backup, restore, and failover design, with recovery targets agreed with the business. -Regular DR tests that prove recovery works.

Requirements:

• Built from scratch. They set up incident management, on-call, SLOs or DR where none existed before. Running a process someone else designed does not count.
• Hands-on today. They wrote production infrastructure code in the last 12 months. They can open a Terraform repo and explain their module and state design.
• Built CI/CD pipelines. They designed deployment pipelines used by multiple teams, including rollback and release gates. Using a pipeline someone else built does not count.
• Built observability. They set up metrics, logging, tracing and alerting for production, and can explain how they measure what customers experience (not just server CPU and memory).
• Real incident command. They led response on a major customer-facing outage and ran the post-incident review.
• Customer-facing SaaS. They ran production for external customers with uptime commitments. Internal tools or batch platforms alone do not count.
• AWS in production as their main cloud.
• Small-team coach. They grew 2-5 engineers. Managing a 30-person org through layers is a different job.
• Clear communicator. Answers a question in under two minutes, then stops.