Hiring guide

How to Hire a Java Developer

Hire a Java developer for real back-end work: Spring and JVM skills, a service work sample, concurrency and testing criteria, red flags and onboarding.

How to Hire a Java Developer

The short answer

Hiring a Java Developer comes down to verifying modern java language features and the standard library, including collections, streams and records, spring boot (or your framework): dependency injection, configuration, data access and transaction boundaries and concurrency: thread safety, executors, completablefuture and virtual threads where relevant before you commit interview time. The process below runs 5 stages, screens on evidence rather than résumé claims, and scores every candidate against the same criteria.

  • Watch for: Only knows older Java idioms and has not used features from recent releases
  • Watch for: Uses framework annotations without being able to explain what they do, especially @Transactional
  • Score on: Correct transaction and error handling
  • Score on: Thread safety and awareness of concurrency risks
For hiring teams

Paste your Java Developer job description; Cohesyve finds, contacts and tests candidates on the real work and ranks them. 14-day free trial for 10 candidates, not charged until it ends.

Applying for a role like this? Practise the assessment free →

If you plan to hire a Java developer, start with the system they will work in: a Spring Boot microservice estate, a large legacy monolith, Android code, or a high-throughput data platform. Java has been in production for a long time, so candidates range from people who know modern Java (records, streams, virtual threads) to those who have maintained one older codebase for years. Test them on code that looks like yours.

Why this role matters

Java often runs the systems that move money, orders and records, so mistakes are expensive. Poor transaction handling corrupts data, careless concurrency causes intermittent failures, and weak JVM knowledge leads to memory and latency problems that are hard to trace. A good Java developer writes code that is predictable under load, keeps services maintainable as they grow, and modernises older code without breaking it.

Where to find candidates

  • Java User Groups (JUGs) in your region and their meetup speakers
  • Conferences such as Devoxx and their speaker lists, and the Java Champions programme for senior and community-minded developers
  • GitHub contributors to Spring, Quarkus, Micronaut or the libraries your system depends on
  • Holders of Oracle Certified Professional Java SE Developer credentials, treated as one signal of language knowledge alongside a work sample
  • Developers at companies running Java at scale in your sector, such as banks, payments and logistics firms
  • Referrals from your current Java engineers and from contractors who have worked on your codebase

Skills to look for

Modern Java language features and the standard library, including collections, streams and recordsSpring Boot (or your framework): dependency injection, configuration, data access and transaction boundariesConcurrency: thread safety, executors, CompletableFuture and virtual threads where relevantJVM understanding: garbage collection behaviour, heap analysis and profilingRelational databases with JPA/Hibernate or JDBC, and knowing when an ORM is causing N+1 queriesTesting with JUnit and Mockito, plus integration tests against real dependencies (for example with Testcontainers)Build tooling with Maven or Gradle and dependency management

Red flags

  • Only knows older Java idioms and has not used features from recent releases
  • Uses framework annotations without being able to explain what they do, especially @Transactional
  • Cannot describe how they diagnosed a memory leak or slow endpoint
  • Shared mutable state across threads with no thought for synchronisation
  • Tests that mock everything, so nothing exercises the database or real serialisation
  • Heavy layers of abstraction for simple features

The interview process

  1. 1

    Experience screen

    Ask about the Java versions, frameworks and system sizes they have worked on, and one production problem they solved. Confirm the match to your stack and the kind of system (services, batch, legacy).

  2. 2

    Code reading exercise

    Show a short piece of your style of Java with a subtle bug, such as a transaction boundary in the wrong place or a race condition. Ask them to find and explain it. This reveals depth faster than writing code from scratch.

  3. 3

    Service work sample

    Give a small Spring Boot service and a ticket: add an endpoint that updates two related records atomically, with validation and tests. A job simulation of the real work is one option for this step. Judge transaction handling, error responses, test quality and readability.

  4. 4

    Design discussion

    Extend the task: what changes if the endpoint must handle many concurrent requests, or call a slow external service. Look for sensible use of timeouts, retries, idempotency and concurrency tools.

  5. 5

    Team interview and references

    Meet the team lead and a peer reviewer. Ask references about code review quality and how they handled production incidents.

For hiring teams

Start the Java Developer interviews from a ranked shortlist

Cohesyve takes your Java Developer job description, finds and contacts candidates and tests each one on an AI job simulation of the job, so the stages above start with people who have already done the work. 14-day free trial for 10 candidates, not charged until it ends.

How to evaluate

  • Correct transaction and error handling
  • Thread safety and awareness of concurrency risks
  • Tests that would catch real regressions
  • Readable code that fits existing conventions
  • Ability to reason about performance and the JVM
  • Pragmatic design without unnecessary layers

Onboarding

  • 1Document your Java version, framework versions and build commands, and have the project build locally on day one
  • 2Walk them through the service map and which services own which data
  • 3Give a first task that touches a real endpoint and its tests
  • 4Share your observability tools so they can read logs, metrics and traces from the start
  • 5Explain your upgrade plans for Java and frameworks so they know which patterns to avoid

Common questions

Does an Oracle Java certification matter when hiring?

It shows solid language knowledge, which can help when screening junior candidates. It does not show framework experience, system design or how they work in a codebase, so still use a work sample.

Should I hire for Spring Boot experience specifically?

If your services run on Spring Boot, yes for anyone who needs to deliver quickly. Developers from Quarkus or Micronaut can adapt because the ideas overlap.

How do I assess someone for a legacy Java codebase?

Use a code reading or refactoring exercise on older-style code. Look for care with behaviour changes, adding tests before refactoring, and patience with existing conventions.

Is Kotlin experience relevant?

Kotlin runs on the JVM and uses the same libraries, so Kotlin developers usually move to Java easily and the reverse is also common. Test in the language you use day to day.

For hiring teams

Hiring a Java Developer? Start with a ranked shortlist

Cohesyve takes your Java Developer job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then ranks them for you.

1,500+

assessments completed

50%

faster time-to-hire

5 min

from JD to assessment

14-day free trial · 10 candidates · Not charged until the trial ends

See Cohesyve in action

Free 30-min walkthrough

See it on your role