Diagnose failures via SSH and large logs
BoxSoftware Engineer · Onsite
Last updated
Diagnose failures via SSH and large logs evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
A production service is failing. You have only SSH access to a host and the log file(s) are very large. How would you efficiently locate relevant errors or time ranges, and what specific commands, filters, or strategies would you use? If this issue recurs, how would you design a centralized logging and search solution, and what trade-offs would you consider?
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.