Customer Value Program Director, GCCS

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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 section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have sections: - Company Overview: description of Docusign. Could go under "About the role"? Actually "About the role" is about the role, not company. But we could treat "Company Overview" as "About the role"? Might be better to put under "About the role" a brief description of the role? The posting includes "What you'll do" which is responsibilities. Also "Job Designation Remote". Also "What you bring" which is requirements/qualifications/skills. Also "Wage Transparency Pay". Also "Benefits". Also "Work Authorization Notice". Also "Life at Docusign". Also "Accommodation". Also "Applicant and Candidate Privacy Notice". Also "States Not Eligible for Employment". Also "Equal Opportunity Employer". Also "EEO Know Your Rights poster = Remote". Many of these are boilerplate to remove. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove sections like Work Authorization Notice, Life at Docusign, Accommodation, Applicant and Candidate Privacy Notice, States Not Eligible for Employment, Equal Opportunity Employer, EEO Know Your Rights poster. Also maybe "Job Designation Remote" is relevant? It describes remote designation; could be part of "Schedule"? Actually schedule is about work schedule (full-time, part-time, remote?). Could be considered schedule info. But we should only include if posting actually states them. It does state "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 schedule/location info. Could be placed under "Schedule". However schedule heading expects maybe work schedule (full-time, part-time, shift). But we can include remote work info under Schedule. We also have "What you'll do" which is responsibilities. We have "Responsibility" (maybe a typo) with bullet points. We have "What you bring" which includes basic and preferred experience, etc. That can be split into Requirements, Qualifications, Skills. But we need to preserve all substantive info; we can't invent or summarize away detail. We need to keep the details as they are, but we can group them under appropriate headings. However we must not create headings with filler text. So we need to ensure each heading has real specific content. We have pay details: Wage Transparency Pay with ranges per location. That's specific content for Pay. We have Benefits: list of benefits (Paid Time Off, Paid Parental Leave, Full Health Benefits Plans, Retirement Plans, Learning and Development, Compassionate Care Leave). That's specific content for Benefits. We have "Job Designation Remote" which could be Schedule. We have "Company Overview" which could be About the role? Actually About the role could be a brief description of the role's purpose. The posting includes "As the Customer Value Program Director, GCCS, you will provide the connective tissue across GCCS's strategic portfolio..." That's more responsibilities. But we could put a short summary under About the role: maybe the first paragraph after Company Overview? Actually the posting starts with Company Overview then "What you'll do". There's no explicit "About the role". But we could treat the first paragraph after Company Overview as "About the role": "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." That is basically role description. So we can put that under About the role. Responsibilities: The bullet list under "Responsibility". We'll put that under Responsibilities. Requirements: Basic qualifications from "What you bring" Basic bullet points. Qualifications: Preferred qualifications from "What you bring" Preferred bullet points. Skills: Could be extracted from both basic and preferred? But we already have basic and preferred; maybe we can combine skills under Skills heading, but we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Skills could be merged into Requirements/Qualifications. But we need to include Skills heading only if there is real specific content for it. The posting does not have a separate "Skills" section; skills are embedded in requirements. So we might omit Skills heading to avoid thin section. However we need to preserve all substantive info; we can keep the skill details under Requirements and Qualifications. That's fine. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to format: - Use

for section headings. - Use

• for any list of duties/requirements/benefits. - Use

  for prose. We must not repeat the job title as a heading. The job title is "Customer Value Program Director, GCCS". Not used as heading. We must not put Job ID/requisition numbers as headings. We must preserve ALL substantive information; do NOT invent or summarize away detail. Thus we need to copy the text exactly as given, but we can format into HTML. We need to be careful not to lose any detail. Let's extract each piece. Company Overview paragraph: "Docusign brings agreements to life. Over 1.5 million customers and more than a billion people in over 180 countries use Docusign solutions to accelerate the process of doing business and simplify people’s lives. With intelligent agreement management, Docusign unleashes business-critical data that is trapped inside of documents. Until now, these were disconnected from business systems of record, costing businesses time, money, and opportunity. Using Docusign’s Intelligent Agreement Management platform, companies can create, commit, and manage agreements with solutions created by the #1 company in e-signature and contract lifecycle management (CLM)." We could place this under About the role? Actually About the role should be role description, not company overview. But we have no separate company overview heading allowed. However we could include company overview as part of About the role? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It does not forbid adding other headings, but says "include a section ONLY when the posting has real, specific content for it". It gives examples but not exclusive list. So we could add a heading like "Company Overview" if we want, but the examples list only those. Safer to stick to those headings. But we need to preserve all substantive info; if we omit company overview, we lose that info. However we could incorporate it into About the role as a preamble: "About the role" could include both role description and company overview? But that might be mixing. However the instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the suggested headings, but we could also use others if needed. However they say "Prefer a few substantive sections over many thin ones." So maybe we can include Company Overview as a section heading (not in the list) but it's still a heading. The instruction does not forbid other headings; it just gives examples. So we could add a heading for Company Overview. But we need to decide. Better to follow the examples: include only those headings if they have content. If we omit Company Overview, we lose that info. But maybe we can put company overview under About the role as a brief description of the role's context? The About the role heading could contain both company overview and role description. That would preserve info. Let's do that: Under About the role, we can have a paragraph that includes the company overview and then the role description. That would be substantive. Thus About the role content: combine company overview paragraph + the role description paragraph (starting with "As the Customer Value Program Director..."). Now Responsibilities: the bullet list under "Responsibility". 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 preserve exactly as written, including punctuation. Now Requirements: Basic bullet points from "What you bring" Basic: - 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 Now Qualifications: Preferred bullet points: - 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