Senior .NET Web Maintenance
Budget: ₹1,500 – ₹12,500 INR
I need an experienced .NET developer—five years or more working hands-on with C# and SQL Server—to step into an existing web application and keep it moving forward. The solution is already live and in daily use, so you’ll be working against a real-world codebase, not a green-field prototype.
The core stack is ASP.NET (a mix of MVC and newer .NET Core services) with a SQL Server back-end. I rely on Entity Framework for data access, Git for version control, and a straightforward CI/CD pipeline. You should feel comfortable reading and refactoring legacy code, designing new features that slot cleanly into established patterns, and optimising T-SQL when a query starts slowing things down.
Key things I’ll be asking you to do:
• Review and refactor existing modules for maintainability and performance
• Design and implement new web features from the backlog
• Tune SQL queries, create or modify stored procedures, and keep the DB schema clean
• Write concise unit tests and supply clear, comment-light code that explains itself
• Submit pull requests with notes that make code review painless
A successful hand-over will be measured by build-pipeline green lights, peer-approved pull requests, and a short knowledge-transfer session that leaves the next person confident in your changes. If that sounds like a typical Tuesday for you, let’s talk timelines and milestones.
The core stack is ASP.NET (a mix of MVC and newer .NET Core services) with a SQL Server back-end. I rely on Entity Framework for data access, Git for version control, and a straightforward CI/CD pipeline. You should feel comfortable reading and refactoring legacy code, designing new features that slot cleanly into established patterns, and optimising T-SQL when a query starts slowing things down.
Key things I’ll be asking you to do:
• Review and refactor existing modules for maintainability and performance
• Design and implement new web features from the backlog
• Tune SQL queries, create or modify stored procedures, and keep the DB schema clean
• Write concise unit tests and supply clear, comment-light code that explains itself
• Submit pull requests with notes that make code review painless
A successful hand-over will be measured by build-pipeline green lights, peer-approved pull requests, and a short knowledge-transfer session that leaves the next person confident in your changes. If that sounds like a typical Tuesday for you, let’s talk timelines and milestones.
Related categories:
.NET
C# Programming
Software Development
ASP.NET
Git
Web Development
.NET Core
CI/CD