SQL Server backend data

What this bullet means

The employer needs a backend developer who can understand database tables, write useful queries, and connect application behavior back to stored data.

Sample app idea

Content Request Database with tables for pages, requests, approvals, issue logs, implementation steps, and deployment notes.

Main build outline

1. Create SQL Server-style tables for content pages, requests, approvals, issue logs, and release steps.
2. Write queries for open requests, overdue requests, issue frequency, and completed deployment notes.
3. Add read-only reporting views that summarize request status by customer, priority, and milestone.
4. Connect the application screens to database-backed records through a service or repository layer.
5. Document the schema and include sample queries in the README.

Portfolio proof

• Database schema diagram or SQL table screenshot.
• Saved SQL queries for requests, issues, reporting views, and milestones.
• README note explaining how the UI depends on SQL-backed records.

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.