Opening with EY_ Devops with Azure

Role & responsibilities

• Experience of IT service business and engineering of multi-year managed services
• From 5-8 years plus of demonstrable enterprise level IT delivery experienc3
• Cloud (3-5 years) in an engineering role using service and hosting solutions such as private/public cloud IaaS, PaaS and SaaS platforms. Experience in engineer technical solutions for Microsoft-centric solutions based on industry standards using Azure or other cloud providers IaaS, PaaS and SaaS capabilities. Nice to have Experience with any of the following: O365, Azure, Azure Stack, Azure AD
• Scripting (3-5 years) having knowledge and experience with Microsoft PowerShell (required) and Linux shell scripting (preferred). Being able to understand and use best practices of completing tasks and finding solutions using existing or building new scripts to help automate todays manual infrastructure and application tasks.
• Configuration Management (2-3 years) – being able to develop recipes for new solutions to deploy consistent systems, enforce configurations and settings through configuration management systems like PowerShell DSC, Chef or Puppet.
• Web Services, API, REST (1-2 years) – Understanding and having experience with leveraging web services (SOAP), different API endpoints including the usage of REST based APIs to be able to be able to build loosely coupled architectures and solutions that are quick to implement and are easy to monitor.
• Networking (1-3 years) - Have a solid understanding of networking capabilities, including load balancers, web application firewalls, network access control lists (NACLs), security groups, routing, tracing, DNS resolution are key to building efficient and stable solutions that prevent business downtime and provide high availability capabilities.
• Documentation (2-3 years) - Being able to create technical documents that provide insight into the design and implementation of a solution provides teams with the ability to effectively communicate their needs and requirements across the organization. The candidate has to be able to produce clear and concise architecture and design documentation that can assist his team and other peer groups in understanding of the built solutions. The candidate must also be able to communicate complex technical issues with sensitivity to diverse audiences and people with different level of technical understanding that range from entry level support teams, management, and technical engineering resources.
• Operational Support awareness (2-3 years) – A good understanding of what it takes to support the deployed applications and solutions is key to providing great service to the end users. The candidate has to be able to put themselves into a position of understanding of their consumer pain points to be able to figure out creative ways not only to find quick workarounds but also analyze the root cause of the problem and come up with ideas of resolving them in the long term.
• Source code management (1-3 years) – Familiarity with source control tools such as Git, Team Foundation Server (TFVC), and SVN are a big part of automation and compliance. Understanding how these tools are and could be used is key to not only provide the proper change control management to new versions of products that are being developed, but also to help provide consistency in deploying those products/solutions throughout environments using automation.