Codex from Zero

From first task to a merged release with Codex as the pair.

recorded hours: 9.5
modules, in order: 7
deployed projects: 3
graded checkpoints: 6

Who it is for, and what you receive.

Software engineers in any language who want Codex as the pair from first task to a merged release.

Before you start

You write software in any language.

Skills

Codex
code review
testing
release engineering

1
The recorded sessions
Taught by an instructor who does the work, taken in order at your own pace, yours for twelve months.
2
Graded work after every module
Exercises and projects marked by Nova against a rubric you can read, with what you did well and what to fix.
3
The projects
Deployed and graded, each one on your record with its repository.
4
Your hiring plan
The same six-part plan the bootcamps use, run with the career agent.
5
The record and the certificate
Every grade at square1ai.com/u/{handle}; a credential ID that resolves at square1ai.com/verify.
6
Nova as your tutor
Help that is about your actual work, because it has read all of it.

The content plan, module by module.

9.5 recorded hours from an instructor, taken in order at your own pace. Nova grades the work at the end of each module.

1
Setup, sandboxes and approvals
- Installing
- Sandbox modes
- Approval policies
- A first task
Graded
Your first shipped change, reviewed
60 min
2
Specs an agent can execute
- What a good spec contains
- Acceptance criteria
- Checking the diff against the spec
Graded
A spec and the diff it produced
90 min
3
Reproduce, then fix
- Triage with an agent
- Failing test first
- Fix and verify
Graded
Three issues closed with failing tests first
90 min
4
Delegating in the cloud
- Cloud tasks
- Parallel delegation
- Bringing work back
Graded
Two parallel tasks merged
60 min
5
Reviewing many diffs a day
- A review checklist
- What to read closely
- Merge discipline
Graded
Nothing to submit; watch and take notes
60 min
6
Security and quality passes
- Threat modelling with an agent
- Static analysis
- Verifying findings
Graded
A hardening pass with verified fixes
90 min
7
Project: a release end to end
- Spec
- Build
- Review
- Release notes
- Ship
Graded
The release, deployed, with notes
120 min

The projects.

Each is deployed and graded by Nova against a rubric you can read before you start.

1
A reviewed feature
Ship a feature through Codex with a spec and review notes that agree.
You hand in
- Spec
- Merged feature
- Review notes
The rubric requires
Spec, diff and review agree.
2
Ten issues
Close ten issues on an open-source repository, each reproduced first.
You hand in
- Ten fixes
- A failing test per issue
The rubric requires
Every fix has a failing test that now passes.
3
A release
A release from spec to production.
You hand in
- Release
- Notes
- Verification
The rubric requires
The release ships with its notes and a green suite.

What you can do at the end.

A Codex workflow for building and maintaining software, ten public fixes, and three graded projects on your record.

1
Set up Codex with sandboxes and approvals and ship a first reviewed change.
2
Write specs an agent can execute and check the diff against them.
3
Reproduce bugs with a failing test before letting the agent fix them.
4
Delegate tasks to the cloud and merge them without regressions.
5
Review many diffs a day with a checklist that catches what matters.
6
Run security and quality passes and verify every fix.

Roles this prepares you for

Software engineer (AI-assisted)
Maintainer

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 the end.

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.
Module by module: Each module ends in graded work; the next opens when you are ready, on your own schedule.
Nova remembers: Help is about your actual work, because the tutor has every submission and every failed exercise of yours.
One page an employer can run: Every grade and project at /verify. An employer opens it and runs the code.

Record, Codex from Zero

Example

Project
A reviewed feature
Spec, diff and review agree.
Graded
Project
Ten issues
Every fix has a failing test that now passes.
Graded
Project
A release
The release ships with its notes and a green suite.
Graded
Every module
6 graded checkpoints
Each module ends in work Nova grades line by line against a rubric you can read.
Graded
After
Your hiring plan
Target roles, the gap map, the proof to send, weekly actions and an interview log.
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.

5 entries, at your own pace. One email when this course opens.

How we help you find a job.

Proof, not a certificate: the projects you deployed are the thing you show, and the tools below are yours to use.

1
Your hiring plan
The same six-part plan the bootcamps use: target roles, the gap map, the proof to send, weekly actions, an interview log, the outcome. You run it with the career agent.
2
A record an employer can run
Your graded projects on /verify. An employer opens it and runs the code.
3
The career agent
Paste a real job posting at /career and it maps the role to your graded work and what to do next.
4
The roles directory
Every role we prepare people for, what it pays and what it asks, at /roles.
5
A path to the live cohort
If you want the instructor, the gates and the hiring sprint, the bootcamp on the same subject is one waitlist away.

One email when this course opens.

Recorded by an instructor who does this work, graded by Nova. The waitlist hears the date and the price first, and nothing is charged before it exists.