AWS jobs in the United States: who is hiring, what they ask for and what they pay

Jobee counted 14,230 open AWS jobs in the United States on 12 November 2026. The picture is clear: Amazon-linked employers dominate, senior roles outnumber entry-level ones by a wide margin, and a large share of postings are remote or do not say where the work happens. Where yearly pay is stated, the middle of the market sits at 175,000 USD.

AWS jobs in the United States: who is hiring and how concentrated the market is

This market is heavily concentrated around a small set of employers. Amazon Web Services, Inc. leads with 2,235 postings, followed closely by Amazon Data Services, Inc. with 2,169, Amazon.com Services LLC with 1,417, and Amazon Development Center U.S., Inc. with 962. Those four employers alone account for a large share of the AWS openings Jobee collected, which tells you that a search for AWS work in the United States is often, in practice, a search across Amazon’s own hiring family.

The rest of the top employer list is much smaller but still useful for showing where AWS-related hiring spills outside that core group. Annapurna Labs Ltd. has 262 postings, Databricks has 238, Bright Vision Technologies has 182, Salesforce has 179, MongoDB has 168, Amazon Kuiper Manufacturing Enterprises LLC has 124, NVIDIA has 103, and Anthropic has 88. That mix says two things. First, AWS skills are not confined to cloud infrastructure teams inside one company. Second, the jobs that mention AWS are attractive to employers building platform, infrastructure, data, and AI systems.

For an applicant, that concentration matters. If the bulk of the openings come from the same employer family, the application patterns, interview style, and job families will often look similar across those listings. A candidate who can speak to cloud infrastructure, platform engineering, systems reliability, and deployment practices should expect those themes to repeat.

AWS jobs in the United States: where the work happens

Remote work is a major part of this market, but not all postings are explicit about location. Of the 14,230 AWS jobs in the United States, 5,615 are remote, which is 39.5%. Another 669 are hybrid, 284 are on-site, and 7,662 do not say where the work happens.

That means more than half of the postings, 53.8%, leave location unstated. For a job seeker, that is a practical warning sign: do not assume a role is remote just because the title or team sounds distributed. If a posting does not say where the work happens, the safest move is to treat location as unresolved until the employer confirms it.

The remote share is large enough that a candidate looking for flexible work has real options, but the market is not fully remote. The presence of 669 hybrid roles and 284 on-site roles shows that AWS hiring in the United States still includes in-office expectations, especially for teams tied to hardware, labs, security, or closely coordinated product work.

The city list reinforces that pattern. Seattle leads with 2,455 postings, far ahead of Austin with 755, New York with 626, San Francisco with 584, and Washington with 525. Herndon has 319, Arlington 294, Boston 199, Dallas 181, Denver 175, Santa Clara 170, and Atlanta 126.

Seattle’s lead is no surprise given how many Amazon-linked postings appear in the data. Austin, New York, San Francisco, and Washington show that the market is not just one-city hiring, and the presence of Herndon and Arlington points to a strong East Coast footprint as well. If you want the best odds of finding a location-specific AWS role, those cities are the first places to watch in this dataset.

What the location data means for applicants

When more than half the postings do not state location, the application process becomes more dependent on direct clarification. Candidates should be ready to ask whether the role is remote, hybrid, or tied to a specific city as soon as the conversation starts, especially if the posting is otherwise attractive. The job advert itself cannot tell you everything here, and the count of unstated location shows why.

AWS jobs in the United States: what seniority employers want

The seniority mix is weighted toward experienced candidates. Senior roles make up 5,991 postings, or 42.1%. Another 1,765 are Lead roles, 919 are Mid-level, 429 are Director, 421 are Principal, 315 are Staff, 313 are Junior, 56 are VP, 48 are Intern, and 14 are C-level. Another 3,959 postings, or 27.8%, do not state seniority.

The biggest single bucket is Senior, and the next most common explicit level is Lead. That is a strong signal that employers want people who can own systems, guide decisions, and work with limited supervision. The relatively small Junior count, 313, shows that entry-level AWS hiring exists, but it is nowhere near the center of the market.

This matters for anyone trying to break in. If you are early in your career, you are not competing in a market built mainly for beginners. The postings show a market where the default expectation is depth: production experience, architectural judgment, and the ability to work across systems. If your experience is lighter, you will need to use the application to show adjacent experience carefully, rather than hoping the title alone will carry you.

The 3,959 postings with no stated seniority add another layer. Some employers either do not label level clearly or use titles that blur it. In practice, that means candidates should not rely only on the title. A role labeled in a vague way may still be aiming at Senior or Lead-level work.

AWS jobs in the United States: what employers ask for alongside AWS

AWS is rarely the only skill in the posting. The most common companion skill is Python, appearing in 4,660 postings, or 32.7%. Azure appears in 3,805 postings, or 26.7%. Google Cloud appears in 3,194, or 22.4%. CI/CD appears in 2,821, or 19.8%. Java appears in 2,580, or 18.1%. SQL appears in 2,512, or 17.7%. Kubernetes appears in 2,376, or 16.7%. Agile appears in 1,978, or 13.9%. TypeScript appears in 1,674, or 11.8%. Linux appears in 1,653, or 11.6%. C++ appears in 1,623, or 11.4%. LLM appears in 1,597, or 11.2%.

That list shows a broad cloud and engineering profile rather than a narrow AWS-only one. Python leads, which suggests a lot of these jobs involve automation, tooling, backend services, data processing, or scripting around cloud systems. The strong presence of Azure and Google Cloud tells you that some employers want multicloud familiarity, not just AWS depth. CI/CD and Kubernetes point to deployment, orchestration, and platform operations. Java, SQL, TypeScript, Linux, and C++ show that AWS roles often sit inside broader software engineering environments, not just cloud administration.

The appearance of LLM in 1,597 postings is a newer signal. Some AWS jobs now sit near AI infrastructure, model tooling, or application features built around language models. That does not mean every AWS role is AI-related, but it does mean that applicants who understand cloud plus modern AI workflows may have an advantage in a slice of the market.

What to do with the skills data

A strong AWS application in this market should not read like a list of AWS services only. The counts show employers often want Python, CI/CD, Kubernetes, SQL, and one or more general engineering languages or cloud platforms as well. If your CV only repeats AWS terms, it may undersell the rest of your profile. If you have Python, Java, Linux, or Kubernetes experience, make that visible because the postings show those skills are in demand.

AWS jobs in the United States: what they pay

Of the 14,230 AWS jobs in the United States, 4,806 state a salary and 9,424 do not. That means 33.8% state a salary and 66.2% do not.

That is a lot of missing pay information. For applicants, it means you should not expect the advert to do the negotiating for you. If two out of three postings do not state a salary, the first call becomes the right time to clarify pay expectations, especially before investing time in later interview rounds.

Where yearly pay is stated, the pay distribution is 142,000 USD at the lower quartile, 175,000 USD at the median, and 215,000 USD at the upper quartile. These figures apply to the 4,614 postings with yearly pay in USD.

The spread suggests that AWS work in the United States can pay well, but the market is broad. The lower quartile at 142,000 USD still sits at a substantial level, while the upper quartile at 215,000 USD shows that some roles, likely the more senior or specialized ones, pay much more. The median at 175,000 USD is the clearest single number for readers scanning the market.

Because salary is only stated in a third of postings, it is worth reading the role level and skill list together. Senior and Lead roles are common, and the pay figures reflect that. Junior candidates should not assume those salary numbers apply to them automatically. A role with no stated seniority and no salary could land anywhere in the range, which is exactly why asking early matters.

AWS jobs in the United States: visa sponsorship and work authorization

Visa language is uncommon in this market, but when it appears it is useful. Out of 14,230 postings, 103 offer visa sponsorship, 898 say they will not sponsor a visa, and 673 say they require work authorization.

The sponsorship count is small: 0.7%. That means most postings do not make sponsorship a selling point. The much larger counts are the postings that either rule it out or require existing work authorization. Together, those two groups show that many AWS employers expect candidates who can already work in the United States without sponsorship.

For applicants who need visa support, the practical lesson is simple: do not wait until late in the process to find out. If a posting says it will not sponsor a visa or requires work authorization, treat that as a hard filter. If it says nothing, do not assume the answer is yes.

AWS jobs in the United States: what the market says overall

This is a senior-heavy, cloud-heavy, and Amazon-heavy market. The strongest employer names are all Amazon-related, the biggest seniority bucket is Senior, and the most common companion skills are Python, Azure, Google Cloud, CI/CD, Java, SQL, and Kubernetes. The biggest city is Seattle, but there are meaningful clusters in Austin, New York, San Francisco, and Washington. Remote work is common, but location is still missing from more than half the postings.

The shape of the market gives candidates a clear plan. If you want AWS work in the United States, show cloud depth, but do not stop there. Show the language and platform skills that match the posting. Treat remote status and salary as open questions unless they are explicitly stated. And if you need sponsorship, check that first because the postings do not imply it.