Tesla

Makes electric cars, robotaxis and grid batteries

Staff Distributed Systems Engineer - Account Master

Backend EngineeringConfirmed live in the last 24 hours

Full-timeFremont, CA, USANo salary listedIn-person

About the Job

Requirements

At least 10 years of experience building backend systems, including prior production ownership of a distributed system at comparable scale: tens of thousands of queries per second, cross-store consistency, and high-cardinality personally identifiable information.
Strong Go programming ability; working Python is a plus for the SI-agent surface.
Deep Kafka experience with ordering, consumer failure, retries, idempotency, and replay.
Experience with MySQL and a search or analytical store such as Elasticsearch or ClickHouse.
A track record of driving technical decisions across multiple teams and shipping the outcome.
Deep judgment on schema evolution, backward compatibility, and migration risk on live systems that other products depend on, including CDC, outbox, or equivalent patterns in production.
Familiarity with a large-scale batch or reconciliation framework; Spark is preferred.
Experience defining SLOs and correctness measurement, not just meeting them.
Operational experience with monitoring, alerting, on-call, and incident response, with a history of eliminating recurring incident classes.
Ability to write design documents partner teams can build against and run reviews that shape their designs.

Responsibilities

Set the multi-year architecture for keeping MySQL, ClickHouse, and Elasticsearch consistent as schema and traffic evolve.
Own the public data contract that downstream products across Tesla depend on, including API shape, event schemas, and compatibility guarantees.
Design and evolve the Kafka change-propagation model so downstream products see changes in order and can replay or backfill them without double-applying.
Drive the platform toward 50,000 queries per second through partitioning, backpressure, and failure handling for single-asset and multi-asset accounts.
Define the SLO framework for availability, latency, and correctness that the team and its partners operate against, including measurement of reconciliation lag, divergence rate, and event-loss detection.
Lead cross-team design reviews for changes that touch customer or asset data, and unblock other teams' designs before they reach production.
Own security, authorization, and auditing for customer and asset data, including how SI-agent workflows written in Python access it; the data is subject to GDPR, CCPA, and similar privacy laws.
Carry the pager, respond to alerts, and eliminate recurring incidents at the class level.
Raise the team's testing standards for retries, duplicate events, and replay; mentor senior engineers and grow the technical bench.
Write design documents that shape the platform's evolution and review documents that affect it.

Desired Qualifications

Working Python ability for the SI-agent surface.
Familiarity with a large-scale batch or reconciliation framework, with Spark preferred.

Category	Engineering & Information Technology
Location	Fremont, California
Requisition ID	256509
Type	Full-time

Job Description

<div class="MSWordContent"><p>Account Master is Tesla’s data record for customers and their assets - think demographics, driver & Robotaxi rider profiles, preferences, or the Powerwall linked to your account. Nearly every surface at Tesla reads from that record, so when the data’s off, customers lose access to what should be theirs - this gets increasingly complex when a product gets delivered, serviced, shared, or transferred. The work now is to keep that data honest as volume heads toward 50,000 QPS and the mix of vehicles, energy systems, and access relationships on an account expands. We’re looking for a distributed systems expert to own this platform end to end: the architecture across services, the contracts other teams build against, and the operational bar the system has to clear.</div>

Job Responsibilities

Set the multi-year architecture for how MySQL, ClickHouse, and Elasticsearch stay consistent as the schema and traffic evolve
Own the public data contract that downstream products across Tesla depend on — API shape, event schemas, and compatibility guarantees
Design and evolve the Kafka change-propagation model so downstream products see changes in order, and can be replayed or backfilled without double-applying
Drive the platform toward 50,000 QPS — partitioning, backpressure, and failure handling for both single-asset and multi-asset accounts
Define the SLO framework for availability, latency, and correctness that this team and its partners operate against, and the measurement behind it (reconciliation lag, divergence rate, event-loss detection)
Lead cross-team design reviews for changes that touch customer or asset data, and unblock other teams' designs before they hit production
Own security, authorization, and audit for customer and asset data, including how SI agent workflows written in Python access it. This data is in scope for GDPR, CCPA, and similar privacy laws
Carry the pager, respond to alerts, and eliminate recurring incidents at the class level, not one at a time
Raise the team's bar for testing retries, duplicate events, and replay; mentor senior engineers on the team and grow the technical bench
Write the design docs that shape how this platform evolves, and review the ones that touch it

Job Requirements

10+ years building backend systems, including prior production ownership of a distributed system at comparable scale — tens of thousands of QPS, cross-store consistency, high-cardinality PII
Strong Go programming ability; working Python is a plus for the SI-agent surface
Deep Kafka experience: ordering, consumer failure, retries, idempotency, and replay
MySQL, plus a search or analytical store (Elasticsearch or ClickHouse)
Track record of driving technical decisions across multiple teams and shipping the outcome
Deep judgment on schema evolution, backward compatibility, and migration risk on live systems that other products depend on. CDC, outbox, or equivalent patterns in production
Familiarity with a large-scale batch or reconciliation framework — Spark preferred
Experience defining SLOs and correctness measurement, not just meeting them
Real operational experience (monitoring, alerting, on-call, incident response) with a history of eliminating recurring incident classes
Ability to write design docs partner teams can build against, and to run the reviews that shape theirs

About the Company

Tesla

Makes electric cars, robotaxis and grid batteries

Tesla makes electric cars and batteries that store power for homes and utilities, and it develops self-driving software and humanoid robots. In 2023, its Model Y became the first electric vehicle to rank as the world's best-selling car. Buyers order the Model 3 sedan, Model Y SUV, or Cybertruck pickup directly from Tesla instead of through dealers, and they charge on its Supercharger fast-charging network. It also sells Megapack and Powerwall batteries, runs a robotaxi service, and charges drivers a monthly fee for self-driving software that still needs their supervision. Tesla was founded in 2003, with Elon Musk as its lead early investor and a recognized co-founder, and it is based in Austin, Texas.

Company size: 10,001+
Company stage: IPO
Headquarters: Austin, TX
Founded: 2003

Recently Posted Jobs

Explore more opportunities at Tesla

See more jobs