.NET
Developer

Takes stories from the Azure Boards or Jira sprint, works within the established layering of controllers, services and repositories, writes C# to the team's existing conventions, and raises the pull request with the ticket linked and tests included.

Adds ASP.NET Core controllers or minimal API endpoints with model validation, correct status codes and DTOs that do not leak entity models, updates the OpenAPI definition, and versions the route instead of breaking existing consumers.

Adds Entity Framework Core migrations, reads the generated SQL before committing it, splits destructive column changes into add-backfill-drop steps, and checks the resulting query is not a Cartesian join hiding behind a lazily loaded navigation property.

Profiles slow requests through Application Insights or MiniProfiler, finds the LINQ pulling an entire table into memory, applies projection, AsNoTracking and split queries where they help, and re-measures before declaring it fixed.

Covers new logic with xUnit tests using Moq for dependencies, plus integration tests through WebApplicationFactory against a containerised database, so the build pipeline catches the regression rather than your customers finding it after release.

Reads teammates' changes for null handling, async-over-sync deadlocks, missing cancellation tokens, swallowed exceptions and connection strings committed into appsettings — leaving review comments that explain why the change matters, not just what to alter.

Maintains the Azure Pipelines or GitHub Actions YAML through restore, build, test, artifact publish and deployment to the App Service slot, and chases down the flaky test or expired service connection blocking everyone else's merges.

Implements hosted services, Hangfire jobs or Azure Functions for work that should not sit inside a web request — invoice generation, overnight file imports, webhook retries — with idempotency and structured logging so a re-run does not double-post.

Builds typed HttpClient wrappers with Polly retry and circuit-breaker policies for the services you depend on — payment gateways, Xero, courier and address validation APIs — handling token refresh and their non-standard error payloads properly.

Works through legacy WebForms or ASP.NET MVC applications: runs the upgrade assistant, replaces web.config configuration and HttpContext dependencies, swaps out abandoned NuGet packages, and moves one module at a time so the application keeps running throughout.

Reproduces the reported fault from Application Insights traces and exception telemetry, isolates it in a failing test first, fixes it and documents the cause on the ticket. Release into production is authorised by your team, not the developer.

Moves connection strings and API keys into Azure Key Vault or user secrets, keeps environment-specific settings out of source control, and makes sure a new developer can run the solution from a clean checkout using documented setup steps.