Senior Software Engineer, Temporal

• BS or MS in Computer Science (or a closely-related degree), or equivalent work experience writing production-grade software
• Fluency in multiple programming languages, and an affinity for learning new ones. We don’t care which, but you should know at least two
• Familiarity with concurrent programming—you should know how to use mutexes and atomics safely
• Familiarity with distributed systems—you should know what to do when you can’t rely on mutexes and atomics
• Experience designing APIs and writing documentation for publicly-available libraries or modules
• A methodical, detail-oriented approach to your work
• Strong technical communication skills—written and verbal—in English
• A deep sense of ownership and personal accountability—you care about the impact of your work, and if something goes wrong, you take responsibility for making it right
• A proactive approach to managing your work—you’ll need to balance working autonomously vs. working closely with others, and recognize when you need help

Desirable

• We have an opening on our SDK team to hire a Senior Software Engineer to help us build a great experience for developers of Temporal-based applications
• Our SDK team makes the Temporal SDKs and the Temporal CLI—the primary ways through which our customers use Temporal
• This is harder than it sounds—SDKs are not mere clients; they act as runtime environments for application code, and coordinate closely with Temporal Server to provide the durable-execution guarantees our customers require
• Take end-to-end ownership of new features, working with others in the SDK and Server teams to deliver exceptional reliability and a great developer experience
• Design and build Temporal SDKs used by customers to work with Temporal in their programming language of choice
• Tightly integrate Temporal SDKs with their respective languages to run application code in a durable, deterministic way
• Maintain and improve the Temporal CLI
• Work directly with our community to debug issues that need expert attention, and get feedback on Temporal SDK features and APIs
• Write publicly-readable technical documentation describing Temporal concepts and APIs
• Go the extra mile to support a customer in need, on the rare occasion that SDK engineering expertise is needed
• Travel to meet your coworkers in meatspace for a week once or twice a year
• Attend the occasional developer conference to talk about how great Temporal is (optional)
• Hours between timezones UTC -7 through UTC -4