DirectJobHub
Jobs · Information Technology · California

Digital Content & Platform Specialist

Tennis Channel · Santa Monica, CA · 3 wk ago
Information Technology$34.6–$38.14/hrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. We need to parse the posting. First paragraph: description of role. Could be "About the role". Then responsibilities list: bullet points after "In this role, you will:" and then many bullet-like sentences. We'll put those in
  • . Qualifications: after "Qualifications:" we have bullet-like lines: "3+ years of experience in live streaming operations preferred", "5+ years of experience in digital media supply chain workflow, content operations, and sports broadcast is a plus", etc. We'll treat as list. Skills: maybe combine some of the qualifications? But we have separate sections: Skills maybe from "Understanding of live sports broadcast and streaming workflows", "Understanding of content operations, publishing, distribution, media supply chain, and transmission.", "Ability to process information from many sources...", "Deep operational familiarity with OTT, connected TV, mobile, web, and partner-platform streaming environments...", "Comfort working with KPIs and metrics...", "Strong tennis knowledge...". Could be Skills. Benefits: later: "Full time positions are eligible for benefits that include participation in a retirement plan, life and disability insurance, health, dental and vision plans, flexible spending accounts, sick leave, vacation time, personal time, parental leave and employee stock purchase plan." Pay: "The base hourly compensation range for this role is $34.60 to $38.14 per hour. Final compensation for this role will be determined by various factors such as a candidates’ relevant work experience, skills, certifications, and geographic location." Schedule: "Digital Content & Platform Specialists work on-site in our Santa Monica, CA office, on a rotating schedule — “following the tournaments” — that includes nights, weekends, swing shifts, and occasional holidays." Also location: Santa Monica, CA office. Could be part of schedule or maybe a separate line but not required heading. We can embed in schedule paragraph. We need to avoid duplication and boilerplate. Remove EEO etc. Remove "About Tennis Channel", "About Sinclair", "About The Team" maybe not needed as they are not specific to role? They are company description; could be omitted as not role-specific. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Tennis Channel", "About Sinclair", "About The Team" are not boilerplate but maybe considered company overview; they might be considered substantive? The instruction says preserve ALL substantive information; but also "Prefer a few substantive sections over many thin ones." It might be okay to include them under a section like "About the Company" but we don't have that heading in allowed list. Allowed headings are only those listed. So we should not add extra headings. Could we incorporate that info into "About the role"? Probably not appropriate. Better to omit company overview as not required heading; but then we would be omitting substantive info. However the instruction says "Preserve ALL substantive information". If we omit, we violate. But we cannot add new headings beyond allowed list. Could we put them under existing headings like "About the role" as a paragraph? That might be okay: we can include company description within About the role paragraph. The heading "About the role" is allowed. So we can put company overview there. Thus we will have sections: About the role (includes role description and company overview), Responsibilities, Requirements (maybe combine qualifications?), Qualifications (maybe separate), Skills, Benefits, Pay, Schedule. But we need to avoid thin sections. Let's decide: - About the role: paragraph summarizing role and company overview. - Responsibilities: list of duties from "In this role, you will:" bullet points. - Requirements: maybe the "3+ years of experience..." etc? Actually those are qualifications. Could treat as Requirements. - Qualifications: maybe the "Extensive experience operating content management systems..." etc? But that overlaps. Better to have one section for Qualifications/Requirements combined? But we have both headings allowed; we could split: Requirements = minimum experience; Qualifications = preferred/experience plus skills. However to avoid thin sections, we could combine into one section called "Qualifications" and include both required and preferred. But we have both headings allowed; we need to decide. Given the posting: after responsibilities, there is "Qualifications:" then bullet list. Then after that there is "Strong tennis knowledge..." etc. Actually the qualifications section includes both required and preferred plus skills. Then later there is "Strong tennis knowledge..." which is part of qualifications. Thus we can have a single Qualifications section containing all bullet points after "Qualifications:" plus the Strong tennis knowledge line. Then Skills maybe not needed separately; but we could extract skill-like statements: "Understanding of live sports broadcast and streaming workflows", "Understanding of content operations, publishing, distribution, media supply chain, and transmission.", "Ability to process information from many sources...", "Deep operational familiarity with OTT, connected TV, mobile, web, and partner-platform streaming environments...", "Comfort working with KPIs and metrics...", "Strong tennis knowledge...". Those could be Skills. But we already have Qualifications covering similar. To avoid duplication, we could treat Qualifications as the bullet list under "Qualifications:" and Skills as the other statements. However there is overlap. Maybe better: Use Requirements for the "3+ years..." and "5+ years..." etc (minimum/preferred experience). Use Skills for the understanding/ability/familiarity/comfort/knowledge statements. Use Qualifications for maybe the "Extensive experience operating content management systems..." etc? Actually that is also a skill. Let's examine the text: "Qualifications: 3+ years of experience in live streaming operations preferred 5+ years of experience in digital media supply chain workflow, content operations, and sports broadcast is a plus Extensive experience operating content management systems for live streaming, VOD and publishing. Understanding of live sports broadcast and streaming workflows Understanding of content operations, publishing, distribution, media supply chain, and transmission. Ability to process information from many sources — transmission vendors, league offices, and internal teams — and synthesize it under time pressure Deep operational familiarity with OTT, connected TV, mobile, web, and partner-platform streaming environments, including platforms such as Roku, Amazon, Apple TV, and similar destinations. Comfort working with KPIs and metrics (uptime, MTTD/MTTR, SLA compliance) used to improve service quality, not to assign blame Strong tennis knowledge, including familiarity with tournaments and the sport" Thus the Qualifications block includes both experience and skill statements. So we could keep Qualifications as a single section containing all those bullet points. Then we may not need separate Skills section. But the instruction allows Skills heading; we could omit if not needed. It says "include a section ONLY when the posting has real, specific content for it". If we put all under Qualifications, we have content for Qualifications. Skills would be empty if we don't extract separate. So we omit Skills. Similarly, Requirements maybe not needed if we put experience under Qualifications. But we could split: Requirements = the experience years; Qualifications = the rest. However the posting lumps them together under "Qualifications:" heading. To preserve original structure, we could keep a single Qualifications section. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. Now craft HTML. We'll start with maybe not required; just use headings and content. We need

    for each section heading. Inside each, we can have

    for prose,

    • for lists. Let's draft. About the role: combine role description and company overview. Paragraph 1: "The Digital Content & Platform Specialist supports the operational readiness, monitoring, QA, and incident response for Tennis Channel’s live events & VOD across its digital ecosystem, including our owned apps, FAST channels, and distribution to partner platforms such as Amazon, Roku, Apple TV, and Fubo. This role goes beyond monitoring: Specialists are expected to build deep fluency in our Content Management System and publishing workflows, know our tournament schedules and content inside and out as the backbone of daily work. Specialists act as first responders when something goes wrong — detecting, triaging, and resolving incidents at Tier 1, escalating when needed, and communicating impact quickly and clearly to stakeholders. Equally important is the proactive half of the role: verifying streams, schedules, metadata, and partner feeds ahead of all matches and major tournaments, catching issues before they become visible to a subscriber or partner, and feeding recurring pain points back to Product and Engineering as a trusted partner rather than a downstream customer. This is an opportunity to help operate — and help shape — a team that is moving from reactive stream-watching to a higher-value role that protects revenue, viewer trust, and the platforms we serve." Then company overview: maybe a paragraph: "Tennis Channel is the only multiplatform destination dedicated solely to tennis year-round. Together, the Tennis Channel flagship network, Tennis Channel 2, and the Tennis Channel app (tennischannel.com) deliver the most accessible and concentrated single-sport coverage anywhere. As the exclusive U.S. home of the ATP Tour and WTA Tour, Tennis Channel features live coverage of every Masters 1000 tournament — including Indian Wells, the Miami Open, Madrid, Rome, Cincinnati, and more — alongside live studio programming including its premier series, TC Live. Tennis Channel 2, a free FAST channel available in over 100 million homes, brings fans matches from across the globe at every level of the game. The Tennis Channel app brings it all together in one place, delivering live and on-demand matches, original content, and a personalized multi-view experience for fans, available on mobile and connected TV devices. Owned by Sinclair, Tennis Channel is also a co-owner of PickleballTV (pickleballtv.com), a joint venture with the Professional Pickleball Association." We can combine into one or two paragraphs. Responsibilities: list from "In this role, you will:" bullet points. Let's extract each bullet: - Actively monitor all delivery platforms — owned apps (iOS, Android), FAST channels, OTT, and VOD — across Apple TV, Roku, Amazon Prime, Fubo, and other partner destinations to ensure continuous, high quality delivery. - Operate Tennis Channel's streaming content management system (CMS) and publishing tools to support live and on-demand programming. - Act as Tier-1 incident command: detect, triage, and classify issues under documented escalation procedures, and communicate business impact to stakeholders quickly and clearly. - Contribute to the team’s SOPs, runbooks, known-issue documentation, and post-incident follow-up to help improve consistency, reduce repeat issues, and strengthen operations across shifts. - Maintain and contribute to the team's proactive communication with internal and external stakeholders across every shift. - Complete pre-event checklists and proactively verify streams, schedules, metadata, and partner feeds ahead of and during major tournaments and marquee matches. - Own content and metadata quality assurance for what publishes — image replacement, descriptions, and video replay replacement — against clear editorial guidelines. - Triage streaming, CMS, publishing, sync, feed, and platform issues at Tier 1, resolving within documented procedures and escalating technical issues, including router, signal, or transmission concerns, to Engineering, vendors, or other internal teams as appropriate. - Produce partner-platform health updates and serve as a point of contact for distribution issues with Amazon, Roku, and other partners. - Identify product or platform flaws, document and escalate issues affecting the consumer experience, partnering with Product and Engineering as a shared stakeholder in outcomes. - Respond professionally and effectively to Tennis Channel Customer Service on consumer inquiries regarding direct to consumer (DTC) products. We'll put each as
    • . Qualifications:

Similar jobs