Lead Release Engineering, Agentic Platform

Lead Member of Technical Staff, Release Engineering, Agentic Platform (Java / Node.js / iOS)

We're hiring an LMTS Release Engineer to lead release management across our Java backend services, Node.js platform layer, and iOS client apps. This is not a traditional CI/CD role, and it is not a hands‑off architect role either. As an LMTS, you'll set the technical direction for how we ship software in the agentic era (where AI agents author code, open PRs, run validation suites, and propose merges autonomously) and you'll build the critical pieces yourself.

You're the senior technical voice on release strategy, the person other engineers elevate to, and the one designing the trust layer that lets us safely ship code authored by humans and agents alike.

• Release strategy across three runtimes. Java (Maven/Gradle, JVM services), Node.js (npm/pnpm, microservices and tooling), and iOS (Xcode, fastlane, App Store Connect, Test Flight). Define one coherent release story across all three and lead its execution.

• Agentic release pipelines. Architect and build the infrastructure that lets AI coding agents propose, validate, and ship changes safely: automated diff review, policy‑as‑code merge gates, signed‑commit attestations, and human‑in‑the‑loop approvals at the right friction points. You own this design end‑to‑end.

• Release automation and tooling. Git Hub Actions / Jenkins / Buildkite pipelines, artifact registries (Artifactory, npm registry, internal Cocoa Pods/SPM mirrors), code signing for iOS, reproducible builds, SBOM generation.

• Branching, versioning, and cut strategy. Trunk‑based development, semantic versioning, release trains, hotfix paths. Define what "ready to release" means for each runtime and enforce it.

• Observability and rollback. Deployment dashboards, canary/progressive rollout for backend, phased iOS rollouts, fast rollback. Mean‑time‑to‑recovery is a metric you own.

• Compliance and supply chain. SLSA‑aligned build provenance, dependency vulnerability gating, secret scanning, license compliance — especially important when agents commit code.

• Technical leadership. Mentor MTS and SMTS engineers on release engineering practices, set the bar for design reviews in this domain, and represent release engineering in cross‑org architecture forums. Influence direction without needing positional authority.

• 8+ years in release engineering, build engineering, or developer infrastructure, with demonstrated technical leadership on a platform‑scale system.

• Hands‑on release experience with at least two of: JVM ecosystem (Maven/Gradle, Spring Boot, JAR/WAR publishing), Node.js ecosystem (npm/pnpm/yarn, monorepos, package publishing), or iOS (Xcode build settings, code signing, provisioning profiles, App Store submission, Test Flight). Working knowledge of the third.

• Deep CI/CD platform expertise — Git Hub Actions, Jenkins, Buildkite, CircleCI, or similar. You can debug a flaky pipeline by reading logs, not by retrying.

• Strong scripting (Bash, Python, or Type Script) and infrastructure‑as‑code (Terraform, Pulumi).

• Deep Git internals — rebases, bisects, signed commits, hooks, monorepo workflows.

• Track record of designing merge policies, branch protection, and release governance for orgs of 100+ engineers.

• Experience leading cross‑team technical initiatives end‑to‑end (from design through rollout) and driving alignment across engineering, security, and product.

• Direct experience integrating AI coding agents (Claude Code, Cursor, Copilot Workspace, Devin, internal agent frameworks) into a development workflow, or a clear, opinionated point of view on how that integration should work.

• Familiarity with policy‑as‑code (OPA, Conftest), attestation frameworks (Sigstore, in‑toto, SLSA), and supply‑chain security tooling.

• Experience running iOS releases at scale: provisioning automation, certificate rotation, App Store review handling, staged rollouts, crash‑rate gating.

• Background in incident response and on‑call leadership.

• Prior experience as the senior‑most engineer in a release/build org, setting technical direction across multiple teams.