Real-time means correctness depends not just on producing the right result but on producing it within a guaranteed time bound, a deadline. It's about determinism, not raw speed: a system that responds in a guaranteed 100 µs every time is more "real-time" than one that's usually 10 µs but occasionally 10 ms. Hard real-time means a missed deadline is a failure (firing an ignition coil, deploying an airbag); soft real-time means occasional misses degrade quality but aren't catastrophic (audio glitches). Embedded systems care because they control physical processes that won't wait, a motor commutation, a control loop, a communication frame must happen on schedule. This is why embedded engineers obsess over worst-case execution time (WCET), bounded interrupt latency, and avoiding non-deterministic constructs (unbounded loops, dynamic allocation, cache/MMU variability), and why MCUs, with predictable timing, dominate hard-real-time roles.
Embedded Systems Fundamentals · Interview question
What does "real-time" mean, and why do embedded systems care about it?
A strong answer
What a weak answer sounds like
You know the answer. Do you know what gets you dinged?
Pro breaks down the answer most candidates actually give to this question — and the specific reason an interviewer marks it down. It’s the difference between sounding correct and sounding senior, on all 472 questions.
From the lesson
What Is an Embedded System?
A computer dedicated to one job inside a larger device, and the MCU-vs-MPU choice (everything-on-one-chip vs an application processor running Linux) that frames every design.