Lead Technical Program Manager

We need to output HTML fragment with sections: About the role? The posting includes "Company Overview", "What you'll do", "Responsibility", "Job Designation", "What you bring", "Wage Transparency", "Benefits", "Life at Docusign", "Accommodation", etc. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must include a section only when posting has real, specific content for it. We must not emit heading with filler like "commensurate with experience". We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Accommodation" maybe not needed? It's not in the list of allowed headings but we could still include if content? 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, but likely we should stick to those categories. However we need to include all substantive info. We can map content to these sections. We have: - Company Overview: could be "About the role"? Actually "About the role" is typical. But we have company overview separate. Could put under "About the role" maybe combine. - What you'll do: could be "Responsibilities". - Responsibility: duplicate of responsibilities. - Job Designation: could be "Schedule"? Actually schedule is about hybrid remote. Could be "Schedule" (Hybrid: 2 days per week). So we can put schedule. - What you bring: could be "Requirements" or "Qualifications" and "Skills". We need to separate basic and preferred. - Wage Transparency: "Pay". - Benefits: "Benefits". - Life at Docusign: maybe not needed but could be omitted as filler? It's somewhat promotional but still substantive. Might be considered boilerplate? It's not EEO but it's culture. Might keep as a section? Not in list but could be omitted to keep to allowed sections. However we must preserve ALL substantive information; we cannot drop culture description if it's substantive. But we could incorporate into "About the role" maybe. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine culture into About the role. - Accommodation: maybe not needed; could be omitted as it's procedural. - Applicant and Candidate Privacy Notice, States Not Eligible for Employment, Equal Opportunity Employer: these are boilerplate EEO etc. Should be removed. Thus we produce sections:

About the role

with company overview and maybe life at Docusign.

Responsibilities

with what you'll do and responsibility details (deduplicate).

Requirements

with basic qualifications.

Preferred Qualifications

with preferred experience.

Skills

maybe combine some skills from what you bring (like mentoring, communication, etc.) but we could also put under Requirements. But we need to avoid thin sections. Could combine Requirements and Skills into one "Requirements" section that includes both basic and preferred and skills. But we have separate headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Requirements for basic qualifications, Qualifications for preferred, Skills for abilities like mentoring, communication, etc. Benefits, Pay, Schedule. Let's extract content. Company Overview: "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)." Life at Docusign: "Working here Docusign is committed to building trust and making the world more agreeable for our employees, customers and the communities in which we live and work. You can count on us to listen, be honest, and try our best to do what’s right, every day. At Docusign, everything is equal. We each have a responsibility to ensure every team member has an equal opportunity to succeed, to be heard, to exchange ideas openly, to build lasting relationships, and to do the work of their life. Best of all, you will be able to feel deep pride in the work you do, because your contribution helps us make the world better than we found it. And for that, you’ll be loved by us, our customers, and the world in which we live." We can combine. Responsibilities: The bullet list under "What you'll do" and "Responsibility". Need to deduplicate repeated sentences. Let's capture unique responsibilities: - Lead the development, deployment, adoption, and continuous improvement of cross-functional processes that enable Product, Engineering, Technical Operations, Finance, Compliance, and go-to-market teams to operate effectively at scale. - Serve as a strategic partner to functional and technical leaders, translating business and technology objectives into scalable operating models, workflows, governance mechanisms, tools, documentation, and measurable outcomes. - Lead complex initiatives from current-state assessment through future-state design, deployment, adoption, stabilization, and continuous improvement. - Function as a central program leader for complex, cross-functional technical programs spanning multiple engineering teams, product areas, business functions, and geographies. - Manage integrated plans, dependencies, risks, stakeholder alignment, and readiness while ensuring that new processes and capabilities are operationally ready and sustained over time. - Lead the end-to-end development and deployment of cross-functional processes, including current-state assessment, future-state design, stakeholder alignment, workflow definition, tooling requirements, documentation, training, communications, rollout, adoption, and post-deployment stabilization. - Partner with Product, Engineering, Technical Operations, Finance, Compliance, Legal, and go-to-market stakeholders to identify operational gaps and design processes that improve execution quality, speed, accountability, scalability, and compliance. - Establish process ownership, decision rights, roles and responsibilities, inputs, outputs, controls, service-level expectations, escalation paths, and success measures. - Develop repeatable operating models, playbooks, templates, workflows, governance routines, and reporting mechanisms that enable consistent execution across teams, pillars, and geographies. - Support the development, deployment, and continuous improvement of the SW capitalization process, including process definition, stakeholder alignment, roles and responsibilities, workflow and tooling requirements, documentation, training, governance, compliance controls, and adoption measurement. - Lead change management for moderate- to high-complexity initiatives affecting multiple teams, pillars, systems, or operating processes. - Define KPIs and leading indicators to measure process performance, adoption, compliance, cycle time, quality, and business impact. - Serve as the central point of contact for cross-pillar coordination, requiring frequent and strategic engagement with Pillar TPMs, Engineering Managers, Product leaders, Finance, Compliance, and other functional partners. - Define the end-to-end program structure; identify participating pillars and teams; and map cross-functional dependencies, decision points, readiness criteria, and adoption milestones. - Own integrated plans that include milestones for design, validation, pilot execution, readiness, rollout, adoption, stabilization, and continuous improvement. - Manage risks proactively by anticipating critical-path issues, adoption challenges, control gaps, and dependency-related delays, and by surfacing options to mitigate them. - Drive completion of process deployments and technical programs on schedule and within budget constraints. - Partner with go-to-market and enablement teams to define communications, training, rollout, and support plans for impacted stakeholders. - Communicate proactively on status, schedules, dependencies, issues, risks, adoption, and business impact to stakeholders, including senior and executive management. - Establish governance across initiatives, including operating cadences, decision forums, escalation paths, reporting structures, KPIs, and executive-level dashboards. - Mentor and coach Pillar TPMs and junior TPgMs; share frameworks, tools, and learnings to elevate the broader Technical Program Management function. - Manage programs and process deployments across disciplines, time zones, and geographies. We can keep as a list

• . Requirements (basic): "Basic 12+ years of experience leading complex, cross-functional programs, operational transformations, or process deployments in SaaS or technology organizationsExperience operating as a system-level or cross-functional Technical Program Manager, owning integrated plans and managing dependencies across multiple engineering teams, product areas, and business functionsExperience designing, deploying, scaling, and continuously improving enterprise processes across multiple teams and geographiesExperience in change-management, including stakeholder analysis, impact assessment, communications, training, readiness, adoption measurement, and reinforcementExperience understanding complex system architectures, data flows, technical trade-offs, and workflow or tooling requirementsExperience engaging meaningfully with engineers and technical leaders without being a hands-on software engineerExperience using enterprise collaboration, workflow, project-management, and reporting tools, including Atlassian tools such as Jira, Confluence, and Portfolio or Advanced ReportingB.S. degree in Computer Science, Business, Engineering, Finance, or a related comparable field of study" We need to split into readable sentences. We'll produce
  • each. Preferred Qualifications: list items. - Experience leading software capitalization, technology-finance, engineering operations, audit-readiness, or comparable technology-related business processes - Familiarity with process controls, policy implementation, compliance requirements, evidence collection, and audit support - Experience applying structured change-management frameworks in a product-development, engineering, finance, or enterprise-operations environment - Experience leading process pilots, phased rollouts, organizational adoption, and post-deployment stabilization - Experience integrating new processes with enterprise systems, workflow platforms, reporting tools, and systems of record - Equally confident working with executive team members and software developers - Ability to distill complex and nuanced business, technical, financial, and process requirements into clear concepts for diverse internal partners - Skilled at dealing with ambiguity and influencing without direct authority in a rapidly growing and changing environment - Experience in a company that has scaled, or experience working across both small and large-scale software development organizations - Strong business acumen and technical background, with the ability to quickly understand and communicate technical concepts, operational challenges, and business impact - Demonstrated experience mentoring or coaching junior TPgMs and contributing to team-wide program management frameworks - Experience defining and using process-performance metrics, adoption measures, operational dashboards, and continuous-improvement mechanisms - Strong written, verbal, facilitation, presentation, and executive communication skills Skills: maybe we can extract some skill items from above like mentoring, communication, etc. But we already have many in preferred. Could create Skills section for abilities like mentoring, communication, influencing, etc. But to avoid duplication, maybe we put skills under Requirements and Preferred. However we need to include a Skills section if we have content. Could list skills like: Mentoring and coaching, Stakeholder analysis, Change management, Process design, Risk management, KPI definition, Governance establishment, Cross-functional coordination, etc. But many are already in responsibilities. Might be redundant. Given instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications and Skills into one "Requirements" section that includes basic, preferred, and skills. But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using all, but we should avoid thin sections. We could still include all if they have substantive content. Let's see if each will have substantive content. - About the role: