AWS jobs: who is hiring, what they ask for and what they pay

# AWS jobs

AWS jobs are heavily weighted toward senior roles, almost half of postings are remote, and the pay that is stated is strongest in USD, with much thinner salary reporting in other currencies. These are Jobee’s counts of open postings collected on 12 November 2026, so the picture below is of live adverts, not a broad labour-market estimate.

AWS jobs on 12 November 2026: what the open postings show

Job seekers coming here usually want the same four things from AWS jobs: who is hiring, how much of the market is remote, what skills are being asked for, and what the pay looks like. The collected postings answer all four clearly enough to guide a search, but they also show where the market is opaque: most adverts still do not state a salary, and many do not even say where the work happens.

The scale is large. Jobee counted 26,280 open AWS jobs, across 4,110 employers. That is a broad market with enough volume to support a targeted search, but also one where the same employer can appear in several different forms, which is why the employer list matters: the biggest names are often not the same as the biggest hiring teams.

A useful way to read this market is to start with the basics of the adverts themselves. Only 7,714 of 26,280 postings were posted in the last 30 days, which means the set is not just fresh openings but also includes older live adverts that are still open. That is relevant if you are applying now: the job may still be active even if it has been visible for a while, but the age of the advert can also mean the team is moving slowly or is repeatedly recruiting for a difficult role.

AWS jobs and the employers posting them

The employer mix is dominated by very large cloud and infrastructure organisations, plus a smaller cluster of data-platform and enterprise software companies.

The first thing this table says is that a very large share of AWS jobs are posted by Amazon-related entities. That matters because the same skill set can appear in different teams with different expectations. One employer may be hiring for platform engineering, another for sales engineering, another for specialist support, another for internal infrastructure. A search for AWS jobs is therefore not one market but several adjacent ones.

The second thing it says is that hiring is not limited to AWS-branded employers. MongoDB, Databricks, Salesforce and NVIDIA all appear among the largest posters. If you are applying for AWS work because you want cloud architecture, distributed systems, automation or infrastructure-heavy roles, those employers may still be relevant even when AWS is not the brand on the door.

For applicants, the practical lesson is to read the employer line closely. The same title can hide different work. An AWS engineer role at one employer may be a customer-facing role, while at another it may be pure infrastructure work. That distinction often shows up later in the advert through the skills section, so the employer list is your first clue about the type of team behind the job.

AWS jobs and how remote the market is

Remote work is a major part of AWS jobs, but the location data is also messy enough that you should not assume every “remote” advert will fit your geography or time zone.

The headline here is simple: almost half of AWS jobs are remote. That is a strong signal for applicants who want flexibility, especially in roles where cloud work can be done from anywhere the employer allows. But the second headline is just as important: nearly as many adverts do not say where the work happens at all.

That means two things for a job search. First, do not assume a silent advert is remote. Second, do not assume it is not remote either. If the location is omitted, the advert is telling you nothing useful yet. In practice, those are the roles where you should ask early rather than late, because a location restriction can remove a job from consideration just as quickly as a salary mismatch.

The hybrid and on-site shares are much smaller than the remote share, but they still matter. A hybrid opening usually signals a role tied to a particular office, team, or customer base. On-site roles are fewer, but they often suggest operational, hardware-adjacent, or tightly controlled environments. If you want flexibility, the best filter is not just “remote” in the title or summary; it is any explicit mention of work location in the body of the advert.

AWS jobs and salary transparency

Salary disclosure is still limited in AWS jobs. Jobee counted 6,845 postings that state a salary and 19,435 that do not. That means most applicants are still applying without knowing pay up front.

That is the part of the market that changes how you apply. When three quarters of ads do not state pay, you cannot use the advert alone to judge fit. You have to decide whether to spend time on a role before knowing whether the compensation is in range.

For applicants, the immediate response is straightforward: if salary is missing, bring it up early. Not as a demand, but as a qualification step. If the employer will not share pay until late in the process, you risk investing time in a role that was never realistically in range.

The salary data that is stated is also uneven by currency, so it should be read carefully and never mixed across currencies. Jobee counted yearly pay in six currencies, with the following distributions and ranges:

USD has by far the largest number of postings with yearly pay, so it is the most informative currency slice in the set. The median there is 175,000 USD, with a lower quartile of 140,000 USD and an upper quartile of 214,000 USD. That suggests many AWS jobs with stated salary are pitched at experienced candidates rather than entry-level applicants.

EUR pay is also worth reading closely, especially because Germany appears among the top countries later in the data. The median stated yearly pay in EUR is 77,000 EUR, with 54,000 EUR at the lower quartile and 104,000 EUR at the upper quartile. That range is broad enough to cover different seniorities, but the number of postings with stated pay is much smaller than the USD set, so it should be treated as a useful clue rather than a full market picture.

For GBP, the median is 95,000 GBP, again with a relatively small number of salary-stating postings. CAD shows a median of 158,000 CAD. PLN and INR appear in even smaller numbers, which is a reminder that salary transparency varies sharply by country and employer.

One important point follows directly from the counts: because 19,435 postings do not state salary, you should expect compensation to remain hidden in many application flows. That is not a reason to skip the market; it is a reason to ask about pay sooner, and to compare offers only after they are in the same currency and yearly format.

AWS jobs and the seniority mix

The seniority profile of AWS jobs is strongly tilted toward experienced applicants.

The obvious finding is that senior roles dominate. Senior alone accounts for 11,539 postings, or 43.9%. Lead adds another 2,998 postings, and Mid-level adds 2,233. Taken together, those three levels make up most of the visible seniority-labelled AWS jobs.

That tells applicants two things. First, the market is not dominated by beginner roles, so if you are early in your career you may need to search more carefully for openings that truly fit. Second, if you already have cloud experience, this is a market that appears to value it.

The “Not stated” group is also large. That means a quarter of adverts do not make the level explicit, which can make search results noisier than they first appear. A role that looks junior in the title may turn out to want a senior engineer, and a role that does not name a level may still be written for someone with deep experience.

For applicants, this is where the rest of the advert matters. If a posting sits in the senior-heavy part of the market but the title is vague, look at the skills list and the pay if it is stated. Those are often the fastest clues to whether the role is really senior, lead, or something more flexible.

AWS jobs and the skills employers ask for alongside AWS

AWS is rarely asked for on its own. Employers usually want it alongside cloud, automation, software engineering, and infrastructure skills.

Python is the most common companion skill, which suggests that many AWS jobs are really asking for people who can automate, script, build tooling, or work in cloud-adjacent engineering roles. The next most common skills are Azure and Google Cloud, which is a striking clue: many employers are looking for multi-cloud familiarity, not just AWS-specific knowledge.

That matters because applicants often present AWS as a platform skill and stop there. The data shows that is not enough for many employers. CI/CD, Kubernetes, SQL, Java, Docker, Terraform and Linux all appear frequently. In other words, employers are looking for the surrounding stack as much as the cloud platform itself.

The appearance of LLM in 3,280 postings is also notable. It suggests that a meaningful slice of AWS jobs now sits close to AI-adjacent infrastructure, integration, or platform work. That does not mean every AWS role is an AI role, but it does mean that cloud jobs increasingly overlap with newer tooling and deployment patterns.

For a candidate, the practical takeaway is not to list AWS alone. A stronger application is one that shows AWS plus the adjacent tools the market repeatedly asks for. If your background includes Python and Terraform, or Kubernetes and CI/CD, those are not side notes in this market; they are central signals.

AWS jobs and where they are concentrated by country

AWS jobs are globally distributed, but the largest concentration is in the United States.

The United States dominates the set, which is not surprising given the employer mix and the size of the cloud market there. After that, the numbers narrow quickly. India, Canada and the United Kingdom form the next cluster, and then a longer tail of countries follows.

Germany’s 472 postings matter here because they show that AWS jobs are present in the German market, but not at the scale of the United States, India, Canada or the United Kingdom. If you are searching from Germany, that means your job search may need to be broader than only AWS-branded roles. You may also need to watch for multinationals hiring in Germany, remote roles open to the country, and employer groups that do not put AWS in the title.

The country table also helps explain why salary data appears in several currencies. The market is international, but the salary disclosure is fragmented by country and employer. That is another reason not to compare currencies with each other. A number in EUR belongs to a different hiring context from a number in USD, even when the role title looks the same.

AWS jobs, visa sponsorship and work authorization

Visa and work authorization language appears in only a small part of the set.

That is a narrow slice of the total, but it is a decisive one for candidates who need sponsorship or already need to know whether they can work legally in the location.

The clearest point is that explicit sponsorship is rare. If you need visa support, you cannot rely on the chance that an employer might help later. The advert either says it or it does not, and only 140 postings say they offer it.

The other two counts are more restrictive than supportive. Some postings say they will not sponsor a visa, and some require work authorisation. That means a candidate who needs sponsorship should treat immigration language as a first-pass filter, not a detail to solve later in the process.

For applicants, that leads to a simple strategy: if you need sponsorship, look for explicit sponsorship language and avoid roles that state the opposite or require local authorisation. The data shows that this is not a common market feature, so filtering early saves time.

What AWS job seekers should do with this market

The numbers point to a clear pattern. AWS jobs are plentiful, but they are concentrated in experienced roles, they often omit salary, and nearly half of them are remote while almost as many leave location unstated.

If you are applying now, use the strongest signals first. Search the senior-heavy roles if you already have cloud experience. Treat Python, CI/CD, Kubernetes, Terraform, Docker and Linux as core companion skills, not optional extras. Be ready for multi-cloud language, because Azure and Google Cloud appear very often alongside AWS. Ask about salary early when it is missing, because most adverts do not state it. And check work location and work authorization at the start, because both are often decisive and often hidden.

The picture is not one of a junior-friendly entry market. It is a market built around cloud operations, platform engineering, infrastructure, automation and adjacent software work. If your background fits that shape, the search is broad. If it does not, the fastest way to improve your odds is to align your CV to the skills employers repeatedly ask for in these postings and to filter aggressively for the level, location and pay you actually need.