We are looking for a Staff Engineer with 9-12 years of experience to lead the technical direction of our Developer Productivity platform. You will own the architecture of our CI/CD systems, Kubernetes-based developer environments, and self-service platform — while driving the strategy for modernizing legacy Jenkins infrastructure without disrupting hundreds of engineers.

You are someone who has built developer platforms at scale, understands the full software delivery lifecycle deeply, and knows how to measure and improve developer productivity with rigor and empathy.

What You Will Do

• Own architecture and roadmap for CI/CD platform, developer environments, and self-service tooling
• Lead the Jenkins modernization strategy — defining migration patterns, shared libraries, and the path to modern CI without big-bang rewrites
• Design and build Kubernetes-native developer environments — ephemeral namespaces, DevSpaces, inner-loop / outer-loop parity
• Build a self-service platform that enables developers to provision environments, run pipelines, and deploy services without platform team intervention
• Define and track developer productivity metrics — DORA metrics, pipeline efficiency, environment provisioning time, developer NPS
• Drive platform reliability — SLOs for CI/CD systems, on-call practices, and incident response for developer tooling
• Mentor senior engineers and set technical direction for the team

Must Have

CI/CD & Release Engineering

• 7+ years hands-on with CI/CD systems — deep expertise in GitHub Actions, GitLab CI, or Tekton at the shared infrastructure level, and Jenkins at scale (shared libraries, distributed agents, plugin management, and migration patterns)
• Experience optimizing pipeline performance — distributed caching, test parallelism, incremental builds, and artifact reuse — and strong understanding of release engineering practices including progressive delivery patterns (feature flags, canary, blue-green, automated rollback)

Kubernetes & Developer Environments

• Deep hands-on with Kubernetes in production — operators, admission webhooks, RBAC, multi-tenancy, and resource management
• Experience with Kubernetes-based developer environments — DevSpaces, Telepresence, vcluster, or ephemeral namespace provisioning — and designing environment parity strategies across dev, staging, and production

Developer Self-Service & IDP

• Hands-on experience building or operating Internal Developer Platforms — Backstage, Port, or custom self-service portals — with golden path templates and PR-based workflow automation
• Platform-as-a-product mindset — treating developers as customers, defining and tracking productivity metrics (DORA, SPACE), and iterating based on adoption data

Cloud & Infrastructure

• Hands-on with at least one of AWS, GCP, or Azure — and experience with multi-cluster Kubernetes management (ArgoCD ApplicationSets, Flux) and cost optimization for CI/CD infrastructure

Observability & Legacy Modernization

• Experience building pipeline observability — build trends, flaky test dashboards, deployment frequency, and MTTR — and proven ability to migrate large engineering organizations off Jenkins while keeping existing infrastructure running

AI-Augmented Engineering

• Uses AI coding assistants — Claude, Cursor, Copilot — daily for CI/CD scaffolding, script generation, documentation, and productivity bottleneck analysis
• Evaluates and recommends AI-powered developer tools for team adoption; actively uses AI to automate repetitive tasks — flaky test triage, dependency upgrades, lint rules — while applying judgment for security-sensitive or high-blast-radius changes

Good to Have

• Familiarity with platform engineering maturity models — measuring and evolving platform capability over time
• Open-source contributions to CI/CD or developer tooling projects

What Success Looks Like

• 3 months: Architecture understood, Jenkins modernization strategy drafted, first platform improvement shipped
• 6 months: Self-service platform significantly improved, DORA metrics baselined and tracked, mentoring 2–3 engineers
• 12 months: Jenkins migration underway with clear milestones, developer productivity measurably improved, platform recognized as a force multiplier