Codex for Software Engineering Bootcamp
Build and maintain real codebases with Codex as the pair, from spec to release.
Codex for Software Engineering Bootcamp is a 12-week live online bootcamp, taught on Zoom by one instructor at about 15 hours a week, with 6 deployed projects and a one-to-one every week. The founding price is A$200, down from A$400. Live sessions run on weekday evenings from 5:30 PM Sri Lanka and India time, with full-day sessions at weekends.
- Week 1Task Brief TemplateA task brief template for Codex, used to ship one small bug fix with tests
- Weeks 1–2Driving CodexA feature shipped through Codex with a written spec and your review notes
- Week 3Issue ReproductionA failing test that reproduces one open-source issue before any fix is attempted
- Weeks 3–4MaintenanceTen real issues closed on an open-source repo, each reproduced first
- Weeks 5–6Parallel workA week of parallel delegated tasks merged into one repo, deployed
- Week 7Dependency AuditA dependency audit of a repo with outdated and vulnerable packages updated and tested
- Weeks 7–8Quality and securityA hardening pass on a service with findings fixed and verified
- Week 9Release ChecklistA release checklist and Docker build that takes a branch from merge to running container
- Weeks 9–10ShippingThe capstone: a product from spec to production with the full workflow
- Weeks 11–12Employer brief and hiring sprintThe employer brief shipped, and demo day
- weeks, live on Zoom
- 12
- hours a week
- 15
- projects to build
- 10
- 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.
You already write software; any language.
- Live on Zoom
- 4h
- Set reading 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 twelve-week plan
Every week has its theme, its topics and what you build, published before you apply and taught live by your instructor.
- 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 parts.
Each part teaches for a week, then you build and deploy a project, then a gate checks it before the next part opens. The project and its gate are the part's entry on your record.
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.
- Key skillsSetup, sandboxes and approvalsSpecs that an agent can executeReading and challenging its workWeek 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 2Project 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 2Spec and diff
A feature shipped through Codex with a written spec and your review notes
You hand in- Spec
- The merged feature
- Review notes
The gateSpec, diff and review agree.
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.
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.
- 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
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. Reserving a spot holds the founding price.
Reserve a seatHow 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.
The whole plan on a few pages: the parts, the projects, the gates and the price. We email it to you.
Get the booklet- 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 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.
Questions people ask.
About Codex for Software Engineering Bootcamp, answered from the plan on this page.
- Claude Code or Codex: which coding agent should an engineering team use?
- How do you delegate coding tasks to an AI agent like Codex without losing control?
- Codex from Zero · 9.5 h on demand
- Claude Code for Engineering Bootcamp · 12-week live bootcamp
- Claude Code from Zero · 10.5 h on demand
One cohort, one instructor. Hold your spot.
A cohort of 25, one instructor, 12 weeks, six things you ship. Spot holders hear the start date first, and nothing is charged before you confirm.
- Six shipped pieces of software, every one reviewed by you
- A repeatable agentic engineering workflow
- A recorded viva
- Your record on /verify
About a minute. No account, no card, and nothing is charged until you confirm.