Java Development Internship

Build backend services the way enterprises actually build them.

Java runs a very large share of the banking, insurance and enterprise systems that quietly keep working. This programme covers Spring Boot, layered architecture, testing and persistence — the stack most Indian enterprise hiring still asks for.

Beginner-friendly4 weeks · remote4 briefs · complete any 2Free to join

What you'll be able to do

Build a REST service with Spring Boot
Structure an application into layers that stay separate
Write tests that survive refactoring
Map objects to a relational database without fighting the ORM

Who it suits

Students who have learned Java syntax and want to build something an employer recognises.

What you'll work with

Java 17+
Spring Boot
JUnit 5
JPA/Hibernate
PostgreSQL
Maven

The project briefs

Complete any 2 of these 4to finish the programme. Assessment criteria are published here so you know what “good” means before you start.

Spring Boot REST Service

~12h estimated

Build a working API with proper layering.

Controller, service, repository — kept genuinely separate. The test of separation is whether you can swap the database without touching the controller.

Assessed against

Five or more endpoints with correct HTTP semantics
Controller, service and repository layers with no leakage
Bean validation on inputs
Consistent error responses, never a raw stack trace

You'll finish with

GitHub repo
API documentation

Persistence with JPA

~12h estimated

Model related data and query it efficiently.

At least three related entities. Then find your N+1 query problem — you will have one — and fix it. Prove it with the generated SQL.

Assessed against

Three or more entities with real relationships
An N+1 problem identified and fixed, with SQL logs as evidence
Database migrations, not schema auto-generation
Transaction boundaries chosen deliberately

You'll finish with

GitHub repo
Migration files
SQL logs before and after

Test Suite That Survives Refactoring

~10h estimated

Write tests that break when behaviour breaks, not when code moves.

Unit tests for logic, integration tests for wiring. Then refactor something internal without changing behaviour — good tests stay green.

Assessed against

70%+ coverage on the service layer
Integration tests using an in-memory or containerised database
A refactor performed with tests staying green
At least one test that genuinely catches a bug you introduced

You'll finish with

GitHub repo
Coverage report
Note on the refactor

Secure and Package for Deployment

~10h estimated

Add authentication and make it deployable.

Spring Security with JWT or session auth, then containerise. Configuration must come from the environment, never from a committed properties file.

Assessed against

Protected endpoints that genuinely reject unauthenticated calls
Configuration externalised, secrets never committed
A Dockerfile that builds and runs
A documented startup procedure someone else can follow

You'll finish with

GitHub repo
Dockerfile
Deployment notes

Free to apply and free to complete. The completion certificate is optional.

Other domains

AI Agents & Automation

Build autonomous agents that use tools, not chatbots that answer questions.

Generative AI & LLMs

Go past prompt tinkering into retrieval, evaluation and cost control.

Machine Learning

Classical ML done properly — including the evaluation everyone skips.

Ready to Transform Your Enterprise with AI?

Book a free 30-minute consultation with our AI architects. Discover how agentic AI can automate your workflows and multiply your team's output.

No commitment required · Free architecture review · NDA protected

Java Development Internship

Build backend services the way enterprises actually build them.

Beginner-friendly4 weeks · remote4 briefs · complete any 2Free to join

The project briefs

Complete any 2 of these 4to finish the programme. Assessment criteria are published here so you know what “good” means before you start.

Spring Boot REST Service

~12h estimated

Build a working API with proper layering.

Controller, service, repository — kept genuinely separate. The test of separation is whether you can swap the database without touching the controller.

Assessed against

Five or more endpoints with correct HTTP semantics
Controller, service and repository layers with no leakage
Bean validation on inputs
Consistent error responses, never a raw stack trace

You'll finish with

GitHub repo
API documentation

Persistence with JPA

~12h estimated

Model related data and query it efficiently.

At least three related entities. Then find your N+1 query problem — you will have one — and fix it. Prove it with the generated SQL.

Assessed against

Three or more entities with real relationships
An N+1 problem identified and fixed, with SQL logs as evidence
Database migrations, not schema auto-generation
Transaction boundaries chosen deliberately

You'll finish with

GitHub repo
Migration files
SQL logs before and after

Test Suite That Survives Refactoring

~10h estimated

Write tests that break when behaviour breaks, not when code moves.

Unit tests for logic, integration tests for wiring. Then refactor something internal without changing behaviour — good tests stay green.

Assessed against

70%+ coverage on the service layer
Integration tests using an in-memory or containerised database
A refactor performed with tests staying green
At least one test that genuinely catches a bug you introduced

You'll finish with

GitHub repo
Coverage report
Note on the refactor

Secure and Package for Deployment

~10h estimated

Add authentication and make it deployable.

Spring Security with JWT or session auth, then containerise. Configuration must come from the environment, never from a committed properties file.

Assessed against

Protected endpoints that genuinely reject unauthenticated calls
Configuration externalised, secrets never committed
A Dockerfile that builds and runs
A documented startup procedure someone else can follow

You'll finish with

GitHub repo
Dockerfile
Deployment notes

Free to apply and free to complete. The completion certificate is optional.