thenewyorktimes

Senior Software Engineer, CI/CD

Apply Now

At a Glance

Location
New York, United States
Work Regime
hybrid
Experience
5+ years
Posted
2026-06-30T16:44:09-04:00

Key Requirements

Required Skills

AWSCI/CDGCPJavaKubernetesNode.jsPythonTerraformTypeScript

Domain Knowledge

  • Engineering
  • Finance
  • Medical

Requirements

designing, building, and operating CI/CD and software delivery systems (for example, GitHub Actions, Argo CD, or equivalent) with clear impact on how teams ship software

Proficiency in at least one general‑purpose programming language such as Go, Python, TypeScript/Node.js, or Java, including

with containers and Kubernetes; package‑management tools such as Helm; infrastructure‑as‑code tools such as Terraform; GitOps‑based deployment workflows; and cloud platforms such as AWS or GCP

Hands‑on experience with GenAI‑assisted developer tools (for example, Cursor, Copilot, or Claude Code) and passion in applying them to delivery workflows, from test generation to background agents running in CI/CD

Experience collaborating with cross‑functional partners (Product, platform, and product engineering teams) to design delivery workflows, communicate trade‑offs, and

adoption of shared platforms

Responsibilities

The Developer Platforms organization provides foundational platforms and tooling to 100+ teams and 750+ engineers through an internal developer platform.

Our Application Delivery team owns the shared software delivery platform (CI/CD, artifact management) and deployment workflows used by hundreds of engineers across News, Cooking, Games and Audio to ship software.

As NYT leans into AI‑assisted development and agentic workflows, Application Delivery is where those changes become real: pipelines, deployment strategies, and guardrails that turn AI‑generated changes into safe, observable releases at scale.

As a Senior Software Engineer on Application Delivery,

build and evolve the delivery platform that every product and platform team relies on.

Your work will shape how code flows from GitHub into production, how we keep deployments boring (in a good way), and how agentic workflows run through CI/CD.