Principal .Net Architect

Position: Lead/Principal .Net Developer/Senior Architect Locations: Remote Duration: 6+Months with possible extensions Key skills: .Net, React, Azure Cloud, AI Engineering (Github copilot preferably or others), MS SQL Description : We are seeking a highly skilled and motivated Principal Engineer/SA/Tech Lead to take full ownership of end-to-end application development. This is a hands-on, individual contributor role for a technologist who thrives on building robust, scalable solutions and is passionate about leveraging AI and cloud technologies. You will be responsible for designing, developing, and delivering complex applications, ensuring technical excellence at every stage. This is not a management, consulting, or general architect position your focus will be on execution and delivery. Key Responsibilities: Take full technical ownership of the entire application development lifecycle, from requirements analysis and design to implementation, deployment. Design and build scalable, high-performance applications. Use AI (at least Copilots) Collaborate with product owners and other engineers to deliver high-quality solutions that meet business objectives. Write clean, maintainable, and well-documented code; perform code reviews Troubleshoot, debug, and optimize applications Required Qualifications: 10+ years of hands-on fullstack development experience (.NET+ReactJS), with a proven track record of delivering complex applications end-to-end. Strong proficiency with Azure, MS SQL. Usage of AI tools(GitHub Copilot is preferred) Solid understanding of modern software architecture patterns (microservices, serverless, event-driven, etc.). Experience with CI/CD pipelines, containerization (Docker, Kubernetes), and infrastructure as code. Excellent problem-solving skills, attention to detail, and a relentless drive for technical excellence. Self-motivated, hard-working, and able to work independently with minimal supervision. Strong communication skills, able to articulate technical concepts clearly to technical and non-technical stakeholders.