> Markdown version of [/jobs/ext/3027814-site-reliability-engineer-infotainment-platforms-validation](https://www.wearedevelopers.com/jobs/ext/3027814-site-reliability-engineer-infotainment-platforms-validation). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Site Reliability Engineer, Infotainment Platforms Validation

- **Company:** Tesla Motors
- **Location:** Palo Alto, CA, United States
- **Salary:** $140,000.0 - $252,000.0
- **Contract:** Permanent contract
- **Skills:** Java (Programming Language), Application Programming Interfaces (APIs), C++ (Programming Language), Continuous Integration, Software Debugging, Linux, Python (Programming Language), Log Analysis, Microsoft UI Automation, Reliability Engineering, Delivery Pipeline, Appium, Backend, Data Pipelines, Docker, Golang
- **Published:** September 22, 2026
- **Apply:** https://jobs.localjobnetwork.com/apply/add/84732648/1

## About the Role

* Strong backend engineering in Python, Go, Java, or C/C++; HTTP APIs, auth, service clients, and production debugging
 * Experience owning data pipelines or large-scale querying (logs, telemetry, warehouses) and turning that into metrics and dashboards
 * Experience with Linux/Unix, CI/CD, and Docker
 * Comfort with mobile UI automation (Appium or similar) as a driver of backend checks, or a proven ability to pick it up
 * Clear, regular communication - you keep partners informed and can explain what failed, why it matters, and what to do next

## Description

Tesla's mobile apps are a primary interface between owners, Robotaxi, and the vehicle. On a self-driving car, that interface is not optional. A broken session or a flaky API leaves a rider with a phone that will not start the trip. A weak test account, a CI job that never really hits the services, or missing fleet telemetry leaves Vehicle Software signing off without proof. This team builds the backend and tooling that close those gaps: cloud API clients between phone and vehicle, identity and session lifecycle, test accounts that take and release ownership of engineering cars, CI that exercises the services the apps depend on, and pipelines that turn vehicle and fleet telemetry into release sign-off. You'll work with mobile and backend engineers to reproduce failures across app, API, and car, growing end-to-end coverage on a shared layer that has to work everywhere. If you're comfortable driving mobile UI automation as a client of those systems and enjoy chasing issues until a
real bug is named, let's talk.
What You'll Do

 * Contribute to the backend that mobile-app automation runs on: Clients for the cloud APIs between phone and vehicle, identity and session lifecycle, and test accounts that can take and release ownership of engineering cars
 * Build internal tooling that helps engineers reproduce, inspect, and debug mobile-app behavior - locally and in CI - without standing up the full stack themselves
 * Build pipelines that pull, query, and analyze logs and telemetry from engineering vehicles and, over time, the fleet; define metrics, write queries, and put dashboards in front of release sign-off
 * Extend CI so tests run repeatably and reliably against the services the app depends on
 * Grow end-to-end mobile-app coverage as clients of those backends on a shared layer that works across platforms
 * Work with engineers across mobile and backend teams to root-cause failures across app, API, and car