Senior Manager, Revenue Enablement

We need to output HTML fragment with sections: About the role, Responsibilities (what you'll do), Requirements (what we're looking for), maybe Benefits, Pay, Schedule. The posting includes Base Salary Range and benefits details. Also includes "Why this role matters" maybe could be part of About the role? But we should only include sections when there is real specific content. We have content for About the role (the paragraph after "About The Role"). Responsibilities: "What you’ll do" bullet list. Requirements: "What we’re looking for" bullet list. Benefits: there is a list of benefits under "US Full-Time Employee Benefits at Ironclad:" etc. Pay: Base Salary Range: $150,000 - $170,000 +bonus +equity. Schedule: Not mentioned; we should not create Schedule section if not present. Also we have "Compensation Range: $150K - $170K" duplicate; we can ignore duplicate. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. The posting includes some boilerplate at start about Ironclad description; that is not part of role specifics? It's company overview; we might keep as part of About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company overview is substantive but not part of role; but we could include it as part of About the role? The heading "About The Role" is present; after that there is a description of the role. The preceding paragraphs about Ironclad are generic company description; they might be considered boilerplate? Not exactly boilerplate like EEO; it's company overview. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview is not those; we could keep it maybe as a preamble before sections? But we must output only HTML fragment; we could include a

with that overview before the headings? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other content outside sections. We could include a

for the company overview before the first heading. However, they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have other content. Thus structure: maybe a

with company overview (the first paragraph about Ironclad). Then

About the role

then

with the role description paragraph. Then

Responsibilities

then

with items from "What you’ll do". Then

Requirements

then
with items from "What we’re looking for". Then

Benefits

then
with benefits list. Then

Pay

then

with salary range and bonus/equity note. Possibly also include note about base salary range etc. We must not include sections with filler like "commensurate with experience". Not present. We need to ensure we preserve all substantive information: include the details about base salary range, bonus, equity, location (San Francisco headquarters). Also include the benefits list exactly as given. Let's extract benefits list: - 100% health coverage for employees (medical, dental, and vision), and 75% coverage for dependents with buy-up plan options available - Market-leading leave policies, including gender-neutral parental leave and compassionate leave - Family forming support through Maven for you and your partner - Paid time off - take the time you need, when you need it - Monthly stipends for wellbeing, hybrid work, and (if applicable) cell phone use - Mental health support through Modern Health, including therapy, coaching, and digital tools - Pre-tax commuter benefits (US Employees) - 401(k) plan with Fidelity with employer match (US Employees) - Regular team events to connect, recharge, and have fun - And most importantly: the opportunity to help build the company you want to work at - UK Employee-specific benefits are included on our UK job postings We should keep all. Now responsibilities list from "What you’ll do": - Own and evolve scalable global enablement programs that improve productivity, field readiness, and front line manager effectiveness. - Build practical AI-forward enablement that helps the Revenue org understand and adopt emerging AI capabilities - Translate Ironclad’s AI and product strategy into clear field sales plays, messaging, and reinforcement that helps the Revenue team position Ironclad’s value effectively in the agentic era. - Partner closely with Revenue leaders to identify business priorities, surface field gaps, and focus enablement on the highest-value opportunities. - Reinforce strong discovery, value-based selling, platform pitch quality, and manager coaching through practical programs, workshops, and certifications. - Help raise the bar on how Ironclad is positioned in the market by equipping the field with stronger AI-era narratives, stronger competitive differentiation, and clearer business-value storytelling. - Partner cross-functionally with Product, Product Marketing, Sales Ops, Legal, Customer Outcomes, and Enablement peers to align readiness, messaging, and execution. - Use data, manager feedback, and field signals to identify where sellers are getting stuck and design targeted programs that improve overall performance. - Define and operationalize success metrics that connect enablement work to meaningful business outcomes, not just completion rates or activity metrics. Now requirements list from "What we’re looking for": - 5+ years of experience in Revenue Enablement, Sales Enablement, Revenue Productivity, Sales leadership, or a closely related GTM role. - Strong fluency with AI tools, workflows, and prompting, plus the ability to turn AI potential into practical field adoption and seller behavior change. - Experience building and scaling enablement programs that improve execution, not just content delivery. - A strong understanding of what drives revenue effectiveness, deal progression, pipeline quality, and manager-led coaching. - Demonstrated experience influencing senior stakeholders and operating effectively in highly cross-functional environments. - Strong facilitation and program design skills across live, virtual, and on-demand formats. - A sharp point of view on how to equip sellers for an AI-shaped market, including messaging, differentiation, workflow adoption, and customer conversations. - Strong communication skills, executive presence, and the ability to bring structure and clarity to fast-moving environments. - High ownership, strong judgment, and a bias for action. Nice to have list: we could optionally include as part of Requirements? The instruction: use sections for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Nice to have could be part of Requirements or maybe a separate "Qualifications" section? But we have both required and nice to have. We could include nice to have as part of Requirements (maybe as a sublist) but better to keep as part of Requirements? The instruction says "Use

• for any list of duties/requirements/benefits". So we can include nice to have as part of Requirements list, maybe separate with a note? But we must preserve all substantive information; we can include them as separate bullet points under Requirements, maybe preceded by a note "Nice to have:" but that would be extra text not in original. Better to create a separate section "Qualifications" for nice to have? However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine required and nice to have into one Requirements section, but we could differentiate with a note? Might be considered adding text not present. Safer to include nice to have as part of Requirements but maybe label them with "Nice to have:" inside the
• ? That would be adding text. Could instead create a separate section "Qualifications" for nice to have. But we already have Requirements; Qualifications could be separate. The instruction allows sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications sections. That seems appropriate: Requirements = must-have; Qualifications = nice to have. Let's do that. Thus:

  Requirements

  with the 9 items.

  Qualifications

  with the nice to have items (4 items). Now Benefits section as described. Pay section: Base Salary Range: $150,000 - $170,000 +bonus +equity. Also note that base salary range represents min and max based at SF headquarters, actual base depends on factors, etc. Also mention equity awards, health benefits etc? But benefits already covered. We'll include the salary description paragraph. We should not include duplicated compensation range line. Now ensure we don't include any boilerplate like "Pursuant to the San Francisco Fair Chance Ordinance..." that's legal; remove. Also remove the line "US Full-Time Employee Benefits at Ironclad:" maybe we keep as intro before list? Could be considered heading? We'll just start list directly; but we might lose the phrase "US Full-Time Employee Benefits at Ironclad:" which is substantive? It's a label. Might be okay to drop as it's just a label; but we could include as a

  before the list. The instruction says preserve ALL substantive information; that label is substantive? It's describing the benefits list. Safer to include as a

  before the

  . However that might be considered extra text not a heading; it's fine. Similarly, we have "UK Employee-specific benefits are included on our UK job postings" - keep as a

  after list. Now About the role: we need to include the paragraph after "About The Role". Also maybe include the preceding company overview? Let's include company overview as a

  before the heading. Thus final HTML:

  [company overview paragraph(s)]

  About the role

  [role description paragraph]

  Responsibilities

  ...

  Requirements

  ...

  Qualifications

  ...

  Benefits

  US Full-Time Employee Benefits at Ironclad:

  ...

  UK Employee-specific benefits are included on our UK job postings.

  Pay

  [salary description]

  Check for any other sections like "Why this role matters" - could be included as part of About the role maybe as another paragraph. It's substantive; we could add another

  after About the role paragraph before Responsibilities. But we already have About the role heading; we could put multiple

  under it. Let's include that paragraph as a separate

  under About the role. Thus About the role section will have two paragraphs: the role description paragraph and the "Why this role matters" paragraph. Now let's craft text exactly. Company overview paragraph(s): The first paragraph: "Ironclad is the leading AI contracting platform that transforms agreements into assets. Contracts move faster, insights surface instantly, and agents push work forward, all with you in control. Whether you’re buying or selling, Ironclad unifies the entire process on one intelligent platform, providing leaders with the visibility they need to stay one step ahead. That’s why the world’s most transformative organizations, from Rivian to the World Health Organization and the Associated Press, trust Ironclad to accelerate their business. We’re consistently recognized as a leader in the industry: a Leader in the Forrester Wave and Gartner Magic Quadrant for Contract Lifecycle Management, a Fortune Great Place to Work, and one of Fast Company’s Most Innovative Workplaces. Ironclad has also been named to Forbes’ AI 50 and Business Insider’s list of Companies to Bet Your Career On. We’re backed by leading investors including Accel, Y Combinator, Sequoia, BOND, and Franklin Templeton. For more information, visit www.ironcladapp.com or follow us on LinkedIn."