Backend APIs and data capture
IoT Digital Platforms
Build small backend services and API endpoints that support forms, integrations, and useful data capture.
What this bullet means
The employer wants web work that goes beyond screens: forms should save data, API routes should be clear, and backend logic should support reporting or follow-up actions.
Sample app idea
Lead Capture API for product interest forms, saved submissions, validation results, and follow-up status tracking.
Main build outline
- Create a backend endpoint for contact, demo request, or product interest submissions.
- Validate required fields and show friendly error messages in the frontend.
- Store submissions in SQL with status, source page, created date, and follow-up notes.
- Add REST-style documentation with example request and response shapes.
- Write tests for validation, successful save, and duplicate or incomplete submissions.
Portfolio proof
- API route list with sample request and response examples.
- SQL schema or database screenshot showing captured web submissions.
- Test output covering form validation and backend save behavior.
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.