Java Spring Boot REST API Development
Budget: ₹12,500 – ₹37,500 INR
I’m setting up a series of REST services built on Java 17 with Spring Boot and need an experienced backend developer to take ownership of both new features and ongoing maintenance. The core of the work is writing clean, test-covered code that exposes reliable, versioned endpoints, backed by a MySQL data store accessed through JDBC and, where appropriate, JPA/Hibernate. All modules sit in a microservice architecture and are managed through Git, so solid branching and pull-request discipline is essential.
While the focus is the backend, it will help if you can speak the same language as our UI team; they primarily work in React and Angular with plenty of vanilla JavaScript, HTML, CSS, Bootstrap—and the occasional PHP snippet for legacy views—so being able to align contract-first API design with frontend needs is a big plus.
I expect:
• Well-structured Spring Boot projects (Gradle or Maven)
• REST endpoints that follow standard HTTP semantics and return consistent JSON
• Swagger/OpenAPI docs generated automatically and kept in sync
• Unit and integration tests (JUnit, Testcontainers or similar) integrated into CI
• Regular, incremental commits with clear messages and timely pull-request reviews
Deliverables are considered complete when the code merges cleanly into main, the pipeline passes, and the new endpoints are reachable in our staging cluster with documentation available at /swagger-ui.
If you enjoy crafting scalable microservices and can hit agreed timelines without sacrificing code readability, let’s talk.
While the focus is the backend, it will help if you can speak the same language as our UI team; they primarily work in React and Angular with plenty of vanilla JavaScript, HTML, CSS, Bootstrap—and the occasional PHP snippet for legacy views—so being able to align contract-first API design with frontend needs is a big plus.
I expect:
• Well-structured Spring Boot projects (Gradle or Maven)
• REST endpoints that follow standard HTTP semantics and return consistent JSON
• Swagger/OpenAPI docs generated automatically and kept in sync
• Unit and integration tests (JUnit, Testcontainers or similar) integrated into CI
• Regular, incremental commits with clear messages and timely pull-request reviews
Deliverables are considered complete when the code merges cleanly into main, the pipeline passes, and the new endpoints are reachable in our staging cluster with documentation available at /swagger-ui.
If you enjoy crafting scalable microservices and can hit agreed timelines without sacrificing code readability, let’s talk.