Backend
Hire .NET Developers
.NET engineers who are equally at home in modern .NET and in the Framework estates still running the business.
.NET earns its place where correctness, tooling and long support horizons matter more than fashion. It is also where a great deal of unglamorous value sits, because a large share of working enterprise software is still on .NET Framework 4.x, out of support in all but name, and running something nobody can afford to switch off.
When hiring, the distinction worth probing is whether someone has actually migrated an application or only worked on one already migrated. Ask how they broke a monolithic Framework application into shippable stages, what they did about a dependency with no .NET Core equivalent, and how they proved the behaviour was identical afterwards. That answer is worth more than any list of frameworks.
What these engineers do
- ASP.NET Core 8 and 9, minimal APIs and MVC with dependency injection used cleanly
- Entity Framework Core, migrations and query tuning on SQL Server or PostgreSQL
- Blazor and Razor for internal tooling where a separate SPA is not worth its cost
- Migration from .NET Framework 4.x to modern .NET without a single big-bang cutover
- Azure App Service, Service Bus and Application Insights in production
Delivered AI-first
Legacy migration is where AI assistance pays for itself in .NET. Assistants are effective at translating Framework-era patterns into their modern equivalents - Web API controllers to minimal APIs, WebForms code-behind into services, System.Web dependencies into abstractions, old EF6 mappings into EF Core - and at generating the characterisation tests that prove behaviour did not change. Every converted file is reviewed, and the tests decide whether the translation held. The measurable effect is throughput per engineer, not fewer reviews.