Question bank from the Java course, weighted toward what a low-latency / systems role screens for — that’s the stated target in the Primetechie path, and file 02 is where those interviews are actually won or lost.

Format: the question, what a strong answer covers, and the detail worth adding that separates memorised from understood. 🔥 = comes up constantly.

Files

  1. Language & Collections — the screening round: equals/hashCode, HashMap internals, generics, streams, records
  2. JVM & Concurrency — the important one: GC, the memory model, volatile, thread pools, virtual threads, false sharing, lock-free structures
  3. Spring, Persistence & Systems — DI, N+1, @Transactional’s silent failures, concurrency control, idempotency, containers, testing

The three answers that matter most

If you prepare nothing else:

  1. “Walk me through a p99 latency investigation.” (02 Q11) — it’s the whole role in one question, and the answer is a method, not a list of causes.
  2. “How do you prevent overselling / lost updates?” (03 Q5) — tests whether you understand isolation levels or just ORM syntax.
  3. “What does volatile guarantee?” (02 Q4) — the fastest way to find out whether someone understands the memory model or has memorised a definition.

Where your real projects come in

The strongest material you have is your own code. Have a crisp story ready for each:

  • direct-debit-sandbox → idempotency, transactions, payments correctness (03 Q5–Q6)
  • record-id-generator → ID generation tradeoffs, batch processing, throughput (03 Q8)
  • The gap to close: no build-your-own systems project finished yet. A lock-free ring buffer or an order-book matching engine would answer 02 Q10 with “I built one” instead of “I’ve read about it” — see project-ideas.
↑ Back to Java