Partner Sales Enablement Content & Solution Strategy Lead — Sage X3

We need to output HTML fragment with sections: About the role (maybe from description), Responsibilities, Requirements (Qualifications), Benefits, maybe Pay? The posting mentions "Competitive salaries that landed us top 5%..." but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention benefits: health, dental, vision, 401k, PTO, parental leave, volunteer days, tuition reimbursement, wellness program, career development. So we can include Benefits section. Pay: they mention competitive salaries but not specific numbers; "Competitive salaries that landed us top 5% of similar sized companies" is vague but still a statement about pay. However instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive salaries" might be considered vague but not exactly placeholder. It's still a statement about pay. Might be okay to include Pay section with that statement. But they said "Prefer a few substantive sections over many thin ones." Could combine Pay into Benefits? Probably better to have Benefits only. Pay section might be thin. I'd omit Pay. Schedule: they mention hybrid, three days per week onsite. That's schedule info. Should we include Schedule section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule: hybrid, three days per week onsite. So we can include Schedule section with that detail. We need headings: About the role (maybe from first paragraph), Responsibilities, Requirements (Qualifications), Benefits, Schedule. We must not repeat job title as heading. Use

for each section heading. Use

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

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. At end there are links to careers homepage, Glassdoor, LinkedIn. Those are boilerplate? Probably navigation/footer. Should remove them. Also remove "What it’s like to work at Sage:" and the links. We need to include the perks list as benefits. Let's extract content. Job Description paragraph: "The Global X3 Enablement Content & Solution Strategy Lead will develop and deliver high-impact enablement content, demonstration strategies, and solution-focused learning experiences for Sage X3 direct Sales, Solution Consulting, and Partner audiences globally. This role will combine strong Sage X3 and sales/presales expertise with content development and solution storytelling. It will translate existing product, marketing, competitive, and industry information into practical enablement assets that improve how X3 is positioned, demonstrated, and sold. The role will work closely with Product, Product Marketing, Learning Services, Solution Consulting, Sales, and Partner Enablement teams, and will remain hands-on enough to demonstrate X3 directly when required. This role is hybrid, three days per week onsite in one of the Sage offices." That's About the role. Key Responsibilities list: bullet points. We need to capture each bullet as

• . List: - Define and execute the global X3 enablement content strategy in alignment with business and regional priorities. - Champion AI to speed up delivery and deliverables quality. - Develop demo videos, demo scripts and scenarios, presales assets, discovery materials, industry-focused enablement, release content, and Consensus demo experiences. - Translate existing sales, product, competitive, and marketing content into practical enablement experiences. - Partner with Sage University and Learning Services to support role-based learning paths, certifications, and competency development. - Develop reusable demo stories and scenarios that can be executed in the standard X3 demonstration environment. - Provide feedback and recommendations on demo environments, datasets, and supporting assets. - Maintain strong functional and presales knowledge of Sage X3 and deliver demonstrations when needed. - Support partner roundtables, release-readiness sessions, certification activities, Sage Discovery Center content, and selected strategic partner engagements. - Create industry-relevant assets using established X3 vertical positioning and available Product and Marketing materials. - Partner cross-functionally on major X3 releases to develop presentations, demo assets, videos, and readiness content. - Promote global reuse of enablement assets while supporting regional localization where appropriate. - Work with Partner Enablement Managers to identify recurring capability gaps and develop scalable content to address them. - Review content effectiveness and field feedback to continuously improve the enablement experience. - Help facilitate and participate in partner resource coaching and feedback. Required Qualifications list: - 7+ years of experience in Solution Consulting, Presales, Sales Enablement, Partner Enablement, Product Enablement, or a related enterprise software role. - Strong knowledge of Sage X3 or comparable ERP solutions. - Proven experience developing demonstrations, videos, presentations, scripts, scenarios, and learning content. - Strong understanding of enterprise software sales cycles, discovery, solution positioning, and value-based selling. - Ability to translate complex product capabilities into clear business value and compelling solution stories. - Strong facilitation, presentation, writing, and communication skills. - Experience working cross-functionally with Product, Product Marketing, Sales, Solution Consulting, Learning Services, and Partner teams. - Ability to manage multiple global initiatives while maintaining quality and consistency. - Experience with platforms such as Highspot, Consensus, LMS tools, or video-production technologies is preferred. - Demonstrated AI content development experience Success Measures: maybe not needed as a section? Could be part of Responsibilities? But it's separate. Could be its own section? The instruction: include a section ONLY when posting has real, specific content for it. Success Measures is specific content. Could be a section "Success Measures". But we already have many sections. Might be okay to include as a subsection? However they said prefer a few substantive sections over many thin ones. Success Measures could be considered thin? It's a list of measures. Could be included under Responsibilities? But it's separate. Might be okay to include as its own section "Success Measures". But we already have About the role, Responsibilities, Requirements, Benefits, Schedule. Adding Success Measures makes 6 sections. Might be okay. But we need to check if any of those sections would be thin/filler. Success Measures includes bullet points: Content Adoption & Scale, Solution & Demo Effectiveness, Enablement Readiness, Commercial Impact. Each with sub-bullets. That's substantive. Thus we can include Success Measures section. Now Benefits: list perks. - Competitive salaries that landed us top 5% of similar sized companies (according to Comparably) - Comprehensive health, dental and vision coverage - 401(k) retirement match (100% matching up to 4%) - 32 days paid time off (21 personal days, 10 national holidays, 1 floating holiday) - 18 weeks paid parental leave for birth, adoption or surrogacy offered 1 year after start date - 5 days paid yearly to volunteer (through Sage Foundation) - $5,250 tuition reimbursement per calendar year starting 6 months after hire date - Sage Wellness Rewards Program ($600 wellness credit and $360 fitness reimbursement annually) - Library of on-demand career development options and ongoing training offerings Schedule: "This role is hybrid, three days per week onsite in one of the Sage offices." Already mentioned in About the role but we can still have Schedule section with that detail. However we might duplicate. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we already included schedule in About the role, we could keep it there and not have separate Schedule section to avoid duplication. But they said do not repeat job title as heading; duplication of content is okay? They said preserve ALL substantive information; not to remove info. If we keep schedule only in About the role, it's still preserved. Having a separate Schedule section would repeat the same sentence, which is duplication but not prohibited. Might be better to avoid duplication and keep schedule only in About the role. However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." They gave Schedule as example heading. So likely they expect a Schedule section if schedule info exists. The About the role already includes schedule; but we could still have Schedule section with that sentence. It's not duplicate info? It's same info but in a different section. Might be okay but could be considered redundant. However they said preserve ALL substantive information; duplication doesn't lose info. It's okay. But they also said "Prefer a few substantive sections over many thin ones." Adding Schedule may make another thin section (just one sentence). Might be better to incorporate schedule into About the role and not have separate Schedule section. However they gave Schedule as an example heading, implying they expect it if schedule info exists. I'd include Schedule section with that sentence. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

  About the role

  ... (the paragraph)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Success Measures

  • Content Adoption & Scale
    • Content utilization
    • Global asset reuse
    • Role-based content adoption
    • Reduced duplication of regional content
  • Solution & Demo Effectiveness
    • Demo effectiveness
    • Presales readiness and competency
    • Adoption of reusable demo stories
    • Partner and Solution Consultant feedback
  • Enablement Readiness
    • Time to release readiness
    • Availability of priority enablement assets
    • Learning-path and certification content readiness
  • Commercial Impact
    • Opportunity influence
    • Improved partner and presales readiness
    • Correlation between asset adoption and commercial performance
  But note: The Success Measures bullet points are originally headings with sub-bullets. We need to represent them as nested lists. Use
  • for each top-level, and inside another
    . Now Benefits:

    Benefits

    • Competitive salaries that landed us top 5% of similar sized companies (according to Comparably)
    • Comprehensive health, dental and vision coverage
    • 401(k) retirement match (100% matching up to 4%)
    • 32 days paid time off (21 personal days, 10 national holidays, 1 floating holiday)
    • 18 weeks paid parental leave for birth, adoption or surrogacy offered 1 year after start date
    • 5 days paid yearly to volunteer (through Sage Foundation)
    • $5,250 tuition reimbursement per calendar year starting 6 months after hire date
    • Sage Wellness Rewards Program ($600 wellness credit and $360 fitness reimbursement annually)
    • Library of on-demand career development options and ongoing training offerings
    Schedule:

    Schedule

    This role is hybrid, three days per week onsite in one of the Sage offices.

    We must ensure we didn't include any boilerplate like "Careers homepage - ..." etc. Remove those. Now check for any repeated content: The About the role paragraph includes schedule sentence; we also have Schedule section repeating it. That's duplication but okay. Now ensure we didn't miss any substantive info: The "Key Responsibilities" we captured all bullets. The "Required Qualifications" we captured all bullets. The "Success Measures" we captured. The "Benefits" we captured all perks. The "Schedule" we captured.