ERP Modules — Asset & Recruitment.

The company tracked assets and recruitment pipelines in spreadsheets — no audit trail, no ownership history, no single view of where a laptop or a candidate actually was. Both processes needed proper modules inside the existing internal ERP.

Two modules, each a full vertical slice: Angular frontends, .NET REST endpoints, and relational schemas underneath. Asset Management covered the asset lifecycle — registration, assignment to employees, transfers, and retirement — with the state history queryable. Recruitment covered the hiring pipeline from opening a position through candidate stages to closure.

Both had role-based flows (an employee sees their assigned assets; an admin manages the fleet), and both had to integrate cleanly with the ERP's existing authentication and employee records rather than inventing parallel ones.

This was where software became real for me: actual users, existing systems to respect, and senior developers reviewing my code. I learned that integrating with what exists is most of the job, that end-to-end testing before release is what lets you sleep, and that schema decisions outlive the code that made them. It's also where I learned to take review feedback as a gift — the habits from those reviews are still in my code today.