Senior Staff Site Reliability Engineer
- Level
- Staff
- H-1B history
- 112 approvals (FY2023)
- Posted
Skills
About this role
Descriptions & Requirements
Job Description and Requirements
We Are Synopsys is the leader in engineering solutions from silicon to systems, enabling customers to rapidly innovate AI-powered products. We deliver industry-leading silicon design, IP, simulation and analysis solutions, and design services. We partner closely with our customers across a wide range of industries to maximize their R&D capability and productivity, powering innovation today that ignites the ingenuity of tomorrow. You Are You have spent a decade building systems that need to stay up, not just run, actually stay up, under production load with real users depending on them. You know that observability is not about dashboards that look good in demos, it is about catching the signal before the page goes out at 2am. You think in SLOs and error budgets because you have lived through enough incidents to know that hope is not a strategy. You are the person who walks into a war room, pulls up three graphs, and knows exactly which service is choking and why. Linux is your native language. You have written enough Bash and Python to automate yourself out of repetitive work, and you know when to reach for Terraform or Ansible to make infrastructure repeatable. Cloud platforms like Azure do not intimidate you because you have built on them, broken things on them, and fixed them under pressure. EDA workloads are not abstract to you. You have worked with Grid Engine, LSF, or SLURM. You understand what it means when a compute-heavy job grid starts behaving strangely, and you know how to instrument it. Elasticsearch, Prometheus, Grafana, these are not buzzwords, they are tools you have deployed, tuned, and scaled. At Synopsys, you will build the observability backbone that keeps our Cloud and on-prem production systems visible, reliable, and ready for what comes next.
What You'll Be Doing
Design, build, and own the SRE and Observability platform that monitors production systems across on-prem and Azure Cloud environments, giving engineering and operations teams a real-time, holistic view of system health Partner with product, infrastructure, and application teams to define SLAs, SLIs, SLOs, error budgets, and KPIs that actually matter, then instrument systems to track them Automate deployment and configuration of monitoring tools using Terraform, Ansible, Bash, and Python to eliminate manual toil and reduce configuration drift Build custom scripts and tooling to extend observability capabilities, including proactive remediation workflows and self-healing automation that catches issues before they become incidents Lead root cause analysis on production incidents, write detailed postmortems for stakeholders, and drive systemic fixes that prevent recurrence Mentor junior SREs and Cloud Operations engineers, providing technical guidance on Linux systems, observability tooling, and SRE best practices Evaluate, test, and integrate new observability and reliability tools and technologies, including AI-assisted monitoring, copilots, and emerging patterns like MCP and RAG The Impact You Will Have Production systems across Synopsys Cloud will be more visible, more reliable, and easier to debug because of the observability platform you build Engineering teams will spend less time firefighting and more time building because your automation catches problems early and fixes them without human intervention Incident response times will drop because the right data will be surfaced at the right time, and teams will know what to look at first SRE practices will become embedded across the organization as you define KPIs, error budgets, and reliability standards that other teams adopt Junior engineers will grow faster because you will teach them how to think about reliability, not just react to alerts The Cloud Operations team will scale more effectively because repeatable, automated workflows replace one-off manual fixes Stakeholders will have confidence in production stability because