Senior Manager, Business Systems

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Docker" repeated twice, then "We're looking for a Senior Manager, Business Systems...". The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include: About the role (maybe we can use "About the role" heading for description of role). The posting includes "We're looking for a Senior Manager, Business Systems..." which is about the role. Could be "About the role". Then "Responsibilities" (list). Then "Qualifications" (list). Then maybe "Nice to Have" could be part of Qualifications or separate "Preferred Qualifications". But instructions only list certain headings; we can still use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. Could also use "Skills" maybe for technical skills. But we have Qualifications and Nice to Have. Could combine Qualifications and Nice to Have under Qualifications? Might be better to have Qualifications (required) and then maybe a separate "Preferred Qualifications" but not in list; but we could still use "Qualifications" for required and maybe "Preferred Qualifications" as a subsection? However instructions: "Prefer a few substantive sections over many thin ones." So maybe combine required and nice-to-have into one Qualifications section, with sub-lists? But we must preserve all substantive info; we can include both required and nice-to-have as separate

under same heading. Also "Benefits" section: there is a "Perks & Benefits" section with details. So we should include Benefits heading. "Pay" section: there is "Compensation & Equity" with salary ranges for Canada and US. So we should include Pay heading. "Schedule": not mentioned; remote-first, flexibility, but no explicit schedule. Probably we should not create Schedule section because no explicit schedule info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we have Pay and Benefits, but not Schedule. We also have "About Docker" description; maybe that is not needed as a section because it's company overview, not role. Could be omitted? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid company overview. But we could include an "About the role" section that includes the description of the role and maybe company overview? However "About the role" likely should contain description of the role and maybe team. The posting includes "We're looking for a Senior Manager, Business Systems to lead our Salesforce development and administration team..." That's role description. Could also include the earlier "About Docker" as company overview but not required. Might be okay to include under "About the role" as a brief intro. We must remove duplicated lines: The "About Docker" appears twice identical; we should keep only one copy. Also remove boilerplate like "Posting Information", "Open vacancy:", "AI in hiring:", "Interview recordings:", etc. Also remove EEO statement at end. Also remove "Docker does not offer visa sponsorship for this role." That's substantive? It's a note about visa sponsorship; maybe we should keep it as part of role details? It's not a heading; could be placed in a paragraph under About the role or maybe as a note. It's substantive info; we should preserve. It's not boilerplate; it's a specific condition. So keep. Also "Compensation & Equity Canada: CA$177,800 – CA$254,000 + equity United States: $128,100 – $183,000 + equity". Keep. Now structure:

About the role

We're looking for a Senior Manager, Business Systems to lead our Salesforce development and administration team and drive the architecture, roadmap, and day-to-day operational health of our Salesforce instance. This is a hands-on technical management role: you'll manage a team of Salesforce developers and administrators, stay close to code and configuration, and also own a small set of adjacent RevOps tools that round out the GTM systems stack. You'll report to the Director, Business Systems and partner closely with Sales, Operations, Marketing, Customer Success, Finance, and Security leadership. Docker does not offer visa sponsorship for this role.

Maybe also include brief company overview? Could add a sentence about Docker being globally distributed remote-first team etc. But that is from About Docker; we could incorporate but not required. Might be okay to include as part of About the role: "Docker is a globally distributed, remote-first team building the tools that define how software gets built and delivered..." but that's more company. Might be okay. But we need to preserve ALL substantive information; we should not omit the About Docker description. It's substantive about company. Should we include it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. Could be in a separate section like "About Docker" but not a standard heading; but we could still use

About Docker

though not in the list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. It likely expects us to use those headings where applicable, but we could also use other headings if needed? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the expected headings; we should stick to them. However we need to include company overview; maybe we can fold it into About the role section as a brief intro. That would preserve the info (though not verbatim). But we must not summarize away detail; we can include the sentences verbatim within the paragraph. That's okay: we are not summarizing, we are just including them. So we can copy the About Docker paragraph into the About the role section. Thus About the role paragraph will contain both the role description and the company overview. Now Responsibilities: we need to extract the list of responsibilities from the posting. The responsibilities are a long paragraph with many items separated by line breaks? Actually they are a list of responsibilities each starting with a verb and separated by line breaks? In the text they appear as a continuous paragraph with line breaks? Let's extract each bullet: - Manage and grow a team of Salesforce developers and administrators, including hiring, performance management, career development, and day-to-day prioritization of their work - Own the Salesforce platform roadmap across Sales Cloud, Service Cloud, CPQ, and integrated third-party systems, balancing production support, technical debt reduction, and net-new delivery - Stay hands-on with architecture and code review for Apex, Lightning Web Components (LWC), Flow automation, and platform security, guiding your team's technical decisions rather than delegating them entirely - Own the Salesforce DevOps and release management lifecycle: Gearset administration, source control, testing frameworks, CI/CD pipelines, deployment governance, and production change management, including planning around end-of-quarter production freezes - Pair heavily with the Technical Architect to execute against their architectural roadmap, with dotted-line accountability for delivering their priorities through your team while retaining direct management authority over your reports - Maintain governance over Salesforce data architecture, security model, sharing rules, profiles, permission sets, and integration/service account hygiene across connected systems - Own or co-own supporting integrations between Salesforce and platforms - Own a set of adjacent RevOps tools outside Salesforce (e.g., Gearset, Gong, Loom) and coordinate with other owners - Manage Agentforce, Slackbot, AI skills, and other AI-driven Salesforce offerings, and evaluate new AI-driven workflow opportunities on the platform - Partner with GTM stakeholders to gather requirements and translate business needs into technical solutions delivered by your team - Set team standards for documentation, testing, and change management, and enforce operating rules for high-risk changes (e.g., Closed/Won opportunity edits, ownership changes) to protect data integrity and downstream automation - Escalate and resolve complex production issues, serving as the team's senior technical point of contact We need to put these in

• . Now Qualifications: required qualifications list: - 5+ years total hands-on Salesforce development experience in enterprise environments and people management - Deep expertise with Apex, Lightning Web Components (LWC), SOQL/SOSL, Salesforce APIs, Flow automation, and platform security - Experience with Salesforce CPQ and billing systems - Experience with RevOps or quote-to-cash processes - Strong understanding of Salesforce DevOps and CI/CD practices (Gearset or similar) - Experience working in high-growth SaaS or technology companies, ideally supporting a globally distributed GTM organization - Strong analytical, communication, and problem-solving skills; comfortable balancing people management with hands-on technical work Nice to Have: - Salesforce Platform Developer I or II, or Salesforce Administrator certification - Familiarity with NetSuite and quote-to-cash business processes and Mulesoft - Familiarity with data warehousing, analytics, or AI-driven workflows - Experience supporting global sales organizations We could combine them under Qualifications heading, maybe separate subheadings? But we cannot add extra headings beyond the allowed? Could still use

  maybe but not instructed. Safer to just list all items under Qualifications, maybe with a note "Nice to have" as part of items? But we need to preserve distinction. Could add a comment inside

  like "(Nice to have)" but that's altering. Better to keep two separate lists under same heading: maybe a

  saying "Required qualifications:" then

  , then another

  saying "Nice to have:" then

  . That preserves info without extra headings. Now Benefits: from Perks & Benefits section: - 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. We need to put these in
  • . Now Pay: compensation details: - Canada: CA$177,800 – CA$254,000 + equity - United States: $128,100