Customer Value Program Director, GCCS

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. We need to parse the posting. Company Overview: description of Docusign. Could be "About the role"? Actually "Company Overview" is about the company, not role. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have sections: - Company Overview (maybe "About the role"? Not exactly. Could be "About the role" but we have company overview. Might treat as "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect only those headings. So we should map content to those headings as appropriate. We have: - What you'll do (Responsibilities) - Responsibility (list of responsibilities) (maybe duplicate) - Job Designation Remote (maybe Schedule? Actually schedule is about remote work? Could be Schedule? Not exactly. Could be "Job Designation" maybe not needed. Could be omitted if not matching headings. - What you bring (Basic ... Preferred ...) (Requirements, Qualifications, Skills) - Wage Transparency Pay (Pay) - Benefits (Benefits) - Work Authorization Notice (maybe not needed) - Life at Docusign (maybe not needed) - Accommodation (maybe not needed) - Applicant and Candidate Privacy Notice (not needed) - States Not Eligible for Employment (maybe not needed) - Equal Opportunity Employer (boilerplate to remove) - EEO Know Your Rights poster = Remote (boilerplate) We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we keep substantive content: Company Overview, What you'll do, Responsibility (maybe combine), What you bring (basic and preferred), Pay, Benefits. Also maybe Job Designation Remote could be considered Schedule? But schedule is about work hours; remote designation is location. Could treat as "Schedule" maybe not. The instruction: include a section ONLY when posting has real, specific content for it. So we need to see if there is specific content for Schedule. The posting mentions "Job Designation Remote: Employee is not required to be in or near an office frequently and works from a designated remote work location for the majority of the time." That's about work location, not schedule. Could be considered under "Schedule"? Not really. Probably we should not create a Schedule section because it's not about schedule (hours). So we omit Schedule. Similarly, we might not have a separate "Qualifications" vs "Requirements" vs "Skills". We need to decide how to split. The posting has "What you bring" with Basic and Preferred experience. Could map Basic to Requirements/Qualifications, Preferred to Skills? Or we could combine into Requirements and Skills. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive information. So we need to include details from Company Overview, Responsibilities, Requirements (basic), Preferred (maybe Skills), Pay, Benefits. We must not invent or summarize away detail. So we need to keep the exact sentences? We can rephrase but must preserve meaning. Safer to keep the original text but maybe break into

and

• . Use

  for prose,

  • for lists. We need to avoid duplication: there is "What you'll do" and then "Responsibility" with similar content. We should combine them into a single Responsibilities section, preserving all points without duplication. Let's extract responsibilities from both sections. First "What you'll do" paragraph: "As the Customer Value Program Director, GCCS, you will provide the connective tissue across GCCS's strategic portfolio, translating leadership priorities into coordinated execution across regions, people, processes, systems, and cross-functional partners. You will lead governance, integrated planning, communications, change management, adoption, and executive visibility for focused CVRP initiatives and other high-priority GCCS programs. You will anticipate dependencies, clarify ownership and decision paths, reduce duplication, and help the organization move from strategy to measurable field execution. This role will be in very close cooperation with the GCCS Operations leadership team. This position is an individual contributor role reporting to the GVP, Global Commercial Customer Success." Then "Responsibility" list (looks like a paragraph with sentences separated by line breaks? Actually it's a block of sentences each starting with a verb). Let's extract each bullet: - Assist the GVP Global Commercial Customer Success to drive and execute a comprehensive program that ensures milestones, manages cross-functional dependencies and risks, and measures and impacts cross region and cross segment IAM adoption - Translate GCCS leadership priorities into integrated plans, milestones, accountable owners, decision paths, and measurable outcomes across CVRP and other strategic initiatives - Lead end-to-end delivery of global and regional programs, driving high-impact alignment across teams, processes, systems, and cross-functional partners from strategy through implementation, adoption, and continuous optimization to maximize customer satisfaction and company success - Establish program governance, including charters, operating cadences, decision rights, RACI models, decision logs, stage gates, escalation paths, ELT updates, and clear forums for decision-making - Track dependencies, risks, issues, decisions, resource needs, and program health; anticipate interdependencies and provide concise executive reporting on progress and required actions - Develop and execute change-management strategies covering stakeholder impact, readiness, communications, manager enablement, training, resistance management, adoption, and reinforcement - Coordinate GCCS, Customer Success Operations, GTM Strategy and Operations, Finance, Enablement, Sales, Renewals, Product, Marketing, Data/Analytics, HR, and regional teams to align priorities and maintain accountability - Improve processes and workflows by identifying root causes, removing systemic barriers, reducing duplicated effort and competing processes, and supporting scalable multi-system execution - Drive consistent launch readiness, field execution, post-launch retrospectives, feedback loops, and continuous improvement across strategic initiatives - Drive and guide the strategy part of regional and global QBR preparations for all GCCS functions (CSAM, SCM, SH) We need to avoid duplication with earlier paragraph. The earlier paragraph includes similar points: provide connective tissue, translate leadership priorities, lead governance, integrated planning, communications, change management, adoption, executive visibility, anticipate dependencies, clarify ownership, reduce duplication, move from strategy to measurable field execution, close cooperation with GCCS Ops leadership, individual contributor reporting to GVP. We can combine but ensure we don't repeat same info. We'll produce a cohesive list that captures all unique points. Now Requirements (Basic) list: - 12+ years of experience in program management or change management supporting Customer Success, Services, Education, Operations, or other customer-facing functions - Experience leading complex, ambitious global and multicultural programs while driving alignment across multiple regions, functions, and diverse stakeholder groups - Experience translating leadership priorities into integrated plans, governance, operating cadences, and accountable execution - Experience supporting software process optimization, cross-functional deployments, operating-model changes, or complex implementations - Experience managing scope, milestones, dependencies, risks, issues, governance, and executive communications while using data to guide decisions - Experience influencing teams without direct authority, with a bachelor's degree or equivalent experience Preferred experience list: - Experience supporting GCCS, Commercial/SMB Customer Success, Scaled Customer Management, or Success Hub operating models - Experience managing strategic initiatives such as CVRP, adoption, retention, renewal, or IAM-conversion programs - Experience developing change impact assessments, readiness plans, manager toolkits, communications cascades, training plans, and adoption strategies - Experience defining ambitious program goals, MVPs or MVDs, success measures, executive reporting, and operating cadences across multiple initiatives to achieve challenging outcomes that elevate overall customer satisfaction and business growth - Experience developing lifecycle, digital, self-service, or one-to-many programs that support customer activation, adoption, retention, or expansion - Experience leading organizational change, process redesign, operating-model transformation, or multi-system execution - Experience evaluating and adopting AI capabilities, automation, or modern operating tools, with strong technical aptitude and ability to solve multi-step operational challenges - Experience with program-management and collaboration tools such as Jira, Smartsheet, Confluence, Tableau, or SQL; ability to synthesize complex information for senior leaders and operate effectively in ambiguity We could map Basic to Requirements/Qualifications, Preferred to Skills. Or we could have Requirements (basic) and Skills (preferred). Qualifications maybe similar to Requirements. We'll decide: Use Requirements for basic, Skills for preferred. Qualifications maybe omitted or combine with Requirements. To avoid thin sections, we could combine Requirements and Qualifications into one section? But instruction says use headings for those categories; we can include both if we have content. We have content for both basic and preferred; we could put basic under Requirements, preferred under Skills, and maybe Qualifications omitted (or combine with Requirements). However we need to avoid filler. We'll include Requirements and Skills. Now Pay: we have wage transparency details with ranges per location. Must keep all specifics. We'll put under

    Pay

    and then maybe a

    with the ranges. Could also use

    • for each location list. We'll preserve the exact numbers. Benefits: we have bullet list of benefits. We'll put under

      Benefits

      and
      • . Now Company Overview: maybe under

        About the role

        ? But it's about company. Could treat as "About the role" but it's not exactly role. However we need a heading for company overview; maybe we can use "About the role" to include company overview as context. The instruction says use

        for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings but suggests those are typical. We'll include About the role with company overview. Now we need to ensure we don't include boilerplate like Work Authorization Notice, Life at Docusign, Accommodation, Privacy, States Not Eligible, EEO, etc. Also remove duplicated lines: we have "What you'll do" and "Responsibility" which we combined. Now produce HTML fragment. Structure:

        About the role

        Company overview paragraph.

        Responsibilities

        • ... each bullet

        Requirements

        • ... basic experience bullets

        Skills

        • ... preferred experience bullets

        Pay

        Wage transparency details: list each location range.

        Benefits

        • ... benefits bullets
        We must not include Schedule section. Check for any other substantive content: Job Designation Remote maybe could be considered under "About the role" as note about remote work. Could incorporate into About the role paragraph: mention that the role is remote. But we might drop it if not needed. However it's substantive about work location. Could add a sentence in About the role: "This position is designated as Remote, meaning the employee works primarily from a designated remote work location." That preserves info. We need to ensure we don't miss any other substantive content like "This Role Is Also Eligible For The Following Bonus: ..." That's part of Pay/Bonus/Stock. We should include that under Pay as well. The posting includes: "This Role Is Also Eligible For The Following Bonus: Sales personnel are eligible for variable incentive pay dependent on their