> Markdown version of [/jobs/ext/4771758-devops-aws-cloud-devops-engineer-minneapolis-mn-hybrid-lorven-technologies-inc](https://www.wearedevelopers.com/jobs/ext/4771758-devops-aws-cloud-devops-engineer-minneapolis-mn-hybrid-lorven-technologies-inc). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # DevOps / AWS Cloud DevOps Engineer - Minneapolis, MN (Hybrid) - Lorven Technologies Inc - **Company:** Lorven Technologies Inc - **Location:** Minneapolis, MN, United States - **Contract:** Permanent contract - **Skills:** Java (Programming Language), Amazon Web Services, Microsoft Azure, Continuous Integration, DevOps, Github, Systems Integration, Software Vulnerability Management, Google Cloud, Kubernetes, Terraform, Docker, Vulnerability Analysis - **Published:** November 18, 2026 - **Apply:** https://www.adzuna.com/details/5969419797 ## About the Role * GitHub and GitHub Actions, hands-on: 3+ years * CI/CD pipeline design, configuration and troubleshooting: 3+ years * Repository and pipeline configuration and integrations: 3+ years * Container platform fundamentals (ECS, Docker or Kubernetes) as they relate to vulnerability remediation: 2+ years * Working with multiple application teams on a standard onboarding process: 2+ years * Clear written and verbal communication Preferred Skills & Attributes (Incl. years) * Terraform / infrastructure-as-code: 1+ years * Hands-on experience with more than one container platform (ECS, Docker, Kubernetes): 2+ years * Public cloud (AWS preferred, Azure or Google Cloud Platform acceptable): 2+ years * Security scanning integrations in pipelines: 1+ years * Java skillset (helpful, not mandatory) ## Description * Configure GitHub repos, GitHub Actions and pipelines to onboard teams to the standardized CI/CD process. * Integrate internally developed security tools into team pipelines. * Complete manual remediation through pipelines, Terraform and container configuration when automation is not feasible. * Partner with application teams to resolve onboarding blockers, and assist other organizations or environments (including non-AWS) as needed. * Report progress and provide evidence of completion.