AWS IAM Engineer

Description
We are looking for AWS IAM Engineer for an immediate need. This is a client-facing role & the candidate will have regular interactions with various client managers.

5 years of minimum IAM and cloud experience

IAM Policy creation & rightsizing

Candidate who has taken on prem to cloud

Work will be 30% solution, 70% technical

Candidate will help establish some base lines for preventing the repeat of what they are clearing up

Need good documentation and procedures to avoid what they have seen already

Work with Devops teams, work with developers to understand the policies that have been created and then automate them

Minimum 8 to 10 Years of IT experience

Required Skills Technical Skills: AWS IAM Domain Skills

Responsible for end-to-end management of the program delivery- which includes service delivery processes- transformation- cost optimization- people practices- customer satisfaction- contractual deliverables- risk management- internal & customer governance and enable business growth.

Responsible for business operations. Business/Customer. Work closely with account management/vertical team for customer satisfaction.

Work closely with internal stakeholders and customer to ensure proper alignment to business objectives.

***Cognizant is recognized as a Military Friendly Employer and is a coalition member of the Veteran Jobs Mission. Our Cognizant Veterans Network Assists Veterans in building and growing a career at Cognizant that allows them to leverage the leadership, loyalty, integrity, and commitment to excellence instilled in them through participation in military service.

**Applicants are required to be eligible to lawfully work in the U.S. immediately; employer will not sponsor applicants for U.S. work authorization (such as an H-1B visa) for this opportunity

Qualifications
5+ years of minimum IAM and cloud experience

IAM Policy creation & rightsizing

Candidate who has taken on prem to cloud

Work will be 30% solution and 70% technical

Candidate will help establish some base lines for preventing the repeat of what they are clearing up

Need good documentation and procedures to avoid what they have seen already