applinity

Senior Software Engineer, Nexus Server

at Temporal Technologies

Location

Seattle, Washington; San Francisco, California

Compensation

$176k–$231k USD

Type

full time

Posted

2 weeks ago

Remote

Yes

Save to queue

Market range · company + function + seniority

$231k—$231k—$278k

p25 · target · p75 · n=20

Posted $231k · in the market band

Tailor your résumé to this role in 30 seconds.

Free account · ATS keyword check · per-job bullet rewrite by Claude.

Tailor my résuméApply on company site

Job description

Summary

As a Senior Engineer, you will get the chance to design, build, and maintain significant portions of our backend functionality for highly scalable, multi-tenant Nexus services (Our durable execution framework for orchestrating work across team and application boundaries for improved modularity, security, debugging, and fault isolation). Examples of the key distributed systems components you’ll own include durable execution, async processing and expand our ability to invoke workflows through more industry standard protocols. Working in the highly collaborative Compute and Artificial Intelligence org, we’ll look to build a new enterprise offering that involves both on-premise and dedicated cloud offerings.

To learn more about Nexus and how our customers use Nexus here - [new window opens]

What You'll Do

  • Design and implement core backend service features for Nexus.

  • 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.

What You'll Bring

  • 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"

Temporal Technologies is an Equal Opportunity Employer. Temporal Technologies does not discriminate on the basis of race, religion, color, sex, gender identity, sexual orientation, age, non-disqualifying physical or mental disability, national origin, veteran status, or any other basis covered by appropriate law. All employment is decided on the basis of qualifications, merit, and business need. We embrace and celebrate differences and diversity.

Temporal is committed to providing access, equal opportunity, and reasonable accommodation for individuals with disabilities in employment, its services, programs, and activities. If you need to request a reasonable accommodation, please let your Recruiter know so we can assist.

More open roles at Temporal Technologies

Hiring velocity, headcount trend, and every open posting on one page.

View Temporal Technologies profile →

Similar roles

Open postings ranked by description similarity — useful if this role isn't quite right.