Broadcast Engineer

We need to output HTML fragment with sections: About the role? The posting includes a summary paragraph after company description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections with real content. We have: - Summary: "As a Broadcast Engineer, you’ll play a critical role..." This could be About the role. - Responsibilities: list of bullet points. - Experience: list of bullet points (these are requirements/qualifications/skills). We need to decide which sections to include. We have "Experience" heading in source but we need to map to our allowed headings: Requirements, Qualifications, Skills. The content includes years of experience, understanding, experience with broadcast infrastructure, networking fundamentals, troubleshooting ability, familiarity with certain technologies, communication skills, self-motivated, willingness to work evenings etc. Could split into Requirements (years, understanding, experience), Skills (troubleshooting, communication, documentation, problem-solving, self-motivated, organized, calm under pressure), Qualifications maybe overlapping. But we should avoid thin sections. Perhaps combine into Requirements and Skills. We also have Pay: "The annualized base salary range for this position in California is $110,00 to $120,000." Note there's a typo: $110,00 to $120,000 (should be $110,000). We must preserve as is. Also note "The base salary offered will factor in internal equity and may also vary depending on the candidate's geographic region, job-related knowledge, skills, and relevant experience, among other factors." That's pay info. Schedule: "Willingness to work evenings, weekends, holidays, and travel as needed to support live productions." Also earlier: "Participate in rotating on-call and event support schedules, including nights, weekends, and holidays as required by live productions." So schedule info exists. Benefits: Not mentioned. So we should not include Benefits section. We also have "All applicants must be at least 18 years of age..." and EEO statements: these are boilerplate to remove. Also the IMPORTANT NOTICE about recruiting scam: remove. Also company description at top: maybe not needed as it's not a section heading; but we could include as About the role? Actually the summary already describes role. The company description could be considered part of About the role? But instructions: do not repeat job title as heading; we can include prose paragraphs under About the role. The company description is not directly about the role but could be considered background; but we might keep it as part of About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the company description? It's not about the role but it's substantive info about the company. However the sections we can use are limited to those headings. We could put company description under About the role as a paragraph before the role summary. That seems acceptable. Thus About the role section will contain: company description paragraph(s) plus the summary paragraph. Now Responsibilities: list bullet points. Requirements: maybe include the "Experience" bullet points that are more about years, understanding, experience with infrastructure, networking fundamentals. Could be Requirements. Skills: include troubleshooting, communication, documentation, problem-solving, self-motivated, organized, calm under pressure, willingness to work evenings etc? But willingness to work evenings is schedule. Might be better to put schedule separate. We have schedule info: rotating on-call, nights, weekends, holidays, willingness to work evenings etc. So Schedule section. Pay section: salary range and note. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Pay, Schedule. We must not include empty sections. Now format: Use

for each heading. Then content: either

for prose, or

• for lists. We need to preserve all substantive information. Let's extract details. Company description: "Cosm is a global technology company that brings experiences to life in immersive environments. We help our partners create spaces and content that blur the lines of real and virtual across three primary markets: Sports and Entertainment, Science and Education, and Parks and Attractions. Cosm was born from the fusion of some of the greatest innovators in the history of technology. Evans & Sutherland, Spitz, Inc., and Cosm Immersive combined forces to power the immersive experiences of the future as Cosm. Innovation is in our DNA." That's a paragraph. Summary paragraph: "As a Broadcast Engineer, you’ll play a critical role in delivering some of the world’s most advanced immersive live productions. Operating from our Los Angeles-based REMI facilities, you’ll oversee the health, quality, and reliability of cutting-edge broadcast systems supporting live sports and entertainment events captured in resolutions of 8K and beyond. This role combines broadcast engineering, systems integration, networking, troubleshooting, and live event operations. You’ll collaborate closely with field engineers, production teams, software developers, and venue operations to ensure every broadcast meets Cosm’s uncompromising quality standards. If you’re someone who thrives in fast-paced live environments, enjoys solving complex technical challenges, and wants to help shape the future of immersive broadcasting, we’d love to hear from you." That's another paragraph. Now Responsibilities bullet list: - Operate, monitor, and maintain REMI broadcast workflows supporting immersive productions at resolutions of 8K and beyond. - Perform technical quality control (QC) of live video, audio, networking, and transmission paths before and during live broadcasts. - Serve as a primary escalation point for technical issues across remote production systems, coordinating with field engineers and venue operators to quickly diagnose and resolve problems. - Configure, deploy, and support broadcast infrastructure including routing systems, switchers, encoders, recorders, graphics systems, monitoring, networking equipment, and signal transport technologies. - Assist with the design, testing, and deployment of new production workflows that improve operational efficiency and expand remote production capabilities. - Support system integrations, upgrades, and validation of emerging broadcast technologies. - Partner with Production, Operations, Software Engineering, and Technical Operations teams to ensure successful execution of live events. - Maintain detailed operational documentation, workflows, and technical procedures. - Proactively identify opportunities to improve system reliability, scalability, and operational efficiency. - Participate in rotating on-call and event support schedules, including nights, weekends, and holidays as required by live productions. Note: The last bullet about rotating on-call could also go to Schedule, but it's in Responsibilities list. We'll keep it there; but we also have schedule info elsewhere. Might duplicate. However we must preserve all info; we can keep it in Responsibilities and also have Schedule section with additional details. That's okay. Now Experience bullet list (under Experience heading): - 3+ years of engineering experience supporting live broadcast, live production, or media technology environments. - Strong understanding of broadcast signal flow, transmission systems, and live production workflows. - Experience with broadcast infrastructure including routing, switching, encoding, recording, monitoring, and IP-based video transport. - Working knowledge of networking fundamentals, including TCP/IP, multicast, VLANs, and managed switches. - Proven ability to troubleshoot complex hardware, software, networking, and production issues in fast-paced live environments. - Familiarity with REMI, cloud-based production, or IP media technologies such as ST 2110, NDI, SRT, RIST, Dante, or PTP is preferred. - Strong communication, documentation, and problem-solving skills with the ability to collaborate across technical teams. - Self-motivated, organized, and able to remain calm under pressure while supporting mission-critical live events. - Willingness to work evenings, weekends, holidays, and travel as needed to support live productions. Now Pay: "The annualized base salary range for this position in California is $110,00 to $120,000. The base salary offered will factor in internal equity and may also vary depending on the candidate's geographic region, job-related knowledge, skills, and relevant experience, among other factors." Also note: "All applicants must be at least 18 years of age at the time of employment. This requirement is in accordance with applicable federal, state, and local labor laws." This is a requirement but could be considered a requirement. However it's a legal boilerplate; but it's substantive info about eligibility. Should we keep? It's not EEO; it's age requirement. Might be considered a requirement. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal requirement about age; might be considered legal boilerplate but it's a bona fide job requirement (must be 18+). It's not EEO. I'd keep it as part of Requirements maybe. But we already have Requirements section; we could add a bullet: "Must be at least 18 years of age at time of employment." Now Schedule: we have schedule info from responsibilities bullet and experience bullet. Let's combine: - Participate in rotating on-call and event support schedules, including nights, weekends, and holidays as required by live productions. - Willingness to work evenings, weekends, holidays, and travel as needed to support live productions. We could also mention that schedule includes nights, weekends, holidays. Now we need to ensure we don't include boilerplate like EEO, scam notice, etc. Now produce HTML. Structure:

  About the role

  Cosm is a global technology company ...

  As a Broadcast Engineer, you’ll play a critical role ...

  Responsibilities

  • ...
  ...

  Requirements

  • 3+ years of engineering experience supporting live broadcast, live production, or media technology environments.
  • Strong understanding of broadcast signal flow, transmission systems, and live production workflows.
  • Experience with broadcast infrastructure including routing, switching, encoding, recording, monitoring, and IP-based video transport.
  • Working knowledge of networking fundamentals, including TCP/IP, multicast, VLANs, and managed switches.
  • Proven ability to troubleshoot complex hardware, software, networking, and production issues in fast-paced live environments.
  • Familiarity with REMI, cloud-based production, or IP media technologies such as ST 2110, NDI, SRT, RIST, Dante, or PTP is preferred.
  • Strong communication, documentation, and problem-solving skills with the ability to collaborate across technical teams.
  • Self-motivated, organized, and able to remain calm under pressure while supporting mission-critical live events.
  • Must be at least 18 years of age at the time of employment.

  Skills

  Maybe we could move some items to Skills: communication, documentation, problem-solving, self-motivated, organized, calm under pressure. But they are already in Requirements. Might be redundant. Better to keep Requirements as is and not have Skills section if it would be thin. However we have many skill-like items; we could split: Requirements: years, understanding, experience, networking knowledge, familiarity with tech, age. Skills: troubleshooting, communication, documentation, problem-solving, self-motivated, organized, calm under pressure. That seems reasonable. Let's do that. Requirements bullet list: - 3+ years of engineering experience supporting live broadcast, live production, or media technology environments. - Strong understanding of broadcast signal flow, transmission systems, and live production workflows. - Experience with broadcast infrastructure including routing, switching, encoding, recording, monitoring, and IP-based video transport. - Working knowledge of networking fundamentals, including TCP/IP, multicast, VLANs, and managed switches. - Familiarity with REMI, cloud-based production, or IP media technologies such as ST 2110, NDI, SRT, RIST, Dante, or PTP is preferred. - Must be at least 18 years of age at the time of employment. Skills bullet list: - Proven ability to troubles