Troubleshoot a Frontend Failure in a Client-Server Application

A frontend app in a client-server setup has begun failing. Walk through how you would pinpoint the failure across the browser, network, backend service, and its dependencies before deciding on a fix.

Constraints & Assumptions

• No specific error code or root cause is provided. Start by narrowing the symptom instead of presuming the backend is at fault.
• Tell apart a blank or broken UI, a failed request, and a successful response that renders wrongly.
• Rely on observability and controlled reproduction; don’t make destructive production changes just to test a hypothesis.

Clarifying Questions to Ask

• What does the user observe, which action causes it, and is it reproducible?
• Does it impact all users, a specific browser or version, a route, or a certain account or data shape?
• When did it start, and what code, configuration, or dependency changed around that time?

Hint: Follow a single failing interaction Link the browser action to its concrete request and response, then cross-reference that request with server-side evidence rather than digging through unrelated logs.

What a Strong Answer Covers

• Symptom categorization and a reproducible failure instance alongside a suitable comparison case.
• Browser console checks, asset loading, request timing, status code, response body, and rendering inspection.
• Correlating the request via backend and dependency traces when evidence directs there.
• Hypothesis-driven isolation, mitigation, verification, and guarding against regressions.
• Caution around authentication, caching, and sensitive data in any captured diagnostic artifacts.

Follow-up Questions

• How would your approach change if the API returned a 200 OK yet the page remained broken?
• What if only a small subset of users experienced the failure after a deployment?

Overview: Debug a frontend failure spanning browser assets, network requests, backend traces, response contracts, caching, and deployment-specific user cohorts.

Read the full Oracle Software Engineer interview experience that this question originates from.