What the system had to solve
The product connects a public job portal with internal HR operations. That means the system must support different levels of trust: a candidate uploading an application, a recruiter reviewing a profile, a manager working with employee data, and administrators controlling companies and catalogs.
Architecture at a glance
Open interactive architecture ↗
Module structure
Vacancy discovery, candidate application, document upload, and tracking-code follow-up for applicants.
Vacancies, candidates, viability, interviews, hiring decisions, and the transition from application to employee.
Digital employee files, profile changes, supporting documents, training, performance, benefits, and review workflows.
Partner-company administration and role-aware data scope so users operate within the records they are authorized to see.
Excel and PDF reports, availability and performance indicators, and operational summaries for decision-making.
Reusable catalogs, email templates, scheduled notification tasks, and activity logging to keep operations traceable.
Security and quality improvements
The system includes BCrypt password handling with transparent upgrade of legacy hashes, reCAPTCHA host validation, file-type and size checks, scoped resource access, audit fields, migration-driven schema changes, and automated tests around critical controller and business cases.
This project demonstrates the ability to work across a real business domain: translating HR processes into modules, protecting sensitive records, evolving a relational schema, and supporting both public and internal users in one platform.
Engineering lessons
Enterprise software quality often comes from the details around the happy path: permissions, review states, auditability, file handling, migrations, email failure states, and the ability to test workflows without exposing secrets or personal documents.