Sr Digital Product Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes About Us, Summary, Essential Duties & Responsibilities, Education & Experience Required, Travel Requirements, What We Offer, Diversity Commitment (but we should remove EEO boilerplate). We should not repeat job title. Use

for section headings. Use

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

  for prose. We need to include sections only when posting has real specific content. Pay and Schedule: posting mentions "Salary range of $130,000-$155,000 based upon experience" and "Eligible for an annual bonus of up to 7.5% of the base salary". Also mentions hybrid schedule: "It is eligible to work a hybrid schedule, generally requiring work in-office and/or show site 2-3 days per week." So we can have Pay section and Schedule section. Benefits: "What We Offer" includes list: Medical, Dental, Vision Insurance, Tuition Reimbursement, Paid Parental Leave, Life, Accident and Disability, Retirement with Company Match, Paid Time Off. So Benefits section. We need to avoid boilerplate: Diversity Commitment is EEO boilerplate; we should remove it. Also "About Us" maybe not needed as a heading? The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings if appropriate? Probably we should stick to those headings where applicable. "About Us" could be considered "About the role"? But they said do NOT repeat the job title as a heading. "About Us" is company description; maybe we can include as a

  under a heading like "About the role"? However they said prefer a few substantive sections over many thin ones. Could combine About Us and Summary into a section like "About the role". But we need to preserve all substantive information. We could have a section "About the role" containing the About Us summary and the Summary paragraph. Or we could have separate sections: "About the role" and "Responsibilities". The instruction says use those headings as examples, not strict list. But we should aim to use those headings where appropriate. Let's decide sections: - About the role (contains About Us and Summary) - Responsibilities (Essential Duties & Responsibilities) - Qualifications (Education & Experience Required) - Skills (maybe we can extract skill list from qualifications? But we could also put under Qualifications. However they said prefer few substantive sections; we could combine Education & Experience and Skills into Qualifications. But we need to preserve all info. Could have Qualifications section containing education, experience, and skills bullet list. - Benefits (What We Offer) - Pay (Salary range and bonus) - Schedule (Hybrid schedule) Travel Requirements: maybe we could include under Schedule or a separate section? Not listed as example but we could include under Schedule or as its own section "Travel". Since they didn't list Travel as example, but we can still include if needed. However they said prefer few substantive sections; we could incorporate travel into Schedule section as a note. We must not include boilerplate like Diversity Commitment. We must not include application instructions, cookie/navigation/legal/EEO etc. We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must output only HTML fragment. Let's craft. First, About the role: combine About Us paragraph and Summary paragraph. About Us: "The Freeman Company is a global leader in events, on a mission to redefine live for a new era. With a data-driven approach and the industry’s largest network of experts, The Freeman Company's insights shape exhibitions, exhibits, and events that drive audiences to action. The integrated full-service solutions leverage a 99-year legacy in event management as well as new technologies to deliver moments that matter." Summary: "The Senior Digital Product Manager is critical to that mission. This role will lead prioritization and execution of ecommerce capabilities across the exhibitor shopping journey, translating customer insights, business priorities, analytics, and technology constraints into a focused product roadmap that drives measurable outcomes. The ideal candidate has a proven track record of delivering complex, customer-facing digital products in an enterprise environment. They should be comfortable operating across product strategy, discovery, agile delivery, stakeholder alignment, analytics, and executive communication. This role will partner closely with engineering, UX design, digital merchandising, marketing, customer experience, and data science teams to improve the end-to-end exhibitor experience. This position will support our Commerce group under our Technology Services team. It is eligible to work a hybrid schedule, generally requiring work in-office and/or show site 2-3 days per week. The ideal candidate will be based out of any of the following locations: Dallas, TX, Chicago, IL, Las Vegas, NV." We could keep location info maybe under Schedule? But schedule is about hybrid schedule; location could be separate but we could keep in About the role. Now Responsibilities: list of duties. We'll convert each sentence starting with a verb into

  . Need to preserve all substantive information. Let's extract bullet points: - Lead the end-to-end ecommerce shopping experience for event exhibitors, driving continuous improvement across product discovery, selection, configuration, checkout, account management, and post-order support. - Own and manage the product roadmap, prioritizing initiatives based on analytics, customer feedback, moderated/unmoderated studies, competitive analysis and stakeholder input, maximizing overall business impact. - Translate strategic priorities into clear product requirements, user stories, acceptance criteria, success metrics, and release plans. - Use analytics, customer feedback, moderated and unmoderated research, competitive analysis, and stakeholder input to identify opportunities and prioritize work. - Partner closely with engineering, QA, UX design, analytics, digital merchandising, marketing, customer experience, operations, and data science to deliver cohesive, end-to-end solutions. - Develop KPIs and measurement plans for new features and enhancements, ensuring outcomes are tracked and learnings are applied to future roadmap decisions. - Manage trade-offs and make clear prioritization recommendations to resolve timeline, scope, resource or business need conflicts. - Mentor business analysts and other product contributors by helping establish strong discovery, documentation, prioritization, and measurement practices. - Serve as a subject matter expert for the digital exhibitor experience and advocate for simple, intuitive, scalable solutions. - Support agile delivery by participating in discovery, backlog refinement, sprint planning, demos, release readiness, QA/UAT, and post-launch measurement. - Present roadmap priorities, progress, results, risks, and recommendations to executive leaders, stakeholders, and cross-functional partners as needed. - Leverage web analytics, financial data, customer insights, competitive analysis, and industry trends to evaluate new opportunities and inform product decisions. - Partner with analytics and data science teams to support AI, personalization, recommendations, guided ordering, cross-sell, upsell, and related commerce capabilities. - Ensure product decisions support Freeman’s broader digital commerce goals, including improved customer experience, higher conversion, revenue growth, operational efficiency, and scalable platform capabilities. That's all. Now Qualifications: Education & Experience Required plus skills. We need to list required experience, education, preferred skills. Let's extract: Required: - 7-10 years’ experience in a product management role, including demonstrated ownership of enterprise-scale digital commerce or ecommerce programs with measurable business impact. - Experience in a B2C Ecommerce environment and demonstrated success driving digital growth, conversion, and revenue outcomes. - Experience with enterprise tools such as Salesforce Commerce Cloud, Salesforce Service Cloud, Adobe Analytics, GA4, Jira, Azure DevOps, Confluence, or similar platforms preferred. - Experience managing vendor relationships, contracts, or technology budgets in support of a digital product roadmap preferred. - Bachelor’s degree in Computer Information Systems, Business or related field required, or equivalent experience. - MBA Preferred. Skills (derived from bullet list after Education & Experience): - Strong customer-first product mindset with the ability to simplify complex workflows into intuitive digital experiences. - Demonstrated ability to own and prioritize a product roadmap in a complex, cross-functional enterprise environment. - Strong analytical skills, including comfort using product usage data, funnel metrics, financial data, customer feedback, and research findings to make decisions. - Excellent written and verbal communication skills, with the ability to tailor messages for executives, technical teams, business stakeholders, and frontline users. - Experience working with UX design, engineering, QA, analytics, merchandising, marketing, customer experience, and operations teams. - Ability to define success metrics, build measurement plans, interpret results, and translate learnings into product recommendations. - Strong problem-solving skills with a bias toward practical, scalable, and measurable solutions. - Experience with ecommerce platforms, digital shopping journeys, personalization, product discovery, search, navigation, checkout, or customer self-service experiences preferred. We could put these under Qualifications as a mix of experience and skills, or separate Skills section. Since they said prefer few substantive sections, we could combine Education & Experience and Skills into Qualifications. Now Benefits: list from What We Offer: - Medical, Dental, Vision Insurance - Tuition Reimbursement - Paid Parental Leave - Life, Accident and Disability - Retirement with Company Match - Paid Time Off We should keep as list. Pay: Salary range of $130,000-$155,000 based upon experience; Eligible for an annual bonus of up to 7.5% of the base salary. Schedule: hybrid schedule, generally requiring work in-office and/or show site 2-3 days per week. Also location based out of Dallas, TX, Chicago, IL, Las Vegas, NV. Travel up to 25% maybe also schedule? Could include travel under Schedule or separate Travel section. Since they didn't list Travel as example, but we could incorporate into Schedule note. We'll make Schedule section containing hybrid schedule, locations, travel. Now we need to output HTML fragment with

  headings and

  or

  • . We must not include any extra text outside HTML. Let's construct:

    About the role

    ... combined About Us and Summary ...

    Responsibilities

    • ...
    ...

    Qualifications

    ... maybe we split into experience and skills? Could use

    for prose and

    for list of skills. But we need to preserve all info. Could do

    for experience/education bullets and

    for skills. But we need to follow rule: Use
    • for any list of duties/requirements/benefits, and

      for prose. So if we have a list of qualifications (experience/education) we should use

      . Skills also list, could be another
      . But we could combine into one list? Might be messy. Better to have two lists: one for Experience & Education, another for Skills. But we need headings? Could keep under same Qualifications heading and have two
      sections. That's okay. Thus:

      Qualifications

      Experience & Education

      ? But they said use

      for section headings; we could still use

      but not specified. Safer to keep only

      headings. So we could have one

      that includes both experience and skills items. But that would mix types. Might be okay but could be less clear. However instruction: "Use
      • for any list of duties/requirements/benefits". So if we have a list of qualifications (requirements) we can use
        . Skills also are requirements, so we can include them in same list. That would satisfy. Thus we will create a single
        under Qualifications containing all items: experience, education, skills. But we need to preserve all info; we can just list each bullet as
        • . That will be long but