Loading...
Loading...
Browse 5 real-world technical and behavioral interview questions about Debugging. Review scenarios, edge cases, and architectural best practices.
Kubernetes CrashLoopBackOff debugging starts with the previous container logs, exit code and pod events. Then separate application crashes from liveness probe kills, bad configuration, missing dependencies and OOMKilled restarts.
Ask the index directly whether the old text is still there, because that single check splits the problem into change detection, queue or write failure, a retire step that left duplicate chunks, or a downstream cache. Then fix the reason you learned about it from a user rather than an alert.
Walk three gates in order for that one request — was the supporting passage retrieved, did it survive into the rendered prompt, does the answer contradict it. Each gate blames a different stage, which is why the diagnosis depends on having logged both the retrieved chunk ids and the prompt as sent.
A failure has to be diagnosable from its artefacts alone, because nobody can attach a debugger to a CI run: that means assertions that report the compared values, a message naming the business expectation, and captured evidence of the state at the moment of failure. Use this automation answer to show the decision, trade-off, and evidence rather than a memorised definition.
Rank the causes by how often they are to blame and test them in that order: target leakage, a validation split that ignored group or time structure, train-serve skew, then genuine distribution shift. One cheap experiment separates most of them, which is rescoring logged production rows offline with the same artefact.