Case Studies / Full-Stack Business Software
HR Operations Platform
A solo-built HR workflow platform connecting employee records, attendance, leave, payroll, policies, reporting, and role-based administration across web and mobile surfaces.
Verified delivery
- 3
- Connected product surfaces: backend, admin, and mobile
- PostgreSQL
- Shared operational data model
- Recorded
- Admin walkthrough with demo data
90-second walkthrough
Admin workflow walkthrough (demo data).
A short excerpt from a recording of the deployed admin portal. It covers organization setup, creating an employee, staff access, and the start of the attendance workflow, all with generated demo records.
Architecture and API proof
One data model across operator and employee workflows.
Sanitized from the implemented project structure and employee-directory GraphQL contract.
Records, approvals, payroll, policies, and reports
Attendance, requests, balances, and documents
One operational model for people, roles, attendance, leave, payroll, documents, and reporting.
Docker-based development runtime
Sanitized API sample
Employee directory query
A reduced read-only selection from the implemented admin query. It shows typed filtering and joined organizational data without exposing authentication, endpoints, IDs, or real employee information.
query EmployeeDirectory($filter: EmployeeFilterInput) {
employees(filter: $filter) {
employeeNumber
fullName
status
department { name }
designation { title }
}
}01 / Challenge
The workflow before the system
HR administration often joins records, attendance, leave, payroll support, documents, and management follow-up across separate files and tools.
02 / Approach
How I designed the response
I independently designed a modular NestJS and GraphQL backend, React admin portal, Expo mobile app, and PostgreSQL data model around those connected workflows.
- Authentication and account provisioning
- Company, department, and role settings
- Employee records and location assignment
- Attendance and leave workflows
- Payroll processing and payslips
- Policy documents and reporting
03 / Outcome
One connected HR system across backend, admin portal, and mobile app: role-based access, employee records, geofenced attendance, leave approvals, payroll, policy documents, and reporting. A full admin walkthrough is recorded on the deployed build with generated demo data.
04 / Workflow
Before
- Records and follow-up are split across spreadsheets and separate tools
- Attendance, leave, payroll, and documents need manual reconciliation
- Reports depend on repeated cleanup
With the system
- Set up companies, departments, roles, and employee records
- Employees record attendance and submit requests from the mobile app
- Managers review approvals, balances, documents, payroll, and reports
- Reports come straight from the same data model
05 / Engineering proof
Architecture
- Bun workspace: NestJS GraphQL backend, React admin portal, Expo mobile app
- Modular monolith with clear HR domain modules
- PostgreSQL with Docker-based local development
- Web admin and mobile app share the same backend workflows
Verified evidence
- Implemented modules: authentication, employees, attendance, leave, payroll, policies, and reporting
- Documented build, typecheck, and test commands for backend, admin, and mobile
- Recorded admin walkthrough on the deployed build, using generated demo data
06 / Judgment
Tradeoffs
- A modular monolith keeps deployment simple while keeping domains separate
Why it matters
- Turns scattered HR admin work into one connected workflow
- Shows ownership of backend, web, mobile, and the data model
What this proves
I can design and build full-stack business software on my own: backend, web, mobile, records, roles, approvals, and reporting.
Continue exploring