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

SQL jobs on 12 November 2026

Jobee counted 19,404 open SQL jobs on 12 November 2026 across the postings it had collected. The market is broad, but it is not vague: the biggest employers, the remote share, the seniority mix, the skills that travel with SQL, and the pay by currency all point in the same direction. Most SQL openings are remote, most ask for senior experience, and Python is the most common extra skill.

Who is hiring for SQL jobs

The largest employer in the set is Amazon.com Services LLC with 1,278 postings. Google follows with 740, then Databricks with 404, Salesforce with 298, Stripe with 264, Bright Vision Technologies with 171, Amazon Data Services, Inc. with 157, Amazon Web Services, Inc. with 151, Sezzle with 142, Truelogic with 133, Anthropic with 132, and NVIDIA with 131.

That list tells you two things about SQL jobs. First, SQL is not confined to one type of company. Big cloud and infrastructure employers are present, but so are finance, software, AI, and services employers. Second, the demand is spread across many teams rather than concentrated in a single kind of role. If you are applying, it is worth expecting different wording from each employer, even when the skill at the center is the same.

The biggest cluster around Amazon-family employers also matters for how you search. A large share of the postings comes from a few employers with many openings, which means one search can surface a lot of closely related roles. If you are using this market to narrow your target, start by grouping employers with repeated SQL hiring and then compare the job descriptions side by side. That is often where the real differences show up: analytics versus data engineering, platform work versus business-facing reporting, or individual contributor versus lead scope.

Where SQL jobs are open

The United States leads the country table with 9,572 postings. India follows with 1,545, Canada with 901, Brazil with 787, the United Kingdom with 733, Mexico with 443, Spain with 309, Poland with 280, Germany with 250, Argentina with 233, Japan with 213, and Ireland with 188.

The country mix shows that SQL hiring is not limited to one region, but the center of gravity is clear. The United States is far ahead of every other country in the set. After that, the openings are spread across several large tech, services, and product markets. For a job seeker, that means there are many places to look, but the largest volume is in one country, and it is also where many of the remote roles are likely to be posted from.

If you are searching by location, this also helps you read the pay table later. Salary in SQL jobs is not one market-wide number. It changes by currency and by region. A posting in the United States is likely to be written very differently from one in India or Germany, and the salary bands reflect that difference.

How remote SQL jobs are

Remote work is the dominant pattern in SQL jobs. 11,879 of 19,404 postings are remote, which is 61.2%. Hybrid roles account for 870 postings, which is 4.5%, and on-site roles account for 679 postings, which is 3.5%. Another 5,976 postings, or 30.8%, do not say where the work happens.

That mix is unusually favorable for anyone who wants flexibility. More than half of the open SQL jobs are remote, while explicit on-site roles are a small share. But the large “do not say” bucket matters. A posting that does not name the work arrangement is not the same as a remote role. If location matters to you, do not assume. Read the ad closely and treat the missing detail as a question to confirm early.

For applicants, this means the first screen can be about clarity as much as fit. If you are only looking for remote SQL jobs, the postings that already state remote are the cleanest target. If you are open to hybrid, the share is much smaller, so those roles may need more location-specific effort. And if you are applying to a role that does not say where the work happens, it is reasonable to ask before you invest time in a long process.

What level SQL jobs want

Senior is the most common level by a wide margin, with 8,355 postings and 43.1% of the set. Mid-level follows with 3,316 postings and 17.1%. Lead roles account for 2,584 postings and 13.3%. The level is not stated in 3,023 postings, or 15.6%. Junior roles account for 744 postings and 3.8%. Director roles account for 487 postings and 2.5%. Staff roles account for 447 postings and 2.3%. Intern roles account for 262 postings and 1.4%. Principal roles account for 160 postings and 0.8%. VP roles account for 15 postings and 0.1%. C-level roles account for 11 postings and 0.1%.

The message is clear: SQL jobs are mostly not entry-level. Senior and lead openings dominate, while junior and intern roles make up a much smaller part of the market. If you are early in your career, that does not mean there are no openings for you, but it does mean the competition is happening in a market designed mostly for people who already know how to use SQL in production work.

If you are a junior candidate, the best reading of this table is not “there are no jobs,” but “the bar is set high.” That means you should expect job descriptions to ask for more than basic querying. Employers likely want evidence that you have used SQL with real datasets, worked with adjacent tools, and can operate with less supervision than a true starter role might suggest.

If you are more experienced, the same table explains why many ads sound broad. Senior SQL jobs often sit inside data engineering, analytics engineering, platform, or product analytics teams. The title may say SQL, but the work can include modeling, cloud services, dashboards, pipelines, or cross-functional delivery.

What SQL jobs ask for besides SQL

Python is the most common skill asked alongside SQL, appearing in 9,024 postings, or 46.5%. AWS appears in 5,226 postings, or 26.9%. Azure appears in 3,502 postings, or 18.0%. CI/CD appears in 3,198 postings, or 16.5%. Agile appears in 2,875 postings, or 14.8%. Tableau appears in 2,828 postings, or 14.6%. Java appears in 2,750 postings, or 14.2%. Google Cloud appears in 2,492 postings, or 12.8%. LLM appears in 2,288 postings, or 11.8%. JavaScript appears in 2,169 postings, or 11.2%. Snowflake appears in 1,978 postings, or 10.2%. Kubernetes appears in 1,910 postings, or 9.8%.

This is the most important part of the market if you are trying to understand what employers really mean by SQL jobs. SQL is rarely the only skill. In nearly half of the postings, Python sits next to it. Cloud skills also show up heavily, especially AWS and Azure. That means many of these jobs are not just about writing queries. They are about building, automating, and operating data work inside cloud environments.

Tableau’s presence shows that reporting and visualization are still a big part of the work. Java and JavaScript suggest that some roles sit closer to application engineering or product systems than pure analytics. Snowflake points to modern warehouse work. Kubernetes and CI/CD show that operational and deployment knowledge matters in a meaningful slice of postings. LLM being present in this list is a sign that some employers now want SQL talent to work near AI-assisted data workflows or data products built around language models.

For applicants, the practical takeaway is simple: SQL alone may not be enough if you want the larger share of openings. If your background includes Python, cloud, BI, or data platform work, make that visible. If it does not, focus on the subset of roles that are closer to reporting, analysis, or database work rather than the wider data engineering market.

What the salary data says for SQL jobs

Salary is stated in 7,356 of 19,404 postings, which is 37.9%. Salary is not stated in 12,048 postings, which is 62.1%.

That means most SQL jobs still do not tell you what they pay. The first implication is that salary should not be treated as a given when you search. The second is that you should expect to discuss pay earlier than you might like, because the posting itself often will not help you decide whether the role is worth your time.

When a job advert does not state salary, you have less room to guess and more reason to ask. For SQL jobs in particular, that matters because the role title can hide a wide range of scope. A posting that says SQL may be a reporting role, a platform role, or a data engineering role. The difference can be large, and the pay often follows the scope more than the tool.

What SQL jobs pay in USD, CAD, EUR, GBP, INR and PLN

For postings with yearly pay in USD, there are 5,761 such postings. The lower quartile is 124,000 USD, the median is 156,000 USD, and the upper quartile is 200,000 USD.

For postings with yearly pay in CAD, there are 331 such postings. The lower quartile is 105,000 CAD, the median is 135,000 CAD, and the upper quartile is 170,000 CAD.

For postings with yearly pay in EUR, there are 289 such postings. The lower quartile is 47,000 EUR, the median is 71,000 EUR, and the upper quartile is 93,000 EUR.

For postings with yearly pay in GBP, there are 90 such postings. The lower quartile is 64,000 GBP, the median is 83,000 GBP, and the upper quartile is 108,000 GBP.

For postings with yearly pay in INR, there are 42 such postings. The lower quartile is 1,227,000 INR, the median is 2,380,000 INR, and the upper quartile is 3,401,000 INR.

For postings with yearly pay in PLN, there are 29 such postings. The lower quartile is 208,000 PLN, the median is 286,000 PLN, and the upper quartile is 324,000 PLN.

The USD set is by far the largest pay sample, so it is the clearest read on the part of the market where pay is most often disclosed. The spread is also wide, which fits what the seniority table already showed. Senior SQL jobs are common, and seniority tends to pull compensation upward.

The smaller currency groups are useful mainly as local guides. They tell you that SQL pay is being disclosed in several markets, but the samples are much smaller than the USD set. That means they are best read as the pay bands of the postings Jobee collected, not as a complete market wage benchmark.

The practical move here is not to chase a single universal SQL salary. It is to use the currency that matches the posting and the country that matches the role. If the ad states pay, compare it to the level and scope in the same posting. If it does not state pay, the omission itself is part of the story. In this data set, most postings still leave salary out.

What an applicant should do with this SQL jobs market

The market rewards people who can show more than SQL. Python is the clearest companion skill, and cloud experience is close behind. If your CV only says SQL, you are leaving out the context that many employers are actually screening for. Put the adjacent tools up front where they belong.

The level mix also suggests that you should read titles carefully. A senior-heavy market means many ads will expect production experience, not just coursework or small projects. If you are early-career, target the smaller junior share and the postings that stress analysis, support, or reporting. If you are experienced, use the senior and lead concentration to your advantage by showing scope, ownership, and cross-team work.

Salary is the last big filter. Because 12,048 postings do not state pay, you should not wait until the end of the process to think about it. If a posting leaves salary out, ask once you know the role is real and aligned. The data says that is the norm, not the exception.

Remote work is a major advantage in this market, but not a guarantee. More than half of the postings are remote, yet a large share still does not say where the work happens. If location matters, treat that as a screening question, not a detail to settle later.

If you want the quickest picture of this market, start with the employers that recur most often, then check whether their postings are remote, whether they state salary, and whether they want Python or cloud skills alongside SQL. That is the pattern the data keeps repeating.