CompanyBench places contract Java developers with US companies, from the benches of US-based C2C vendors and Indian IT vendors working offshore: Spring Boot and Kafka engineers, and developers who move estates from Java 8, 11 or 17 to Java 21 or 25. Java rates are quoted per requirement. Within 48 hours of a confirmed requirement you see at least 3 vetted, masked Java profiles, under one CompanyBench agreement.
This page is for engineering managers with Java work waiting: a services backlog, a Spring Boot upgrade, a Java 8 monolith to break up, or a Kafka pipeline that falls over at month end. It covers the Java and Spring Boot versions that matter this quarter, the Oracle JDK license change of October 2026, what to test and what goes wrong. Other stacks are on the US technologies page.
Java versions in late 2026: what is supported
Oracle names a long-term support (LTS) release every two years. The versions most US companies run, from Oracle's Java SE support roadmap:
| Version | General availability | Oracle Premier Support until | Extended Support until |
|---|---|---|---|
| Java 8 (LTS) | March 2014 | March 2022 | December 2030 |
| Java 11 (LTS) | September 2018 | September 2023 | January 2032 |
| Java 17 (LTS) | September 2021 | September 2026 | September 2029 |
| Java 21 (LTS) | September 2023 | September 2028 | September 2031 |
| Java 25 (LTS) | September 2025 | September 2030 | September 2033 |
Three points on that roadmap matter for hiring this quarter. Java 17 left Premier Support in September 2026; Oracle waives the Extended Support fee for Java 17 from October 2026 to September 2029, but teams on 17 are now planning the move to 21 or 25. Licensing changed too: Oracle JDK 17 updates released from October 15, 2024, and Oracle JDK 21 updates released from October 20, 2026, are under the Java SE OTN license, the same as Java 8 and 11, and Oracle tells users who want permissively licensed builds to move to Oracle JDK 25 or later. The next planned LTS is Java 29, in September 2027.
Spring Boot: the upgrade most Java contracts are really about
Most US Java work runs on Spring Boot, and the Spring Boot version often matters more than the Java version. Spring Boot 3.0 made Java 17 the minimum and moved every dependency from Java EE to Jakarta EE APIs, which means every `javax` import in your code changes. The current line, Spring Boot 4.2, needs Java 17 or later, works up to Java 27, and requires Spring Framework 7.1 and a Servlet 6.1 container. Spring Boot 4.0 also moved to Jackson 3.0.
| Where you are | What the work looks like | Who to ask for |
|---|---|---|
| Spring Boot 2 on Java 8 or 11 | Two jumps: Java 17 first, then the Jakarta namespace move to Spring Boot 3, then on to 4 | A developer who has done a Jakarta migration on a codebase your size, with test-first habits |
| Spring Boot 3 on Java 17 | Move to Spring Boot 4 and Java 21 or 25: dependency updates, Jackson 3 changes, removed deprecations | A senior Spring developer who reads release notes before touching code |
| Java EE or plain servlets on an app server | A larger move: rebuild services on Spring Boot or keep the app server and upgrade it | A modernization lead who can plan it in stages |
| Current versions | Feature work, performance, new services | Backend developers matched to your domain and messaging stack |
Which Java developer do you need?
| Java work | Day to day | Put in the requirement |
|---|---|---|
| Spring Boot microservices | REST and gRPC services, service boundaries, resilience, observability | Spring Boot, Spring Data JPA, Spring Security, OpenTelemetry or Micrometer, Docker and Kubernetes |
| Event-driven and Kafka | Producers, consumers, retries, dead-letter topics, schema evolution | Kafka consumer groups and offsets, idempotent consumers, Schema Registry |
| Legacy modernization | Java 8 monoliths split or upgraded, app server estates moved to Spring Boot | Strangler patterns, contract tests, both old and new stacks |
| Performance and JVM | Latency, memory leaks, garbage collection tuning, thread dumps | JFR, heap and thread dump analysis, GC logs, load testing |
| Full-stack Java | Spring Boot APIs plus an Angular or React front end | Both halves named in the requirement |
Android is a separate hire: most new Android work is in Kotlin, and Java backend skills do not cover mobile builds and releases.
What to test in a Java interview
Senior Java CVs list the same twenty frameworks. These questions separate people who run Java in production from people who list it:
- Virtual threads. Ask when they would use them. Oracle's Java 21 guide says they suit tasks that spend most of their time waiting on I/O, not CPU-heavy work, should never be pooled, and that on Java 21 a `synchronized` block pins the thread to its carrier. A candidate who suggests a fixed pool of virtual threads has read a headline, not the docs.
- Transactions. Show a Spring service where one method calls another `@Transactional` method on the same class. Ask why the transaction does not start. Self-invocation through the proxy catches out many experienced developers.
- JPA performance. Give a repository that loads orders and then their lines in a loop. Ask them to find the N+1 queries and fix them with a fetch join or an entity graph.
- Kafka failure. Ask what happens when a consumer crashes after writing to the database but before committing the offset. Look for idempotent processing and a dead-letter topic, not "it won't happen".
- Production debugging. Ask how they would find a memory leak in a service that slowly fills its heap. Good answers name heap dumps, JFR and GC logs, and say what they look for in each.
- The last upgrade. Ask about the last Java or Spring Boot upgrade they ran: what broke, how long it took, and what they would do differently.
Java developer contract rates
Java rates are quoted per requirement, for offshore developers from India and for US-based C2C developers. Each profile on the shortlist shows its hourly or monthly rate before you interview, and there is no placement fee. What moves the rate:
- Domain. Banking, payments and insurance work with audit trails and reconciliation pays more than general backend work.
- Messaging and scale. Kafka at volume, low-latency services and JVM tuning are narrower skills than CRUD services.
- Modernization leadership. Someone who can plan a Java 8 to 25 move and review others' code sits above a developer who builds to a plan.
- Hours and location. Full US-hours overlap, US-based engineers and on-site days are priced separately from offshore work.
How hiring a Java developer works
- Send the requirement: the kind of Java work, Java and Spring Boot versions, JDK distribution, messaging and database, cloud, the next three months of work, overlap hours, remote or on site, and length.
- We confirm it and agree a rate range, then route it to IT vendors whose benches include Java developers on those versions.
- Within 48 hours at least 3 masked profiles reach you (initials, role, years, certifications, location, rate), each listing the Java and Spring Boot versions and the systems the developer has worked on.
- Interviews run through CompanyBench, which books the call; contact details stay private on both sides.
- You choose a developer. You sign with CompanyBench, and CompanyBench signs a back-to-back agreement with that developer's employer.
- The developer starts on your codebase. You approve timesheets monthly and receive one CompanyBench invoice, and CompanyBench pays the vendor.
How we vet Java developers
- Government ID matched to the person on the profile.
- A Java assessment matched to the work: Spring and JPA for service roles, offsets and retries for Kafka roles, a staged plan for modernization roles.
- Proxy and deepfake interview screening, so the engineer you approve is the one who commits code.
- Oracle Java and cloud certifications verified when the profile lists them.
- A UAN check against dual employment for Java developers employed in India.
- A background check.
Example: Spring Boot 2 on Java 11 to Spring Boot 4 on Java 25
Example: an insurance software team runs six Spring Boot 2 services on Oracle JDK 11, with Kafka between them. The requirement reads: one senior Java developer who has completed a Jakarta EE migration, Spring Boot and Kafka, remote from India with four hours of overlap with Eastern time, six months, and one lead review a week from the team's architect. Plan: Java 17 first, then Spring Boot 3 and the `javax` to `jakarta` move, then Spring Boot 4 on Java 25, service by service with a green build between steps. Three masked profiles come back with rates and the Java and Spring Boot versions each developer has migrated. The architect sends each candidate the dependency list before the interview and asks which libraries will block the Jakarta move, picks one, and the developer starts with build access and read-only production metrics on day one.
Mistakes US teams make hiring Java contractors
- No versions in the requirement. "Java developer" with no Java or Spring Boot version gets you profiles from Java 6 maintenance to greenfield Java 25. Put both versions in the first line.
- Treating the Jakarta move as find and replace. Changing `javax` imports is the easy part. Libraries that never moved to Jakarta are what stall a Spring Boot 3 upgrade; list them before the contract starts.
- Upgrading Java and every library in one branch. Upgrade in steps with a green build between each, so a failure points to one change.
- Kafka without failure handling. Ask for retries, a dead-letter topic and idempotent consumers in the definition of done, not after the first incident.
- Ignoring the JDK license. Running Oracle JDK 17 or 21 in production under a license meant for development is an audit risk. Decide the JDK build when you plan the upgrade.
- No production access for production problems. A contractor hired to fix latency needs metrics, logs and traces from week one.
How the C2C arrangement works for a Java hire
The Java developer stays on their IT vendor's payroll; the vendor contracts with CompanyBench and CompanyBench contracts with you, so your team works with one counterparty. Our US hiring overview covers the engagement model, and C2C, W2 and 1099 compared covers who carries payroll tax for a Java contractor. Comparing backends? See .NET developers for Microsoft estates and Node.js developers for JavaScript services. Ready? Send a requirement.
Frequently asked questions
How much does it cost to hire a Java developer?
CompanyBench quotes Java rates per requirement, for offshore developers from India and for US-based C2C developers. Seniority, domain, Kafka or JVM tuning depth and the hours you need covered move the rate. Each shortlisted profile shows its hourly or monthly rate before any interview, and there is no placement fee.
Which Java version should we be on?
Java 21 or Java 25 for most teams. Oracle's roadmap shows Java 17 left Premier Support in September 2026, Java 21 has Premier Support until September 2028 and Java 25 until September 2030. Spring Boot 4.2 needs Java 17 or later, so your Spring Boot target often decides the Java version too.
Do we have to pay for Oracle JDK 21?
For new updates in production, check your license. Oracle states that Oracle JDK 21 updates released from October 20, 2026 are under the Java SE OTN license, which does not cover free production use, and points users who want permissive terms to Oracle JDK 25 or later. Many teams run an OpenJDK build instead; decide before you upgrade.
How long does a Spring Boot 2 to 3 upgrade take?
It depends on codebase size, test coverage and how many libraries never moved to Jakarta EE. A small service with good tests can move in days; a large monolith can take months. Ask a candidate to estimate after reading your dependency list, and treat any estimate given before that as a guess.
Can I hire a freelance Java developer through CompanyBench?
Not as a 1099 freelancer. CompanyBench supplies Java developers employed by IT vendors on C2C terms: the developer stays on the employer's payroll and you contract with CompanyBench. You get contractor flexibility with vetting, one monthly invoice and replacement terms set out in your contract.
Will AI replace Java developers?
Not for the work most Java contracts are about. AI coding tools speed up boilerplate and tests, but a Jakarta migration, a Kafka failure analysis or a JVM memory leak still needs someone who knows your system and takes responsibility for the change. Ask candidates how they use AI tools and how they review what those tools produce.
How soon does a Java shortlist arrive?
At least 3 masked Java profiles with rates arrive within 48 hours of confirming the requirement. Start dates depend on each developer's notice and your onboarding; sending the dependency list and granting build access early is what shortens the first week.
Tell us what you need
A vetted shortlist within 48 hours of confirming the requirement. No fees until someone starts.
Sources
- Oracle Java SE Support Roadmap
- Spring Boot reference: system requirements
- Spring Boot 3.0 release notes
- Spring Boot 4.0 release notes
- Oracle Java SE 21 documentation: virtual threads
Last reviewed November 22, 2026.
More for United States
- CompanyBench US
- C2C requirements for vendors and bench sales teams
- C2C vs W2 vs 1099: what corp-to-corp means for buyers and vendors
- Hire .NET developers on contract: C#, ASP.NET Core and .NET upgrades
- Hire AI developers on contract: ML, LLM and MLOps engineers
- Hire AWS consultants and cloud engineers on contract
- Hire Azure consultants and cloud engineers on contract
- Hire contract developers and IT consultants by technology

