You will get your ASP.NET Core or .NET API bug fixed, with a regression test
Rising Talent
Project details
A bug that survives into production is rarely where the error message points. I find the root cause, fix it cleanly, and prove it with a regression test that fails before my change and passes after — so the same bug does not come back a week later.
I am a senior .NET engineer with 11+ years of production experience, currently building multi-tenant SaaS APIs that pass strict senior review and quality gates every day. I work on ASP.NET Core and .NET Framework, Web APIs, Entity Framework and EF Core, SQL Server, async and deadlock issues, and slow endpoints.
Every tier includes:
• A written root-cause note in plain language: what broke, why, and what changed
• A regression test proving the fix
• Code that matches your project's existing style and conventions
If the bug is bigger than one fix — recurring timeouts, deadlocks, N+1 queries — the Advanced tier adds profiling and before/after benchmarks, so you see the improvement instead of taking my word for it.
I communicate in writing and reply daily. A delivery is complete when the fix runs green in your project.
I am a senior .NET engineer with 11+ years of production experience, currently building multi-tenant SaaS APIs that pass strict senior review and quality gates every day. I work on ASP.NET Core and .NET Framework, Web APIs, Entity Framework and EF Core, SQL Server, async and deadlock issues, and slow endpoints.
Every tier includes:
• A written root-cause note in plain language: what broke, why, and what changed
• A regression test proving the fix
• Code that matches your project's existing style and conventions
If the bug is bigger than one fix — recurring timeouts, deadlocks, N+1 queries — the Advanced tier adds profiling and before/after benchmarks, so you see the improvement instead of taking my word for it.
I communicate in writing and reply daily. A delivery is complete when the fix runs green in your project.
Programming Languages
ASP.NET, C#Coding Expertise
Performance OptimizationWhat's included
| Service Tiers |
Starter
$10
|
Standard
$35
|
Advanced
$80
|
|---|---|---|---|
| Delivery Time | 2 days | 3 days | 5 days |
Number of Revisions | 1 | 2 | 2 |
Bug Investigation | |||
Fix Documentation | |||
Detailed Code Comments | - | - | - |
1 review
(1)
(0)
(0)
(0)
(0)
This project doesn't have any reviews.
JD
JD D.
Aug 5, 2026
Dynatrace WMI IIS Extension
Truly amazed by the effort of this project. Ahmed is the real deal.
About Ahmed
Senior .NET Developer | ASP.NET Core APIs, Azure, Cosmos DB, C#
Nanterre, France - 10:28 pm local time
What I do best:
• ASP.NET Core APIs — versioned REST APIs, role-based access control, multi-tenant architecture, FluentValidation, clean vertical-slice structure
• Azure data — deep Cosmos DB expertise (partition design, change-feed pipelines, indexing policies, zero-downtime backfills) plus SQL Server, PostgreSQL and EF Core with disciplined migrations
• Architecture — modular monoliths and microservices done right: CQRS, DDD, MediatR, Result-based error handling, contracts that never break consumers
• Integrations — e-signature providers, rate-limited government APIs, registry exports with strict file formats, RabbitMQ, Redis, SignalR real-time
• Full-stack when the job needs it — Angular, React and TypeScript front-ends shipped in production at Sodexo, Bolloré, TUI and Canon
• Quality — TDD with xUnit, SonarQube-clean code, benchmark-driven performance work. Every change ships production-ready.
How I work: small verified increments, before/after evidence for every performance claim, honest estimates, no surprises. My code survives strict senior review every single day — yours will get the same standard.
Available now for full-time or part-time engagements (100% remote, CET) — I reply daily.
Send me your API, performance, or migration problem and you'll get a concrete first step within 24 hours.
Steps for completing your project
After purchasing the project, send requirements so Ahmed can start the project.
Delivery time starts when Ahmed receives requirements from you.
Ahmed works on your project following the steps below.
Revisions may occur after the delivery date.
Reproduce and diagnose
I run your project, reproduce the bug, and pin the root cause, not just the symptom.
Fix with a regression test
A clean, minimal change plus a test that fails before the fix and passes after it.