Technology · Mid-career

Java Developer Resume Example

A resume for a Java developer in the middle of their career, set in payments and insurance. It shows how to make the JVM ecosystem visible (Spring Boot, Hibernate, Kafka, Maven, JUnit) and how to write about upgrades, performance tuning and testing in a way another Java developer will respect.

The example resume

Laid out in the Technical Global template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.

Priya Raghunathan

Java Developer

  • priya.raghunathan@example.com
  • +1 555 0127
  • New York · London · Mumbai
  • github.example.com/priya-raghunathan

Professional summary

Java developer with six years of experience building payment and insurance services on Spring Boot. Strongest in event-driven design with Kafka, JVM performance tuning and well-tested code (JUnit 5, Testcontainers). Currently maintains a card authorisation service that processes about 4 million transactions a day.

Work experience

Java Developer

Kestrel Quay Payments, Bengaluru

Jan 2023 – Present

  • Developed and maintained the card authorisation service in Java 21 and Spring Boot 3, handling peaks of 300 transactions a second with p99 latency under 120 ms
  • Replaced synchronous settlement calls with Kafka events and an outbox table, removing the duplicate postings that had caused about 15 manual corrections a month
  • Tuned G1 garbage collection and connection pool settings after heap dump analysis, cutting latency spikes during collection pauses from 800 ms to under 150 ms
  • Led the upgrade from Java 11 to 21 and Spring Boot 2.7 to 3.2 across 9 services, including the javax to jakarta namespace migration
  • Wrote integration tests with JUnit 5 and Testcontainers against real PostgreSQL and Kafka, raising line coverage of the ledger module from 48% to 82%

Associate Software Engineer

Fernhill Mutual Insurance Technology, Bengaluru

Jul 2020 – Dec 2022

  • Built REST endpoints for policy quotes and renewals in Spring Boot with Hibernate, serving 60 broker offices
  • Rewrote the nightly premium calculation with Spring Batch and chunked processing, shortening the run from 3 hours 20 minutes to 45 minutes
  • Fixed N+1 query problems in Hibernate mappings, found through SQL logging, halving load time for the policy search screen
  • Moved the build from Ant to Maven with a shared parent POM and added SonarQube quality gates to the Jenkins pipeline

Skills

Languages: Java (8 to 21), Kotlin, SQL

Frameworks: Spring Boot, Spring Security, Spring Batch, Hibernate/JPA

Messaging and data: Kafka, PostgreSQL, Oracle Database, Redis, Flyway

Testing: JUnit 5, Mockito, Testcontainers, WireMock

Build and delivery: Maven, Gradle, Jenkins, Docker, Kubernetes, SonarQube

Certifications

Oracle Certified Professional: Java SE 17 Developer

Oracle

2023

Education

BE Computer Engineering

Westbank Institute of Engineering, Bengaluru

2016 – 2020

Open this example in the resume builder Start empty with this template

Why this resume works

  • The summary names Spring Boot, Kafka and JUnit 5 in its first two sentences, so a reader checking against a typical Java back-end advert sees the match before reaching the experience section.
  • Java versions are stated (Java 21, Spring Boot 3, the 11 to 21 upgrade), which tells the reader the experience is current and that Priya has carried out a migration many teams still have ahead of them.
  • The garbage collection bullet says how the problem was found (heap dump analysis) and what was changed (G1 and pool settings), which is the detail a JVM-literate interviewer will ask about.
  • Throughput and latency figures are modest and precise: 300 transactions a second at p99 under 120 ms is believable for a card service and easy to discuss.
  • The earlier role shows the less glamorous work (Hibernate N+1 fixes, Spring Batch, Ant to Maven) that makes up much of real enterprise Java development.

What employers look for in this role

  • Design and build services and REST APIs with Java and Spring Boot
  • Write unit and integration tests with JUnit and Mockito
  • Model data and write efficient queries through JPA/Hibernate or plain SQL
  • Diagnose performance problems using thread dumps, heap dumps and profilers
  • Maintain Maven or Gradle builds and the pipelines that run them
  • Keep services current through Java and framework upgrades
  • Take part in code reviews and production support

Skills to consider

List only the skills you can back up with an example. These are the ones that come up most for this kind of role.

Core Java
Collections and generics, Streams and lambdas, Concurrency (executors, CompletableFuture, virtual threads), JVM memory model and garbage collection, Records and sealed types, Exception handling design
Frameworks and data
Spring Boot, Spring Security, Spring Data JPA and Hibernate, Kafka or RabbitMQ, PostgreSQL, Oracle Database or MySQL, Flyway or Liquibase
Build, test and run
Maven or Gradle, JUnit 5 and Mockito, Testcontainers, Docker and Kubernetes, Jenkins or GitHub Actions, Profilers such as JFR and VisualVM

More bullet points to adapt

Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.

  • Introduced virtual threads for outbound HTTP calls in a Spring Boot 3.2 service, raising throughput in load tests by 35% without restructuring the code
  • Replaced hand-written JDBC in the reporting module with Spring Data JPA projections, removing 2,400 lines of mapping code
  • Added idempotency keys to the refund API so that retried requests could no longer create duplicate refunds
  • Cut service start-up time from 48 seconds to 19 by removing unused auto-configurations and lazy-loading 3 heavy beans
  • Wrote a Gradle convention plugin shared by 14 repositories, so dependency versions are upgraded in one place
  • Traced a thread pool exhaustion incident to a blocking call inside a Kafka listener and moved the work to a bounded executor

Words that recur in adverts

These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.

  • Java 17 or 21
  • Spring Boot
  • microservices
  • REST APIs
  • Hibernate/JPA
  • Kafka
  • JUnit and Mockito
  • Maven or Gradle
  • multithreading
  • SQL
  • Docker and Kubernetes
  • CI/CD
  • design patterns

Which sections to include

Put the summary first and make sure it names your Java version range and main framework, because adverts for Java roles are usually specific about both. Experience comes next and should carry the evidence: services built, upgrades completed, performance problems diagnosed. Group the skills section by layer (language, frameworks, data and messaging, testing, build) so a reader can check the stack quickly. Certifications such as Oracle's Java SE exams are optional but fit naturally after skills. Education goes last once you have two or more years of experience.

Mistakes to avoid

  • Writing "Java" with no version, which leaves the reader guessing whether your experience stops at Java 8; state the versions you have worked with and any upgrade you carried out.
  • Listing "Spring" as a single skill when adverts distinguish Spring Boot, Spring Security, Spring Data and Spring Batch; name the modules you have actually used.
  • Padding the skills list with legacy technology you would not want to work in again (Struts, EJB 2, JSP) without saying it was part of a migration.
  • Claiming "microservices" when the bullets describe one large application; describe the architecture you really worked in, since a well-kept monolith is nothing to hide.
  • Omitting how you tested, even though Java adverts routinely ask for JUnit and Mockito by name; say what kind of tests you wrote and what they ran against.

Questions and answers

Should I list every Java version I have used?

A range is enough: "Java (8 to 21)" tells the reader you know both older codebases and current language features. Mention a specific version inside a bullet when it matters, such as an upgrade you led or a feature like virtual threads that you used.

Is an Oracle Java certification worth including?

Include it if you hold one. It does no harm, and some employers, particularly consultancies and large enterprises, ask for it. It will not replace evidence of real work, so keep it to a single line after the skills section and let the experience bullets do the persuading.

How do I show Spring Boot experience if my current project uses an older framework?

Be accurate about your paid work and add what you have done outside it: a migration proof of concept, an internal tool or a personal project built with Spring Boot. Label it clearly as a project. Interviewers generally accept self-taught framework knowledge when the Java fundamentals underneath are solid.

Do Kotlin or Scala belong on a Java developer resume?

Yes, if you have used them, because they show range on the JVM and many Java teams have some Kotlin. Keep Java first in the list and in the summary when the role is advertised as Java. To see which terms from the advert your resume is missing, paste both into the keyword checker.