Java
Developer

Picks up stories in the existing microservice across controller, service and repository layers, applies Bean Validation on request objects, and maps between DTOs and entities following the project's package structure rather than inventing a new one per feature.

Covers business logic with JUnit 5 tests and Mockito mocks, adds Testcontainers-based integration tests so repository code runs against a real PostgreSQL or MySQL instead of H2, and keeps the coverage gate in the build passing.

Writes forward-only Flyway or Liquibase migrations, resolves checksum and ordering conflicts across branches, and keeps column changes backwards compatible so the previous application version continues running during a rolling deployment.

Enables SQL logging to find the N+1 select behind a lazy collection, replaces it with a fetch join or entity graph, corrects fetch type and cascade settings, and checks the JDBC batch size on bulk inserts.

Implements producers and consumers with a sensible partition key, handles offset commit and retry semantics deliberately, adds a dead-letter topic for poison messages, and monitors consumer lag rather than assuming the group is keeping pace.

Manages dependency versions through the BOM or Gradle version catalogue, resolves conflicting transitive versions, strips unused dependencies, and upgrades libraries carrying published CVEs after reading the changelog for breaking API changes.

Keeps the build, test, SonarQube scan, container image and artefact publish stages working, repairs the stage that broke after an agent image change, and keeps the pipeline quick enough that the team does not route around it.

Reads teammates' changes for thread safety on shared state, blocking calls on reactive threads, resources never closed, exceptions swallowed into an empty catch, and log statements that would print personal data into Kibana.

Works from logs in Kibana or Splunk and traces in Datadog or New Relic to reproduce the fault, requests a heap or thread dump where memory pressure or a stuck pool is suspected, and writes the cause into the incident record.

Reviews garbage collection logs and heap sizing against the container memory limit, right-sizes the HikariCP pool against the database's connection ceiling, and sets timeouts so a slow downstream call fails fast instead of exhausting the thread pool.

Implements the Spring Security configuration for the OAuth2 or JWT scheme in use, validates token scopes at each endpoint rather than only at the gateway, and keeps credentials in the vault or config server instead of application.yml.

Keeps the OpenAPI specification generated from the code accurate, writes the README covering local setup and required environment variables, and records runbook steps for each alert this service raises so on-call is not guesswork.