Sales Enablement Manager (US East Coast)

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes description of role, responsibilities, requirements, nice-to-haves, benefits. No explicit Pay or Schedule. So we should not include Pay or Schedule sections. Also we need to avoid repeating job title as heading. Also no Job ID. We need to preserve all substantive information, remove boilerplate like EEO, etc. Also remove application instructions (like "Apply now and help us turn our GTM teams into a world-class sales engine." maybe considered application instruction? It says "Apply now and help us..." Might be considered call to action; we should remove application instructions. Also remove cookie/navigation/legal/EEO etc. Also remove duplicated lines. We need to include sections: About the role (maybe intro paragraph), Responsibilities (the bullet points under emojis), Requirements (must-haves), Qualifications? Might be overlapping with Requirements; but we can treat Requirements as must-haves, Qualifications maybe nice-to-haves? Or we could combine. The instruction: Use headings for those categories if content exists. We have must-haves (requirements) and nice-to-haves (maybe qualifications). Also we have skills? Could be under Skills heading: communication, organized, etc. But we can incorporate into Requirements. Better: Sections: About the role (intro paragraph), Responsibilities (the bullet list under emojis), Requirements (must-haves), Qualifications (nice-to-haves), Benefits (the benefits list). No Pay or Schedule. We must not include placeholder text. Ensure we don't include sections with filler. Now craft HTML. We need to wrap content in appropriate tags:

About the role

then

... intro paragraph(s) ...

. Then

Responsibilities

then

• ... each bullet.

. Then

Requirements

then

• ... must-haves.

. Then

Qualifications

then

• ... nice-to-haves.

. Then

Benefits

then

• ... benefits.

. We need to preserve all substantive information: The intro includes many paragraphs about n8n, mission, etc. We need to keep that but maybe condense? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all details, not remove any. However we can combine paragraphs into

tags; we must not lose any info. So we need to include the entire description about n8n, the founding, stats, etc. Also the role description paragraphs before responsibilities. Also the "This role is fully remote from the states of Massachusetts, Virginia, NY, NJ or Florida." That's location info; we should keep it maybe in About the role or Responsibilities? Probably About the role. We also need to keep the line: "If you’re applying, try n8n out - whether you’re technical or not - and share a screenshot of your first workflow with us. The easiest place to start is here: app.n8n.cloud/register." That's application instruction? It's encouraging to try n8n; might be considered part of the description but could be considered application instruction. The instruction says remove application instructions. This line is basically a call to action for applicants to try n8n and share a screenshot. That's likely an application instruction. So we should remove it. Also remove "We’re in a defining moment of an incredible journey. Come and build with us." That's maybe fluff but still substantive? It's part of the description; not strictly application instruction. Might keep. We need to remove EEO boilerplate at end: "n8n is an equal opportunity employer..." etc. Remove that. Also remove "Location disclaimer: If you see multiple job postings..." etc. Also remove "Why join us?" section? That's substantive; we could incorporate into About the role or maybe a separate section? But we have no heading for "Why join us?" but we could keep its content under About the role or maybe under Benefits? Actually "Why join us?" includes paragraphs about building something from ground up, supportive team, etc. That's substantive; we should keep it. Could be placed under About the role as additional paragraphs. We also need to keep the benefits list exactly as given. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now craft HTML. We'll need to escape any HTML special characters? The text includes emojis and maybe apostrophes; fine. Let's compile. About the role paragraph(s): Start: "The AI orchestration of your wildest imagination. n8n is the open workflow orchestration platform built for the new era of AI. We give technical teams the freedom of code with the speed of no-code, so they can automate faster, smarter, and without limits. Backed by a fiercely inventive community and 500+ builder-approved integrations, we’re changing the way people bring systems together and scale ideas for impact. Since our founding in 2019, we’ve grown into a diverse team of over 260 - working across Europe and the US, connected by a shared builder spirit and with our centre of gravity in Berlin. Along the way, we’ve: Cultivated a community of more than 650,000 active developers and buildersEarned 190K+ GitHub stars, making us one of the world’s Top 40 most popular projectsBacked by top investors, from Sequoia’s first German seed to our SAP's recent strategic investment - bringing us to a $5.2bn valuation That’s the company we’ve built. Now we’d love to see what you can build." Note there is missing punctuation; we keep as is. Then: "We’re in a defining moment of an incredible journey. Come and build with us. This role is fully remote from the states of Massachusetts, Virginia, NY, NJ or Florida. We’re now looking for a Sales Enablement Manager to make sure our GTM team scales just as fast - and just as effectively. 🎯 Your main goal will be to enable GTM teams to close more deals faster by providing the knowledge, resources, and training they need to succeed at every stage of the buyer journey. You’ll be helping us build on early-stage existing foundations (onboarding, certifications, tooling) and take it to the next level as we scale. This is a high-impact, hands-on role with a direct line to revenue outcomes. 🚀" We could keep the emojis as part of text. Now Responsibilities: The bullet points under emojis: - Build onboarding that shortens ramp time and boosts impact Design and deliver world-class onboarding for new GTM team members across Sales, Customer Success, and Solutions Engineering. Track and continuously improve ramp time through tailored strategies and performance feedback loops. Collaborate with leadership to define what “great” looks like across roles and build onboarding paths accordingly. - Create scalable enablement programs that drive revenue Translate product updates, GTM strategies, and technical concepts into clear, actionable content. Identify knowledge gaps and build role-specific enablement initiatives to address them. Design certifications and training frameworks (e.g. demo, discovery, technical proficiency) to ensure consistency and quality across the field. - Run high-impact enablement events and internal comms Support the planning and execution of team-wide enablement moments like SKOs, regional kickoffs, and quarterly readiness sessions, partnering closely with sales and revenue leadership on strategy and messaging. Act as the voice of enablement for GTM teams, making sure they have the right information at the right time, through the right channels. Partner closely with Product, Product Marketing, and RevOps to sync launches, messaging, and process changes. - Measure what matters and make enablement a growth driver Define and track KPIs to demonstrate enablement’s impact on sales productivity, pipeline velocity, and deal size. Build a competency scorecard with GTM managers to support coaching and performance management. Use insights from sales calls, Gong data, and product usage to continuously refine your programs. We need to format as

• each bullet? The instruction: Use
  • for any list of duties/requirements/benefits. So each top-level bullet could be a
  • containing sub-bullets? Could nest
    inside
    • . Simpler: make each responsibility as a
    • and include the sub-points as separate sentences within same
    • separated by
      or just sentences. But we need to preserve all detail; we can include line breaks using
      . However using
      • for any list; we can treat each responsibility as a
      • and inside we can have
        for sub-items. That's acceptable. Thus:

        Responsibilities

        • Build onboarding that shortens ramp time and boosts impact
          • Design and deliver world-class onboarding for new GTM team members across Sales, Customer Success, and Solutions Engineering.
          • Track and continuously improve ramp time through tailored strategies and performance feedback loops.
          • Collaborate with leadership to define what “great” looks like across roles and build onboarding paths accordingly.
        ...
        Similarly for Requirements (must-haves): List: - Based in the states where we can currently hire: you are currently located on the East Coast in one of the states where we can hire (Massachusetts, Virginia, New York, New Jersey or Florida). - Sales enablement experience in PLG SaaS: You have 4+ years of enablement experience at fast-growing SaaS companies, ideally building enablement from scratch in a PLG environment. - Deal complexity experience: You've enabled teams selling mid-market to enterprise deals (6 to low-7 figures). - Technical buyer fluency: You understand how to sell to technical personas (CTOs, engineering managers) and can translate that into training that resonates with a technical AE audience. - Learning program design: You’ve built high-quality, scalable training programs tailored to different GTM roles and seniority levels. - Strong communicator: You excel at turning complex technical concepts into clear, compelling, and actionable content for sales teams. - Organized and proactive: You’re structured, self-directed, and take ownership without needing hand-holding. - Customer-first mindset: You focus on enabling the team to better articulate our value and deliver better buyer experiences. We'll put each as
        • . Qualifications (nice-to-haves): - Passion for automation and AI: You’re excited by the space we’re building in — and it shows. - Familiarity with n8n: You’ve used the product (or are eager to start). Benefits list: need to capture all bullet points under Benefits section. Benefits list as given: - Competitive compensation 💸 – We offer fair and attractive pay. - Ownership 💪 – Our core value is to “empower others,” and we mean it—you’ll get a slice of n8n with equity. - Work/life balance 🏖️ – We work hard but ensure you have time to recharge:Europe: 30 days of vacation, plus public holidays wherever you are. US: 20 vacation days, 8 sick days, plus public holidays wherever you are. - Health & wellness 🩺 –Europe: We provide benefits according to local country norms.*US: Multiple low-premium, low-deductible medical plans with coverage for individuals and families—plus a no-cost premium HDHP option with a pre-seeded HSA—along with dental and vision coverage. - Future planning 💰 –Europe: We provide pension contributions according to local country norms.*US: 401(k) retirement