Manager, Global Sales Commissions

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

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Let's extract sections: - Intro about Couchbase: description of company. Could be "About the role"? Actually "About the role" is typical heading for role description. The intro before "Manager, Global Sales Commissions" includes company description. That could be considered "About the role" or maybe "About Couchbase". But we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: Job title: Manager, Global Sales Commissions (not to be repeated as heading) Location: Raleigh, NC (hybrid, 3 days/week in office) Reports To: Director of Global Payroll & Equity Then description: "As the Manager, Global Sales Commissions, you will lead, modernize, and scale the administration of our global sales compensation program...." That's role overview. Could go under "About the role". Then "What You'll Do" with subsections: Strategy & Process Transformation, Operations & Execution, Systems & Analytics, Leadership & Collaboration. Those are responsibilities. So we can put under

Responsibilities

and then maybe

• for each bullet? The content includes paragraphs with bold headings. We need to preserve all substantive info; we can convert each bullet into
• items, maybe grouping. We have "What You'll Bring" with Minimum Qualifications and Preferred Qualifications, plus Education. That's qualifications/requirements/skills. We need to separate: Requirements (maybe minimum qualifications), Qualifications (preferred?), Skills (technical). The instructions: Use headings for Requirements, Qualifications, Skills. We need to decide mapping. We have: Minimum Qualifications: - Experience: 8+ years... - Transformation Track Record... - People Management... - Stakeholder Alignment... - Technical & Analytical Mastery... Preferred Qualifications: - Systems Expertise... - Agility & Precision... - Executive Communication... - Professional Skills... - Education: Bachelor’s degree... Thus we could put Minimum Qualifications under

  Requirements

  , Preferred Qualifications under

  Qualifications

  , and maybe Skills under

  Skills

  (but we already have technical & analytical mastery etc). However we might combine. But we must not create sections with filler. We have real content for Requirements, Qualifications, Skills. So we can include all three. Pay: The posting includes "Base Pay Range $140,000—$148,000 USD". Also mentions bonus, commissions, other benefits. So we have Pay section. Benefits: There's a "Why Couchbase? Benefits" section describing benefits. So we include Benefits. Schedule: The posting includes location hybrid 3 days/week in office. That's schedule info. So we can include Schedule. We must not repeat job title as heading. Also not include Job ID/requisition numbers. We need to remove boilerplate: EEO statements, diversity encouragement, accommodation note, etc. Also remove "Learn More About Couchbase News and Press Releases..." etc. Also remove "Visit couchbase.com and follow us on LinkedIn and X." etc. Also remove "Want to be part of our story? Apply today!" etc. We need to preserve all substantive information: company description? Might be considered part of About the role? The intro about Couchbase is generic company description; maybe we should keep it as part of About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the company description as part of About the role? It's not about the role but about the company. However we only have allowed headings; we could put it under About the role as a paragraph describing the role context. It's substantive. Thus About the role section will contain: company description plus the role overview paragraph. Let's extract company description paragraph(s): "Couchbase, the operational data platform for AI, empowers businesses to succeed by bringing data to life in new ways. Major market-leading companies rely on Couchbase for mission critical operational, analytical, mobile and AI workloads. Built to replace legacy infrastructure and fragmented data services, Couchbase empowers enterprises with a unified platform architected for performance, flexibility and global scale. With Couchbase, organizations bring their data to life, launching game‑changing customer experiences, exploring the limitless potential of AI, and seamlessly extending applications from the cloud to the edge and beyond. Couchbase’s AI‑ready technology and enterprise partnership model eliminate complexity and reduce total cost of ownership, enabling teams to stay agile, innovative and secure. Couchbase believes data should never slow you down, but act as the foundation for your next breakthrough. Discover why Couchbase is trusted to help the world’s biggest players scale, move fast and stay resilient, no matter what’s next on their roadmap. Visit couchbase.com and follow us on LinkedIn and X." We need to remove the "Visit couchbase.com and follow us on LinkedIn and X." as it's navigation/link? It's maybe considered boilerplate? It's a call to action but not part of role. Might be considered navigation? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Visit couchbase.com..." is not exactly navigation but could be considered promotional. Might be okay to keep? It's not about the role. Safer to remove it as it's not substantive to the role. Also "Want to be part of our story? Apply today!" is application instruction, remove. Thus About the role will include the company description up to before "Visit couchbase.com..." maybe we keep until "roadmap." Then we add role overview. Role overview paragraph: "As the Manager, Global Sales Commissions, you will lead, modernize, and scale the administration of our global sales compensation program. In this pivotal position, you will drive strategic process transformation—establishing robust, automated, and efficient commission workflows from the ground up to support our rapidly growing organization. You will serve as a primary strategic partner across Sales, RevOps, FP&A, Accounting, Payroll, and IT to ensure commission plans are administered accurately, complex adjustments are handled swiftly, and payments are delivered seamlessly. If you are a collaborative leader who thrives in a dynamic environment and excels at navigating financially and operationally critical decisions, we invite you to make a lasting impact with our team." We keep that. Now Responsibilities: We need to capture all bullet points under "What You'll Do". The headings inside are bold: Strategy & Process Transformation, Operations & Execution, Systems & Analytics, Leadership & Collaboration. Under each there are sub-bullets. We need to preserve all substantive info; we can flatten into
• items, maybe each sub-bullet as
• . Let's extract: Strategy & Process Transformation: - Modernize & Scale: Drive continuous process improvement and operational change to elevate commission administration from legacy methods into a streamlined, highly automated, and scalable global model. - Policy & Frameworks: Draft, establish, and maintain comprehensive commission-related policy and procedure documentation. Operations & Execution: - End-to-End Execution: Oversee the end-to-end administration of global sales compensation plans with meticulous attention to detail, maintaining 100% payout accuracy and on-time distribution. - Agile Adjustments: Rapidly process plan modifications, crediting adjustments, compensation exceptions, and mid-year plan updates with high precision. - Governance & Audit: Ensure all variable pay operations strictly adhere to internal standards; execute daily financial controls and serve as the primary operational liaison for external audit requests. Systems & Analytics: - Software Management: Supervise and optimize our commission software environment (Xactly), partnering with internal IT and external consultants to implement new functionality, updates, and custom rules. - Reporting & Insights: Build monthly/quarterly reporting, prepare commission and sales incentive payment summaries, execute what-if financial scenario analyses, and deliver plan effectiveness insights to executive leadership. Leadership & Collaboration: - Team Leadership: Directly manage, coach, and performance-manage a dedicated team of Commission Analysts based in Bangalore, India, alongside external implementation consultants. - Cross-Functional Alignment: Partner seamlessly across RevOps, Sales Leadership, FP&A, Accounting, Payroll, and IT to align compensation strategies, financial impacts, data pipelines, and system integrations. - Enablement & Support: Develop commission communication materials and train members of Sales and Field Operations; serve as a diplomatic point of contact for resolving complex plan questions, payment inquiries, and escalations. We'll put each as
• . Now Requirements (Minimum Qualifications): - Experience: 8+ years of progressive experience in sales compensation management, sales finance, or financial analytics, with a proven track record leading global commission operations. - Transformation Track Record: Demonstrated success building, standardizing, or transforming commission operations and driving adoption across matrixed teams. - People Management: Prior success managing direct reports, offshore teams (specifically in India), and external advisory resources. - Stakeholder Alignment: Proven ability to manage and align a wide array of senior stakeholders across Sales, RevOps, Finance, Payroll, Accounting, and IT. - Technical & Analytical Mastery: Expert-level capability in Microsoft Excel and experience analyzing complex, multi-tiered payout structures. Now Qualifications (Preferred Qualifications): - Systems Expertise: Hands-on proficiency with Xactly or similar enterprise commissions tools. - Agility & Precision: High degree of agility with the ability to execute fast turnaround times on plan adjustments without sacrificing precision. - Executive Communication: Strong business acumen with the ability to translate technical compensation data into actionable executive presentations and strategic recommendations. - Professional Skills: Exceptional communication, analytical, strategic thinking, and interpersonal skills; highly motivated, detail-oriented, and adaptable in a fast-paced environment. - Education: Bachelor’s degree in Finance, Accounting, Business Administration, or a related field. Now Skills: We might not have a separate skills section beyond what's already covered. Could we create Skills from technical & analytical mastery etc? But we already have those under Requirements and Qualifications. The instruction: Use headings for Skills if posting has real specific content. The posting does not have a separate "Skills" section; but we could treat technical & analytical mastery as skills. However we already used them. To avoid duplication, maybe we omit Skills section if no distinct content. But we need to decide: The instruction says "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one? But we have separate headings allowed. We could put Requirements (minimum) and Qualifications (preferred) and maybe Skills not needed. However we must include sections only when posting has real specific content for it. Does posting have specific content for Skills? It mentions "Technical & Analytical Mastery: Expert-level capability in Microsoft Excel and experience analyzing complex, multi-tiered payout structures." That's a skill. Also "Systems Expertise: Hands-on proficiency with Xactly or similar enterprise commissions tools." That's also skill. Could be considered skills. But we already placed them under Requirements/Qualifications. To avoid missing content, we could create a Skills section that includes those skill-based items, but then we would duplicate content. The instruction says preserve ALL substantive information; not duplicate? It didn't forbid duplication but said remove duplicated lines. Duplicating content would be duplication. So better not to duplicate. So we can assign the skill items to either Requirements or Qualifications. Since we already have Requirements (minimum) and Qualifications (preferred), we can keep them there and omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now Benefits: Extract from "Why Couchbase? Benefits