Sr. Engineering Manager

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.

A Little About Us

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.

A Lot About You

We’re hiring an Sr. Engineering Manager to lead a 2-pizza team responsible for two company-critical platform initiatives to be completed in 2026:

CI/CD modernization: migrate ~30,000 pipelines to GitHub Actions, and ensure all new repos/apps default to GitHub Actions with the right governance, templates, and paved paths

Artifact platform modernization: migrate our on‑prem JFrog stack to JFrog Cloud with changes that are as fast and transparent as possible for development teams

We’re moving to a product-first model: clear “golden paths,” measurable DX outcomes, service ownership, and continuous evolution. This team will own Artifactory as a long-term product/service, not a one-time project.

This role has no expectation of hands-on coding but you are technically fluent enough to guide architecture, drive crisp execution, and make tradeoffs with Infrastructure and Security partners.

What you’ll do

Lead the team and build a product-first platform culture

• Lead, coach, and grow the across CI/CD platform work, automation, governance, and artifact management

• Establish a product operating model: customer discovery with internal dev teams, roadmap prioritization, success metrics, and ongoing iteration.

• Create a high-ownership culture with strong engineering fundamentals: reliability, observability, testing, rollout discipline, and crisp incident learnings.

Own the GitHub Actions migration program

• Deliver a migration plan that can succeed at scale (~30,000 pipelines) with multiple execution modes depending on repo needs

• Build a “migration factory” operating model: segmentation, throughput targets, exception handling queues, escalation paths, and rollbacks

• Ensure all new repos/apps start on GitHub Actions via strong “paved roads”

Drive an AI/agentic automation strategy to reduce toil and accelerate outcomes

• Lead delivery of agentic AI automation that can generate, migrate, validate, and maintain CI/CD workflows at scale.

• Define quality and safety guardrails for AI-driven changes: staged rollouts, test/CI validation gates, policy checks, regression suites, and human-in-the-loop escalation for edge cases.

• Make the system measurable: track automation success rates, defect leakage, rollback rates, and the “exception profile” over time to drive continuous improvement.

Own Artifactory as a long-term service

• Lead the end-to-end migration from a single on‑prem instance (with homegrown caching layers) to JFrog Cloud

• Simplify and standardize the artifact platform experience

• Own the service “day 2”: SLIs/SLOs, incident response posture, capacity planning, lifecycle management, and ongoing product evolution.

Define governance and integrations across the CI/CD + artifact ecosystem

• Partner with Security to implement pragmatic controls without blocking developer velocity

• Own cost outcomes for SaaS

What success looks like

• 100% pipeline migration by end of year, with clear burn-down reporting and minimal disruption to app teams

• All new repos/apps on GitHub Actions by default using ap