Live Operations Associate

We need to output HTML fragment with sections for headings where there is real content. Must not repeat job title. No Job ID. Remove boilerplate like application instructions, EEO, etc. Keep substantive info: role description, responsibilities, experience, maybe hybrid working, benefits, culture? The instructions: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes "Compensation N/A" and "Location not specified". So we should NOT create Pay or Schedule sections because they are N/A/not specified. Benefits: there is a paragraph about benefits, but it's generic: "Roku is committed to offering a diverse range of benefits... Our comprehensive benefits include global access to mental health and financial wellness support and resources. Local benefits include statutory and voluntary benefits which may include healthcare (medical, dental, and vision), life, accident, disability, commuter, and retirement options (401(k)/pension). Employees are supported in taking time off... It's important to note that not every benefit is available in all locations or for every role." This is somewhat generic but still mentions benefits. The rule: never create Benefits section unless posting actually states them. It does state benefits, albeit generic. Should we include? It says "prefer a few substantive sections over many thin ones." Benefits is somewhat generic but still content. Might include. However, we must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits, so we can include Benefits section. But we must ensure not to include placeholder like "not specified". The benefits paragraph is not placeholder; it's actual description albeit generic. So we can include Benefits. Hybrid working: there is a paragraph about hybrid working. That's not a standard heading but could be under "Work Arrangement" maybe not in list. The allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can only use those headings. So we need to map content to those headings. "About the role" could contain role snapshot description. "Responsibilities" for responsibilities list. "Requirements" or "Qualifications" for experience/skills. "Skills" maybe for technical skills. "Benefits" for benefits. We should not create Pay or Schedule. We must not repeat job title. Use

for each section heading. We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from the posting. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we strip things like "Ready to apply? Review the details above and continue to the employer's site to start your application." Also "Role snapshot Compensation N/A Location Location not specified Technologies AWSAzureGCPTerraformPythonBash Certifications SAA-C03". That's metadata; we should fold minor metadata into a short

or drop it. Probably drop it. We need to keep the description about team, role, responsibilities, experience, hybrid working, benefits, culture? Culture maybe not a standard heading; could go under About the role? Might be okay to include as part of About the role. We must not create sections with filler. So we will produce sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits. Possibly also "Work Arrangement" but not allowed; maybe we can include hybrid working under About the role or Requirements? Better to include under About the role as it's about work arrangement. We need to use

• for any list of duties/requirements/benefits. So responsibilities list should be
  • . Requirements list maybe also
    • . Skills list maybe
      • . Benefits list maybe
        • . We need to use

          for prose. We must output only HTML fragment, no /, no markdown. Let's extract content. About the role: includes description of team, mission, what team works on, what is the role, how will I use AI at Roku? Also maybe culture. We'll combine into prose paragraphs. Responsibilities: list of responsibilities bullet points from "What are the responsibilities of the role?" That's a long list each starting with a verb. We'll turn each into

        • . Requirements/Qualifications: The posting has "What experience would help someone be successful in this role at Roku?" That's a list of experience/qualifications. We'll treat as Requirements. Skills: Could separate technical skills like AWS, Azure, GCP, Terraform, Python, Bash, certifications, scripting, observability tools, etc. But we already have many in requirements. Might combine. To avoid thin sections, maybe we just have Requirements and Responsibilities and Benefits. But we need to follow instruction: prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits. That's four sections. We need to include Benefits section with the benefits paragraph. We must not include Pay or Schedule. Let's craft. About the role: include paragraphs about Roku mission, Live Operations FAST team, role description, AI usage, hybrid working, culture maybe. We need to ensure we don't repeat content verbatim too much? It's okay to copy. We'll produce:

          About the role

          Roku is the #1 TV streaming platform in the U.S., Canada, and Mexico, aiming to power every television in the world. The Live Operations FAST team focuses on delivering high-quality, seamless experiences across the Free Ad-Supported Streaming Television (FAST) channel ecosystem, managing the full lifecycle of FAST channel onboarding and ongoing channel health, collaborating with service partners, content publishers, and internal stakeholders.

          As a Live Operations Associate, you will be a key operational partner to FAST channel publishers and internal teams, guiding new channels through onboarding and ensuring established channels meet Roku's quality and compliance standards. You will coordinate across cross‑functional teams (content, engineering, partnerships, ad operations) to drive smooth channel launches and manage ongoing changes to live channel configurations, working alongside infrastructure, engineering teams, and service providers to support observability, automation, and encoding pipeline health as the FAST ecosystem scales.

          You will serve as a trusted point of contact for service partners, manage expectations, communicate clearly through ambiguous situations, and keep projects moving. As part of a shared‑resources team you will flex to support any region as needed, bringing in‑country localized knowledge and technical depth.

          At Roku, AI agents handle most keystroke‑level coding; engineers act as technical leads, setting context, planning work, verifying outputs, and recovering when the agent goes off course. The company encourages curiosity, adaptability, and excitement to grow alongside these technologies.

          Roku fosters an inclusive and collaborative environment where teams generally work in the office Monday through Thursday, with Fridays flexible for remote work (except where five‑day attendance is required). The culture emphasizes problem‑solving, action, collaboration, trust, and a pragmatic approach to innovation.

          Responsibilities: list. We need to capture each bullet from responsibilities: - Leading and coordinating FAST channel onboarding end-to-end, working with content partners and internal teams to meet launch milestones and quality standards - Serving as the primary operational contact for assigned service partners, building strong relationships and ensuring issues are resolved efficiently - Managing ongoing FAST channel configurations, including schedule updates, metadata changes, feed ingestion, and EPG alignment - Monitoring channel and pipeline health using observability tools; validating ingestion, triaging transcode and CDN delivery issues, and escalating incidents with clear context to engineering or peer technical teams - Driving automation of repetitive operational workflows through scripting, and collaborating with cloud infrastructure, operations, or business teams on capacity planning, incident reviews, or retrospectives - Driving change management efforts — communicating process or platform changes clearly to partners and internal stakeholders, and supporting smooth transitions - Coordinating cross-functionally with content, engineering, ad operations, and partnerships teams to resolve channel health issues and deliver on partner commitments - Flexing to support any region as part of a shared resources model, bringing regionally informed operational knowledge to ensure localized requirements are met - Tracking and managing multiple concurrent workstreams, maintaining clear documentation and status visibility for leadership and stakeholders - Driving continuous improvement efforts by identifying operational inefficiencies, proposing process enhancements, and helping implement changes that scale with team growth - Leveraging AI tools and emerging technologies to improve operational workflows, accelerate content review, and support faster, smarter decision-making across the team - Assisting in developing and refining operational playbooks, onboarding guides, and internal tooling to improve team efficiency and consistency - Maintaining service level expectations through proactive communication and timely follow-through on partner inquiries and escalations - Supporting the training and onboarding of new team members as the FAST operations team grows We'll put each as
        • . Requirements: list from "What experience would help someone be successful in this role at Roku?" We'll capture each bullet. Let's extract: - 4+ years of experience in digital media operations, streaming, or a related field, ideally working with content partners or service teams of varying sizes - Hands-on knowledge of FAST and VOD channel ecosystems, linear programming schedules, EPG management, metadata formats (XML, JSON), encoding pipelines, video packaging (HLS, DASH), and CDN delivery architecture - Experience with cloud infrastructure platforms (AWS, GCP, or Azure); familiarity with Infrastructure as Code tools such as Terraform or CloudFormation and well-architected framework principles - AWS Certified Solutions Architect – Associate (SAA-C03) or equivalent cloud certification - Scripting proficiency in Python, Bash, or similar — able to automate a workflow, parse a feed, or write a diagnostic tool when needed - Working knowledge of observability tooling (e.g., Datadog, Grafana, ELK, CloudWatch) to monitor pipeline health, identify issues, and support incident response - Strong organizational skills with a detail-oriented mindset — tracking details so nothing falls through the cracks - Excellent communication skills, both written and verbal, with the ability to explain technical concepts clearly to non-technical partners and adapt tone for different audiences - Demonstrated ability to manage competing priorities across multiple partners or projects simultaneously - Experience with change management or process improvement in an operational context - Familiarity with in-country localized requirements for FAST channel distribution — including regional content standards, metadata conventions, and compliance considerations - Collaborative, team-first approach with a track record of working effectively across internal technical and business groups - Working knowledge of productivity tools including Office, Confluence, Jira, Lucid, and project tracking software; familiarity with CMDB and CMS systems - A continuous improvement mindset — looking for ways to make the process better each time - You have built fluency across the agentic engineering toolchain — coding harnesses like Claude Code or Cursor, MCP servers, custom skills, or agent frameworks. And you can describe projects where you shipped real work with these tools. You know how to drive an agent, verify its output, and ramp on an unfamiliar codebase with an agent helping you - Bachelor's degree in Business, Communications, Engineering, or a related discipline preferred - Experience with DAI/SSAI technologies, DRM, or content protection schemes - Ability to conduct business in multiple languages, particularly English and German or French We'll put each as
        • under Requirements. Benefits: we need to capture the benefits paragraph. It's a bit long; we can break into

          or

          • . Since it's a description, we can use

            . But instruction: use

            • for any list of duties/requirements/benefits. Benefits is not a list but a description; we can use

              . However we could also split into bullet points: global access to mental health and financial wellness support; local benefits include statutory and voluntary benefits which may include healthcare