Blokken AIFIELD GUIDE
← Back to home
THE WORK, NOT THE HYPE

Data Analyst with AI.

Explore how AI changes your work — and what to learn next.

A practical guide to
the work ahead
Data AnalystSQL QueryingGrowing Practice

SQL Querying

Draft SQL from the schema and stated metric definition.

The workflow, side by side

Traditional workflow

Before generative AI assistance
  1. 1

    Clarify the goal using an orders table and a monthly revenue question

  2. 2

    Define revenue and reporting dates

  3. 3

    Write joins and filters

  4. 4

    Reconcile totals with known records

  5. 5

    Check the result against the agreed criteria

  6. 6

    Communicate the outcome and record the decision

AI-assisted workflow

AI contributes. You guide and verify.
  1. 1

    Define the goal, constraints, and permitted information

  2. 2

    Provide relevant, sanitized context from an orders table and a monthly revenue question

  3. 3

    Ask AI to draft SQL from the schema and stated metric definition

    AI + YOU
  4. 4

    Inspect suggestions against original evidence and domain rules

  5. 5

    Revise the output and independently validate the result

    YOU
  6. 6

    A responsible professional approves and communicates the outcome

HUMAN CHECKPOINT

Is the AI-generated analysis consistent with the business definition of the metric?

Your judgment matters

The shift: Validating AI-generated SQL and interpreting business meaning. Foundational skills still matter.

Build the skills behind the work.

A practical learning path for Data Analyst.

GO A LITTLE DEEPEROpen only what you need
What changes — and what doesn’tSkills & responsibilities
AI HELPS WITH
AnalyzeReview

Draft SQL from the schema and stated metric definition. The output is a starting point to inspect, not a decision to accept automatically.

STILL YOUR RESPONSIBILITY

Verify data quality, define metrics, interpret uncertainty, and explain findings.

Skills to develop

FoundationsSQL, statistics, data modeling, and business definitions.

AI collaborationProviding task-specific context and requesting explicit assumptions.

VerificationChecking an orders table and a monthly revenue question against independent evidence.

Professional skillsCommunicating tradeoffs and taking responsibility.

Where AI can go wrong3 things to check

A plausible but wrong answer

A join can multiply order rows and inflate revenue. It can fail the underlying goal even when it sounds convincing.

Your check

Aggregate at the correct grain or avoid summing repeated order totals.

Missing or invented context

AI may fill gaps with unsupported assumptions, which can send the work in the wrong direction.

Your check

Trace claims to original evidence and ask the relevant person about unknowns.

Information shared in the wrong place

Sensitive records or code can cross confidentiality boundaries if supplied to an unsuitable tool.

Your check

Use approved tools, share the minimum context needed, and follow your organization’s rules.

Try a quick exerciseA practical scenario

Joining orders to order_items repeats each order total for every item.

What is the most important next step in this scenario?
Sources & contextEvidence behind this example

These are illustrative workflows, not claims that AI is always better or that every organization works this way. The scenarios and checkpoints are editorial teaching examples.

Reviewed September 2026 · Growing PracticeO*NET — Business Intelligence AnalystsA related occupation used to ground analytical tasks; Data Analyst is a broader title.Microsoft — Responsible use of Copilot in Power BIDocuments analytical assistance and the need to review generated queries and provide model context. Power BI examples use DAX; our SQL examples are editorial adaptations.How we build these examples