Java/Spring and React stack

What this bullet means

The employer wants full-stack comfort with a backend service framework and a modern JavaScript frontend. For a C# portfolio, the honest match is showing the same architecture patterns with .NET while noting any Java or React practice separately.

Sample app idea

Claims Intake Portal with a service-based backend, REST endpoints, form validation, and a React-style responsive frontend workflow.

Main build outline

1. Build a small claims intake workflow with a backend endpoint for creating and retrieving claim records.
2. Create frontend screens for claim entry, confirmation, search, and detail review.
3. Keep validation rules shared in backend services and display friendly validation messages in the UI.
4. Add a README note mapping the backend framework, API route, frontend component, and database table responsibilities.
5. Include an honest technology note separating built portfolio skills from technologies still being practiced.

Portfolio proof

• Screenshot of claim intake and claim detail screens.
• README section mapping frontend screens to backend API endpoints.
• Commit history showing backend and frontend work in separate, readable steps.

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.