SevyDevy

Design over-the-air updates for car fleets

PremiumCloud infrastructureHard

  • OTA
  • Staged rollout
  • Code signing

Quick answer

This cloud infrastructure interview question asks you to design over-the-air updates for car fleets. Aim for a design that runs reliably and securely in the cloud at a sensible cost, then explain the services, regions, deployment and trade-offs. Interviewers want to see how you balance reliability, security and cost.

The problem

Design over-the-air updates for car fleets: the path from a monorepo commit to software running in 2 million cars. It covers CI builds, tests, signing, staged rollout, delta downloads, rollback and A/B partitions in the car. The hard part is that a bad update can affect driving safety, so every stage needs a gate.

Each car has a main computer and several smaller controllers (ECUs) that must end up on versions known to work together. Updates download in the background, install to the inactive partition and switch only when the car is parked. Many markets regulate vehicle software updates (UN Regulation No. 156), so every release needs records, test evidence and approvals.

What must the system do?

  • Commit to car: A merged commit can become a signed release for each hardware variant, with tests and approvals recorded at every gate.
  • Staged rollout: Releases go to cohorts (engineering cars, employees, 1%, 10%, 50%, 100%) per variant and market, and pause automatically on bad signals.
4 more requirementsUnlock to see all

How well must it do it?

  • Safety: No unsigned or untested image ever installs, and a failed update never leaves a car unable to drive.
  • Speed: 95% of the fleet on a normal release within 14 days; a critical security fix within 72 hours.
2 more requirementsUnlock to see all

What scale should you design for?

Use these numbers in your estimates.

The scale numbers unlock with this questionUnlock

Key concepts

  • OTA
  • Staged rollout
  • Code signing
  • A/b partitions
  • Delta updates
  • Hardware in the loop

How you’ll practise

6 short steps · save and come back any time
  1. Requirements
  2. Environments and topology
  3. Deployment pipeline
  4. Reliability and disaster recovery
  5. Observability and cost
  6. Wrap-up

Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.

What do interviewers look for?

In any cloud infrastructure design round.

  • Clarifies availability, security and cost targets
  • Chooses managed services with reasons
  • Plans regions, zones and failover
  • Covers identity, secrets and network boundaries
  • Explains deployment, rollback and observability
  • Keeps an eye on cost as usage grows

Questions people ask about this interview question

Which design type is this question?
It is a cloud infrastructure question. You design over-the-air updates for car fleets and explain your choices the way you would in an interview.
Is this question asked at entry level?
It is marked Hard. It suits engineers preparing for senior interviews, where you are expected to drive the discussion and go deep on trade-offs.
What should I cover first?
Start with the workloads, the availability target and the security and cost limits. Agree on scope with the interviewer before you design anything.
Can I practise it for free?
It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.

Related questions

Updated · Written by the SevyDevy team

Premium questionSign up free, then unlock it