# Senior Developer Experience Engineer-AI Infrastructure Operations at Nscale > United States · Senior · DevOps / SRE / Infra · open. Source: https://alderhq.app/jobs/greenhouse%3Anscaleoperationsukltd%3A5026694101 (read 2026-11-11). ## Facts (observed) - Company: [Nscale](https://alderhq.app/companies/nscale) - Location text: Houston; New York; San Francisco; Seattle; Houston; New York; San Francisco; Seattle - Where it can be done from (inferred): United States (evidence: "Location: Houston; New York; San Francisco; Seattle; Houston; New York; San Francisco; Sea") - Posted: 2026-11-03 (8 days ago) - First seen by alder: 2026-11-07 · last verified: 2026-11-11 - Reposted: 0 times · edited: 0 times - Apply on the employer's site: https://job-boards.eu.greenhouse.io/nscaleoperationsukltd/jobs/5026694101 - Skills listed (inferred): Python, Go, Kubernetes, Docker, Distributed systems ## Pay and sponsorship - Posted pay: not posted - Market band for similar posted roles (Houston, n 6): p25 $106k, median $191k, p75 $238k ## Description (the employer's text) ### Senior 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 senior engineering role for someone who sets the bar for how Nscale ships software and then pulls the rest of the team up to it. You'll own the hardest problems on the delivery platform: the GitHub, GitOps, and change automation every engineer depends on, and the design decisions that decide whether it holds up as the company grows. Your customers are internal developers, and the measure of the job is how quickly and safely they get to production. ### What You'll Do - Own the delivery platform end to end, from pull request to production. Set the roadmap and the direction, not just respond to what breaks or what gets requested. - Define the paved road: golden paths, repo and workflow templates, release conventions, and deployment standards that make the safe way to ship also the easy way. - Own the internal developer portal (Backstage or equivalent) as the front door to the paved road: the service catalog, software templates, and docs, with adoption and ownership data to show it is used. - Set the technical direction for GitOps across Argo CD and Flux, including multi-cluster promotion, drift detection, and a clear position on when to use which. - Own the build and release layer and its performance: 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. - Design and lead change management automation into Jira Service Management, working with Security, audit, and engineering leadership so that evidence, risk tiering, and approvals come from the pipeline instead of from manual tickets. - Set the SLOs and SLIs for the delivery platform (lead time, deploy success rate, CI queue time, rollback time) and use adoption and developer feedback data to decide what to build next. - Grow the team, not just the systems. Mentor engineers through design review, pairing, and incident debriefs, and hold the bar for quality and maintainability. - Get in early on design reviews and architecture decisions across Engineering, so deployability, rollback, and change requirements are built in from the start. - Lead the hardest delivery platform incidents and the root causes nobody else can crack, and turn each one into a change that keeps it from coming back. - Influence without authority. Bring other teams onto shared tooling by earning their trust, retiring the old way, and showing the numbers. ### What You'll Bring - 6-10 years in platform engineering, SRE, DevOps, or software engineering, with real ownership of CI/CD or deployment systems used by many engineering teams. - Strong software engineering skills (Python, Go, or similar). You build tools other engineers adopt, not scripts that run once and rot. - Deep experience with GitHub at organization scale (Actions, self-hosted runners, rulesets, permissions and governance) and with GitOps tooling (Argo CD, Flux, or both) on Kubernetes. - Experience automating change management or release approval against a ticketing system, ideally Jira Service Management, and the judgment to balance compliance needs against developer speed. - Solid command of Kubernetes, Linux, networking, and distributed systems, with the sense to know where the real failure modes hide. - Experience with secrets and identity in pipelines (Vault, short-lived credentials, OIDC) and with artifact and supply chain management. --- Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/greenhouse%3Anscaleoperationsukltd%3A5026694101 and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.