> Markdown version of [/jobs/ext/4620640-senior-software-engineer-nexus-server](https://www.wearedevelopers.com/jobs/ext/4620640-senior-software-engineer-nexus-server). 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).

---

# Senior Software Engineer, Nexus Server

- **Company:** TEMPORAL LLC
- **Location:** San Francisco, CA, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), Code Coverage, Distributed Systems, Cisco Nexus Switches, Open Source Technology, Cloud Services, Multithreading, Git
- **Published:** November 7, 2026
- **Apply:** https://www.juju.com/job/28_25197_21df90b6a6b8ffcfbee695eadb7c1cc6-2308998885

## About the Role

* At least 6 years of experience in a production environment as an "Arranger" and/or "Builder/Enhancer" of highly scalable distributed systems. see HERE for more info re: "Arranger" and/or "Builder/Enhancer"
 * Solid computer science fundamentals in distributed systems concepts including multi-threading and concurrency.
 * 2+ years experience developing customer facing APIs and Frameworks
 * Experience writing concurrent code in production with languages like Go or Java or other applicable languages with skill level as "high end of Intermediate" and/or "Advanced" or "Expert" levels. see HERE for more info re: "high end of Intermediate" and/or "Advanced" or "Expert levels"

## Description

* Provide appropriate test coverage for unit, integration, and performance for your feature ownership area.
 * Clearly document design choices and operational knowledge to successfully deploy and run service with those features.
 * Provide appropriate service level logs and metrics to make features operational for cloud service setup.
 * Provide appropriate alerts, dashboards, and runbooks for production.

What You Won't Do

 * Work in an office (unless you want to, but you'd be by yourself). Temporal is a fully-remote company.
 * Commit code that's poorly-tested or works "most of the time". Temporal aspires to be "Reliable as Gravity", and we expect your code to be the same.
 * Work behind closed doors. The SDKs are open source-that means PRs and comments are open to the public, too. See Temporal Git here.
 * Sit in meetings all day. We mostly communicate in writing, and use meetings mainly for status updates and thorny issues that need input from the whole group.