Cloud Engineer

This is Onsite Position which can be worked from any *** Approved Office Location.

• Can you please provide a summary of the project/initiatives which describes what’s being done? This is a Platform Engineering position mainly works on Azure Cloud Environment.
• What are the top 5-10 responsibilities for this position? (Please be detailed as to what the candidate is expected to do or complete on a daily basis)
• 1.Creating Infrastructure in Azure CSP using Terraform and ADO .
• 2.Creating IAC Pipelines using Git Lab runners.
• 3.Strong working knowledge about resources in Microsoft Azure .
• 4.Work with different App teams to understand the Adhoc Requirements , troubleshoot the existing platform related issues and implement the changes.
• 5.Strong Knowedge in converting ADO pipines in to Terraform IAC Pipeines.
• 6.Should be good Understanding and Hands on experience in creating and trouble shooting the issues related Azure Data Factory , VNET's, Route tables , NSG , Purview , Azure storage , Appication Contexts , AKV , Subscriptions
• 7.Building custom VM images using Packer.
• What skills/technologies are required (please include the number of years of experience required)? Hands on Experience on Ansible , Azure , Azure ADO , Got Lab Runners , Azure VM , Azure Image Services , Terraform ,
• What skills/attributes are preferred (these are a desired, not required)? AWS, Python , Hashi Corp , Gitlab Runners.
• What does the interview process look like?
  o How many rounds? 2 Rounds
  o Video, phone, or in person? Teams Video
  o How technical will the interviews be? Will covering Medium to Advanced topics on Azure Platform .
  
  1.Creating Infrastructure in Azure CSP using Terraform and ADO .
  2.Creating IAC Pipelines using Git Lab runners.
  3.Strong working knowledge about resources in Microsoft Azure .
  4.Work with different App teams to understand the Adhoc Requirements , troubleshoot the existing platform related issues and implement the changes.
  5.Strong Knowedge in converting ADO pipines in to Terraform IAC Pipeines.
  6.Should be good Understanding and Hands on experience in creating and trouble shooting the issues related Azure Data Factory , VNET's, Route tables , NSG , Purview , Azure storage , Appication Contexts , AKV , Subscriptions
  7.Building custom VM images using Packer.
  8.Deploying and troubleshooting Azure Windows / Linux VMs, Scale Sets and Load balancers.
  9.Deploying and troubleshooting App Services / Function Apps and Azure Automation accounts.
  10. Supporting Weekly Releases on Non Business hours.
  11. Should have good knowledge about creating Jira Tasks , Service Now Change requests.
  
  
  

  Is this a remote position? If not, what *** locations can a resource work and how many days a week will they be required to work onsite? OnSite position(Mandatory 3 to 4 days in a week) .Any *** preferred location.

  
  
  • Can you please provide a summary of the project/initiatives which describes what’s being done? Working on Various Project initiatives around Infrastructure automation and trouble shooting activities in Azure CSP.
  • What are the top 5-10 responsibilities for this position? (Please be detailed as to what the candidate is expected to do or complete on a daily basis) . Working on Various Project initiatives around Infrastructure automation and trouble shooting activities in Azure CSP and PROD support activities.
  • What skills/technologies are required (please include the number of years of experience required)? Terraform , Ansible , Azure Networking concepts , Azure Trouble shooting , Git Lab , Git Lab runners , ITSM Service Now , Jira . Advanced in depth knowledge about Azure servircies and Automation.
  • What skills/attributes are preferred (these are a desired, not required)? Certifications in Azure , Hashi Corp Terraform.
  • What does the interview process look like?
    o How many rounds? 2 Rounds
    o Video, phone, or in person? Team Video Interview.
    o How technical will the interviews be? Covering Medium and Advanced Concepts Azure services , Networking Trouble shooting , Terraform automation , Ansible Automation.
  
  
  
  ------------------------DO NOT EDIT BELOW THIS LINE, PLEASE INSERT JOB DESCRIPTION ABOVE--------------------------------- A cloud engineer is an IT professional responsible for any technological duties associated with cloud computing, including design, planning, management, maintenance and support. Job Responsibilities for Cloud Engineer: ï1⁄2Installs and maintains cloud-based applications, systems, and associated infrastructures. ï1⁄2Translates business requirements into code and documentation while managing the life-cycle and communication for assigned projects. ï1⁄2Analyzes and defines business requirements to determine specifications and standards. ï1⁄2Oversees the proper implementation and integration of web and cloud-based applications. ï1⁄2Stays informed of emerging cloud technologies and evaluates the value to the organizationï1⁄2s operations. ï1⁄2Monitors system performance, troubleshooting and resolving errors. ï1⁄2Ability to consult with internal and external resources to develop cloud solutions for a range of products. ï1⁄2Ensures quality of the solutions are robust, scalable and efficient to meet the needs of the business. Knowledge and Skills for Cloud Engineer ï1⁄2Requires experience with one or more cloud platform. ï1⁄2Experience working with large infrastructure hosting environments including knowledge of Application Hosting, distributed messaging architectures, network technologies (Ex: VPNs, TCP/IP, Firewalls, Routing, etc.), security technologies (Ex: public key cryptography and infrastructure, smart cards, authentication, authorization, etc.). ï1⁄2Demonstration of thorough understanding of how discrete infrastructure components work together to provide reliable and secure hosting environment. ï1⁄2Vast understanding of cloud services and solutions in platforms such as Azure or AWS ï1⁄2Comprehensive understanding of IT security best practices and threat protection ï1⁄2Must have a good understanding of connected embedded systems tradeoffs, protocols, etc.