Courses / Live bootcamps
Codex for Software Engineering Bootcamp
Build and maintain real codebases with Codex as the pair, from spec to release.
- 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.
Working software engineers, any language, who want Codex as the pair from spec to release, including the maintenance nobody enjoys.
Before you start
You already write software; any language.
Skills
- Codex
- TypeScript or Python
- testing
- maintenance
- CI/CD
- security review
A week, about 15 hours
- Live on Zoom
- 4h
- Recorded lessons and exercises
- 6h
- The project
- 5h
- 1
Six deployed projects
Each graded by Nova against a published rubric and signed off by the instructor at the gate.
- 2
The recorded lessons
The track's lessons and exercises, graded line by line, open for twelve months after the cohort ends.
- 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
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
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
The certificate
A credential ID that resolves at square1ai.com/verify to the real completion.
- 7
The hiring sprint
Weeks 11 and 12: CV and portfolio from graded work, applications, mock interviews scored against the role, demo day.
- 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
Driving Codex
Weeks 1 to 2Week 1
Driving Codex
- Setup, sandboxes, approvals
- Specs an agent can execute
- Reading and challenging its work
You build: First feature with a written spec
Week 2
Project 1: spec and diff
- Spec discipline
- Review notes
You build: A feature shipped through Codex with spec and review
Project 1, the gate at week 2
Spec and diff
Ship a feature through Codex from a written spec, and show the spec, the diff and your review agree.
You hand in
- Spec
- The merged feature
- Review notes
The gate
Spec, diff and review agree.
- 2
Maintenance
Weeks 3 to 4Week 3
Maintenance
- Bug triage with an agent
- Reproduce before fixing
- Dependency and framework upgrades
You build: Issues reproduced with failing tests
Week 4
Project 2: ten issues
- Open-source contribution etiquette
- Test-first fixes
You build: Ten real issues closed on an open-source repo
Project 2, the gate at week 4
Ten issues
Close ten real issues on an open-source repository, each reproduced with a failing test first.
You hand in
- Ten merged or submitted fixes
- A failing test per issue
The gate
Every fix has a failing test that now passes.
- 3
Parallel work
Weeks 5 to 6Week 5
Parallel work
- Delegating tasks in the cloud
- Reviewing many diffs a day
- Merging without regressions
You build: A day of delegated tasks; squads form
Week 6
Project 3: the parallel week
- Merge queues
- Regression suites
You build: A week of parallel delegated tasks merged into one repo
Project 3, the gate at week 6
The parallel week
Delegate a week of tasks to Codex in the cloud and merge them into one repository without a regression.
You hand in
- Task log
- Merged diffs
- Suite results
The gate
No regression in the suite across the merged work.
- 4
Quality and security
Weeks 7 to 8Week 7
Quality and security
- Threat modelling with an agent
- Static analysis and secrets
- Performance profiling
You build: A hardening pass
Week 8
Project 4: hardening
- Reproducing findings
- Verifying fixes
You build: Findings fixed and verified on a real service
Project 4, the gate at week 8
Hardening
Threat-model, analyse and profile a service with the agent, and fix what you find.
You hand in
- Threat model
- Findings with reproductions
- Fixes
- Verification
The gate
Findings are reproduced, fixed and verified.
- 5
Shipping
Weeks 9 to 10Week 9
Shipping
- Release engineering with agents
- Documentation and changelogs
- On-call with an agent
You build: Release pipeline
Week 10
Project 5 and the viva
- Spec to production
- Defending the decisions
You build: A product from spec to production; the viva
Project 5, the gate at week 10
Spec to production
A product from a written spec to production through the full workflow.
You hand in
- Spec
- The product
- Release pipeline
- Changelog
- On-call plan
The gate
The viva: defend what the agent did and what you decided.
- 6
Employer brief and hiring sprint
Weeks 11 to 12Week 11
Employer brief
- A real problem from a hiring partner, in squads
- A partner's engineering 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 engineering 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 shipped pieces of software, ten public fixes with your name on them, and a repeatable workflow for building and maintaining software with an agent.
- 1
Set up Codex with sandboxes and approvals and write specs an agent can execute.
- 2
Triage, reproduce and fix bugs with an agent, always with a failing test first.
- 3
Delegate work to the cloud, review many diffs a day and merge without regressions.
- 4
Threat-model, statically analyse and profile a service with an agent, and verify the findings.
- 5
Ship a product from spec to production with agent-run release engineering.
- 6
Defend what the agent did and what you decided, on camera.
Roles this prepares you for
- Software engineer (AI-assisted)
- Maintainer
- Developer productivity engineer
- Engineering manager
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, Codex for Software Engineering Bootcamp
Example
- Week 2Graded, gate signed
Spec and diff
Spec, diff and review agree
- Week 4Graded, gate signed
Ten issues
Every fix has a failing test that now passes
- Week 6Graded, gate signed
The parallel week
No regression in the suite across the merged work
- Week 8Graded, gate signed
Hardening
Findings are reproduced, fixed and verified
- Week 10Graded, gate signed
Spec to production
A viva: defend what the agent did and what you decided
- Week 12Graded, gate signed
Employer brief
The brief's owner accepts the result
- Weeks 1 to 12Kept
Twelve 1-1 notes
What your instructor saw in your work each week, and what you agreed to do next.
- Week 12Kept
Your hiring plan and its outcome
Target roles, the gap map, applications, interviews and where you landed.
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.
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
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
The hiring sprint
Weeks 11 and 12: CV, portfolio, applications, mock interviews, and demo day in front of hiring partners.
- 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
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
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.