Jobs · Analyst · New York

Business Analyst, Digital Product Management

A+E Global Media · New York, United States · 1 mo ago
Analyst$97k–$112k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, there is a description: "A+E Global Media offers a work environment where employees collaborate in office 3 times per week. New hires must be commutable to one of our current office locations in New York City, Los Angeles, Chicago, and Stamford, CT. Please refer to the job description for any specific division requirements." That's about work environment and location. Could be "About the role" or maybe "Responsibilities"? It's more about the role context. We'll put under "About the role". Then "Division Story ..." is narrative about team; could be part of About the role as well. Then "Job Description The Role - Business Analyst, Digital Product Management" then description of role. That's responsibilities. Then "More About What You’ll Do" bullet list of duties. That's responsibilities. Then "BASIC REQUIREMENTS:" list of requirements. That's requirements. Then "Compensation Annual Pay Range: $97,391 - $112,000 Annual Incentive Target: 10.00% ..." That's Pay. Then "A+E offers a competitive total compensation package, which includes healthcare coverage, 401k matching, and a range of other benefits." That's Benefits. Schedule: The posting mentions "collaborate in office 3 times per week." That's schedule info (hybrid). So we can include Schedule section with that detail. We should not include boilerplate EEO etc. We must not repeat job title as heading. Already not. We need to use

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

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can combine similar info. We need to avoid filler like "commensurate with experience" etc. Not present. We need to output only HTML fragment. Let's structure:

    About the role

    A+E Global Media offers a hybrid work environment where employees collaborate in the office three times per week. New hires must be commutable to one of the company’s office locations in New York City, Los Angeles, Chicago, or Stamford, CT. The Technology team is described as innovative, collaborative, and fun‑focused, modernizing core solutions with a cloud‑first approach and guided by its “Technology Code.”

    That captures the work environment and division story. Next responsibilities:

    Responsibilities

    • Help shape and evolve digital experiences that bring A+E’s brands and stories to audiences across A&E, HISTORY, and other editorial sites.
    • Launch new features and manage ongoing enhancements, partnering with Editorial, UX/UI, Engineering, and other teams to translate business and audience needs into thoughtful, scalable solutions.
    • Contribute throughout the product lifecycle—from identifying opportunities and defining requirements to prioritizing work, supporting delivery, and evaluating results.
    • Balance audience needs, business priorities, and technical considerations while bringing structure and clarity to complex initiatives.
    • Oversee the content management systems (CMS) that support editorial experiences, ensuring platforms and workflows remain stable, intuitive, and adaptable.
    • Work closely with editorial producers to understand day‑to‑day needs, identify pain points, and translate opportunities into actionable product and technical requirements.
    • Partner with editorial producers, Engineering, UX/UI, and other stakeholders to understand business and audience needs and translate them into clear product and technical requirements.
    • Define and document workflows, use cases, user stories, acceptance criteria, and other requirements needed to design, build, test, and launch new capabilities.
    • Prioritize initiatives and enhancements by balancing audience impact, editorial and business goals, technical considerations, dependencies, and available resources.
    • Guide new features and enhancements through the product development lifecycle, maintaining stakeholder alignment and proactively identifying risks, questions, and dependencies.
    • Manage and continuously improve the CMS platforms that support A+E’s editorial sites, focusing on efficient, reliable, and scalable tools and workflows.
    • Partner with editorial producers to evaluate current processes, identify inefficiencies, and implement technology or workflow improvements that make content creation and publishing easier.
    • Collaborate with UX/UI and Engineering to evaluate solutions, understand technical tradeoffs, and ensure experiences meet user and business needs.
    • Oversee the implementation and ongoing evolution of privacy and consent‑management initiatives across digital experiences.
    • Partner with Legal and Engineering to translate privacy requirements into actionable product and technical changes and support responsible data practices.
    • Support testing and validation to ensure new features meet defined requirements and deliver the intended experience.
    • Monitor launched experiences, stakeholder feedback, and available data to identify opportunities for optimization.
    • Stay current on emerging technologies, audience behaviors, privacy trends, and digital publishing capabilities, identifying opportunities to evolve products, platforms, and ways of working.
    That seems comprehensive. Now Requirements: We have BASIC REQUIREMENTS list. Also there is "BA/BS in related field is preferred." That's a qualification. We could have Requirements section for the bullet list, and Qualifications for education? But we can combine. The instruction: Use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have requirements (experience, skills). We have qualifications (BA/BS preferred). We have skills (maybe we can separate). But we can also put all under Requirements and not create Qualifications if not needed. However we have a specific qualification: BA/BS in related field is preferred. That's a qualification. We also have skills list embedded in requirements: strong analytical, problem-solving, communication, etc. Could be separate Skills section. But we need to avoid thin sections. Perhaps we can combine Requirements and Qualifications into one Requirements section, and Skills into another if we have enough. Let's extract: From BASIC REQUIREMENTS: - At least four years of product management and/or business analysis experience supporting digital products, ideally using data-informed practices to guide decisions. - Experience supporting full-stack websites and applications, with a foundational understanding of content management systems, HTML, CSS, and modern digital technologies. - Strong analytical and problem-solving skills, with the ability to translate complex or ambiguous needs into clear, actionable requirements. - Demonstrated ownership and accountability, including the ability to move initiatives forward independently, surface risks early, and follow through from definition through delivery. - Ability to manage multiple priorities and stakeholders in a fast-paced environment while maintaining strong organization and attention to detail. - Strong communication and collaboration skills, with the ability to work effectively across creative, editorial, business, design, legal, and technical teams. - Ability to communicate technical concepts clearly to nontechnical audiences and business or audience needs effectively to technical teams. - A thoughtful, curious approach, with the willingness to ask questions, challenge assumptions, and work with partners to identify the right solution. - Ability to balance immediate business needs with longer-term product and platform considerations, creating scalable solutions rather than one-off fixes. - Basic understanding of Agile methodologies and experience working in an Agile product development environment. - Familiarity with tools such as Jira is a plus. - Strong technical, creative, and strategic acumen, with the ability to connect audience needs, business objectives, design considerations, and technical capabilities. - Familiarity with visual design and information architecture concepts and the ability to collaborate effectively with UX/UI partners. - Curiosity about changes in audience behavior, technology, and the market, with the ability to identify emerging product opportunities. - A willingness to contribute beyond individual projects by identifying opportunities to improve processes, tools, and team effectiveness. - BA/BS in related field is preferred. We could split: Requirements (experience and core competencies) and Qualifications (education). Skills could be the soft skills like communication, analytical, etc. But many of those are also skills. Given the instruction to prefer a few substantive sections over many thin ones, maybe we combine all into one Requirements section, and maybe a separate Skills section for the soft skills? But that could be thin. Alternatively, we could have Requirements (experience and technical) and Qualifications (education). And maybe Skills not needed. But we have a lot of skill-like items; we could put them under Requirements. Let's decide: We'll have:

    Requirements

      (list all the bullet points from BASIC REQUIREMENTS, including BA/BS preferred as a bullet) That covers experience, skills, education. Then we have Pay section:

      Pay

      Annual Pay Range: $97,391 - $112,000. Annual Incentive Target: 10.00%. Compensation will be based on qualifications, skills, competencies, location, and experience. A+E offers a competitive total compensation package.

      But we also have Benefits separate. Benefits:

      Benefits

      A+E offers a competitive total compensation package that includes healthcare coverage, 401k matching, and a range of other benefits.

      Schedule:

      Schedule

      Employees collaborate in the office three times per week (hybrid work model).

      We should not include fluff like "Learn more at www.aegm.com/careers." That's application instruction; we should drop. We should not include EEO boilerplate. Now check that we haven't missed any substantive info: The division story about Technology team, we included in About the role. The location info included. The "Please refer to the job description for any specific division requirements." That's a reference; we can drop as it's not substantive. The "Job Description The Role - Business Analyst, Digital Product Management" we used as heading? Not needed. We captured responsibilities. We captured requirements. We captured pay. We captured benefits. We captured schedule. Now ensure we didn't repeat any content unnecessarily. Check that we didn't include any placeholder like "commensurate with experience". Not present. Now format: Use

      for each section heading. Use
      • for lists. Use

        for prose. We need to output only HTML fragment, no or . Let's craft. Potential issues: The responsibilities list is long; we need to ensure we didn't miss any bullet from "More About What You’ll Do". We included many but need to verify we covered all. Let's list the original responsibilities from the posting: From "Job Description The Role - Business Analyst, Digital Product Management": - Help shape and evolve the digital experiences that bring A+E’s brands and stories to audiences across A&E, HISTORY, and other editorial sites. - Launch new features and manage ongoing enhancements, partnering with Editorial, UX/UI, Engineering, and other teams to translate business and audience needs into thoughtful, scalable solutions. - Contribute throughout the product lifecycle—from identifying opportunities and defining requirements to prioritizing work, supporting delivery, and evaluating results. - Success requires the ability to balance audience needs, business priorities, and technical considerations while bringing structure and clarity to complex initiatives. - You will also oversee the content management systems (CMS) that support our editorial experiences, helping ensure that platforms and workflows remain stable, intuitive, and adaptable. - You will work closely with editorial producers to understand their day-to-day needs, identify pain points, and translate opportunities into actionable product and technical requirements. Then "More About What You’ll Do" bullet list: - Partner with editorial producers, Engineering, UX/UI, and other stakeholders to understand business and audience needs and translate them into clear product and technical requirements. - Define and document workflows, use cases, user stories, acceptance criteria, and other requirements needed to design, build, test,

Similar jobs