Senior Data Ops Engineer, Data Activation & Products - Activision

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must include sections only if posting has real specific content. We need to extract content. Job description includes: "Your Mission" paragraph, then responsibilities list, then qualifications, then nice to have, then "What Success Looks Like", then "Our World" (company description), then "Rewards" (benefits), then pay range. We need to map to headings: About the role (maybe from "Your Mission" and description). Responsibilities (list). Requirements (maybe qualifications). Skills (maybe nice to have). Benefits (from Rewards). Pay (pay range). Schedule (maybe from "Work arrangements: option to be based in LA office and follows an onsite work schedule of Monday through Thursday or be remote." So schedule info present. We must not include boilerplate like EEO etc. Remove navigation etc. Also remove duplicated lines. We must preserve all substantive info. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

... mission paragraph ...

Responsibilities

• ... each responsibility ...

Requirements

• ... qualifications list ...

Skills

• ... nice to have ...

Benefits

• ... benefits list ...

Pay

In the U.S., the standard base pay range for this role is $102,800.00 - $190,204.00 Annual. ... maybe also mention incentive compensation not guaranteed.

Schedule

This role has the option to be based in our Los Angeles (Pen Factory) office and follows an onsite work schedule of Monday through Thursday or be remote. Work arrangements may change at the company’s discretion to meet business needs.

We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive info: include mission paragraph, responsibilities list (each bullet), qualifications list, nice to have list, benefits list, pay paragraph, schedule paragraph, also maybe "Our World" description? That's company description; could be part of About the role? Might be considered extra but it's substantive. The instruction: "Prefer a few substantive sections over many thin ones." Could include "Our World" as part of About the role or maybe separate section "About Activision". But headings list only includes those specific headings; we shouldn't create other headings. So we can incorporate "Our World" into About the role paragraph. Thus About the role paragraph will contain mission paragraph + "Our World" description. Let's extract mission paragraph: "Your Mission We are looking for a Site Reliability Engineer to help improve the reliability, observability, and operational maturity of our data platforms, Kubernetes-based deployment systems, internal applications, and cloud environments. This role sits at the intersection of SRE, DevOps, and data. The ideal candidate is comfortable operating production systems, troubleshooting across infrastructure and applications, and helping teams deploy and support services more safely. The role does not require someone to be a data engineer, but they should be excited about the systems that support modern data engineering, including Databricks, Spark, Airflow/Astronomer, streaming pipelines, event systems, internal tools, and backend services. We are especially interested in a creative, curious engineer who enjoys learning new technology and using AI-accelerated development practices to solve problems faster and more thoughtfully. You should be excited to experiment with agentic development tools, automation frameworks, and emerging platform capabilities, while applying sound engineering judgment. This role has the option to be based in our Los Angeles (Pen Factory) office and follows an onsite work schedule of Monday through Thursday or be remote. Work arrangements may change at the company’s discretion to meet business needs." Wait schedule part appears in mission paragraph; but we also have schedule section later. Might duplicate. Better to keep schedule separate and not repeat in About the role. However the mission paragraph includes schedule info; we could keep it there but then schedule section would be duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we include schedule in About the role, we still need schedule section? It says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can have schedule section with the schedule info; we could also keep schedule info in About the role but that would be duplication. Duplication is not prohibited but we should avoid redundant? Not explicitly forbidden but better to avoid duplication. We could remove schedule sentence from About the role and keep it only in Schedule section. However the mission paragraph originally includes that sentence; removing it would be omitting substantive info. But we could keep it in About the role and not have a separate Schedule section, but then we lose the schedule heading. The instruction says include a section ONLY when the posting has real, specific content for it. It doesn't forbid having the content elsewhere. So we could omit Schedule section and keep schedule info in About the role. But the heading list includes Schedule as a possible heading; we are not required to use it. So we can skip Schedule section. Thus About the role will include mission paragraph (including schedule sentence). Then we will have Responsibilities, Requirements, Skills, Benefits, Pay. We need to ensure we don't include "Your Talent Professional can share this role’s range details for your local geography during the hiring process." That's part of pay paragraph; we keep. Now extract responsibilities list: after "Responsibilities" heading, bullet points start with "Monitor service health, respond to alerts, and participate in incident response for cloud, Kubernetes, application, and data platform environments." etc. We'll capture each sentence as a list item. Let's copy them: - Monitor service health, respond to alerts, and participate in incident response for cloud, Kubernetes, application, and data platform environments. - Investigate reliability issues across Kubernetes, networking, DNS, application runtime behavior, Databricks jobs, Spark workloads, orchestration systems, event systems, and dependent services. - Support the reliability of internal applications, APIs, workers, streaming consumers, event-driven services, and deployment workflows used by data engineering and business teams. - Build and maintain dashboards, alerting, runbooks, and operational documentation that improve detection and recovery speed. - Improve observability for Databricks environments, including job health, Spark streaming workloads, structured streaming metrics, cluster behavior, failures, latency, throughput, and cost signals. - Help route Spark streaming metrics, operational logs, event-system signals, and platform health signals into monitoring tools such as Grafana. - Contribute to alerting patterns for Databricks workflows, Airflow/Astronomer DAGs, dbt jobs, data freshness, pipeline failures, event lag, dead-letter queues, and production data dependencies. - Contribute scripts and automation that reduce repetitive operational work and improve environment hygiene. - Support release and deployment reliability by validating changes, improving rollback readiness, and strengthening change safety. - Partner with data engineers, analytics engineers, and software engineers to improve reliability across pipelines, services, internal tools, event systems, and data products. - Participate in post-incident follow-up and help close corrective actions that prevent recurrence. - Support platform modernization and migration efforts, including orchestration platform changes, deployment system improvements, and shared reliability standards. Now qualifications list after "Qualifications": bullet points: - 5+ years of experience in SRE, DevOps, cloud infrastructure, platform engineering, software engineering, data platform operations, or related production-support roles. - Hands-on experience supporting Kubernetes-based workloads, deployment systems, cloud infrastructure, or production application environments. - Familiarity with Linux, HTTP, DNS, containers, Kubernetes, Git-based workflows, and scripting in Bash, Python, or similar languages. - Experience with monitoring, logs, metrics, dashboards, alerting, and incident management practices. - Comfort working with event systems such as Kafka, Google Pub/Sub, Kinesis, or similar technologies, including topics, subscriptions, consumers, retries, lag, and dead-letter queues. - Strong troubleshooting mindset, clear communication, and comfort operating in a production-support environment. - Interest in data platforms, data engineering systems, orchestration, streaming workloads, event-driven architecture, internal developer tools, and production data services. Now "Nice to Have" list: - Experience with Kubernetes deployment and release tooling such as Helm, ArgoCD, or similar GitOps workflows. - Experience with CI/CD automation using GitHub Actions, GitLab CI, Jenkins, or similar pipelines. - Familiarity with infrastructure as code using Terraform or similar provisioning tools. - Familiarity with Databricks, Spark, Spark Structured Streaming, Airflow, Astronomer, dbt, Kafka, Pub/Sub, object storage, or lakehouse architectures. - Experience with observability tools such as Grafana, Prometheus, Cloud Monitoring, Datadog, Splunk, or similar platforms. - Experience supporting internal applications, APIs, event-driven services, streaming consumers, or backend workers. - Exposure to data reliability concepts such as freshness, latency, completeness, pipeline health, data quality checks, and dependency-aware alerting. - Exposure to SLOs, SLAs, error budgets, postmortems, or formal reliability practices. Now Benefits list from "Rewards": after "Rewards Requirements" heading? Actually text: "Rewards Requirements We provide a suite of benefits that promote physical, emotional and financial well-being for ‘Every World’ - we’ve got our employees covered! Subject to eligibility requirements, the Company offers comprehensive benefits including: Medical, dental, vision, health savings account or health reimbursement account, healthcare spending accounts, dependent care spending accounts, life and AD&D insurance, disability insurance;401(k) with Company match, tuition reimbursement, charitable donation matching;Paid holidays and vacation, paid sick time, floating holidays, compassion and bereavement leaves, parental leave;Mental health & wellbeing programs, fitness programs, free and discounted games, and a variety of other voluntary benefit programs like supplemental life & disability, legal service, ID protection, rental insurance, and others;If the Company requires that you move geographic locations for the job, then you may also be eligible for relocation assistance. Eligibility to participate in these benefits may vary for part time and temporary full-time employees and interns with the Company. You can learn more by visiting https://www.benefitsforeveryworld.com/." We need to turn that into list items. The benefits are separated by semicolons and commas. We'll split into logical items: - Medical, dental, vision - Health savings account or health reimbursement account - Healthcare spending accounts - Dependent care spending accounts - Life and AD&D insurance - Disability insurance - 401(k) with Company match - Tuition reimbursement - Charitable donation matching - Paid holidays and vacation - Paid sick time - Floating holidays - Compassion and bereavement leaves - Parental leave - Mental health & wellbeing programs - Fitness programs - Free and discounted games - Variety of other voluntary benefit programs like supplemental life & disability, legal service, ID protection, rental insurance, and others - Relocation assistance (if required to move geographic locations) We'll keep as list items. Now Pay: paragraph: "In the U.S., the standard base pay range for this role is $102,800.00 - $190,204.00 Annual. These values reflect the expected base pay range of new hires across all U.S. locations. Ultimately, your specific range and offer will be based on several factors, including relevant experience, performance, and work location. Your Talent Professional can share this role’s range details for your local geography during the hiring process. In addition to