> Markdown version of [/jobs/ext/1472485-developer-productivity-engineer](https://www.wearedevelopers.com/jobs/ext/1472485-developer-productivity-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Developer Productivity Engineer - **Company:** Together Ai - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Salary:** $180,000.0 - $250,000.0 - **Contract:** Permanent contract - **Skills:** JavaScript (Programming Language), Artificial Intelligence, Automation of Tests, Continuous Integration, Cursor (Graphical User Interface Elements), Software Debugging, Github, Monitoring of Systems, Python (Programming Language), Ansible, Prometheus, Next.js, Software Construction, TypeScript, Pulumi, ReactJS, Grafana, Kubernetes, Production Code, Front End Software Development, Terraform, Golang - **Published:** July 28, 2026 - **Apply:** https://www.dice.com/job-detail/8182e0f5-b9ed-480d-a038-98a658826dfe ## About the Role * 5+ years building software in production, with a strong track record of owning systems or services end to end, from design through operation. * Strong software engineering fundamentals. You write production-quality code and have built and operated real services, not just scripts or test automation. * Proficiency in Python, Go, and JavaScript/TypeScript for tooling, automation, and enablement. * Deep experience with CI/CD systems (GitHub Actions, ArgoCD, GitOps) and building scalable, reusable pipelines. * Experience with containerized development workflows and local dev tooling (e.g., Skaffold). * Experience building starter templates and scaffolding, with engineering teams, to accelerate new service creation. * Hands-on experience with AI coding tools (e.g., Claude Code, Cursor, Copilot) and a habit of using them to move faster and ship more. * A builder's mindset and strong ownership. You like creating the tools and systems other people depend on. * Rigor in diagnosing systemic issues: flaky tests, build latency, deployment failures. Nice to have * Kubernetes expertise (EKS, K3s) and experience optimizing containerized builds. * Infrastructure as Code (Terraform, Ansible, Pulumi). * Front-end tooling familiarity (React, Next.js, Jest) to optimize front-end dev workflows. * Monitoring and observability (Prometheus, Grafana, Honeycomb) to debug bottlenecks. ## Description At Together AI, you'll own the systems and tooling that let our engineers ship quickly and reliably: CI/CD pipelines, release infrastructure, local dev environments, and the testing systems the whole engineering team depends on. This is a high-leverage, build-heavy role. You'll take on big projects and drive them end to end: building a full-stack release service with deployment orchestration, rebuilding the front-end build pipeline, standing up testing infrastructure that kills flaky builds. The goal is straightforward: engineers should spend their time building products, not fighting their tooling. This is an engineering role focused on building systems, not a QA or manual testing role. You build the infrastructure that makes manual effort unnecessary. Responsibilities * Build and own the production systems engineers rely on: release services with deployment orchestration (canary, blue/green), reusable CI/CD pipelines, and self-service tooling. * Build testing infrastructure: the frameworks and harnesses that make tests fast and reliable, and track down flaky tests and slow builds at the systems level. * Build and maintain local dev environments and containerized workflows so engineers can spin up and iterate fast. * Create starter templates and shared tooling (CLIs, codegen, IDE integrations) so teams can stand up new services in minutes. * Be the go-to engineer for GitHub Actions and GitOps: defining problems, untangling pipeline issues, and improving how the org works with them. * Improve front-end build tooling and developer workflows alongside product engineers. * Work across the org to find the biggest sources of friction and fix them at the root. Document what you build so others can use it. ## Related Videos - [Developer Experience in the Age of AI](https://www.wearedevelopers.com/videos/1118-developer-experience-in-the-age-of-ai) - [Innovating Developer Tools with AI: Insights from GitHub Next](https://www.wearedevelopers.com/videos/1268-innovating-developer-tools-with-ai-insights-from-github-next) - [Why segmenting your infrastructure into tiers makes your infrastructure design better](https://www.wearedevelopers.com/videos/1960-why-segmenting-your-infrastructure-into-tiers-makes-your-infrastructure-design-better) - [Go with the Flow: Stop the Leaks Before Your Memory's a Waterfall!](https://www.wearedevelopers.com/videos/100073-go-with-the-flow-stop-the-leaks-before-your-memory-s-a-waterfall) - [Engineering Productivity: Cutting Through the AI Noise](https://www.wearedevelopers.com/videos/1691-engineering-productivity-cutting-through-the-ai-noise) - [Bringing AI Model Testing and Prompt Management to Your Codebase with GitHub Models](https://www.wearedevelopers.com/videos/1536-bringing-ai-model-testing-and-prompt-management-to-your-codebase-with-github-models) ## Related Articles - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Transforming Software Development: The Role of AI and Developer Tools](https://www.wearedevelopers.com/magazine/527-transforming-software-development-the-role-of-ai-and-developer-tools) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)