Site Reliability Engineering Team Lead (Principal SRE)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. No job title heading. No Job ID. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines. Must preserve all substantive info. We need to parse the job description. Key sections: - Summary: "A Moving Experience. Site Reliability Engineering Team Lead (Principal SRE) Job Description Summary ..." The summary includes description of role. Could be "About the role" or "Job Summary". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for summary. - "What We Offer" includes benefits: compensation and benefits package details. That's Benefits section. - "About Cerence" is company overview; could be part of About the role? Might be separate but not in list. Could be omitted or included under About the role? Probably we can include under About the role or maybe a separate "About the company" but not in allowed headings. Since only allowed headings list, we should map content to those headings. The company overview could go under About the role (maybe as part of role description). But we need to preserve all substantive info; we can include it in About the role paragraph. - "The Opportunity" also describes role; could be part of About the role. - "Principal Responsibilities" is a list; that maps to Responsibilities heading. - "Required Qualifications" and "Preferred Qualifications" map to Qualifications heading (maybe separate Required and Preferred but we can combine under Qualifications). Could also split into Requirements and Qualifications but we have both headings. The instruction list includes Requirements and Qualifications as separate possible headings. We could put Required Qualifications under Requirements, Preferred under Qualifications, or combine. Better to follow typical: Requirements = required qualifications, Qualifications = preferred qualifications. We'll do that. - "Skills" maybe not explicitly listed but we could extract from qualifications (like hands-on experience, etc.) but we already have those under Requirements/Qualifications. Could create Skills section for technical skills like Kubernetes, etc. But we already have them in qualifications. Might be redundant. Better to not create Skills unless there is explicit skills list. There's no separate skills bullet list; we can omit Skills. - Benefits: we have "What We Offer" includes compensation and benefits package details: Annual bonus opportunity, Insurance coverage, Paid time off, Paid holidays, Company contribution to RRSP, Equity awards, Remote/hybrid work. Also note that compensation and benefits subject to terms. That's Benefits. - Pay: Not explicitly stated (no salary range). So we should NOT create Pay section because no specific content. - Schedule: Not explicitly stated (no mention of full-time/part-time/hours). So omit Schedule. We must not include boilerplate like EEO, security policies, etc. Remove duplicated lines (like repeated Cerence description). We need to preserve all substantive info: role description, responsibilities, required qualifications, preferred qualifications, benefits, company overview, opportunity description. We must not invent or summarize away detail. So we need to keep specifics like SLI/SLO/SLA targets up to 99.95%, etc. Let's extract substantive paragraphs. From the text: **Job Description Summary** (first paragraph): "The Site Reliability Engineering Team Lead (Principal SRE) leads Cerence's Site Reliability Engineering team, owning the reliability, availability, and operational health of our cloud-native automotive AI platform. This role combines technical leadership of the team and the function with deep technical credibility: you will help select and mentor the team, define the reliability roadmap, govern SLI/SLO/SLA targets, and champion a blameless culture. You will serve as the Tier 2 technical escalation point for major incidents, partner with development leadership to embed reliability into the SDLC, and set strategic direction for observability and automation. This is a Principal-level role on our technical track, with no direct reports: you lead the team and own the function through technical authority. The ideal candidate brings a strong hands-on background in SRE, cloud platforms, and container orchestration, and a track record of leading site reliability teams." **What We Offer**: "We offer a generous compensation and benefits package (in addition to the base salary), including: - Annual bonus opportunity - Insurance coverage (medical, dental, vision, life, and disability) - Paid time off - Paid holidays - Company contribution to the RRSP (Registered Retirement Savings Plan) - Equity awards for certain positions and levels - Remote and/or hybrid work available depending on the position All compensation and benefits are subject to the terms and conditions of the underlying plans or programs, as applicable, and may be amended, terminated, or replaced from time to time." **About Cerence** (first occurrence): "Cerence Inc. (Nasdaq: CRNC | cerence.com) is the global industry leader in creating unique, moving experiences for the automotive world. Spun out from Nuance in October 2019, Cerence works with all of the world's leading automakers — from Ford and Fiat Chrysler to Daimler, Audi and BMW to Geely and SAIC — to transform how a car feels, responds and learns. Our track record is built on more than 20 years of industry experience and more than 325 million cars on the road today, across more than 70 languages." Later there is another Cerence description (duplicate) with 500 million cars etc. We need to preserve all substantive info but avoid duplication. The second description includes slightly different numbers (500 million cars). Both are substantive; we should keep both? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. The two Cerence paragraphs are similar but not identical; they have different numbers (325 million vs 500 million) and slightly different wording. Both are substantive; we should keep both but avoid duplication of identical lines. They are not identical, so we keep both. However, we might combine them into one paragraph but that would summarize away detail (changing numbers). Better to keep both as separate paragraphs under About the role or maybe a separate "About the company" heading but not allowed. We could put them under About the role as separate paragraphs. **The Opportunity**: "We are looking for an experienced Principal SRE to lead our Site Reliability Engineering team and own the reliability function. In this role, you will own the reliability of Cerence's cloud-native voice, gesture, and gaze solutions — systems that power immersive automotive AI experiences at global scale. The function is yours end to end: the reliability roadmap, the SLI/SLO standards, the on-call model, the Tier 2 escalation path, and approval authority over high-risk production change. You will set the team's technical direction, build a sustainable team culture, and be the bridge between reliability practice and product delivery. This is a hands-on leadership role. You will bring both leadership experience and deep technical credibility, enabling you to earn the trust of your team, hold informed architectural conversations, and make sound trade-offs under pressure." **Principal Responsibilities** (list): - Technical Leadership: Help select, mentor, and technically develop the team, across multiple locations; Set technical direction and priorities for the team, and contribute performance and growth input to their managers; Design and maintain a sustainable on-call rotation; monitor page load and team health as first-class concerns - Reliability Strategy: Own and drive the team's reliability roadmap across a 2–3 quarter horizon; Define and govern SLI/SLO/SLA frameworks to hold the contracted availability targets for our customer programs, which run as high as 99.95% - Incident & Production Excellence: Serve as the Tier 2 technical escalation point for major incidents, partnering with the Global Operations Center, which owns incident management and response; Champion blameless postmortem culture — model it, reinforce it, and ensure it produces actionable outcomes; Lead and continuously improve Production Readiness / NFR reviews with development teams; Contribute to root cause analysis and own the systemic improvements that come out of it; Act as a named approver for high-risk and out-of-window production change - Observability & Automation: Set the strategic direction for metrics, dashboards, and alerting across SLI/SLO, escalation, and automation layers; Drive development and adoption of CI/CD automation pipelines for service deployments, rollbacks, and operational tasks; Partner with DevOps and platform teams to evolve shared infrastructure - Cross-Functional Engagement: Partner with development managers and architects to embed reliability into the SDLC by default; Participate in service reliability consulting and architectural reviews; Communicate reliability posture and risk clearly to technical and non-technical stakeholders **Required Qualifications**: - 8+ years of hands-on experience in site reliability, DevOps, or cloud platform roles, including time leading a team or owning a function - A track record of setting technical direction and holding standards across a team — with or without formal authority - Hands-on experience with container orchestration frameworks (Kubernetes, Docker, Istio) - Experience with public cloud platforms (Azure primarily; AWS and Google Cloud) - Familiarity with observability tooling — metrics pipelines, dashboarding, and alerting (e.g., Zabbix, Prometheus, Grafana) - Experience with CI/CD pipelines and infrastructure-as-code practices (e.g., Terraform, Flux) - Proficiency in at least one scripting or programming language (Python, Go, Shell, etc.) - Strong UNIX/Linux background, including system configuration, performance debugging, and network fundamentals (Layer 4/5, DNS, HTTP/S, TLS) - Excellent written and verbal communication skills in English **Preferred Qualifications**: - Previous site reliability leadership experience - Experience leading distributed or multi-site technical teams - Background in high-availability service design (redundancy, failover, blast radius) - Experience with log aggregation and analytics platforms (Loki, Thanos) - Familiarity with ITSM and project tooling (Jira, Confluence) - Experience in automotive, embedded, or latency-sensitive production environments We also have a repeated Cerence description later (the second one). Let's capture that: "Cerence Inc. (Nasdaq: CRNC and www.cerence.com) is the global industry leader in creating unique, moving experiences for the automotive world. Spun out from Nuance in October 2019, Cerence is a new, independent company that has quickly gained traction as a leader in the automotive voice assistant space, working with all of the world’s leading automakers – from Ford and Fiat Chrysler to Daimler, Audi and BMW to Geely and SAIC – to transform how a car feels, responds and learns. Its track record is built on more than 20 years of industry experience and leadership and more than 500 million cars on the road today across more than 70 languages. As Cerence looks to the future and continues an ambitious growth agenda, we need someone to join the team and help build the future of voice and AI in cars. This is an exciting opportunity to join Cerence’s passionate, dedicated, global team and be a part of meaningful innovation in a rapidly growing industry." We should keep this as well, maybe under About the role or a separate "About the company" but not allowed. We'll include under About the role as additional paragraphs. Now we need to output HTML fragment with headings

and content in

or

• . We must not include any other tags like or . Just the fragment. We need to decide which headings to use: - About the role (h3) containing: Job Description Summary, The Opportunity, Cerence descriptions (both), maybe also mention that it's Principal-level role etc. We'll combine all descriptive paragraphs. - Responsibilities (h3) containing the list of responsibilities (maybe break into subheadings? Not allowed; only

  for section headings. Inside we can have

  for prose and

  • for lists. The responsibilities are given as bullet points