1

Distributed Systems Software Engineer Jobs in California

Systems Software Engineer

San Jose, CA · On-site

$202K - $240K/yr

Systems Software Engineer Location: San Jose, CA (Onsite) Duration: 6+ months contract Role and Responsibilities As a Senior System Software Engineer, you will join the GPU Software Validation team ...

... debugging distributed applications Experience debugging at all levels of an operating system ... of software engineer career experience Expertise in at least one of C++/Objective-C/Swift ...

Systems Software Engineer

Redwood City, CA · On-site

$211K - $251K/yr

As a System Software Engineer, you'll focus on the runtime itself which encompasses the IPC layer ... Experience building observability or tracing infrastructure for distributed or multi-process ...

Systems Software Engineer Company: Picarro Location: Santa Clara, CA Education: Bachelor's Degree Required Position Overview Picarro is seeking a Systems Software Engineer to design, develop, and ...

Systems Software Engineer

Santa Clara, CA · On-site

$120K - $130K/yr

Systems Software Engineer Company: Picarro Location: Santa Clara, CA Education: Bachelor's Degree Required Position Overview Picarro is seeking a Systems Software Engineer to design, develop, and ...

About The Role We're looking for a Senior Systems Software Engineer who can take ownership of the ... Architect and maintain infrastructure components (e.g., distributed services, data pipelines ...

Systems Software Engineer

Santa Clara, CA · On-site

$203K - $240K/yr

They are seeking a Systems Software Engineer to design, develop, and maintain robust software systems that support scientific instrumentation and data-driven applications. Responsibilities : • ...

Systems Software Engineer

Santa Clara, CA · On-site

$203K - $240K/yr

Picarro is a leading company in optical spectroscopy solutions, seeking a Systems Software Engineer to design, develop, and maintain software systems for scientific instrumentation. The role involves ...

next page

Showing results 1-20

Distributed Systems Software Engineer information

What are the key skills and qualifications needed to thrive as a Distributed Systems Software Engineer, and why are they important?

To thrive as a Distributed Systems Software Engineer, you need strong programming skills (often in languages like Java, Go, or C++), a deep understanding of algorithms, networking, and distributed computing concepts, typically supported by a degree in computer science or a related field. Familiarity with tools and frameworks such as Kubernetes, Apache Kafka, Docker, and cloud platforms (AWS, GCP, or Azure) is highly valued, as are certifications in cloud or devops technologies. Excellent problem-solving, teamwork, and communication skills help you design scalable solutions and collaborate across teams. These skills are crucial for building reliable, efficient, and scalable distributed systems that power modern applications and services.

What is the difference between Distributed Systems Software Engineer vs Cloud Software Engineer?

AspectDistributed Systems Software EngineerCloud Software Engineer
Required CredentialsBachelor's in CS or related, experience with distributed architecturesBachelor's in CS, experience with cloud platforms (AWS, Azure)
Work EnvironmentDevelops scalable distributed applications, often in data centers or on-premisesBuilds and maintains cloud-based solutions, deploying on cloud platforms
Employer & Industry UsageTech companies, data centers, distributed computing firmsCloud service providers, SaaS companies, enterprises adopting cloud
Search & Comparison IntentUnderstanding roles in distributed architectureComparing cloud-focused development roles

While both roles involve building scalable software, a Distributed Systems Software Engineer focuses on designing and implementing distributed architectures, whereas a Cloud Software Engineer specializes in deploying and managing applications on cloud platforms. The roles often overlap but differ mainly in their environment and specific technical focus.

What are the typical challenges faced by Distributed Systems Software Engineers when ensuring system reliability?

Distributed Systems Software Engineers often encounter challenges like handling network partitioning, ensuring data consistency across nodes, and effectively managing system failures. They need to design resilient architectures that can recover gracefully when components fail, and implement robust monitoring to detect issues early. Collaborating closely with DevOps, QA, and other engineering teams is crucial to address these challenges and maintain high availability and performance in complex, distributed environments.

What are Distributed Systems Software Engineers?

Distributed Systems Software Engineers are professionals who design, develop, and maintain software that runs across multiple computers or servers, working together to achieve a common goal. They build systems that are reliable, scalable, and efficient, often handling large volumes of data and user requests. Their work involves solving challenges related to network communication, data consistency, fault tolerance, and system coordination. These engineers frequently use technologies like cloud computing platforms, message queues, and databases to ensure smooth operation across distributed environments.
What are popular job titles related to Distributed Systems Software Engineer jobs in California? For Distributed Systems Software Engineer jobs in California, the most frequently searched job titles are:
What job categories do people searching Distributed Systems Software Engineer jobs in California look for? The top searched job categories for Distributed Systems Software Engineer jobs in California are:
Infographic showing various Distributed Systems Software Engineer job openings in California as of July 2026, with employment types broken down into 92% Full Time, 6% Part Time, and 2% Contract. Highlights an 94% Physical, 1% Hybrid, and 5% Remote job distribution.
Backend Software Engineer - Distributed Systems - 1818

Backend Software Engineer - Distributed Systems - 1818

PlacingIT

Palo Alto, CA

$170K - $250K/yr

Full-time

Posted 2 days ago


Job description

Backend Software Engineer – Distributed Systems - 1818


Location: San Francisco or Palo Alto, CA (Hybrid – 4 Days Onsite)
Job Type: Full-Time
Compensation: $170,000 – $250,000 Base Salary + Equity

About the Role

We're looking for a Backend Software Engineer with strong expertise in distributed systems to help build and scale the core platform powering a high-performance infrastructure product.

This role focuses on designing and maintaining highly reliable backend systems that operate at production scale. You'll solve challenging problems involving concurrency, resource allocation, distributed coordination, and system reliability while partnering closely with engineering teams across the organization.

If you're passionate about distributed systems, backend architecture, and building software that operates reliably under heavy load, we'd love to hear from you.

What You'll Do

  • Design, build, and evolve highly scalable distributed backend systems.

  • Develop core orchestration services responsible for resource allocation and platform operations.

  • Build backend services that efficiently manage reservations, scheduling, and capacity allocation.

  • Improve system stability, fault tolerance, and operational reliability.

  • Design solutions for concurrency, race conditions, asynchronous processing, and distributed coordination.

  • Collaborate with engineering teams to ensure seamless integration across platform services.

  • Ship features end-to-end, including architecture, implementation, database migrations, deployment, monitoring, and operational support.

  • Contribute to CI/CD pipelines, cloud infrastructure, and deployment automation.

  • Participate in on-call rotations and production incident response.

  • Help improve operational tooling, automation, and engineering best practices.

Required Qualifications

  • 3+ years of backend software engineering experience (5–8 years preferred).

  • Strong experience building and maintaining production distributed systems at scale.

  • Proven expertise handling concurrency, asynchronous processing, race conditions, and distributed architectures.

  • Professional experience developing production systems in Python.

  • Experience working at a high-growth startup or well-recognized technology company.

  • Strong understanding of software architecture, scalability, and backend system design.

  • Excellent debugging and problem-solving skills.

Technical Qualifications

Candidates should have experience with many of the following technologies:

Programming

  • Python

Infrastructure & Cloud

  • Kubernetes

  • Docker

  • AWS

  • Google Cloud Platform (GCP)

  • Terraform

Databases & Operations

  • PostgreSQL

  • Infrastructure as Code (IaC)

  • Monitoring and observability tools

  • CI/CD pipelines

Preferred Qualifications

  • Experience building marketplace, auction, exchange, reservation, or billing systems.

  • Experience designing distributed scheduling or resource allocation platforms.

  • Strong systems design background.

  • Full-stack engineering experience with a backend focus.

  • Experience influencing technical architecture and engineering decisions.

What We're Looking For

The ideal candidate enjoys solving difficult distributed systems challenges and takes pride in building reliable, scalable backend infrastructure.

Successful candidates will demonstrate:

  • Strong software engineering fundamentals.

  • Deep understanding of distributed systems and backend architecture.

  • High ownership and accountability.

  • Ability to work across multiple areas of the engineering stack.

  • Excellent collaboration and communication skills.

  • Curiosity, adaptability, and a desire to continuously improve complex systems.

  • Experience operating and maintaining production software—not just building prototypes.

Candidates Unlikely to Be a Fit

The following backgrounds generally do not align with this opportunity:

  • Engineers who have only built prototypes or MVPs without owning production systems.

  • Candidates who specialize in a single technology area and are unwilling to work across the broader backend platform.

  • Engineers with limited experience designing or operating distributed systems.

  • Candidates with multiple job tenures under two years over the past five years.