Major Incident Manager

Who is Sonar? Sonar enables organizations to ship agentic code with confidence. Code creation is abundant, but confidence is scarce. Our core platform, SonarQube, verifies over 750 billion lines of code every day, delivering agentic verification and governance for all code. Trusted by more than 7 million developers and 75% of the Fortune 100, including teams at Nvidia, ServiceNow, Booking.com, Goldman Sachs, AstraZeneca, and Ford Motor Company, Sonar enables organizations to reduce outages, improve security, and lower the cost and risk of agentic software development. Founded in Geneva and now headquartered in Austin, Texas, Sonar has a global team working across offices and hubs, including Silicon Valley, London, Bochum, Barcelona, Singapore, Tokyo, and the Washington, D.C. area. At Sonar, we’re enabling enterprises to build agentic software factories that can move quickly while maintaining the control, consistency and evidence required to ship with confidence. Position description We are still at the beginning of our growth journey, so we are putting new processes, technologies, and tools in place on a continuous basis. Your role is a pivotal engineering contributor to the tooling and services to automate and enhance the software development lifecycle, empowering our fellow SonarSourcers to deliver with speed, confidence, and security. You would be a member of a team that delivers solutions across all of our 5 offices: Austin (Texas, US), Geneva (Switzerland), Bochum (Germany) and Singapore. As a Major Incident Manager, you use and create automation tools to monitor and observe production infrastructure services both on premises and in the cloud. You are allergic to repetitive tasks, preferring to maximize automation and reliability. You are expert in change management, infrastructure management, system support, and configuration management.

What you will do

System Health Monitoring, Alert Triaging, and Error Budget Management: Dedicate time to monitoring critical security infrastructure (e.g., identity platforms, firewalls, compliance systems) and core infrastructure components. Focus on using and maintaining dashboards tied to Service Level Objectives (SLOs) , triaging high-severity alerts, and analyzing the current Error Budget burn rate to guide prioritization for the rest of the day. Infrastructure as Code (IaC) and Policy as Code Development: Spend the largest portion of time writing, reviewing, and testing code (e.g., Python, Go, Terraform, or proprietary tools) to automate the deployment, configuration, and security hardening of infrastructure. This involves treating infrastructure and security policies as software to ensure consistency and prevent configuration drift. Toil Elimination and Automation of Operational Tasks: Identify, scope, and implement automated solutions for manual, repetitive, and time-consuming tasks (toil) related to security patching, compliance checks, certificate rotations, or infrastructure maintenance. The goal is to continuously reduce the operational workload for the team. Security Pipeline and Observability Maintenance: Maintain and enhance the DevSecOps security tools integrated into the pipelines (e.g., static analysis, vulnerability scanning, security configuration checks). Ensure the end-to-end logging, metrics, and tracing (observability) systems for both infrastructure and security tools are robust, accurate, and provide immediate diagnostic capability during incidents. Incident Response Engineering and Post-Mortem Action: Participate in the on-call rotation and actively engage in engineering solutions derived from post-mortems. This means turning incident root causes into preventative measures implemented via code, improving runbooks into automated actions, and reducing Mean Time To Resolution (MTTR) for future incidents.