Claude Code for Engineering Bootcamp
Run an engineering workflow where Claude Code writes, tests and ships under your review.
Claude Code for 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 1CLAUDE.md SetupA CLAUDE.md file and project settings that make Claude Code follow a repo's conventions
- Weeks 1–2Driving Claude CodeA feature shipped to a real repo entirely through Claude Code, with your review log
- Week 3Characterisation TestsA test file that pins the current behaviour of one legacy module before any change
- Weeks 3–4Codebases you did not writeA refactor of a legacy codebase with tests added first, deployed
- Weeks 5–6Agentic workflowsA team workflow: hooks, skills and a review gate, in use on a repo
- Week 7Review ChecklistA review checklist run by Claude Code on a pull request, with its findings logged
- Weeks 7–8QualityA security and performance pass on a real service, with findings fixed
- Week 9Spec to PlanA written spec turned into a task plan by Claude Code, with each step tracked in GitHub
- Weeks 9–10ShippingThe capstone: a product feature 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 to run an engineering workflow where Claude Code writes, tests and ships under their review.
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, context and CLAUDE.mdTasks, plans and reviewWhen to trust, when to readWeek 1
Driving Claude Code
- Setup, authentication, permissions
- CLAUDE.md and project context
- Tasks, plans and review
- When to trust and when to read
You build: First feature through Claude Code with a review log
Week 2Project 1: a feature, reviewed
- Explaining every hunk of a diff
- Review logs as evidence
You build: A feature shipped to a real repo entirely through Claude Code
Project 1 · the gate at week 2A feature, reviewed
A feature shipped to a real repo entirely through Claude Code, with your review log
You hand in- The merged feature
- CLAUDE.md
- A review log explaining each change in your own words
The gateEvery change in the diff is explained in your own words.
What you can do by week 12.
Six shipped features and refactors, every one reviewed by you, and a repeatable agentic engineering workflow you can install on any team's repository in a day.
- 1
Set up Claude Code on a real repository with project context that makes the agent better, and drive it through plans, tasks and reviews.
- 2
Map a codebase you did not write with an agent, add tests first, and refactor without changing behaviour.
- 3
Build a team workflow of hooks, skills and subagents that stops a bad change before it lands.
- 4
Run security and performance passes with an agent and verify every finding yourself.
- 5
Ship a feature from spec to production through the full workflow, with CI/CD, release notes and an incident plan.
- 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
A feature, reviewed
Every change in the diff is explained in your own words
- Week 4Graded, gate signed
The refactor
Coverage rises and behaviour is unchanged
- Week 6Graded, gate signed
The team workflow
A bad change is stopped by the workflow, not by luck
- 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 Claude Code for Engineering Bootcamp, answered from the plan on this page.
- Claude Code or Codex: which coding agent should an engineering team use?
- How do you start using Claude Code on a real codebase?
- Claude Code from Zero · 10.5 h on demand
- Codex for Software Engineering Bootcamp · 12-week live bootcamp
- Codex from Zero · 9.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 features and refactors, 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.
