Senior Site Reliability Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. We need to parse the posting. First part: "At Precisely, we're not just building software — we're shaping the future of data integrity..." That's about company overview. Could be "About the role"? Actually "Overview:" then description of SRE role. Could be "About the role" section. Then "This position is 100% remote within the U.S., with a preference for candidates located in the Mountain or Pacific Time zones." That's schedule? Actually schedule info: remote, location preference. Could be placed under "Schedule" maybe? But schedule usually refers to work hours, shift, on-call. There's also on-call schedule later. So we can treat remote location as maybe "Schedule" or maybe not a section. The instruction: include a section only when posting has real specific content for it. We have remote location and time zone preference; that could be under "Schedule" (maybe not). But we also have on-call schedule details later. So we could have a "Schedule" section covering remote work and on-call rotation. We have "What you will do:" list of responsibilities. That's Responsibilities. Then "What we are looking for:" includes Required and Preferred. That could be Requirements (maybe required) and Qualifications (maybe preferred). But we need to decide mapping: The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to allocate content accordingly. We have required education, experience, skills. That's Requirements. Preferred skills could be Qualifications or Skills. There's also a separate "Skills" heading; we could put required technical skills under Skills? But we already have required list includes many skills. Might be better: Requirements = education + experience baseline. Qualifications = preferred skills. Skills = maybe specific technical proficiencies? However we have a lot of skill details in required. Could split: Requirements: education + years experience. Qualifications: high-level developing SME competency etc. Skills: specific proficiencies (Terraform, Ansible, AWS, scripting, etc). But we need to avoid duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details somewhere. We can have multiple sections but each heading only if real content. We could do: - About the role: company overview + role overview (first paragraphs). - Responsibilities: bullet list from "What you will do:". - Requirements: education requirement, 5+ years experience, maybe also "Travel is required: No — approximately 0%." (that's not a requirement but could be under Requirements or Schedule). We'll put travel under Requirements maybe. - Qualifications: maybe "Preferred Skills (a plus but not required):" list. - Skills: maybe we could treat required technical proficiencies as Skills. But then we would duplicate some content if we also put them under Requirements. Better to separate: Requirements = education + experience + travel. Qualifications = preferred skills. Skills = required technical proficiencies (Linux, Terraform, Ansible, AWS, scripting, monitoring, networking, CI/CD, RCA, SLOs, ORR, cross-functional, change advisory, AI tools). That seems reasonable. - Benefits: none mentioned explicitly. No benefits details. So we should not include Benefits section. - Pay: none mentioned. So omit. - Schedule: remote work, time zone preference, on-call schedule details. Also mention on-call rotation covering after-hours, weekends, holidays, etc. So we can put that. We must not include boilerplate like "Application and Interview Impersonation Notice", privacy notice, etc. Now we need to format with

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must output only HTML fragment, no /, no markdown. Let's craft. First, About the role: combine company overview and overview of role. Paragraph: "At Precisely, we're not just building software — we're shaping the future of data integrity. As a global leader in data quality, data enrichment, and location intelligence, Precisely helps thousands of the world's most trusted brands make confident decisions with data they can rely on. We're an AI-first organization, which means artificial intelligence isn't a buzzword here — it's woven into how we build products, how we work, and how we think about solving complex problems for our customers. When you join Precisely, you join a team of curious, driven innovators who believe that better data makes the world run better. If you're ready to do meaningful work at the intersection of AI and data — and help define what's possible — we'd love for you to apply!" Then overview of SRE: "Overview: The Site Reliability Engineer (SRE) is responsible for the reliability, performance, and scalability of Precisely's infrastructure platforms across CEDAR (CCX) — an on-premises, private cloud managed services environment; RapidCX (RCX) — an AWS cloud environment for SaaS-delivered customer communications management; and Hosted Managed Services (HMS) — an AWS cloud environment supporting managed client deployments. This role bridges software engineering and systems operations, building automation, observability tooling, and reliability standards to ensure platform availability and operational excellence. SREs are enabling partners: they set reliability standards, define what 'reliable' looks like for each service, validate production readiness, and coach engineering teams on operational best practices. Engineering teams own the reliability outcomes of the services they build; the SRE ensures they have the standards, tooling, and guidance to meet them. As a Senior SRE, this role is regarded as a platform expert across CCX, RCX, and HMS, taking on the majority of complex reliability engineering work, mentoring less experienced engineers, and contributing to release triage and coordination efforts." We can put that as prose (

  ). Might be long but okay. Now Responsibilities: list from "What you will do:" each bullet. We need to preserve all details. Let's extract bullet points: - Define and maintain reliability standards across CCX, RCX, and HMS, including SLOs, SLIs, and error budgets. - Define standards for actionable alerting, meaningful logging, and diagnostic tracing; partner with engineering teams to ensure those standards are met. - Serve as a platform expert and lead complex reliability engineering work across on-premises, private cloud, and AWS environments. - Build and maintain infrastructure-as-code, deployment automation, monitoring, alerting, and observability tooling using Terraform, Ansible, Datadog, and scripting languages. - Partner with engineering teams to embed reliability, operability, scalability, backup, recovery, and failure-mode considerations into service design and delivery. - Lead Operational Readiness Reviews and validate production and disaster recovery readiness for qualifying changes. - Contribute to release triage, deployment coordination, maintenance windows, and change and security reviews. - Lead response to complex P1/P2 incidents, serve as incident commander when required, and communicate status clearly to technical and non-technical stakeholders. - Author root cause analyses and post-incident reports, identify recurring patterns, and implement preventive automation to reduce manual toil and improve MTTR. - Maintain operational runbooks, reliability backlogs, and team knowledge resources covering monitoring gaps, recurring incidents, and operational risks. - Use Precisely-provided AI tools for automation, incident analysis, troubleshooting, runbook creation, solution testing, and architecture documentation. - Ensure infrastructure configurations meet security, compliance, vulnerability-remediation, and data-protection requirements. - Mentor Associate SREs and SREs, coach engineering teams on production diagnostics and operational practices, and contribute to cross-team design reviews. - Lead project-based work, coordinate on-call coverage, and model strong operational discipline and follow-through. - Participate in a rotating on-call schedule covering after-hours, weekends, and holidays, including critical production changes and escalations within defined SLA windows. We'll put each as

• . Now Requirements: education, 5+ years experience, travel 0%. We could also include "High-level, developing subject-matter-expert competency in one or more complex infrastructure domains (e.g., cloud platform engineering, IaC automation, observability, or on-premises virtualization)." That seems like a requirement? It's under "What we are looking for:" Required section includes that bullet. Actually reading: Under "What we are looking for:" there is "Required:" then list includes: - Educational requirements (equivalent work experience will be accepted in place of the education requirement): Bachelor's degree in Computer Science, Information Systems, Engineering, or equivalent practical experience. - 5+ years of systems or infrastructure engineering experience in an enterprise production environment. - High-level, developing subject-matter-expert competency in one or more complex infrastructure domains (e.g., cloud platform engineering, IaC automation, observability, or on-premises virtualization). - Advanced proficiency with Linux (RHEL/Oracle Linux) across multiple environments (on-premises and cloud, not just multi-site). - Proficient with Terraform for infrastructure-as-code; experienced with Ansible role development beyond basic hands-on use. - Experience deploying and managing workloads in AWS at an intermediate level: EC2, ECS, S3, VPC, IAM, CloudWatch, Auto Scaling. - Proficiency with at least one scripting language (Python, Bash) for automation development. - Demonstrated experience designing monitoring system architecture and alerting strategy — not just operating existing dashboards (Datadog preferred). - Solid understanding of TCP/IP networking, DNS, load balancing, and distributed systems. - Experience designing and managing CI/CD pipelines and deployment automation standards. - Strong analytical skills; demonstrated experience authoring root cause analyses for complex incidents and identifying systemic, preventive fixes from recurring incident patterns. - Ability to define SLOs and lead Operational Readiness Reviews (ORRs); comfortable partnering with engineering teams on production readiness. - Demonstrated ability to work cross-functionally with engineering teams on reliability standards and observability requirements. - Experience participating in change advisory processes and contributing to capacity and reliability planning. - Travel is required: No — approximately 0%. - AI Skills/Knowledge: Active, proficient use of Precisely-provided AI tools (GitHub Copilot, Claude, or equivalent) for complex automation, solution testing, and architecture documentation is a required baseline for this role — not a differentiator — and includes mentoring others on AI-assisted engineering practices. - Apply AI tools for complex automation, incident analysis, and runbook authoring. - Mentor other engineers on AI-assisted engineering practices. - Maintain fluency with Precisely-approved AI coding assistants as a baseline expectation. Thus many of these are required skills. So we need to decide where to put them. The instruction says we have sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put all required items under Requirements (including education, experience, technical proficiencies, AI skills). Then Qualifications could be preferred skills. Skills section maybe redundant. But we have a separate Skills heading; we could put nothing there (omit). Better to follow instruction: include a section only when posting has real specific content for it. So if we put all required content under Requirements, we may not need Qualifications or Skills if we treat preferred as Qualifications. But we also have preferred skills list; that could go under Qualifications. Then we might not need Skills section. However we have a heading "Skills" in the list; we can omit if no specific content. That seems okay. Thus: - Requirements: education, 5+ years experience, high-level developing SME competency, Linux proficiency, Terraform, Ansible, AWS intermediate, scripting language, monitoring design, TCP/IP networking, CI/CD, analytical skills/RCA, ability to define SLOs/lead ORRs, cross-functional work, change advisory participation, travel