Java backend interview practice
A useful incident answer explains why a symptom occurs and how to check the proposed fix. Backend Drills helps you rehearse that explanation with supplied evidence and explicit trade-offs.
A 90-second explanation structure
- State the evidence. Name the observation that separates your leading hypothesis from another plausible cause.
- Explain the mechanism. Connect the observation to resource ownership, transaction boundaries, ordering or another concrete invariant.
- Contain the impact. Choose an action that reduces current harm and state its limitations.
- Prevent recurrence. Describe the design change and a test that would have caught the failure.
Start with three foundations
- The database is quiet. The pool is full.: Checkout latency spikes while database CPU stays low. Find what is holding the connections.
- The rollback that never happened.: A transaction annotation is present, yet a failed import leaves rows behind.
- One event. Two shipments.: A consumer restart repeats a side effect even though the producer is idempotent.
Practice with a partner
Read the brief without revealing the answer. Explain your first check aloud. Ask your partner which observation would disprove your diagnosis, and revise the explanation when it depends on an unstated assumption. Compare the debrief only after committing to a response.
Choose a topic for your next session
Explore Spring transactions, persistence, concurrency, PostgreSQL, messaging, caching and distributed systems in the full scenario catalog. The 14-day plan covers foundation cases; the wider library supports targeted practice.
This is a decision workbook. It does not run Java code, grade free-form answers with AI, or reproduce actual company interview questions.
Three complete drills are free without an account or card. The full edition requires a verified purchase when checkout is available. These fictional exercises provide learning feedback, not hiring predictions.