Employee Management API

Store, update, retrieve, and paginate employee records through an authenticated API.

CRUD over employee records, authenticated access, paginated reads, and documented endpoints — scoped deliberately small.

Controllers route requests to services and data-access objects. DTOs, validation, JPA entities, security configuration, and exception handling have separate responsibilities.

Use a layered Spring application for a bounded CRUD problem. A single relational database keeps persistence straightforward; pagination avoids returning the entire collection in one response.

This repository is an interview exercise. Its documented Basic Authentication and example credentials are development choices, not a production identity design. No deployment scale or employer ownership is implied.

Public documentation explains the package boundaries, PostgreSQL setup, secured access, and OpenAPI dependencies.

A bounded problem is the right place to be strict about layering. Keeping controllers free of persistence concerns cost nothing here and is the habit that pays off on larger domains.

Built as an interview exercise against a fixed brief and a short timebox, which set the scope deliberately narrow: one entity, one database, no infrastructure beyond what the task required.

Endpoints are authenticated, but the Basic Authentication and example credentials in the repository are development conveniences and not a production identity design. A real deployment needs token-based authentication, hashed credentials in a datastore, and secrets supplied by the environment.

Replace Basic Auth with token-based authentication, add integration tests that exercise the data layer rather than mocking it, and support filtering and sorting alongside pagination.