Azure .Net Developer(AIS)

Job Description

Job Location: Pan India Responsibilities Job Description Around 3-8 years of IT experience in developing Integrations/APIs solutions or relevant solution development A min of 2 to 4 years of relevant experience with Azure Integration Services like Azure Logic Apps, Azure Functions. Strong Knowledge of Azure PaaS components like Azure Storage, Azure Logic Apps, Integration account, creating schema maps using visual studio in integration account ,Azure Functions, API Management, Key Vault, Service Bus Proficient with Azure Platform Development (Azure Functions, Azure Services, Azure Storage, Logic Apps) Should have good understanding of Azure VM, VNET, Storage, Subscriptions, Security Knowledge of working with ARM template and service principle Detailed understanding of end-to-end best practice across the API / integration lifecycle An understanding of the business domain and its language. The ability to elicit requirements from the business and the ability to understand the specifications of the data sources Knowledge of project delivery methodologies, including Lean and/or Agile and/or DevOps Knowledge of IT security and compliance requirements Experience in working with the larger teams, natural teams, speeded across various regions Good to Have Configure and manage CI/CD pipelines (e.g., source control, build tool, CI server, artifact and dependency repository, etc.) ERP knowledge (D365/SAP IDOC file processing) is advantage Experienced with either MuleSoft, Microsoft Biztalk or SQL Server Integration Service Roles and Responsibilities Build, design, and deploy solutions, new integrations/APIs and update existing API functionalities (enhancements or bugfixes) on Azure Integration Services ( Logic Apps, APIM & Azure functions) and update existing APIs functionality (enhancement/defect fix); Unit/UAT Testing of the API integration Works from written specifications and pre-established guidelines to perform the functions of the job and maintains documentation of process flow/ validate the solution end to end before any implementation Documentation should be produced in parallel to the implementation so that the assets can easily be understood in Exchange and elicit feedback