Nscale · posted · checked
Developer Experience Engineer-AI Infrastructure Operations
JiraKubernetesLinuxPython$100k – $170kOn-site · New York, San Francisco and Seattle
Who can apply
On-site · New York, San Francisco and Seattle
Location: Houston; New York; San Francisco; Seattle
.
Developer Experience Engineer
Houston; San Francisco; Seattle; New York
About Nscale
Nscale is the GPU cloud built for AI. We run high-performance, cost-efficient infrastructure for AI-native startups and global enterprises, from bare metal up through the platform services teams actually build on. Our culture runs on ownership, accountability, and speed. We move with urgency, we tell each other the truth, and everyone here stays close to the infrastructure that makes AI work.
The Role
This is a career-level engineering role for someone who wants to own the path from commit to production. You'll take real surface area: the CI/CD, GitOps, and change automation that Nscale's engineers use every day to ship. Internal developers are your customers, and you'll be expected to make their route to production faster, safer, and less manual over time.
What You'll Do
Build and own the tooling that carries code from pull request to production, including GitHub Actions workflows, runners, and Argo CD and Flux deployment pipelines.
Own the build and release layer: build tooling, remote caching, container image builds, base images, the artifact registry, and release versioning and promotion, so builds are fast, reproducible, and cheap to run.
Own local and ephemeral test environments, including LocalStack, so engineers can test against cloud APIs on a laptop or in CI before anything reaches a shared environment.
Automate change management: connect git, CI, and deploy events to Jira Service Management so change records, risk tiers, and approvals are created and updated without manual ticket work.
Define and maintain SLOs, SLIs, and dashboards for the delivery platform (CI queue time, build duration, deploy success rate, rollback time, GitOps sync latency) so developers can see its health at a glance.
Treat developer toil as a bug. Find the slow, manual, or error-prone steps between a merge and a running service, and remove them with code.