Full-stack development in a final-year team project
Status
Final-year project in development
Technologies and practices
Java 21 · Spring Boot · React · PostgreSQL
Starting point
Disconnected profiles and opportunities
→
What I deliver
Identity and communication platform
→
What this enables
Find and connect in one place
Responsible for the work described
Anny Gabrielly
Where to access
On the web · Open project link
Project stage
Final-year project in development
Real capture of the public interface · October 30, 2026
The problem
Professionals and companies need a space to introduce themselves, find opportunities and communicate. In this academic project, that also means handling different identities, permissions, persistence and account consistency.
What I built
In Help, my Software Engineering final-year project, I work on a full-stack platform with professional profiles, a feed, jobs, courses, messages and notifications. The React frontend communicates with a Java/Spring API with backend authentication and rules.
Impact across front and back
Front-end
Profiles, search and communication in a React interface. Flows need to reflect the active account and keep names, photos and state consistent across screens.
React
Vite
Estado da sessão
Back-end
A Java/Spring API with JWT authentication, account-type rules and persistence. Identity, profile isolation, session, message and notification tests support the platform’s evolution.
Java 21
Spring Security
PostgreSQL
JWT
Decisions behind the solution
Identity in every operation
Users and companies have dedicated flows. Sessions and authenticated participants are handled in the backend to prevent profile data mixing.
Communication across account types
Messages, followers and notifications account for sender and recipient identities, with dedicated tests for social scenarios.
From local development to deployment
H2 for development and PostgreSQL for production. Backend and frontend have separate responsibilities and environment configuration.
Beyond the happy path
Tests cover isolation, session changes, tokens and communication; an operational checklist guides checks with four accounts.
Verification matrix for two users and two companies; a checklist is not an executed result.
Results in context
An evolving academic team project. This case presents my full-stack work and project evidence without treating interface demo content as employment outcomes.
