PowerShell Developer

Job Description

Greetings from Reliable Software Resources Inc!!!

This is Sreekanth G from Reliable Software Resources Inc and I am writing to see whether you are interested in an exciting/challenging opportunity at Peoria, IL Onsite.

Our client is interested in hiring a Powershell Developer who can use Powershell and VMWare, and SVN.

Please let us know whether you would like to be considered. We hope you do as this is truly a great opportunity to make a difference. If you are interested please respond back to this e-mail with your updated resume and a summary of your key skills and the compensation you are looking for. You can also reach me at 248-237-7009.

The details of the position are as mentioned below:

Kindly find the JD below for your reference

Title: Powershell Developer

Location: Peoria, IL

Duration: Long term

Term: Contract / Fulltime 

Interview Process: Phone then Skype/On-Site

Remote Option: No

Required: Tasks & Duties

Excellent communication Skills are required 

1. 3+ years of Powershell Scripting: PowerShell Guru (understands how PowerShell interacts with API). 

2. Automation within a virtual environment (VMware/Hyper-V). PowerCLI is VMware’s API, but it doesn’t have to be PowerCLI (preferred)-other automation tools are acceptable: Need to know how to use PowerShell to interface with VMware

3. Experience with Storage Automation, how scripting automation relates to NAS environment 

Job Description:  

• Update all scripts for powercli version 6. Most scripts may need slight changes due to how VMware went to modules instead of snapins

• Get all VMware PowerCli scripts into SVN (GIT)

• Use existing scripts and new scripts to create a Powershell module for all the VMware scripts. This module could then be called for writing scripts and be the single safe source for all VMware scripting

• Decommissioning script – remove networking, storage, run final checks, etc for EOL hosts

• Orchestrator workflows for everyday changes to VM

• Remedy integration into Orchestrator

• All non-outage resource changes should be an Orchestrator(vRO) workflow that will create and process change tickets and do the work. 

• Automated role syncing between all vCenters

• Automated top level permissions syncing between all vCenters

• Automated scripted build of a new vCenter

• VDS scripting – Automated deployment of new VDS switches and enforcing consistent config on them. 

• Host profile syncing between vCenters

• VUM config syncing between vCenter   

If interested, please send a reply with your Updated Resume

Qualifications

Additional Information

All your information will be kept confidential according to EEO guidelines.