
AWS DevOps Lead
- Minneapolis, MN
- $80,000-158,000 per year
- Permanent
- Full-time
- Experience working in the AWS Solution
- Passion for continuous improvement and advancing technology solutions
- Strong understanding of the Cloud native architecture principles
- Strong client management and communication skills
- In-depth experience architecting complex AWS public Cloud platform solutions (PaaS, SaaS, IaaS)
- Containerization and PaaS approaches and tools (e.g., Cloud Foundry, Kubernetes, Docker Enterprise, AWS Stack)
- Ability to work with ambiguity and visualize solutions for emerging concepts
- Experience architecting both PaaS and IaaS enterprise solutions
- Experience and understanding of large-scale infrastructure deployments in enterprise-wide environments required
- Muat have handson Experience as an AWS Cloud Solutions Architect
- Hands on Experience in Jira/Confluence
- Responsible for taking an app team from initial kickoff through all stages of cloud migration.
- Achieve monthly, quarterly and annual targets for number of applications moved to the cloud. Drive multiple applications
- simultaneously through various stages of Application cloud migration. Develop a robust plan (derived from standard steps in Cloud migration factory), execute on the same.
- Responsible for timely delivery; manage accurate and most current (on daily basis) work schedule.
- Conduct kickoff for Application Teams at beginning of Application Migration and communicate with all the stakeholders
- Strong critical thinking and problem-solving skills.
- Organizing kickoffs for migrations of applications from on prem to cloud
- Ability to follow standardized steps for migration factory
- Ability to work under pressure
- Ability to work well effectively with team-members with effective interpersonal, verbal and written communication skills
SAP as service providerWe use the following session cookies, which are all required to enable the website to function:
- "route" is used for session stickiness
- "careerSiteCompanyId" is used to send the request to the correct data center
- "JSESSIONID" is placed on the visitor's device during the session so the server can identify the visitor
- "Load balancer cookie" (actual cookie name may vary) prevents a visitor from bouncing from one instance to another