Serg M.
.NET Full Stack \ Blazor Developer / .Net Developer \ AI-Assisted Dev
.Net developer | Blazor developer | .Net full stack engineer | 15+ years in enterprise software | 5+ years in Blazor and modern .NET βοΈ You need one engineer who owns backend and UI instead of coordinating two. βοΈ Your legacy .NET app blocks every new feature and nobody wants to touch it. βοΈ Your reporting screens are so slow that users export everything to Excel. βοΈ Performance and tech debt have started reaching your customers. βοΈ You want software that survives the developer who wrote it. If any of that sounds familiar, we should talk. ββββββββββββββββββββ Core expertise ββββββββββββββββββββ I work as a .net developer first: C#, ASP.NET Core, APIs, SQL, and service boundaries that still make sense a year later. On top of that I ship as a blazor developer on blazor server and blazor webassembly, and I close the loop as a .net full stack engineer from schema to interface. Most of my work falls into three buckets: new business applications, migrations off aging .NET Framework code, and rescuing systems that grew faster than their architecture. Over 15+ years I have covered architecture, implementation, database design, and delivery, with C# as my primary language and SQL as the backbone of nearly everything I build. ββββββββββββββββββββ What I deliver ββββββββββββββββββββ As a .net developer I build asp.net, ASP.NET Core, ASP.NET Web API, ASP.NET MVC, .NET Framework, and .net core services with restful api backends that stay clean while the product grows. Data access runs on Entity Framework or tuned SQL against Microsoft SQL Server and MySQL, depending on what the workload deserves. As a blazor developer I build interactive applications with blazor webassembly, blazor server, .net blazor, and blazor c#, using MudBlazor plus blazor syncfusion or blazor telerik when a project needs dense grids and real reporting. Migration work is a specialty: .NET Framework and WCF systems moved to .net core in stages, each step deployable, no feature freeze. For cross-platform work I build with blazor maui as a maui developer and c sharp developer, applying a clean mvvm structure. Where serverless fits, I deploy with azure serverless and azure function. On the frontend I am comfortable with HTML, HTML5, CSS, CSS 3, JavaScript, and jQuery for classic web work, and with Angular, AngularJS, React, and Node.js when a project already lives there. I also handle Web Design, WordPress integrations, and light Adobe Photoshop work when a project needs an engineer with an eye as well as a compiler. ββββββββββββββββββββ Best-fit project types ββββββββββββββββββββ β’ Legacy .NET Framework to .net core migrations without a rewrite β’ New business applications built to outlive their first year β’ Reporting and back-office platforms with heavy data grids β’ Secure API and backend systems led by a .net developer β’ Blazor web platforms led by a blazor developer β’ .net full stack dashboards and internal tooling β’ Xamarin to MAUI moves and cross-platform apps ββββββββββββββββββββ Why clients hire me ββββββββββββββββββββ You get a senior .net developer who can own the domain model and the APIs, a blazor developer who ships the UI without a second contractor, and .net full stack ownership from the first commit to production. I finish features end to end instead of leaving seams between layers, I stay reachable after delivery, and I look for the cause instead of patching the symptom. When I disagree with a technical decision, I say so before it is expensive. π οΈ Broader collaboration scope I also work with Angular, AngularJS, React, Node.js as a react node developer, along with xamarin, wordpress, figma, Adobe Photoshop, Web Design, flutterflow, and obs for streaming setups. I can slot into a java developer heavy team and keep css responsive layouts consistent across devices. As an AI-Assisted Dev I use Cursor, cursor.ai, Claude, GitHub Copilot, and agentic ai in a review-first workflow: the tools draft, I verify, the tests decide. It speeds up refactoring, test coverage, and documentation without shipping code nobody understands. π§© Delivery approach Discovery β technical alignment β architecture definition β iterative implementation β documentation β handover. You always know what is being built, why, and what comes next. π Availability Based in Ukraine with solid working overlap for EU and US teams. I communicate clearly in English, keep a predictable schedule, and treat your codebase like it has to outlive the contract, because it usually does. If you need a senior .net developer, a strong blazor developer, and real .net full stack ownership in one hire, let's talk.