Parth T.

Azure and .NET engineer, Microsoft certified in Azure development in 2021: Top Rated, 100% Job Success, 1.1K+ hours and $20K+ earned on Upwork. I build production backends with .NET Core, Azure Functions, App Service and practical AI integrations. That experience spans 9+ years of .NET development, with current specialization in Azure-native backend systems. Most clients bring me one of four situations: • An existing .NET application needs better performance, cleaner APIs or a controlled modernization path. • An Azure workload needs Functions, App Service, SQL, Cosmos DB, Service Bus, deployment pipelines or cost review. • A business wants to add AI to an existing product without turning the system into an unreliable demo. • A manual process can be connected through APIs, n8n automation or an MCP integration. WHAT I BUILD • ASP.NET Core and .NET Core REST APIs • Azure Functions and event-driven backend services • Azure App Service deployments and Azure DevOps CI/CD • SQL Server, Azure SQL, PostgreSQL and Cosmos DB data layers • Service Bus, RabbitMQ, scheduled jobs and background processing • Microservices, API integrations and SaaS backend modules • AI-enabled integrations inside existing .NET applications • n8n workflows that connect business systems and APIs • MCP connections that give approved AI tools controlled access to business data or actions • Azure architecture and cost reviews based on the workload's real requirements AI-POWERED ENGINEERING, WITH ENGINEERING JUDGMENT I use AI to accelerate research, scaffolding, refactoring, testing and technical documentation. Generated code is still reviewed, understood and tested before it reaches a client environment. For AI features, I first define the input, expected output, permissions and human-review boundary. Then I add the model or tool connection, structured output, validation, logging, retries and error paths. This keeps the feature useful inside the business process instead of leaving it as a disconnected proof of concept. My recent technical work also includes multiple n8n automations and MCP integrations. I can connect those capabilities to a .NET and Azure system when they are the right fit. I will not force an AI agent, n8n or MCP into an architecture when a normal API or background service is the better answer. SELECTED PRODUCTION PROOF • 1075-hour backend engagement, $25,800 earned and 5.0 feedback. • 178-hour Lead Backend Engineer engagement using C#, .NET Core, Microsoft SQL Server, TypeScript and Docker, also rated 5.0. The client's review: “Great developer. Exactly what we needed.” • Energy monitoring and control platform work involving .NET 8, Azure Functions, Azure Data Factory, SQL Server, Cosmos DB, Service Bus, Blob Storage, Table Storage, tests and CI/CD. • Digital cabin platform work using .NET 8/10 microservices, RabbitMQ, Firebase notifications, Azure deployment, scheduled processing, Azure Functions and SQL Server audit data. • Microsoft Fabric user study completed for an Upwork Enterprise client with 5.0 feedback. • Prior Azure resource cost-management engagement. HOW I APPROACH AN EXISTING SYSTEM 1. Map the current architecture, failure points, data flow and deployment process. 2. Separate urgent fixes from architecture work that can wait. 3. Define a small first milestone with acceptance criteria. 4. Build with tests, useful logs and a deployment path the team can operate. 5. Document the decisions, known tradeoffs and recommended next steps. This approach works well for inherited codebases because it creates progress without pretending the whole system should be rewritten. When modernization is needed, I can help plan framework upgrades, separate backend responsibilities, move suitable workloads to Azure, and introduce messaging or serverless processing in controlled stages. AZURE COST AND DELIVERY DISCIPLINE Cloud architecture affects both engineering quality and monthly cost. I review hosting choices, resource sizing, storage patterns, database usage, scheduled workloads, monitoring and deployment flow before recommending more services. The answer may be Azure Functions, App Service, a background worker or a simpler API. The workload should decide. WORKING STYLE Clients have tagged my work as clear, reliable, solution-oriented, collaborative, accountable and detail-oriented. I communicate blockers early, keep milestones visible and explain technical decisions in business terms. If you have a .NET backend, Azure workload or AI integration to build or repair, send me the current stack, the main problem and the result you need. I will reply with the first architecture decision, the largest risk I see and a practical starting milestone.