Clean code, tests, and reviews
Influencer Marketing SaaS
Write clean, maintainable, tested, and well-documented code while participating in code reviews and following best practices.
What this bullet means
The employer wants code that can survive a team environment: readable names, small methods, tests, documentation, review feedback, and no mystery behavior.
Sample app idea
Campaign Deliverable Tracker with validation, service-layer tests, README setup notes, and a code-review checklist.
Main build outline
- Create validation rules for required campaign fields, budget range, due dates, and deliverable status.
- Write focused service tests for validation and status-change behavior.
- Add a README section for setup, test running, architecture, and coding standards.
- Use a code review checklist for naming, small methods, error handling, tests, and no secrets.
- Show one before-and-after refactor in the commit history.
Portfolio proof
- Test results screenshot or terminal output.
- README setup, test, and coding standards sections.
- Code review checklist included in the repository documentation.
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.