ERP Modules — Asset & Recruitment.
Two full ERP modules shipped to internal users during my internship — my first production software.
During my internship I built the Asset Management and Recruitment modules of an internal ERP in Angular and .NET — full CRUD workflows with role-based flows, integrated into existing systems and tested end-to-end before release.
- Role
- Developer intern
- Timeline
- Jan 2023 — Jul 2023
- Team
- Me + senior developers reviewing
- Users
- Internal operations & HR teams
01 — The problem
The problem
The company tracked assets and recruitment 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 ERP.
02 — What I built & learned
What I built & learned
Two full vertical slices — Angular frontends, .NET REST endpoints, SQL schemas. Asset Management covered the lifecycle from registration through assignment, transfer and retirement; Recruitment covered the pipeline from opening a role to closing it. Both had role-based flows and integrated with the ERP's existing auth and employee records rather than inventing parallel ones. It's where software became real for me: I learned that integrating with what exists is most of the job, that schema decisions outlive the code that made them, and to take review feedback as a gift.
If you only remember four things
- Full-stack vertical slices: Angular UI, .NET APIs, SQL schemas.
- Role-based flows integrated with existing ERP auth and records.
- Shipped to real internal users with end-to-end testing.