Job Description & Details
This is a heavy-duty 24/7 Incident Commander and SRE-leaning support role embedded directly in the automotive connected car space. If you thrive under pressure, love managing high-stakes P1 war rooms, and understand how data flows from a vehicle's TCU to cloud backends, this gig is right up your alley.
What You'll Actually Be Doing
Your day will revolve around monitoring system health, triaging anomalies, and acting as the central nerve center when things go sideways. You'll spend a lot of time analyzing observability dashboards, cutting through alert noise, and spinning up incident bridges. When a remote service fails—like an OTA update or a remote lock/unlock command for a connected vehicle—you'll coordinate cross-functional responders across OEM partners, tier-1 suppliers, and cloud providers to drive the issue to closure and lead the post-incident RCA.
The Core Tech Stack
You're going to live inside observability and APM tooling, specifically Datadog, Grafana, Dynatrace, and MaxGauge. The team needs someone who doesn't just look at dashboards, but actually understands time-series data, log aggregation, and metric traces. On top of that, domain expertise in Telematics is non-negotiable; you need to understand eSIM/OTA provisioning, API gateways, messaging queues, and how vehicle data flows interact with cloud infrastructure.
Interview Expectations
Expect the interviewers to drop you straight into a hypothetical P1 crisis scenario to test your Incident Commander composure and decision-making under pressure. They'll likely ask you how you handle conflicting priorities and noisy alerts when multiple downstream services are failing simultaneously, looking to see if you can methodically triage and drive stakeholder communication without losing your cool. They will also drill down into your Telematics knowledge, asking specific questions about data flows between vehicles and backend cloud platforms to verify your automotive background.
Application Advice
Make sure your resume doesn't just read like a generic IT support ticket logger. You need to explicitly highlight your experience acting as an Incident Commander or running war rooms for high-severity P1/P0 outages. Weave in the exact toolsets mentioned in the description—like Datadog, Grafana, Dynatrace, and Jira—alongside strong keywords like Connected Car, Telematics, TCU, and ITIL practices so you easily sail past the initial ATS filters.