Architecture and feature planning

What this bullet means

The employer wants a junior engineer who can think about design tradeoffs, ask good questions, and connect feature ideas to the existing system.

Sample app idea

Feature Proposal Tracker for capturing feature ideas, affected screens, data changes, risks, and architecture notes.

Main build outline

1. Create feature proposal records with goal, user value, affected pages, and affected data.
2. Add fields for risks, dependencies, open questions, and suggested architecture approach.
3. Build a review status workflow for draft, discussed, approved, deferred, and rejected.
4. Add a detail page that makes tradeoffs easy to scan.
5. Document one feature proposal with a small diagram or table.

Portfolio proof

• Screenshot of a feature proposal detail page.
• README architecture discussion note.
• Small feature-impact table.

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.