Java Developer interview questions
Effective Java interview questions test object-oriented judgment, JVM understanding, and Spring experience against real production incidents — not keyword definitions. Ask about a garbage-collection or memory problem they solved, how they design services, and what they test first.
What a java developer interview must assess
- →Design judgment: interfaces, composition, when patterns help vs obscure
- →JVM in production: memory, GC behavior, profiling a real incident
- →Spring depth: dependency injection, transactions, actuator/observability
- →Concurrency: real race conditions they have caused or fixed
Sample java developer questions — and what to listen for
1. Describe a production memory or GC problem you investigated on the JVM. What did the evidence show?
Listen for: Heap dumps, GC logs, a named tool (JFR, VisualVM, async-profiler) and a root cause — leaked references, oversized caches — with the fix verified.
2. Tell me about a race condition or concurrency bug you dealt with. How did you find and fix it?
Listen for: Understanding of shared mutable state, synchronization choices (locks vs concurrent collections vs immutability), and how they reproduced it.
3. How do you decide what gets a unit test vs an integration test in a Spring service?
Listen for: Testing the seams: business logic unit-tested, wiring and persistence integration-tested (Testcontainers or similar), no cargo-cult 100% coverage.
Red flags
- ✕Quotes design patterns but cannot say when one hurt them
- ✕Never looked at GC logs or a heap dump
- ✕"Spring handles transactions" with no idea what @Transactional actually does
Generate the full java developer interview kit
Tuned questions for your specific opening — screening, behavioral, and technical, each with listen-for and red-flag notes, plus a weighted scorecard rubric. Paste your job description for best results — or generate the java developer job description first.
How it works
- 1
Describe the role
A one-line brief or the full job description — the questions are generated for THIS role, not from a generic bank.
- 2
Get the kit
Screening, behavioral (STAR), and technical questions — each with what a strong answer sounds like, the red flag, and a follow-up probe — plus a weighted scorecard rubric.
- 3
Ask or automate
Copy the kit as markdown for your interviews, or let the AI interviewer ask every candidate the same questions and score against the rubric.
Questions
What makes a good interview question?
It asks for past behavior ("tell me about a time…"), maps to a competency the role needs, and is asked to every candidate the same way. Decades of IO-psychology research show structured interviews predict job performance far better than unstructured conversation — hypotheticals and puzzles mostly measure confidence.
Is this interview question generator free?
Yes — no account, no email. Describe the role (or paste the job description) and you get the full kit: questions with listen-for and red-flag notes plus a weighted scorecard rubric, copyable as markdown.
How many interview questions should I ask?
In a 45–60 minute interview: 2–3 screening checks, 4–5 behavioral questions with follow-ups, and 4–6 role-specific probes is realistic. Fewer questions asked deeply beat many asked shallowly — the follow-up is where the signal lives.
Should every candidate get the same questions?
Yes — that is what "structured interview" means, and it is both more predictive and more defensible (EEOC/fairness). Same questions, same rubric, scores recorded per answer. It is exactly what the AI interviewer automates.