Staff Software Engineer, Cloud Data Storage

<div class="content-intro"><h3><strong>About Us</strong></h3> <div>Temporal is an open source programming model that can simplify code, make applications more reliable, and help developers focus on the important things like delivering features faster. We are on a mission to be the reliable foundation of every developer’s toolbox, and are building the team that will make that happen.</div> <div> </div> <div>Our values guide us —they are present in how we show up, make decisions, and work together to make an impact. We’re curious, driven, collaborative, genuine and humble.</div> <div> </div> <div>Temporal is growing and we are looking for those who share our values, challenge 'standard' thinking, and want to influence our future. If you have a passion for improving the developer experience, building world-class open-source software and communities, and want to be a part of our amazing team, we'd love to hear from you!</div></div><div> <p><strong>Summary</strong></p> <p>Cloud Data Store (CDS) owns the storage, retrieval, and lifecycle of all workflow data at planet scale. We design the persistence APIs, build storage abstractions that run across cloud vendors, and deliver the observability that lets customers trust their state machines for years. <em><strong>[To see more detail re: the Temporal CDS Eng team, <a href="https://temporalio.notion.site/Join-Temporal-s-Cloud-Data-Store-CDS-Team-21b8fc56773880028492cfbd915b0b60" target="_blank">click here</a>]</strong></em></p> <p>As a <strong>Staff Engineer</strong>, you will get the chance to design, build, and maintain significant portions of our backend functionality for highly scalable, multi-tenant services. You’ll own the custom persistence stack for Temporal Cloud which includes a Write Ahead Log, various metadata stores (Cassandra, etcd), multi-level caches, tiered storage etc. </p> <h3><strong>What You'll Do</strong></h3> <ul> <li><strong>Design build distributed data systems</strong> – craft APIs, schemas, and replication paths that keep petabytes of workflow history durable and query-able. Clearly document design choices and operational knowledge to successfully deploy and run service with those features.</li> <li><strong>Drive reliability performance</strong> – own SLOs, create chaos-test plans, profile hot paths, and lead incident reviews. </li> <li><strong>Technical leadership</strong> – break down roadmap epics, mentor mid-level engineers, steward design docs through RFC. </li> <li><strong>Cross-team collaboration</strong> – partner with the Server, Cloud, and DX teams to land features end-to-end. </li> </ul> <h3><strong>What You'll Bring</strong></h3> <ul> <li>5 or more years of experience as an "Arranger" and/or "Builder/Enhancer" of highly scalable distributed systems.<a href="https://temporalio.notion.site/Distributed-Systems-Concurrency-2526e6dfce4947d39fd3a40f9f07652a"> <em>see HERE</em></a><em> for more info re: "Arranger" and/or "Builder/Enhancer"</em></li> <li>Solid computer science fundamentals in distributed systems concepts including multi-threading and concurrency.</li> <li>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.<a href="https://temporalio.notion.site/Distributed-Systems-Concurrency-2526e6dfce4947d39fd3a40f9f07652a"> <em>see HERE</em></a><em> for more info re: "high end of Intermediate" and/or "Advanced" or "Expert levels"</em></li> <li>Experience building and running services on AWS. Bonus: Microsoft Azure and Google GCP experience.</li> <li>Experience with Elastic Search and/or Clickhouse</li> </ul> <h3><strong>Nice to Have</strong></h3> <ul> <li>Prior contributions to Temporal, Cadence, or other workflow engines.</li> <li>Deep expertise in a storage domain (LSM trees, columnar stores, transactional logs, etc.).</li> <li>Operated multi-region, ≥99.99 % uptime services.</li> <li>Experience working with Op ... (truncated, view full listing at source)