• Lead a team building the inner dev loop. Own the end-to-end experience from laptop-in-box to first pull request: workstation imaging and configuration, privilege and access workflows, enterprise connectivity, developer tooling, and the AI-powered development environment that ties it all together. • Turn "weeks to onboard" into "ready in an hour." The benchmark is real: a developer receives their machine, opens it, and is writing code for their team within their first hour. Your team designs and builds the systems that make that possible at enterprise scale. • Make agentic development tools a first-class citizen. AI coding tools aren't a plugin someone installs later—they're part of the standard environment your team ships. You also ensure developers actually know how to use them well: the workflows, the review patterns, the practices that separate real productivity gains from novelty. • Lead by building. This is not a program management role. You write code, review code, and architect solutions alongside your team. Your credibility comes from what you ship. • Engage deeply with program teams. Your team's work only succeeds if it fits how real engineering teams operate. You stay connected to 3–5 active programs, understand their constraints, and bring those lessons back to improve what you're building. • Drive measurable impact. Success shows up in the metrics: onboarding time collapses, developer satisfaction improves, AI tool adoption climbs, and teams spend less time wrestling with their environment and more time delivering mission software. • Stay ahead of the curve. Continuously evaluate emerging tools and practices—in workstation management, developer environments, and agentic development—and incorporate what's worth adopting into the enterprise standard.