Skip to content

Courses / Live bootcamps

Live bootcampTaught live on Zoom, one instructor

Fine-Tuning and Open-Weights Bootcamp

Post-train, evaluate and deploy your own model for a real task.

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.

Engineers who need a model they own, for cost, latency, privacy or a task hosted APIs do badly. A GPU budget of about A$150 over the twelve weeks is stated up front.

Before you start

Python, some PyTorch, and a GPU budget (we say how much).

Skills

  • Python
  • PyTorch
  • LoRA
  • DPO
  • evals
  • serving
  • data curation

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

    Open weights

    Weeks 1 to 2

    Week 1

    Open weights

    • The open model landscape
    • Running and serving open weights
    • Benchmarks and baselines
    • Licences

    You build: Baseline eval

    Week 2

    Project 1: the baseline

    • Reproducibility
    • Choosing the task

    You build: Reproducible baseline of three models

    Project 1, the gate at week 2

    Baseline

    Pick the right open model for a structured-extraction task.

    You hand in

    • Eval harness
    • Three baselines
    • Report

    The gate

    Reproducible from the repo.

  2. 2

    Data

    Weeks 3 to 4

    Week 3

    Data

    • Building a training set
    • Synthetic data
    • Filtering and deduplication
    • Provenance and licensing

    You build: Curated dataset

    Week 4

    Project 2: the data

    • Provenance per example
    • Documentation

    You build: Documented training set

    Project 2, the gate at week 4

    Training data

    Build the data that will make the model better.

    You hand in

    • Curated set
    • Synthetic augmentation
    • Provenance and licence per example

    The gate

    Every example has a source and a licence.

  3. 3

    Supervised fine-tuning

    Weeks 5 to 6

    Week 5

    Supervised fine-tuning

    • LoRA and full fine-tuning
    • Training loops and checkpoints
    • Evals during training
    • Overfitting

    You build: SFT run; squads form

    Week 6

    Project 3: SFT

    • Held-out evaluation
    • Deploying a checkpoint

    You build: A fine-tuned model that beats the baseline

    Project 3, the gate at week 6

    SFT

    Beat the baseline.

    You hand in

    • LoRA fine-tune
    • Checkpoints
    • Training evals
    • Deployed endpoint

    The gate

    The gain measured on a held-out set.

  4. 4

    Preference tuning

    Weeks 7 to 8

    Week 7

    Preference tuning

    • DPO and its relatives
    • Reward signals
    • Safety tuning

    You build: DPO run

    Week 8

    Project 4: preference

    • Preference sets
    • Win-rate evals

    You build: Preference-tuned model with a win-rate eval

    Project 4, the gate at week 8

    Preference tuning

    Make it prefer the right answers.

    You hand in

    • DPO run
    • Preference set
    • Win-rate eval

    The gate

    Win rate against the SFT model measured.

  5. 5

    Deployment

    Weeks 9 to 10

    Week 9

    Deployment

    • Quantisation and serving
    • Cost per token versus a hosted API
    • Monitoring a custom model

    You build: Serving plan

    Week 10

    Project 5 and the viva

    • The model in production
    • Defending the data and the cost

    You build: Your model in production with monitoring and a cost comparison; the viva

    Project 5, the gate at week 10

    Production

    Serve it cheaper than the API.

    You hand in

    • Quantised model
    • Serving
    • Monitoring
    • Cost comparison

    The gate

    The viva: defend the model, its data and its cost.

  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 model 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 model 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.

A post-training method from data to serving, and a model you trained and own, with the numbers to show when it beats the hosted API.

  1. 1

    Choose among open-weight models with reproducible baseline evals.

  2. 2

    Build a training set with provenance, licensing and filtering, including synthetic data.

  3. 3

    Fine-tune with LoRA and full fine-tuning, with checkpoints and evals during training.

  4. 4

    Preference-tune with DPO and measure win rate against the SFT model.

  5. 5

    Quantise, serve and monitor a custom model and compare its cost to a hosted API.

  6. 6

    Defend a model, its data and its cost.

Roles this prepares you for

  • ML engineer (LLM)
  • Applied scientist
  • AI engineer (fine-tuning)

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, Fine-Tuning and Open-Weights Bootcamp

Example

  1. Week 2

    Baseline

    The baseline is reproducible from the repo

    Graded, gate signed
  2. Week 4

    Training data

    Every example has a source and a licence

    Graded, gate signed
  3. Week 6

    SFT

    The gain is measured on a held-out set

    Graded, gate signed
  4. Week 8

    Preference tuning

    Win rate against the SFT model is measured

    Graded, gate signed
  5. Week 10

    Production

    A viva: defend the model, its data and its cost

    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.