Debugging and root-cause analysis
Website Support & Maintenance
Investigate broken website behavior across code, browser, database, hosting, and third-party integrations.
What this bullet means
The employer wants a repeatable troubleshooting approach that separates symptoms from the actual cause and confirms the fix before closing a ticket.
Sample app idea
WordPress Incident Log plugin using PHP, WordPress hooks, MySQL, JavaScript, and browser troubleshooting notes.
Main build outline
- Create a PHP WordPress plugin page for reproduction steps, browser details, affected URL, and screenshots.
- Use WordPress post metadata to keep symptom, root cause, workaround, and final fix separate.
- Add a PHP and JavaScript checklist that requires a browser test before an issue is closed.
Portfolio proof
- Issue detail screenshot showing reproduction steps, root cause, fix, and verification.
- Test notes that confirm the bug was checked on the affected browser and device.
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.