> Markdown version of [/jobs/ext/3389878-software-engineer-developer-experience-full-stack](https://www.wearedevelopers.com/jobs/ext/3389878-software-engineer-developer-experience-full-stack). 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). --- # Software Engineer, Developer Experience (Full-Stack) - **Company:** Superhuman LLC - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Salary:** $200,000.0 - $300,000.0 - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Amazon Web Services, Microsoft Azure, Cloud Computing, Continuous Integration, Python (Programming Language), Software Engineering, TypeScript, Cloud Platform System, Backend, Kubernetes, Build Tools, Front End Software Development, Golang, Programming Languages, Microservices - **Published:** September 8, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=51cb9ea0af0aad56 ## About the Role We're looking for a full-stack Software Engineer to join our Developer Experience team and help build the next generation of engineering velocity inside Superhuman Docs. The ideal candidate is energized by making other engineers faster and happier, brings strong communication and product sense alongside their engineering skills, and thrives across a broad, fast-moving stack. This is a high-autonomy, high-impact role on a foundational team that moves fast from idea to production., * Has a minimum of 5 years of experience in software engineering, with meaningful full-stack exposure across both front-end and back-end development. (We're hiring across a range-some roles may lean more front-end and others more back-end, with back-end depth especially valuable for core tooling work.) * Is comfortable in more than one programming language and picks up new ones quickly-we care far more that you know at least two languages well (e.g., Go, Python, Java, TypeScript) than about any specific one. * Has hands-on experience with CI/CD systems, build tooling, and developer workflow automation. * Has experience with large-scale build systems such as Bazel-or a very similar system used at large engineering organizations * Is comfortable with cloud-native environments (AWS, Azure, or GCP) and containerized workflows such as Kubernetes. * Is comfortable working across hybrid architectures that mix a monolith with microservices, and with high-volume, complex release processes. * Has strong empathy and communication skills-this role is half conversation, acting as a spokesperson and trusted partner to both engineers and business-unit leaders. * Is genuinely motivated by improving how other engineers work, rather than by shipping product features-and enjoys continuously learning across a broad and evolving technology stack. * Embodies our EAGER values-is ethical, adaptable, gritty, empathetic, and remarkable. ## Description * Serve as the embedded Developer Experience partner and spokesperson for the Docs business unit-implementing what the central platform team builds within the BU's context, resolving issues autonomously where you can, and aligning with the central team where you can't. * Bridge the gap between engineers and business-unit leads, turning day-to-day developer friction and leadership priorities into a clear, prioritized DevX roadmap. * Build full-stack internal tooling and self-service platforms-front-end interfaces and back-end services alike-tailored to how the Docs team actually works. * Improve the release process and own and enhance CI/CD pipelines and deployment tooling so that shipping code is a safe, fast, and boring event, even at a high release cadence. * Streamline the inner loop of local development across a hybrid monolith-and-microservices codebase: fast local environments, quick feedback, and reliable, low-flake test suites. * Work hands-on with build systems (such as Bazel or equivalents) and containerized, cloud-native infrastructure (Kubernetes) to make builds and pipelines faster and more reliable. * Create and maintain codebase-specific golden paths, templates, and documentation that make the right way to build the easy way to build. * Define and track both org-wide developer-productivity metrics and Docs-specific metrics-and use data to validate the impact of every change you ship.