APPLYDJINN

AWS jobs and hiring demand in Minneapolis, Minnesota, United States

Core and required roles are separated from contextual and optional mentions so the headline does not overstate job intent.

Explore AWS by location
Minneapolis, Minnesota, United States

Select up to five markets; results and hiring evidence update together.

3core + required roles4context + optional mentions1remote-friendly▼ -3 this week

Employer concentration

Amazon accounts for 4 of 7 mentions (57%). The remaining 3 mentions span other employers.

View without top 1 employer →View without top 3 employers →
AWS market intelligence visualization

Provider-specific demand with transferable foundations

AWS market guide

AWS vacancies range from application teams using a few managed services to platform roles responsible for multi-account infrastructure, security, reliability, and cost. Service names are useful only when paired with operating depth.

7 live roles4 hiring companies14% remote-friendly

Vacancy evidence map

Where AWS carries hiring weight

Each segment represents roles where AWS was parsed at that evidence tier. This keeps a required production skill separate from contextual stack language.

1 Core2 Required3 Supporting1 Optional
3core + required43% of mentions
1.8roles per company4 employers

Market interpretation

What AWS demand means in practice

ApplyDjinn tracks where AWS is core, required, supporting, or optional. That distinction helps separate cloud-platform ownership from a role that merely deploys an application to AWS. Related technologies reveal whether the work is container, serverless, data, security, or networking heavy.

Strong candidate evidence maps services to architecture: why a managed database, queue, Lambda function, EKS cluster, IAM boundary, or observability stack was chosen. Include the scale, recovery, security, and cost constraints that shaped the design.

Cloud platformBackend systemsData infrastructureCloud security

Reading the market

Signals to look for

  • Terraform, Kubernetes, Docker, CI/CD, and observability often define platform roles.
  • Backend roles commonly pair AWS with APIs, queues, databases, and event-driven design.
  • Security-heavy vacancies emphasize IAM, network boundaries, encryption, and audit trails.

Geographic demand

Top AWS locations

Minneapolis, Minnesota, United States7Minnesota, United States7United States7Austin, Texas, United States2Des Moines, Iowa, United States2Detroit, Michigan, United States2Indiana, United States2Indianapolis, Indiana, United States2

Questions candidates ask

AWS hiring FAQ

How many AWS services should appear on a CV?

Only the services supported by meaningful project or production evidence. A focused architecture story is stronger than a long inventory.

Does AWS experience transfer to Azure or GCP roles?

Many foundations transfer, but provider-specific identity, networking, data, and operations patterns may still require a ramp-up.

How AWS appears in job requirements

Inferred from the title and requirement wording in 7 active roles; each role is counted once. Read the methodology.

Posting evidence, not a company-wide stack claim
Main / core
14%(1)
Required
29%(2)
Supporting / context
43%(3)
Nice-to-have
14%(1)

Skills mentioned with AWS

A shared posting does not always require both skills. Explicit alternatives are counted separately.

Cloud7 together2 both requiredAutomation4 together0 both requiredAzure3 together1 both required1 alternativesDistributed Systems3 together0 both requiredGCP3 together1 both required1 alternativesReliability Engineering3 together1 both required

Role graph

Roles hiring for AWS

Software Engineering 3Customer Success 2Sales & Account Management 1Security 1

Latest roles mentioning AWS

Enterprise Customer Success Manager

Required

Palo Alto Networks — Indiana, United States; Austin, Texas, United States; Des Moines, Iowa, United States; Detroit, Michigan, United States; Indianapolis, Indiana, United States; Jefferson City, Missouri, United States; Madison, Wisconsin, United States; Memphis, Tennessee, United States; Minneapolis, Minnesota, United States; Oklahoma City, Oklahoma, United States; Topeka, Kansas, United States

Software Development Engineer, AWS

Core

Amazon — Minneapolis, Minnesota, United States

Enterprise Customer Success Manager

Required

CyberArk — Cincinnati, OH, United States; Austin, Texas, United States; Des Moines, Iowa, United States; Detroit, Michigan, United States; Indianapolis, Indiana, United States; Jefferson City, Missouri, United States; Madison, Wisconsin, United States; Memphis, Tennessee, United States; Minneapolis, Minnesota, United States; Oklahoma City, Oklahoma, United States; Topeka, Kansas, United States

HCLS Principal Account Executive, US HCLS Payors , Global HCLS

Context

Amazon — Minneapolis, Minnesota, United States

System Development Engineer, STRADA

Context

Amazon — Minneapolis, Minnesota, United States

Sr Staff Software Engineer- Access Security

Nice

ServiceNow — Minneapolis, Minnesota, United States

View all 7 roles mentioning AWS →