OOP, REST, MVC, and ORM
Technology and Software Solutions
Solid understanding of OOP, RESTful APIs, MVC architecture, and ORM.
What this bullet means
The employer wants a foundation in how web apps are structured: models, controllers or pages, services, database mapping, and API boundaries.
Sample app idea
Support Ticket API and Admin Portal with ticket models, service classes, REST-style endpoints, MVC or Razor page structure, and ORM-backed persistence.
Main build outline
- Create entity models for users, tickets, categories, comments, and status history.
- Use an ORM such as EF Core to map entities to database tables.
- Build REST-style endpoints or page handlers for list, detail, create, update, and close actions.
- Keep business rules in services instead of placing them directly in the UI.
- Document the MVC or page flow and the object model in the README.
Portfolio proof
- Schema or entity relationship diagram in the README.
- Screenshot of a list and detail workflow backed by database records.
- README section mapping OOP, REST, MVC, and ORM to the project.
Minimal documentation
- README with the business problem, screenshots, setup notes, and technology stack.
- One requirements note that maps the job bullet to the sample feature.
- One test plan note with happy path, validation, and edge case checks.
- One honest portfolio note that says this is self-directed practice, not employer work.
Modern .NET stack
- Blazor Server or ASP.NET Core Razor Pages.
- C# services with validation and dependency injection.
- SQL Server locally, then SmarterASP SQL Server or Azure SQL.
- Optional Azure App Service, GitHub Actions, Docker, and AI helper feature.