Principal Engineer, DevEx

It takes powerful technology to connect our brands and partners with an audience of hundreds of millions of people. Whether you're looking to write mobile app code, engineer the servers behind our massive ad tech stacks, or develop algorithms to help us process trillions of data points a day, what you do here will have a huge impact on our business—and the world.

We are a high-impact team within the CTO organization, dedicated to accelerating outcomes for internal development teams. We own the entire CI/CD and artifact ecosystem, leading the platform work, automation, governance, and long-term service ownership. Our mission is centered on critical platform modernization and moving to a product-first operating model that emphasizes clear "golden paths," measurable Developer Experience (DX) outcomes, and continuous evolution.

To achieve this, we champion a high-ownership culture with strong engineering fundamentals (reliability, observability, testing), drive an AI/agentic automation strategy to reduce toil at scale, and define governance in partnership with Security to ensure developer velocity.

We're hiring a Principal Developer Experience Engineer to lead the modernization of the CI/CD portion of our internal developer platform. The immediate focus is a high-scale migration: moving ~30,000 pipelines to Git Hub Actions, with a target of 100% migration by end of year and ensuring that all new repos/apps start on Git Hub Actions by default.

• Design an agentic AI automation that can translate and migrate pipelines to Git Hub Actions workflows
• Automate PR creation and iteration
• Build "safe at scale" operations: migration batching, progress tracking, exception queues, rollback strategies, and clear ownership boundaries.
• Establish evaluation/quality loops for the agent: regression tests, correctness checks, policy checks, and measurable success criteria (not just "it looks right").

• Define governance for Git Hub Actions at enterprise/org scale
• Build and maintain reusable workflows

• Establish best practices for Artifactory repository structure and operations
• Standardize how CI publishes and consumes artifacts with secure defaults and consistent metadata
• Maintain conventions that scale (including repository naming/constraints and guardrails)

• Define when to use Git Hub-hosted vs self-hosted runners and document the default paths
• Help design runner governance and access boundaries using runner groups (runner groups create a security boundary and control access)
• Partner with infra/security where ownership sits elsewhere, but be accountable for the end-to-end developer experience

• Enable app teams through office hours, migration support, design-partner engagements, and iterative improvements to reduce friction
• Treat CI/CD as a product: measure adoption, reliability, and developer satisfaction - and iterate based on data

• 100% of Screwdriver pipelines migrated to Git Hub Actions by end of year, with transparent burn-down tracking and a stable landing zone
• All new repos/apps start on Git Hub Actions using approved templates and reusable workflows
• Clearly defined governance for allowed actions/workflows, plus scalable guardrails and upgrade paths
• Consistent Artifactory usage for containers + npm (publish/consume patterns, permissions, retention), reducing break/fix and "tribal knowledge"
• Tangible DX improvements: faster time-to-green, fewer flaky failures, fewer support tickets, and predictable CI costs

• Practical experience building LLM/agentic AI systems where correctness, guardrails, and evaluation matter (not just ad-hoc prompting)
• Senior-level experience building production-quality systems, platform tooling, or internal developer platforms
• Deep CI/CD expertise: pipeline design, troubleshooting, reliability improvements,…