Scheduled job stopped silently
A scheduled background job (a nightly cleanup or billing run) silently stopped running after a deploy, and nobody noticed until downstream effects appeared days later. How do you respond and prevent it?
What a strong answer looks like
Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.
0:00 of about 20 min
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.