Docusign is looking to hire a Lead Product Manager who will own the product strategy for a unified engineering metrics platform that answers the critical question: Is Al adoption actually improving developer productivity? Build a single source of truth connecting Al tool usage, code metrics, deployment velocity, incident management, and code review data. Work with engineering leaders to define what productivity means for your organization, measure it rigorously, and inform Al investment decisions with evidence instead of intuition. This position is an individual contributor role reporting to the Sr. Director, Technology & Business Operations. Responsibility Design and own a system that integrates data from multiple sources (source control, CI/CD, code review platforms, incident management, Al tools) into a single, queryable destination Ensure the platform is flexible enough to support metric exploration and iteration-not locked into a specific metric definition upfront Work with engineering leaders to define what productivity means for your organization Conduct interviews and surveys to understand how developers and leaders think about productivity Establish baseline measurements before Al adoption Identify leading and lagging indicators. Test hypotheses. Iterate on metric definitions based on feedback and validation Build visibility into the total cost of Al adoption (direct and indirect) Create mechanisms to compare productivity changes against cost Identify which cohorts, tools, and use cases show highest ROI vs. low/negative ROI. Surface early warning signals (adoption flat-lining, cost rising without productivity gains, developer dissatisfaction) Develop decision frameworks for go/no-go tool adoption and resource allocation Work with engineering leaders to align on what productivity means and which metrics matter Design dashboards for different audiences (leaders, teams, individuals, executives) Build feedback loops to refine metrics based on usage and impact. Surface actionable insights that drive decisions about tooling, process, and budgets Build organizational capability and knowledge around Al adoption Develop and share best practices for Al tool usage, prompt engineering, code review of Al-generated code, security considerations, and ethical use Create learning resources (guides, training, case studies) that help developers use Al effectively Facilitate knowledge sharing across teams about what’s working and what isn’t Help the organization move from “we have Al tools” to “we know how to use them well” Validate assumptions about Al impact through ongoing feedback and data Identify when metrics aren’t capturing real productivity shifts or business impact Demonstrate willingness to pivot measurement approach Conduct regular quarterly reviews to compare cost and productivity trends, and identify divergences and adjust strategy