1

Day Shift Distributed Systems Engineer Jobs in California

Distributed Systems Engineer

San Francisco, CA ยท On-site

$250K - $400K/yr

Building a distributed system for millions and billions of AI agents running on E2B * Building an ... (4 days on-site, 1 day WFH) offices in San Francisco and Prague, Czech Republic . We already ...

Role As a distributed systems engineer, you'll work across the stack to solve problems as they come up and help build Archil volumes. You'll have significant influence over the technical and product ...

Distributed Systems Engineer

San Francisco, CA ยท On-site

$200K - $300K/yr

Massive Market : We're building critical infrastructure for the biggest technological shift of our ... Build leverage (via AI) - projects that take a week today should take a day next time. * Share your ...

Sr. Distributed Systems Engineer

San Francisco, CA ยท On-site

$123K - $168K/yr

Role As a distributed systems engineer, you'll work across the stack to solve problems as they come up and help build Archil volumes. You'll have significant influence over the technical and product ...

Software Engineer, Distributed Systems

San Francisco, CA ยท On-site +1

$203K - $241K/yr

We're scaling fast, and we're looking for experienced distributed systems engineers across a variety of teams. Whether you're passionate about storage, compute orchestration, developer tooling ...

next page

Showing results 1-20

People also search for

Day Shift Distributed Systems Engineer information

What is the difference between Day Shift Distributed Systems Engineer vs Network Systems Engineer?

AspectDay Shift Distributed Systems EngineerNetwork Systems Engineer
CredentialsBachelor's in CS or related, certifications like AWS, Cisco (CCNA)Bachelor's in CS or related, certifications like Cisco (CCNA), CompTIA Network+
Work EnvironmentDesigning, deploying, maintaining distributed systems, cloud environmentsManaging network infrastructure, configuring routers/switches, troubleshooting connectivity
Industry UsageTech, cloud providers, large-scale enterprise systemsTelecommunications, data centers, enterprise networks

The Day Shift Distributed Systems Engineer focuses on building and maintaining distributed computing environments, often in cloud or data center settings. In contrast, a Network Systems Engineer specializes in network infrastructure, ensuring connectivity and security. Both roles require technical certifications and work in tech-driven industries, but their daily tasks and focus areas differ significantly.

What are popular job titles related to Day Shift Distributed Systems Engineer jobs in California? For Day Shift Distributed Systems Engineer jobs in California, the most frequently searched job titles are:
What job categories do people searching Day Shift Distributed Systems Engineer jobs in California look for? The top searched job categories for Day Shift Distributed Systems Engineer jobs in California are:
What cities in California are hiring for Day Shift Distributed Systems Engineer jobs? Cities in California with the most Day Shift Distributed Systems Engineer job openings:

Distributed Systems Engineer

Tensorlake, Inc.

San Francisco, CA โ€ข On-site

Full-time

Posted 24 days ago


Job description

Our core mission at Tensorlake is to unlock your data wherever it is. We believe that people should have access to the best tools to parse, extract, and manipulate data, run data applications, so they can spend more time putting knowledge into action.
We're looking for engineers who want to build the operating system for AI Data Applications and Workflows.
About the role
We're looking for experienced distributed systems engineers to build the core infrastructure for our durable application runtime. This is a systems programming role-you'll be writing the schedulers, runtimes, and data plane components that other engineers build applications on top of. Some of the things you'll work on in this role
  • Build and evolve our durable application runtime to support advanced data processing and machine learning workflows
  • Design and implement core components of our cluster scheduler to improve resource utilization, reduce costs, and maximize performance
  • Write systems-level code in Rust for our data plane and execution engine
  • Design and build new capabilities for our SDKs
  • Work closely with the rest of the engineering team to take something from an idea to a polished product

About you
  • You have 5+ years of experience building distributed systems infrastructure-not configuring or operating it, but designing and implementing it from scratch
  • You've written production systems in Rust or other systems programming languages (C, C++, Go at the systems level)
  • You understand how cluster schedulers, databases, and runtimes work at the implementation level because you've built or contributed to them
  • You can autonomously lead, design, and build fault-tolerant systems
  • You enjoy diving deep into performance challenges at the systems level-memory allocation, concurrency primitives, network protocols
  • You want to be part of the entire product development process, from customer research to implementation

This role is not a fit if...
  • Your experience is primarily in DevOps, SRE, or platform operations (Terraform, Kubernetes administration, CI/CD pipelines)
  • You're looking for a role focused on automation, tooling, or infrastructure-as-code rather than building core systems
  • You haven't written substantial code in a systems programming language

Things you should know
  • We're a startup, and we expect people to be able to wear multiple hats at any given time.
  • We're distributed across the US and Europe, and everyone is self-sufficient to get work done even when nobody else is around.
  • We do not expect people to work all the time, but we expect everyone to follow up on their commitments.
  • We're a small team with high ownership and we're passionate about what we do.
  • Our tech stack is somehow diverse. You'd be mostly working with Rust, Python and FoundationDB on your day to day. But you'll also need to understand TypeScript, Go, and Terraform enough to touch parts of our backend infrastructure.