Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 125 ยท Getting Started

SQL Careers and Where SQL Is Used

See where SQL is used at work. Analyst, data engineer, DBA, BI developer and backend roles, the skills ladder for each, common certifications and industries, with live queries per role.

SQL is one of the few skills that has stayed useful for fifty years. It was designed in the 1970s, and today it sits underneath online shops, banks, hospitals, games, social networks, spreadsheets and the dashboards that managers look at every morning. Different jobs use it in very different ways, though, and knowing those differences helps you decide what to learn next and where to practice.

This lesson is a map, not a promise. Job titles vary between companies, salaries depend on country, experience and employer, and we deliberately don't quote numbers that would be out of date by next year. What does stay stable is the shape of the work, so that is what we describe. Each role below comes with a live query typed the way someone in that role might actually write it, run against a small shop database.

One language, five ways to use it

Role Typical question What they do with SQL
Data analyst "Which products drove sales last month?" Reads data: filters, joins, aggregates, window functions, then charts or reports the result
BI developer "Can the sales dashboard refresh daily?" Builds the views and models that feed dashboards; cares about definitions and consistency
Data engineer "Move yesterday's orders into the warehouse." Writes pipelines: transforms, incremental loads, data-quality checks, performance tuning
Backend developer "Show this customer their last 10 orders." Embeds queries in application code; designs tables, indexes and transactions
Database administrator (DBA) "Why did the nightly job get slow?" Runs the database itself: backups, security, monitoring, upgrades, query plans

Many people do several of these. A small company's "developer" often designs the schema, writes the queries, adds the indexes and restores the backup. Larger companies split the roles.

The analyst: reading and summarizing

Analysts spend most of their time with SELECT, JOIN, GROUP BY and window functions. The goal is an answer a human can act on.

SQL Analyst: revenue by category ยท database: shop

Press Run (or Ctrl + Enter) to see the result here.

Notice the choices that matter more than the syntax: cancelled orders are excluded on purpose, COUNT(DISTINCT ...) avoids counting an order once per item, and the result has readable column names. An analyst's real skill is deciding what the question means before writing a line. Related lessons: Joins, GROUP BY and Window Functions.

The BI developer: making numbers reusable

A dashboard should not contain a different copy of "revenue" in every chart. BI developers package definitions into views so that everyone reads the same logic.

SQL BI developer: one definition of revenue ยท database: shop

Press Run (or Ctrl + Enter) to see the result here.

Every chart that reads order_revenue now agrees on what an order is worth, and if the definition changes, you change one view. See Views.

The data engineer: moving and checking data

Data engineers build pipelines that copy data from many sources into one analytical store and verify it arrived intact. Their SQL is full of sanity checks:

SQL Data engineer: data-quality checks ยท database: shop

Press Run (or Ctrl + Enter) to see the result here.

The first two queries return nothing wrong here, and that is the point: a pipeline runs checks like these every night, and a non-empty result raises an alarm. Skills that matter in this job are JOINs, INSERT ... SELECT, CTEs, window functions for de-duplication, and understanding indexes and query plans.

The backend developer: SQL inside an application

A backend developer rarely types queries by hand. The application builds them from user actions, and parameters carry user input safely. Here is the kind of query behind an "order history" page:

SQL Backend developer: a page of one customer's orders ยท database: shop

Press Run (or Ctrl + Enter) to see the result here.

In production that 3 is a bound parameter, never text pasted into the SQL string, which is what prevents SQL injection. A backend developer also owns the schema, indexes for the hot queries, transactions for multi-step changes, and migrations.

The DBA: looking after the database itself

A DBA's questions are about the system: Is it backed up? Who may read what? Which queries are slow, and why? Many of the tools are database-specific, but the idea of asking the database about itself is universal. SQLite exposes its catalog like this:

SQL DBA: inspecting the schema ยท database: shop

Press Run (or Ctrl + Enter) to see the result here.

Other systems use information_schema and system views, and every serious database has EXPLAIN to show how a query will run. See query plans and Backup and Maintenance.

A skills ladder

Whatever role you aim for, the order in which to learn SQL is roughly the same. This site's chapters follow it:

  1. Foundations: SELECT, WHERE, ORDER BY, LIMIT, NULL, basic functions.
  2. Aggregation and joins: GROUP BY, HAVING, inner and outer joins. This is the line between "knows SQL" and "can answer real questions".
  3. Subqueries, CTEs and set operations: break a hard question into readable steps.
  4. Window functions: rankings, running totals, "compared with the previous row" analysis. They separate good analysts from average ones.
  5. Changing data and design: INSERT, UPDATE, DELETE, transactions, keys, constraints, normalization.
  6. Performance: indexes, query plans, avoiding full scans.
  7. A specific system: PostgreSQL, MySQL, SQL Server, Oracle, or a cloud warehouse, with its dialect differences. See SQL dialects.

Around that, learn adjacent tools: a spreadsheet and a charting tool for analysis, Python or R for statistics, Git for versioned queries, and a command-line client for your database.

Certifications and portfolios

Vendors and cloud providers offer certifications, typically around their own products: Microsoft's data and Azure exams, Oracle's database certifications, and the data and analytics tracks of the major cloud providers (AWS, Google Cloud). They can help when a job posting names a specific platform, and they prove commitment, but they rarely replace evidence of skill. Check each vendor's current list before planning your studies, because exam names change often.

The strongest evidence is a small portfolio: two or three projects on a public dataset, with the questions, the SQL, and a short write-up of what you found. The Projects chapter of this tutorial is a good source of ideas, and so is rebuilding the analyses from your own interests (sports results, public transport data, a game's statistics).

Where SQL shows up

  • Retail and e-commerce: orders, inventory, customers, recommendations.
  • Finance and insurance: ledgers, risk, fraud checks, regulatory reports. Accuracy and transactions matter most.
  • Healthcare: patient records, scheduling, research cohorts, with strict privacy rules.
  • Technology and media: product analytics, A/B tests, streaming statistics, ad reporting.
  • Logistics and travel: routes, bookings, availability, real-time tracking.
  • Government and education: census-style statistics, enrollment, open data.
  • Everywhere else: SQL is also hidden inside tools you may already use, such as spreadsheet connectors, BI products, mobile apps (SQLite is on almost every phone) and data notebooks.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which role is most concerned with backups, security and the performance of the database system itself?

    A DBA runs the database as a system (backups, access control, monitoring, upgrades and tuning). Analysts and BI developers mostly read data.
  2. 2. Why does a BI developer define revenue in a view instead of copying the calculation into each report?

    A shared view keeps definitions consistent across dashboards and avoids the situation where two charts report different numbers for the same name.
  3. 3. In the backend example, why is the customer id written as a parameter (?) in real application code?

    A bound parameter is sent as data, so it can never change the meaning of the statement. Pasting user input into the SQL string is how injection happens.
  4. 4. What is the best evidence of SQL skill for a job application?

    Certificates can help for a named platform, but projects show that you can turn a vague question into correct queries and an answer.

Summary

  • The same SQL serves analysts, BI developers, data engineers, backend developers and DBAs; each leans on a different part of the language.
  • Analysts need joins, aggregation and window functions; engineers add data-quality checks and pipelines; backend developers add parameters, transactions and indexes; DBAs add backups, security and query plans.
  • Learn in a steady order: foundations, aggregation and joins, subqueries and CTEs, window functions, changing data and design, performance, then one specific database system.
  • Certifications can support a platform-specific job, but a small portfolio of real analyses usually shows more.
  • SQL appears in nearly every industry, often hidden inside other tools.

Next: SELECT in Depth, where you'll start the Querying Data chapter with everything SELECT can do.