Skip to content

Courses / Live bootcamps

Live bootcampTaught live on Zoom, one instructor

Analytics Engineer Bootcamp

SQL, modelling and AI-assisted analysis that a finance team trusts.

weeks, live on Zoom
12
hours a week
15
deployed projects
6
minutes 1-1, every week
30

Who it is for, and what you receive.

Analysts with some SQL and spreadsheet fluency who want to own the metrics layer a finance team trusts, with AI on top of it.

Before you start

Some SQL; spreadsheets fluency.

Skills

  • SQL
  • dbt
  • metrics layers
  • dashboards
  • LLMs over data
  • governance

A week, about 15 hours

Live on Zoom
4h
Recorded lessons and exercises
6h
The project
5h
  1. 1

    Six deployed projects

    Each graded by Nova against a published rubric and signed off by the instructor at the gate.

  2. 2

    The recorded lessons

    The track's lessons and exercises, graded line by line, open for twelve months after the cohort ends.

  3. 3

    Live on Zoom every week

    A 90-minute live code review, a 60-minute squad lab, 60 minutes of office hours, and a 30-minute 1-1 with your instructor.

  4. 4

    Your hiring plan

    Opened in week 1 and reviewed in every 1-1: target roles, the gap map, the proof list, weekly actions, an interview log, the outcome.

  5. 5

    The record

    Every grade and every project with its repository at square1ai.com/u/{handle}, and the recording of your viva, verifiable by any employer.

  6. 6

    The certificate

    A credential ID that resolves at square1ai.com/verify to the real completion.

  7. 7

    The hiring sprint

    Weeks 11 and 12: CV and portfolio from graded work, applications, mock interviews scored against the role, demo day.

  8. 8

    Nova for twelve weeks

    A tutor with every submission of yours in its memory, at 2am as well as in class.

Twelve weeks in six blocks.

Each block teaches for a week, then you build and deploy a project, then a gate checks it before the next block opens. The project and its gate are the block's record entry.

Live time each week on Zoom: a 90-minute class where the instructor reviews real submissions, a 60-minute squad lab, 60 minutes of office hours, and your own 30-minute 1-1. Nothing is lectured live; the recorded lessons do that.

  1. 1

    SQL mastery

    Weeks 1 to 2

    Week 1

    SQL mastery

    • Advanced SQL
    • Window functions and performance
    • Reading a query plan

    You build: A reporting layer

    Week 2

    Project 1: reporting

    • Correctness
    • Time budgets

    You build: A reporting layer over a real schema, deployed

    Project 1, the gate at week 2

    Reporting

    A reporting layer over a real e-commerce schema that is correct and fast.

    You hand in

    • Queries
    • Query plans
    • Timing report

    The gate

    Queries are correct and within a time budget.

  2. 2

    Modelling

    Weeks 3 to 4

    Week 3

    Modelling

    • Dimensional modelling
    • dbt-style layers and tests
    • Documentation

    You build: A model layer

    Week 4

    Project 2: the model layer

    • Tests per model
    • Descriptions

    You build: A tested, documented model layer

    Project 2, the gate at week 4

    The model layer

    Dimensional models with a test and a description for every one.

    You hand in

    • Models
    • Tests
    • Documentation

    The gate

    Every model has tests and a description.

  3. 3

    Metrics

    Weeks 5 to 6

    Week 5

    Metrics

    • A metrics layer
    • Definitions people agree on
    • Reconciling to finance

    You build: Metrics layer; squads form

    Week 6

    Project 3: reconciled

    • To the cent
    • Definition governance

    You build: A metrics layer reconciled to the books

    Project 3, the gate at week 6

    Reconciled

    A metrics layer that agrees with finance.

    You hand in

    • Metrics layer
    • Definitions
    • Reconciliation

    The gate

    Revenue reconciles to the cent.

  4. 4

    Self-serve

    Weeks 7 to 8

    Week 7

    Self-serve

    • Dashboards and semantic layers
    • AI over the metrics layer
    • Governance

    You build: An AI assistant over metrics

    Week 8

    Project 4: the assistant

    • Citing definitions
    • Guardrails

    You build: An assistant that answers questions over the metrics layer

    Project 4, the gate at week 8

    The assistant

    An AI assistant over the metrics layer that cites its definitions.

    You hand in

    • Semantic layer
    • Assistant
    • Governance rules

    The gate

    Answers cite the metric definition they used.

  5. 5

    Operating it

    Weeks 9 to 10

    Week 9

    Operating it

    • Freshness, incidents, on-call
    • Cost
    • Change management

    You build: Platform operations design

    Week 10

    Project 5 and the viva

    • The platform with monitoring
    • Defending a number to its source

    You build: The analytics platform with monitoring and a change process; the viva

    Project 5, the gate at week 10

    The platform

    Operate the analytics platform with monitoring and a change process.

    You hand in

    • Freshness monitoring
    • Incident process
    • Cost report
    • Change process

    The gate

    The viva: defend a number all the way to its source.

  6. 6

    Employer brief and hiring sprint

    Weeks 11 to 12

    Week 11

    Employer brief

    • A real problem from a hiring partner, in squads
    • A partner's analytics problem
    • Working to someone else's definition of done

    You build: The employer brief in progress

    Week 12

    Hiring sprint

    • CV and portfolio built from graded work
    • Applications and follow-ups in the hiring plan
    • Mock interviews scored against the role
    • Demo day

    You build: Project 6 delivered; demo day

    Project 6, the gate at week 12

    Employer brief

    A partner's analytics problem.

    You hand in

    • The brief delivered
    • Demo day

    The gate

    The brief's owner accepts the result.

What you can do by week 12.

Six deployed analytics systems ending in a metrics layer finance trusts and an AI assistant that cites its definitions, which is the analytics job as it now exists.

  1. 1

    Write advanced SQL, read a query plan and hit a time budget.

  2. 2

    Build dimensional models with tested, documented layers.

  3. 3

    Build a metrics layer with definitions people agree on and reconcile it to the books.

  4. 4

    Put dashboards, a semantic layer and an AI assistant over the metrics with governance.

  5. 5

    Run the analytics platform: freshness, incidents, cost, change management.

  6. 6

    Defend a number all the way to its source.

Roles this prepares you for

  • Analytics engineer
  • BI engineer
  • Data analyst (senior)
  • Metrics or semantic-layer engineer

No placement rate is shown, because there are no graduates to count yet. The roles above are what the projects are built for.

Your record at week 12.

Every exercise and project is graded by Nova against a rubric you can read, and every grade is kept on one page an employer can open and run. This is what the programme writes to it.

Graded, line by line
Nova reads every submission against the brief and the rubric and returns a score, what you did well and what to fix.
Six gates
A block does not open until the previous project passes its gate. You always know where you are and what is next.
A weekly 1-1
Thirty minutes with your instructor, who has already read your code before the call.
One page an employer can run
Every grade, project and the viva recording at /verify. An employer opens it, runs the code and watches you defend it.

Record, Analytics Engineer Bootcamp

Example

  1. Week 2

    Reporting

    Queries are correct and within a time budget

    Graded, gate signed
  2. Week 4

    The model layer

    Every model has tests and a description

    Graded, gate signed
  3. Week 6

    Reconciled

    Revenue reconciles to the cent

    Graded, gate signed
  4. Week 8

    The assistant

    Answers cite the metric definition they used

    Graded, gate signed
  5. Week 10

    The platform

    A viva: defend a number all the way to its source

    Graded, gate signed
  6. Week 12

    Employer brief

    The brief's owner accepts the result

    Graded, gate signed
  7. Weeks 1 to 12

    Twelve 1-1 notes

    What your instructor saw in your work each week, and what you agreed to do next.

    Kept
  8. Week 12

    Your hiring plan and its outcome

    Target roles, the gap map, applications, interviews and where you landed.

    Kept

The entries, not the grades: those are yours to earn. The page lives at /verify and an employer needs no account to open it.

8 entries, twelve weeks. One email when applications open.

No account, no card. One email when it opens; we never sell before it exists.

How we help you find a job.

The last block is not curriculum. It is the hiring sprint, and the proof you built in the ten weeks before it.

  1. 1

    Your hiring plan, from week 1

    Six parts you and your instructor keep: target roles, the gap map from real postings, the proof to send, weekly actions, an interview log, the outcome. Read before every 1-1.

  2. 2

    The hiring sprint

    Weeks 11 and 12: CV, portfolio, applications, mock interviews, and demo day in front of hiring partners.

  3. 3

    A record an employer can run

    Your six deployed projects and the recorded viva on /verify. An employer opens it, runs the code and watches you defend it.

  4. 4

    The career agent

    Paste a real job posting at /career and it maps the role to your graded work and what to do next.

  5. 5

    The roles directory

    Every role we prepare people for, what it pays and what it asks, at /roles.

One email when applications open.

Fifty seats, one instructor, twelve weeks. The waitlist hears the date and the price first, and nothing is charged before the cohort exists.

No account, no card. One email when it opens; we never sell before it exists.