Company: Help Me Buddy IT Pvt. Ltd.
Duration: 18 May 2026 – 28 June 2026
| Item | Details |
|---|---|
| Duration | 6 Weeks |
| Company | Help Me Buddy IT Pvt. Ltd. |
| Project | VendorBridge ERP |
| Backend | ASP.NET Core Minimal API |
| Frontend | React |
| Database | PostgreSQL |
| ORM | Entity Framework Core |
| Authentication | JWT |
| Architecture | Layered Architecture |
| APIs | REST |
| Documentation | Swagger |
During my summer internship at Help Me Buddy IT Pvt. Ltd., I worked on a real-world ERP application called VendorBridge.
VendorBridge is a Procurement & Vendor Management ERP that helps organizations manage their complete procurement workflow digitally—from vendor registration to purchase orders and invoices.
This internship was my first experience building a large-scale backend using ASP.NET Core Minimal APIs and Entity Framework Core.
Before this internship, I had experimented with .NET but had never built a complete production-style application.
I wanted to understand how modern backend systems are designed beyond simple CRUD applications.
ASP.NET Core Minimal APIs appealed to me because they provide a lightweight approach to building REST services while still supporting dependency injection, middleware, authentication, validation, and Entity Framework Core.
This internship gave me an opportunity to apply these technologies to a real business problem.
Many companies still manage procurement using Excel sheets, emails and paper documents.
This creates several problems:
VendorBridge solves these problems by bringing the entire procurement lifecycle into one application.
One of the biggest lessons from this internship was learning that software is not just about writing APIs.
Every feature starts with understanding a business workflow.
Instead of asking:
“What tables do I need?”
I learned to ask:
“How does procurement actually work?”
Understanding vendors, RFQs, quotations, approvals, purchase orders, and invoices helped me design a backend that reflected real-world business processes.
The hardest part wasn’t writing code—it was understanding procurement itself.
Terms like:
were completely new to me.
I spent the first few days learning the business process before implementing the database schema.
This internship changed how I approach backend development.
Some important lessons were:
If I had more time, I would add several production-ready improvements.
Rather than focusing only on CRUD operations, I tried to build features commonly found in production software.
Some examples include:
The backend follows a layered architecture.
React Frontend
↓
REST APIs
↓
Minimal API Endpoints
↓
Business Logic
↓
Entity Framework Core
↓
PostgreSQL
Keeping the application modular made it easier to maintain and extend.
Procurement officers can
Vendors can submit quotations for published RFQs.
One of my favorite modules.
The system compares vendor quotations based on
making vendor selection much easier.
Managers review procurement requests before purchase orders are generated.
This creates a proper approval chain inside the organization.
After approval,
The ERP automatically creates invoices which can later be exported as PDF.
The dashboard provides
which helps management take better decisions.
The project contains multiple interconnected tables including
Entity Framework Core handled relationships and migrations efficiently.
This internship taught me much more than simply writing APIs.
I learned
Designing relationships was much harder than writing controllers.
Choosing where to place foreign keys, handling cascading deletes, and modelling approval workflows required several iterations before arriving at a clean design.
Designing relationships between multiple modules was challenging.
Thinking through foreign keys and business rules took much longer than writing CRUD APIs.
Implementing secure authentication with JWT and role-based authorization helped me understand how modern backend applications protect APIs.
By the end of the internship I had built a complete backend application using modern Microsoft technologies.
More importantly, I became comfortable with
This project gave me confidence to build larger backend systems in the future.
When I started this internship, I thought backend development was mostly about writing CRUD APIs.
By the end, I realized that backend engineering is really about solving business problems through software design.
Building VendorBridge taught me how authentication, database modelling, API design, and business workflows fit together to create a complete application.
This internship strengthened my interest in backend engineering and gave me confidence to build larger systems using the .NET ecosystem.