Senior Developer Experience Engineer-AI Infrastructure Operations

Nscale•Houston, NY

About The Position

Nscale is hiring a senior engineering leader to own and shape the developer delivery platform used across the company. The role is accountable for how software moves from pull request to production, including the GitHub, GitOps, build, release, and change automation systems on which engineers depend. The successful candidate will set the platform roadmap and technical direction, define secure and consistent delivery standards, and measure success by how quickly and safely internal developers can ship.

Requirements

6–10 years of experience in platform engineering, SRE, DevOps, or software engineering, including ownership of CI/CD or deployment systems used by multiple engineering teams.
Strong software engineering skills in Python, Go, or a similar language, with experience building tools adopted by other engineers.
Deep experience with GitHub at organization scale, including Actions, self-hosted runners, rulesets, permissions, and governance.
Experience with GitOps tools such as Argo CD and/or Flux on Kubernetes.
Experience automating change management or release approvals with a ticketing system; Jira Service Management is preferred, and sound judgment balancing compliance and developer speed.
Strong command of Kubernetes, Linux, networking, and distributed systems.
Experience with secrets and identity in pipelines, such as Vault, short-lived credentials, or OIDC, as well as artifact and supply-chain management.
Experience owning a build and release system at scale, including performance, reproducibility, cache strategy, release versioning and promotion, runner fleet capacity and cost, and artifact registry design.
Experience designing and operating an internal developer platform, including a developer portal such as Backstage or similar, and driving adoption across engineering teams.
Experience establishing reliability practices, including SLOs, observability and alerting, incident processes, and sustainable on-call practices.
A track record of treating developers as customers through surveys, adoption metrics, documentation, and retiring tools that are no longer useful.
A track record of serving as a trusted senior voice in design reviews and incidents, including making decisions under pressure.
A habit of helping colleagues develop and succeed.
Participation in an on-call rotation for the delivery platform.

Nice To Haves

Experience with local cloud emulation, such as LocalStack, and ephemeral or preview environments.
Experience with policy as code, such as OPA or Kyverno, Terraform automation, and software supply-chain practices such as SBOMs and image signing.
Experience with AI or GPU workloads, high-performance computing, or bare-metal environments.

Responsibilities

Own the delivery platform end to end, set its roadmap, and guide its technical direction.
Define golden paths, repository and workflow templates, release conventions, and deployment standards.
Own the internal developer portal, including its service catalog, software templates, documentation, and adoption and ownership data.
Set technical direction for GitOps across Argo CD and Flux, including multi-cluster promotion and drift detection.
Own build and release systems, including build tooling, remote caching, container image builds, base images, artifact registry, release versioning, and promotion.
Own local and ephemeral test environments, including LocalStack, for testing against cloud APIs on laptops and in CI.
Design and lead change-management automation into Jira Service Management, integrating evidence, risk tiering, and approvals into the pipeline.
Set delivery-platform SLOs and SLIs and use adoption data and developer feedback to guide improvements.
Mentor engineers through design reviews, pairing, and incident debriefs, and uphold quality and maintainability.
Participate early in cross-engineering design reviews and architecture decisions to incorporate deployability, rollback, and change requirements.
Lead difficult delivery-platform incidents, identify root causes, and implement changes to prevent recurrence.
Influence teams to adopt shared tooling by earning trust, retiring legacy approaches, and demonstrating results.
Help shape the delivery-platform on-call rotation and make it lighter over time.