Senior Sales Enablement Program Manager

We need to output HTML fragment with sections: About the role? Actually we have "About Docker" intro but we should not repeat job title. We need sections: About the role? The posting includes "About Docker" description; we can treat that as "About the role" or maybe "About Docker". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include only sections that have real specific content. We have content: About Docker (company description) - could be "About the role" maybe but it's about company. Could treat as "About the role". We'll include that. Responsibilities: we have a list under "Responsibilities" with sub-bullets. We'll output

• each bullet. Requirements: Not explicitly a separate section; but we have "Qualifications" which includes Required and Strongly Preferred. Could treat "Qualifications" as Requirements? The instruction includes Requirements and Qualifications separate. We have "Qualifications" section with Required and Strongly Preferred. We could map Required to Requirements, Strongly Preferred to Skills? Or we could treat "Qualifications" as Requirements and then "Skills" as Strongly Preferred? The instruction says we can include sections only when posting has real specific content. We have both Required and Strongly Preferred; we could output Requirements (Required) and Skills (Strongly Preferred). Or we could combine into Qualifications. But they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use Requirements for required qualifications, Qualifications for preferred? Actually they differentiate Requirements vs Qualifications vs Skills. Usually Requirements = mandatory, Qualifications = preferred, Skills = specific abilities. We'll allocate: - Requirements: Required qualifications (4+ years experience, technical aptitude, writing skills, video experience, LMS, project management, cross-functional, organization, attention to detail). - Qualifications: Strongly Preferred (experience with technical/platform/security/governance features, Mindtickle, video tools, familiarity with SaaS sales motions, Command of the Message, organizing content libraries, graphic design background, exposure to containerization/DevOps/Docker). - Skills: maybe we could list specific skills like "Technical aptitude", "Writing & editing", "Video production", "LMS course building", "Project management", "Cross-functional collaboration", "Content organization", "Attention to detail". But that overlaps with Requirements. Might be redundant. Better to follow the posting: they have Required and Strongly Preferred. We'll map Required to Requirements, Strongly Preferred to Qualifications, and maybe omit Skills unless we have distinct skills not covered. Could also treat Skills as "Technical aptitude, writing, video, LMS, collaboration, organization". But that would duplicate. Safer to include Skills as a subsection of Qualifications? But instruction says we can include only when posting has real specific content. We have specific content for Skills? Not explicitly a "Skills" heading. Might be better to omit Skills section. Benefits: we have "Perks & Benefits" with list. So we include Benefits section. Pay: we have compensation ranges for Canada and US. So include Pay section. Schedule: we have remote-first, flexibility, etc. That's schedule info. So include Schedule section. We must not include boilerplate like EEO, visa sponsorship, posting information, AI in hiring, interview recordings, etc. Also remove duplicated lines. We must preserve all substantive information. So we need to include all details from About Docker, Responsibilities, Requirements (Required), Qualifications (Strongly Preferred), Benefits, Pay, Schedule. We must not invent or summarize away detail. Must keep specifics like numbers, etc. We need to format as HTML fragment: use

  for each section heading, then content:

  for prose,

  • for lists. We must not repeat job title as heading. The job title is "Senior Sales Enablement Program Manager". Not to be used as heading. We must not put Job ID/requisition numbers as headings. We need to ensure we don't include filler like "commensurate with experience". Not present. Let's extract content. About Docker paragraph(s): "About Docker Docker has been one of the most loved brands in developer tooling, trusted by more than 20 million monthly users and over 20 billion container image pulls. From solo founders to the world's largest companies, developers rely on Docker to build, share, and run their applications across our suite of products including Docker Desktop, Docker Hub, and Docker Scout. We are a globally distributed, remote-first team building the tools that define how software gets built and delivered. As AI agents redefine software development, Docker is at the center of that shift, providing the sandboxed environments, verified images, and secure infrastructure that make autonomous workflows trustworthy by default." We can keep as a single paragraph. Responsibilities: there are subheadings: Content Needs & Requirements, Content Production, Cross-Functional Collaboration, Content Governance & Findability. Each has bullet-like sentences. We'll turn each sentence into
  • . Might need to keep the subheadings? Not required; we can just list items. But we could preserve subheadings as part of li text. Simpler: each bullet as li. Let's list them: - Partner with PMM, Product, Marketing, technical subject matter experts, and GTM leaders to identify content needs and translate them into clear requirements. - Turn input from Sales and cross-functional stakeholders into structured content briefs and production plans. - Prioritize content requests based on business impact, GTM execution needs, and field urgency. - Write, design, and produce enablement content across formats: documents, playbooks, one-pagers, and decks. - Build and maintain courses, quizzes, and certifications for onboarding and ongoing training within Mindtickle. - Develop scripts, storyboards, and recordings for training and demo videos in partnership with subject matter experts. - Partner with our AI Governance (AIG) overlay team to produce enablement content — feature walkthroughs, FAQs, talk tracks, and battle cards — that translates technical AI Governance capabilities into clear, sales-ready value positioning. - Build content that reinforces and extends Docker’s Command of the Message sales methodology, ensuring messaging, positioning, and value language stay consistent across all enablement materials. - Work closely with PMM, Product, Marketing, and technical subject matter experts to ensure content is accurate, timely, and aligned to launches and positioning. - Partner with GTM leaders to make sure training collateral supports GTM execution, effectiveness, and accuracy in the field. - Build a working technical understanding of Docker’s product — including AI Governance and other technical capabilities — directly from teams like AIG, then translate that understanding into content the field can use with confidence. - Serve as a liaison between Sales and Product, Marketing, and PMM to keep content grounded in what the field actually needs. - Own a single source of truth for enablement content, retiring duplicates and outdated material as new content ships. - Organize and tag content so it’s easy to search and find within Mindtickle and other systems, for both Sales and the broader GTM audience. - Maintain a consistent voice, structure, and visual standard across all enablement content. - Use completion data, quiz results, and field feedback to identify what’s working and what needs to be reworked. That's all responsibilities. Requirements (Required): - 4+ years of experience creating content in a sales enablement, marketing, instructional design, or training role, ideally in SaaS. - Strong technical aptitude and curiosity — comfortable building a working understanding of Docker’s product and features (including more technical areas like AI Governance) and translating that understanding into simple, sales-ready value positioning. This role does not require deep engineering expertise, but does require the ability to learn technical concepts and explain them simply. - Strong writing and editing skills, with the ability to turn complex or technical information into clear, engaging content. - Experience producing video content, from scripting through basic editing. - Comfort building courses, assessments, or certifications in an LMS (Mindtickle experience a plus). - Proven ability to manage multiple content projects at once and hit deadlines without sacrificing quality. - Strong cross-functional collaboration skills — you can work with PMM, Product, Marketing, technical subject matter experts, and GTM leaders, and manage competing priorities. - Experience organizing content so it’s easy to search, find, and trust as a single source of truth. - Excellent attention to detail and a strong sense of visual and brand consistency overall. Qualifications (Strongly Preferred): - Experience creating enablement content for technical, platform, or security/governance-related features (e.g., access controls, compliance, or AI governance). - Hands-on experience with Mindtickle or a similar sales enablement/LMS platform. - Experience with video recording/editing tools (e.g., Camtasia, Vidyard, Loom). - Familiarity with SaaS sales motions and Command of the Message or similar frameworks. - Experience organizing content libraries or knowledge bases — tagging, taxonomy, and search — in a CMS or LMS. - Background in graphic design or presentation design. - Exposure to containerization, DevOps tooling, or developer platforms (Docker experience a significant plus). Benefits (Perks & Benefits): - Remote-first by design – Work from your home, with offices in Seattle and Paris for connection and collaboration. - Flexibility that fits your life – We trust you to manage your schedule while delivering great work. - Time to recharge – Generous PTO, designated quarterly Whaleness Days, and a designated end-of-year Whaleness break. - Home office support – Set up your workspace for comfort and success. - Technology stipend – Equivalent to US$100 net per month to help support your work. - Learning & development – Annual stipend for conferences, courses, certifications, and continued learning. - Parental leave – 16 weeks of paid parental leave after six months of employment. - Equity for all full-time employees – Share in Docker's long-term success as we continue to grow. - Comprehensive benefits – Medical, retirement, and paid holidays vary by country. - Docker swag – Because representing the whale never gets old. Pay: - Canada: CA$184,450– CA$263,500 + equity - United States: $133,000 – $190,000 + equity (note there is a typo missing a zero? Actually "$133,000 – $190,00 + equity". We must preserve exactly as posted? It says "$133,000 – $190,00 + equity". Likely missing a zero; but we must not invent or summarize away detail. We should preserve exactly as given: "$133,000 – $190,00 + equity". We'll keep that. Schedule: - Remote-first by design – Work from your home, with offices in Seattle and Paris for connection and collaboration. - Flexibility that fits your life – We trust you to manage your schedule while delivering great work. But note schedule content duplicates benefits; but we can still include schedule items. However we should not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It didn't say to avoid duplication across sections. But we might avoid repeating same sentences in both Benefits and Schedule. However schedule is about remote-first and flexibility; those are also in benefits. Could we keep them only under Schedule and not duplicate in Benefits? But benefits list includes those items; they are substantive. If we remove them from Benefits, we lose info. So we need to keep them somewhere. Could keep them under Benefits and not repeat under Schedule, but then schedule section would be empty or just generic. Better to keep schedule section with those points, and keep benefits section with all points (including those). Duplication is okay as long as we preserve all info. The instruction didn't forbid duplication. We'll include both. Now we need