Interview scorecard template

Java Developer interview scorecard

Evaluate Java Developer candidates across 4 weighted areas: technical proficiency, systems and trade-offs, evidence and rigour, and collaboration and communication. Technical proficiency leads at 35%, so check depth in modern Java (records, streams, virtual threads) plus Spring Boot, JPA/Hibernate, Maven or Gradle, and how they handle concurrency and garbage collection tuning. Use the rubric to compare role-specific evidence consistently.

See AI scoring
software datajavajvm tuningmicroservicesspring boot
TL;DR
For technical proficiency, look for evidence the candidate names JDK versions used, explains collection or concurrency choices precisely, and describes GC or heap tuning done on a real service. For systems and trade-offs, look for evidence the candidate walks through a specific architecture, quantifies throughput or latency effects, and states what they deliberately chose not to build. Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework

What to assess and how to score it

Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.

01
Evaluation factor

Technical proficiency

35% weight

Check depth in modern Java (records, streams, virtual threads) plus Spring Boot, JPA/Hibernate, Maven or Gradle, and how they handle concurrency and garbage collection tuning.

Evidence to listen for

  • Command of the languages, frameworks, and data tools the role actually uses
  • Understands correctness, performance, and failure modes, not just syntax
  • Has opinions on testing and can justify them
  • Reads and reasons about code they did not write

Five-point scoring guide

1
Poor

Cannot work independently; fundamentals are missing.

2
Needs Improvement

Weak fundamentals; output needs heavy review.

3
Satisfactory

Competent for the role; needs guidance on complex or unfamiliar work.

4
Very Good

Strong practitioner; handles hard problems with little guidance.

5
Excellent

Names JDK versions used, explains collection or concurrency choices precisely, and describes GC or heap tuning done on a real service.

02
Evaluation factor

Systems and trade-offs

25% weight

Probe service decomposition calls: monolith versus microservices, REST versus Kafka messaging, caching with Redis, connection pooling, and where they accepted latency or consistency trade-offs.

Evidence to listen for

  • Reasons about scale, latency, cost, and failure before writing code
  • Names the trade-off they chose and what they gave up
  • Understands the data lifecycle end to end
  • Anticipates what breaks at ten times the volume

Five-point scoring guide

1
Poor

No thinking beyond the immediate task; no awareness of scale or failure.

2
Needs Improvement

Limited architectural awareness; struggles with design decisions.

3
Satisfactory

Works within an existing design; makes sound local decisions.

4
Very Good

Designs for scale and maintainability; articulates trade-offs clearly.

5
Excellent

Walks through a specific architecture, quantifies throughput or latency effects, and states what they deliberately chose not to build.

03
Evaluation factor

Evidence and rigour

25% weight

Test testing and debugging habits: JUnit 5 and Mockito coverage, integration tests with Testcontainers, profiling via JFR or async-profiler, and diagnosing production memory leaks.

Evidence to listen for

  • Validates results rather than trusting output
  • Knows how their work is measured and what a bad result looks like
  • Can describe a time their own analysis or model was wrong and how they caught it
  • Careful about data quality, leakage, and silent failure

Five-point scoring guide

1
Poor

Ships unvalidated work; no notion of how correctness is checked.

2
Needs Improvement

Validates superficially; misses obvious quality or leakage issues.

3
Satisfactory

Reasonable checks in place; rigour drops under time pressure.

4
Very Good

Validates thoroughly; can name a real error they caught in their own work.

5
Excellent

Cites heap dumps, thread dumps, or APM traces that located a real defect, with before and after metrics.

04
Evaluation factor

Collaboration and communication

15% weight

Assess pull request review behaviour, working with QA and product on ticket scope, and how they explain a refactor or tech debt case to non-engineers.

Evidence to listen for

  • Explains technical work to non-technical stakeholders
  • Gives and takes code or peer review constructively
  • Documents enough that the work survives their absence
  • Aligns with team process rather than working around it

Five-point scoring guide

1
Poor

Cannot work in a team; resistant to feedback.

2
Needs Improvement

Communication issues create rework; lone-wolf tendencies.

3
Satisfactory

Adequate team member; documentation and review participation are light.

4
Very Good

Communicates well; reliable reviewer and collaborator.

5
Excellent

Gives concrete review examples, defends design decisions without defensiveness, and translates technical risk into delivery impact.

Put this rubric to work

Score every candidate against the same standard

Add these weighted factors to Hirevire and let AI evaluate recorded answers against your rubric.

Explore AI Scorecards