Front End Developer

We need to output HTML fragment with sections: About the role? Actually the posting includes Company Description, Job Description, The Opportunity, Why This Role Matters, What You'll Do, Qualifications, How We Do It, Bonus Points, Why You’ll Love It Here, Additional Information (but we need to remove boilerplate like EEO, legal, etc). Also we need to include sections only when there is real specific content. Use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. No Job ID. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to preserve all substantive information. Let's parse the posting: Company Description: VERSANT (Nasdaq: VSNT) is an industry-changing media and entertainment business... (list of brands). This is substantive. Job Description: The Opportunity ... etc. We need sections: maybe "About the role" (or "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. But we can also have other headings? Likely we should stick to those categories. However we have content like Company Description, Why This Role Matters, What You'll Do, Qualifications, How We Do It, Bonus Points, Why You’ll Love It Here, Additional Information. We need to map to allowed headings. We could treat: - About the role: combine Company Description + The Opportunity + Why This Role Matters? Or separate? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings, but not limited to them? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those exact headings when we have content for those categories. If we have other content not fitting, maybe we still need to use those headings? The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only output sections that correspond to those headings if we have content. If we have content that doesn't fit any of those headings, maybe we still need to output something else? But likely we can map content to those headings. Let's map: - About the role: could include company description and overview of the role (The Opportunity, Why This Role Matters). That seems appropriate. - Responsibilities: What You'll Do (list of duties). Use

  • . - Requirements: Qualifications (required qualifications). Use
    • . - Skills: maybe Bonus Points? Or How We Do It? Actually "How We Do It" describes core competencies/trust etc. Could be considered Skills? Or maybe "Skills" section for technical skills? The Qualifications already list required qualifications. Bonus Points could be "Skills" or "Preferred Qualifications". The instruction includes Skills as a possible heading. So we can put Bonus Points under Skills. - Benefits: The posting mentions "Why You’ll Love It Here" (benefits/culture). Also includes "This is a fully remote position. Team members should expect opportunities for in-person collaboration..." That's about work arrangement, could be Benefits or Schedule? There's no explicit Pay or Benefits. There's mention of compensation in Additional Information (pay range). That's Pay. So we need a Pay section if there is real specific content. The posting says: "VERSANT Media is committed to fair and equitable compensation practices. We include a good faith pay range for each position to comply with applicable state and local pay transparency laws..." It does not give actual numbers. It says "Actual compensation will be based on factors such as the candidate's skills, qualifications, experience, and location and may include additional forms of compensation and benefits such as health insurance, retirement plans, paid time off, etc." That's not a specific range; it's generic. According to instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Since they didn't give actual numbers, we should not create a Pay section. Similarly Benefits: they mention health insurance, retirement plans, paid time off etc as part of compensation but not specific. Might be considered filler? It's generic. Probably we should not create Benefits section unless specific benefits listed. There's no specific list. So we skip Benefits and Pay. - Schedule: They mention fully remote, with occasional in-person ~10% time. That's schedule info. Could be Schedule section. It's specific: fully remote, expect opportunities for in-person collaboration approx 10% of the time. That's substantive. So we can create a Schedule section. Thus sections: About the role, Responsibilities, Requirements, Skills, Schedule. We need to ensure we don't repeat job title as heading. Not include Job ID. We need to remove boilerplate: EEO, legal, accommodation, etc. Also remove "As part of our selection process, external candidates may be required to attend an in-person interview..." That's maybe part of process but could be considered application instructions? It's not exactly application instruction but could be considered part of selection process. The instruction says remove application instructions. That line is about interview process; maybe we should remove it. Also remove "VERSANT Media's policy is to provide equal employment opportunities..." etc. Remove all EEO and legal paragraphs. Also remove "VERSANT Media is not accepting unsolicited assistance from search firms..." etc. Also remove duplicated lines. Now craft content. About the role: combine company description and the opportunity/why role matters. Let's write a concise paragraph preserving all substantive info. Company Description: VERSANT (Nasdaq: VSNT) is an industry-changing media and entertainment business and home to trusted brands that shape culture, inform audiences, and build lasting connections. It operates across four core markets: political news and opinion, business news and personal finance, golf, and sports and genre entertainment. These markets are served through a powerful portfolio of iconic and innovative brands, including CNBC, MS NOW, USA Network, Golf Channel, Oxygen, E!, SYFY, and Versant's sports division USA Sports, along with complementary digital assets including Fandango, Rotten Tomatoes, GolfNow and GolfPass. The Opportunity: Versant is seeking a Front-end Developer to join our Creative Operations team and help build intuitive, production-focused tools for creating, managing, and deploying real-time graphics. This role will initially focus on supporting Versant’s growing sports portfolio, developing web-based interfaces that connect graphics workflows with live statistical data across properties including the WNBA, college basketball, college football, and Golf Channel. Over time, the scope may expand to support additional businesses and production use cases across Versant. You will design and develop GUI applications that enable production teams to access, review, and control live data-driven graphics within existing Sync and Viz Engine environments. You will also work with sports data provider APIs and backend services to surface current statistics clearly and help ensure dependable graphics execution during live productions. Although the role has a strong front-end focus, you will have opportunities to deepen your experience with APIs, backend services, and real-time data workflows, supporting continued growth across the full technology stack. Why This Role Matters: Creative Operations manages company-wide Sync software and backend infrastructure while supporting sports, CNBC, MS NOW, and other enterprise initiatives. The tools and integrations developed in this role will help establish scalable workflows for Versant’s expanding sports portfolio and advance our live production capabilities for 2027 and beyond. This is a fully remote position. Team members should expect opportunities for in-person collaboration, team gatherings, planning sessions, or other business needs approximately 10% of the time. We could keep the remote note in Schedule section instead. Thus About the role could exclude the remote note. Let's keep About the role: Company Description + The Opportunity + Why This Role Matters (excluding remote note). Then Schedule section will have remote and in-person 10%. Now Responsibilities: What You'll Do list. List items: - Design, develop, and enhance intuitive web-based interfaces that allow production teams to create, manage, review, and control real-time graphics. - Partner with graphics and production teams working in Viz Engine and Unreal Engine to understand workflows, identify needs, and translate them into reliable production tools. - Integrate front-end applications with backend services, sports data providers, and APIs to support accurate and timely data-driven graphics. - Contribute across the software development lifecycle, including requirements gathering, prototyping, development, testing, QA, deployment, and production support. - Help ensure tools perform reliably in live production environments by troubleshooting issues, improving workflows, and collaborating with technical and production stakeholders. - Build solutions with scalability and maintainability in mind as Versant’s sports and enterprise production needs evolve. These are bullet points. Requirements: Qualifications (required). List: - Experience developing modern web applications using technologies such as React, Node.js, TypeScript, JavaScript, HTML, and CSS. - Experience integrating applications with APIs and real-time communication technologies such as REST, gRPC, or WebSockets. - Familiarity with development environments and tools such as Visual Studio Code or JetBrains Rider. - Experience with source control and collaborative software development workflows using GitHub or comparable tools. - Working knowledge of scripting languages such as Go, Bash, or Python. - Understanding of the software development lifecycle and experience working within Agile development practices. - Comfort developing and troubleshooting across Mac/Linux and Windows environments. - Ability to work effectively with technical and non-technical partners in production-focused environments where reliability and responsiveness matter. Skills: Bonus Points list: - Experience working with AI platforms, libraries, or models such as Google Gemini, Vertex AI, ChatGPT, or Anthropic. - Experience managing Agile development work through tools such as Jira. - Knowledge of databases and caching technologies such as MongoDB or Redis. - Exposure to backend or server-side technologies including C#, Java, or C++. - Familiarity with containerization, orchestration, and CI/CD technologies such as Docker, Kubernetes, Rancher, or Argo CD. - Experience with real-time graphics platforms such as Viz Engine or Unreal Engine. - Experience supporting newsroom, sports, broadcast, or live show production environments, including tools such as Fonn Saga or Avid iNEWS. Schedule: Fully remote position; team members should expect opportunities for in-person collaboration, team gatherings, planning sessions, or other business needs approximately 10% of the time. We should not include Pay/Benefits sections. Now output HTML fragment with

      headings and appropriate

      or

      • . We need to ensure we don't include any markdown fences. Let's craft:

        About the role

        VERSANT (Nasdaq: VSNT) is an industry-changing media and entertainment business and home to trusted brands that shape culture, inform audiences, and build lasting connections. It operates across four core markets: political news and opinion, business news and personal finance, golf, and sports and genre entertainment. These markets are served through a powerful portfolio of iconic and innovative brands, including CNBC, MS NOW, USA Network, Golf Channel, Oxygen, E!, SYFY, and Versant's sports division USA Sports, along with complementary digital assets including Fandango, Rotten Tomatoes, GolfNow and GolfPass.

        Versant is seeking a Front-end Developer to join our Creative Operations team and help build intuitive, production-focused tools for creating, managing, and deploying real-time graphics. This role will initially focus on supporting Versant’s growing sports portfolio, developing