WorkZen organizes common HR workflows into a backend domain for employee records, attendance, leave and payroll.
The problem
HR data combines personal records with workflow state and calculations. The system needs authenticated access, role boundaries, consistent persistence and auditable decisions.
Technical deep dive
How the system holds together.
HR Domain
The documented domain covers employees, attendance, leave and payroll. Salary and tax calculation are treated as business logic rather than presentation-only arithmetic.
Authentication and RBAC
Spring Security and JWT provide the documented authentication foundation, while role-based access control separates protected HR actions.
Auditability
HR workflows benefit from traceable state changes. Exact audit tables and fields are not claimed without the implementation source.
Diagrams
System surfaces.
ARCHITECTUREWorkZen Architecture
DATABASEHR Data Model
Engineering decisions
Why I made these decisions.
Why PostgreSQL?
Relational persistence suits connected HR records and workflow state.
Why JWT and RBAC?
HR operations need authenticated users and explicit boundaries around protected data.
Why calculate salary in the backend?
Salary and tax rules belong close to validated domain inputs, not only in a client UI.
Testing
The page describes the documented domain and security concerns without inventing coverage metrics.
Deployment & DevOps
No deployment service is claimed beyond the technologies documented in the portfolio.