Staff DevOps Engineer

We need to output only HTML fragment, no html/body tags. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. The posting includes: About Us (but we shouldn't repeat job title; we can have About the role? Actually "About Us" is company description; we could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have: - Position Overview (description of role) -> could be "About the role". - Core Responsibilities -> "Responsibilities". - Developer Experience (subcategory under responsibilities) but we can include under Responsibilities. - Incident & Operational Excellence -> also responsibilities. - Technical Leadership -> responsibilities. - Key Qualifications -> could be "Qualifications" or "Requirements". They have "Key Qualifications". Also "Preferred Qualifications". So we can have a Qualifications section (maybe combine required and preferred). Could also separate Requirements vs Qualifications but we need to follow instruction: use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Skills maybe from technical skills. Could create a Skills section for specific technologies. We have Benefits: they described benefits package. So include Benefits. Pay: they gave compensation range $190,000 - $235,000 per year. So include Pay. Schedule: not mentioned. So we should NOT include Schedule heading because no specific content. We also have "Special Work Conditions" (sedentary). That's not a standard heading; we could maybe include under Benefits? But instruction: only include sections when posting has real specific content for it. Could we create a "Work Conditions" heading? Not in allowed list. Probably we should omit it or fold into a paragraph under Benefits or About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." For special work conditions, maybe we can include as a short paragraph under Benefits or About the role. But better to include as a short paragraph under Benefits? Might be okay. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning). We need to remove EEO boilerplate, CA residents privacy, etc. Also remove "Benefits Are Subject To Eligibility Requirements." maybe keep? It's part of benefits description; it's substantive but maybe considered boilerplate? It's a statement about eligibility; we can keep it as part of benefits. We need to remove duplicated lines. We need to output only HTML fragment. Let's structure:

About the role

Position Overview: We are looking for a Staff DevOps Engineer to serve as a technical anchor for our platform engineering practice. In this role you will own the design and evolution of our CI/CD pipelines, Kubernetes infrastructure on AWS EKS, and the developer experience tooling that hundreds of engineers depend on daily. Staff-level engineers at this organization are expected to operate with significant autonomy, identify and resolve systemic problems before they become incidents, and raise the technical bar across the teams they partner with.

Maybe also include About Us? Could incorporate into About the role? The About Us is company description; maybe we can include as a short paragraph under About the role or separate? The instruction says use headings like About the role, Responsibilities, etc. So we can put company description under About the role as well. But we need to preserve all substantive information: About Us paragraph about Cast & Crew, family of brands, etc. So include that in About the role section. Thus About the role will contain both company overview and position overview. Next Responsibilities: combine Core Responsibilities, Developer Experience, Incident & Operational Excellence, Technical Leadership. We'll list as

• items. We need to preserve all bullet points. Let's extract responsibilities: From Core Responsibilities: - Platform & Infrastructure: Architect and continuously improve CI/CD pipelines in Azure DevOps, including pipeline-as-code standards, templating strategies, and artifact promotion workflows across environments. - Own the health and evolution of our AWS EKS clusters — node lifecycle, autoscaling, networking (VPC/CNI), RBAC, and cluster upgrades with minimal service disruption. - Design and enforce Infrastructure-as-Code practices using Terraform or equivalent tooling; champion GitOps patterns across engineering teams. - Drive platform reliability improvements informed by observability data from New Relic, working closely with SRE to translate dashboards and alerts into actionable platform changes. Developer Experience: - Define and maintain golden-path templates for containerized workloads — Dockerfile standards, Helm chart libraries, and local development parity with production. - Partner with engineering teams to accelerate onboarding of new services onto the platform and reduce toil through automation. Incident & Operational Excellence: - Act as an escalation point for complex infrastructure incidents coordinated through PagerDuty; participate in on-call rotation and lead post-incident reviews for platform-layer failures. - Identify recurring failure modes and drive systemic fixes that reduce page volume and MTTR across the platform. - Maintain and improve runbooks and platform documentation in Confluence, ensuring knowledge is accessible and current. Technical Leadership: - Define and socialize DevOps standards — pipeline design, container hygiene, secret management, and deployment safety — across a multi-team engineering organization. - Conduct architecture reviews and provide technical guidance on infrastructure-impacting decisions made by product engineering teams. - Mentor senior and mid-level engineers; grow internal platform capability through pairing, code review, and structured knowledge sharing. - Identify tooling gaps and build the business case for platform investments, working with engineering leadership to prioritize roadmap items. We'll list each as separate
• . Next Qualifications: we have Key Qualifications (required) and Preferred Qualifications. We can have a Qualifications section with two subheadings? But only allowed headings are the list; we could just list all qualifications under Qualifications heading, maybe separate required vs preferred within
  with notes. But we need to preserve all details. Let's extract: Key Qualifications: - 8+ years of DevOps or platform engineering experience, with at least 2 years operating at a Staff or Principal level in an organization of 100+ engineers. - Deep, hands-on expertise with Kubernetes — EKS specifically preferred — including troubleshooting workloads, networking, storage, and cluster operations at scale. - Strong command of Azure DevOps Pipelines, including YAML pipeline authoring, library management, service connections, and environment promotion gates. - Proven track record designing and maintaining CI/CD systems for microservice architectures with multiple independent teams as consumers. - Experience operating observability platforms (New Relic, Datadog, or similar) to drive proactive reliability improvements, not just reactive alerting. - Proficiency in at least one scripting language (Python, Bash, or Go) and Infrastructure-as-Code tooling (Terraform, Pulumi, or CDK). - Familiarity with feature flag patterns and operational considerations around progressive delivery (Unleash or equivalent is a plus). - Excellent written communication skills — you default to documentation and can translate complex infrastructure decisions into guidance engineers actually read. Preferred Qualifications: - Experience with data engineering or ML infrastructure workloads on Kubernetes (Spark on EKS, Argo Workflows, Airflow). - Background contributing to or maintaining internal developer portals (Backstage or similar). - Familiarity with FinOps practices and tooling for AWS cost attribution and optimization across shared Kubernetes clusters. - Experience in SRE-adjacent roles; comfort with SLO/SLI definition and error budget policy. We'll include these under Qualifications. Skills: Could we extract specific skills? Might be redundant with qualifications. But we could create a Skills section for specific technologies: Azure DevOps, AWS EKS, Terraform, New Relic, etc. However we already have them in qualifications. To avoid duplication, maybe we skip Skills section unless we have distinct skill list not covered. The instruction: prefer a few substantive sections over many thin ones. So we can omit Skills. Benefits: we have description: "We take care of our people. When you join Cast & Crew, you're backed by a benefits package built around what matters most. From comprehensive medical, dental, and vision coverage, to a 401(k) match, generous PTO, paid parental leave, health and wellness programs, tuition reimbursement, and employee discounts. We’re committed to helping you thrive, professionally, and personally. Benefits Are Subject To Eligibility Requirements." We'll include that as
  • items maybe. Pay: compensation range $190,000.00 - $235,000.00 per year. We'll include Pay section with that. Schedule: not present, omit. We also need to include maybe a short paragraph for Special Work Conditions? Could fold into Benefits or About the role as a note. But we could add a short

    under Benefits: "Special work conditions: Sedentary – involves sitting most of the time but may involve walking or standing for brief periods; may require exerting up to 15 lbs. of force occasionally." That preserves info. We must remove EEO boilerplate, CA residents privacy, etc. Now construct HTML. We'll start with

    About the role

    then

    containing company overview and position overview. We need to ensure we don't repeat job title as heading. The job title is Staff DevOps Engineer; we are not using it as heading. Now produce HTML. Let's craft:

    About the role

    At Cast & Crew, we’ve empowered creativity and supported the global entertainment industry for decades. Together with our family of brands - Backstage, CAPS, Checks & Balances, Final Draft, Media Services, Sargent-Disc, and The TEAM Companies – we operate as a combined entertainment technology and services provider offering industry standard screenwriting accounting software, digital payroll products, data & reporting, and a host of creative tools. The industry continues to move faster than ever, and the need for our expertise, our technology, and our people has never been greater. We are a production’s best ally every step of the way. #OneCastOneCrew

    We are looking for a Staff DevOps Engineer to serve as a technical anchor for our platform engineering practice. In this role you will own the design and evolution of our CI/CD pipelines, Kubernetes infrastructure on AWS EKS, and the developer experience tooling that hundreds of engineers depend on daily. Staff-level engineers at this organization are expected to operate with significant autonomy, identify and resolve systemic problems before they become incidents, and raise the technical bar across the teams they partner with.

    Then Responsibilities:

    Responsibilities

    • Platform & Infrastructure: Architect and continuously improve CI/CD pipelines in Azure DevOps, including pipeline-as-code standards, templating strategies, and artifact promotion workflows across environments.
    • Own the health and evolution of our AWS EKS clusters — node lifecycle, autoscaling, networking (VPC/CNI), RBAC, and cluster upgrades with minimal service disruption.
    • Design and enforce Infrastructure-as-Code practices using Terraform or equivalent tooling; champion GitOps patterns across engineering teams.
    • Drive platform reliability improvements informed by observability data from New Relic, working closely with SRE to translate dashboards and alerts into actionable platform changes.
    • Define and maintain golden-path templates for containerized workloads — Dockerfile standards, Helm chart libraries, and local development parity with production.
    • Partner with engineering teams to accelerate onboarding of new services onto the platform and reduce toil through automation.
    • Act as an escalation point for complex infrastructure incidents coordinated through PagerDuty; participate in on-call rotation and lead post-incident reviews for platform-layer failures.
    • Identify recurring failure modes and drive systemic fixes that reduce page volume and MTTR