Skip to main content

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

Jobee counted 9,627 open SQL jobs in the United States on 22 November 2026, and the market is dominated by senior remote roles, large employers, and postings that often ask for Python, AWS, Tableau, or Azure.

Jobee counted 9,627 open SQL jobs in the United States on 22 November 2026. These are Jobee’s counts of open postings on that date. The market is mostly remote, mostly senior, and often pairs SQL with Python, cloud tools, and analytics platforms; salary is shown in most postings, and the yearly pay that is stated clusters around 156,000 USD.

SQL jobs in the United States: who is hiring

A small number of employers account for a large share of the SQL openings Jobee collected. Amazon.com Services LLC leads with 1,228 postings, followed by Google with 471, Databricks with 212, Bright Vision Technologies with 159, Salesforce with 157, Amazon Data Services, Inc. with 142, Stripe with 134, Amazon Web Services, Inc. with 132, Anthropic with 117, Waymo with 102, Sigma Computing with 85, and NVIDIA with 80.

That list tells you something practical about this market: SQL work is not confined to database administration roles. It sits inside large engineering, data, cloud, and platform teams. The biggest employers here are looking for people who can use SQL as part of a broader data stack, not just write queries in isolation.

For an applicant, the concentration matters. A role at one of the very large employers often means a more formal process, a broader skills checklist, and a title that may not say “SQL” even when SQL is central to the work. If you are targeting this market, search beyond exact job titles and look for postings where SQL is one requirement among several.

SQL jobs in the United States: how remote the market is

Remote work dominates this slice. 5,760 of 9,627 postings are remote, which is 59.8%. Hybrid roles account for 446 of 9,627 postings, which is 4.6%. On-site roles account for 432 of 9,627 postings, which is 4.5%. Another 2,989 of 9,627 postings, or 31.0%, do not say where the work happens.

That means the location field is often incomplete, but where employers do specify it, remote is far more common than hybrid or on-site. For job seekers, the main takeaway is simple: a SQL search in the United States is not primarily a commuting search. It is usually a remote search, and even when work location is not stated, many postings leave room for flexibility.

This also changes how you apply. If you need remote work, you should not assume the absence of a location label means in-office. The posting may simply be underspecified. That makes the location filter useful, but not enough on its own; the responsibility shifts to reading the full advert carefully.

SQL jobs in the United States: what seniority employers want

Senior roles make up the biggest share of the market. There are 4,235 senior postings, which is 44.0%. Mid-level roles account for 1,534 postings, or 15.9%. Lead roles account for 1,332 postings, or 13.8%. 1,313 postings, or 13.6%, do not state a seniority level.

The rest of the market is much smaller. There are 351 junior postings, 348 director postings, 295 staff postings, 114 intern postings, 88 principal postings, 12 VP postings, and 5 C-level postings.

The message is clear: employers want experienced SQL talent more than entry-level help. Even when the job is not explicitly labeled senior, the surrounding skill list often pushes it in that direction. That is useful if you already have experience, because the market is broad. It is harder if you are early in your career, because junior and intern roles are a small minority.

If you are applying without deep experience, pay close attention to the postings that do not state seniority. They may be the most flexible on background, but they also may not be junior at all. In this market, “not stated” often means you need to read the details and infer the level from the responsibilities.

SQL jobs in the United States: what else employers ask for

SQL is rarely asked for alone. The most common companion skill is Python, which appears in 4,499 postings, or 46.7%. AWS appears in 2,468 postings, or 25.6%. Tableau appears in 1,589 postings, or 16.5%. Azure appears in 1,585 postings, or 16.5%. Agile appears in 1,317 postings, or 13.7%. CI/CD appears in 1,297 postings, or 13.5%. Java appears in 1,234 postings, or 12.8%. LLM appears in 1,107 postings, or 11.5%. Google Cloud appears in 1,062 postings, or 11.0%. Snowflake appears in 1,033 postings, or 10.7%. JavaScript appears in 960 postings, or 10.0%. Salesforce appears in 936 postings, or 9.7%.

This is the clearest picture in the whole dataset. Employers are not hiring for “SQL only” work; they are hiring for data roles where SQL is the baseline and other tools define the real job. Python leads by a wide margin, which suggests that scripting, analysis, automation, or data engineering work is commonly attached to the role. Cloud skills are also prominent: AWS, Azure, and Google Cloud all show up often enough to matter.

The analytics stack is visible too. Tableau and Snowflake both appear frequently, which points to reporting, dashboarding, and data platform work. The appearance of CI/CD and Agile suggests that some of these jobs sit inside product and engineering teams rather than in isolated reporting functions. Java, JavaScript, and Salesforce widen the picture further: SQL skills are being used in systems work, application-adjacent work, and customer-platform work as well.

For an applicant, the practical lesson is not to treat SQL as your only proof point. In this market, employers want to see SQL alongside at least one other tool from the data or engineering stack. If your background includes Python, cloud services, dashboards, or pipelines, put that close to the top of your application because it matches what these postings ask for most often.

SQL jobs in the United States: which cities show up most

The strongest city counts are in Seattle with 663 postings, San Francisco with 632, Washington with 499, New York with 418, Mountain View with 223, Austin with 217, Sunnyvale with 158, Nashville with 123, Chicago with 95, Atlanta with 88, Santa Clara with 77, and San Jose with 59.

That pattern is familiar for a data-heavy job market. The biggest clusters are in major tech and business centers, with especially strong concentration on the West Coast and in a few large East Coast and national-market cities. Seattle and the San Francisco Bay area stand out most strongly, which fits the employer list dominated by large technology and platform companies.

Because remote work is so common, city counts do not fully define the market. Still, they matter for hybrid and on-site applicants, and they matter if an employer’s posting is location-bound even when the role is remote-friendly in other cases. If you are location-sensitive, Seattle, San Francisco, Washington, New York, Mountain View, and Austin are the places that show up most often in this dataset.

SQL jobs in the United States: how many are recent

3,026 of 9,627 postings were posted in the last 30 days, which is 31.4%.

That tells you the market is active, but not every opening is brand new. A substantial share of the collected postings were older than the recent window, which means the page includes both fresh roles and roles that have stayed open long enough to remain visible. If you are applying, do not assume the newest-looking role is the only one worth your time. The market is broad enough that older postings may still be live.

The other practical point is pacing. Because the collection contains many openings, you can build a targeted list rather than applying blindly. The postings are numerous enough to reward filtering by seniority, employer, remote status, and companion skills.

SQL jobs in the United States: what they pay

Salary is stated in 5,652 of 9,627 postings, which is 58.7%. 3,975 of 9,627 postings, or 41.3%, do not state a salary.

That means pay transparency is better than in many markets, but it is still incomplete. More than two-fifths of the postings do not show pay, so you should not expect a salary figure in every advert. The job search implication is straightforward: if salary matters to you, treat the first screening call as the place to clarify it whenever the advert leaves it out.

For the 5,363 postings that state yearly pay in USD, the lower quartile is 125,000 USD, the median is 156,000 USD, and the upper quartile is 200,000 USD.

Those figures point to a strong compensation band for SQL talent when employers do disclose pay. The median at 156,000 USD suggests that the jobs being advertised are often more than basic query-writing roles. That fits the seniority data and the companion-skill data: many of these are data, analytics, or engineering jobs where SQL is one part of a larger stack.

The spread from 125,000 USD at the lower quartile to 200,000 USD at the upper quartile also suggests meaningful variation by employer, scope, and experience. Roles tied to cloud platforms, data engineering, or larger product teams are likely to sit higher in the band than simpler reporting roles, though the postings themselves are what should guide your expectations.

If a posting does not state a salary, that does not mean it pays poorly. It means you do not have enough information yet. In this market, because so many employers do publish pay, a missing salary is a reason to ask early rather than later.

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

Visa sponsorship is explicitly offered in 131 of 9,627 postings, which is 1.4%. 475 of 9,627 postings, or 4.9%, say they will not sponsor a visa. 667 of 9,627 postings, or 6.9%, say they require work authorization.

That is a narrow sponsorship market. Very few postings explicitly offer sponsorship, while several more state restrictions up front. If you need sponsorship, you cannot rely on the general size of the market. You need to focus on the small set of postings that actually say they can sponsor.

If you already have work authorization, the data still helps. Employers are telling you early and directly when that is required, which saves time if you do not fit the constraint. If the posting says nothing either way, it may still be worth asking, but the safest assumption is that the employer may have an unstated preference.

SQL jobs in the United States: what this means for applicants

This market rewards breadth. The biggest employers are large technology and platform companies. Most roles are remote or at least not tied to a fixed office. Seniority skews high. SQL almost always travels with another skill, especially Python and cloud tools. Salary is shown in a majority of postings, and when it is shown, the yearly pay sits in a solid professional range.

That means a strong application should not present SQL as a lone skill. It should show the surrounding work: analysis, pipelines, dashboards, cloud systems, data modeling, or product analytics. The postings themselves point toward hybrid skill profiles, and that is where applicants should focus.

If you are deciding whether to apply, use the counts as a filter. Remote roles are common enough to prioritize. Senior roles are common enough to search for even if your title is different. Salary is common enough that you can compare offers, but absent often enough that you should still ask. And if you need sponsorship, the small number of postings that offer it means you should screen for that requirement first.

What this rests on

Counted on 22 November 2026 across the openings Jobee had collected. Every figure above comes from this list.

open SQL jobs in the United States
9,627
employers hiring
2,477
posted in the last 30 days
3,026 (31.4%)
are remote
5,760 (59.8%)
are hybrid
446 (4.6%)
are on-site
432 (4.5%)
do not say where the work happens
2,989 (31%)
state a salary
5,652 (58.7%)
do not state a salary
3,975 (41.3%)
offer visa sponsorship
131 (1.4%)
say they will not sponsor a visa
475 (4.9%)
say they require work authorization
667 (6.9%)

See the SQL jobs in United States open now.