Courses / Live bootcamps
Software Engineering with AI Bootcamp
Ship a full-stack product with coding agents, then prove the defect is fixed.
- 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.
People with some programming who want to become full-stack engineers the way the job now works: with coding agents, and with proof the code is right.
Before you start
Some programming; the first block starts from a blank repo.
Skills
- TypeScript
- React
- APIs
- databases
- testing
- coding agents
- CI/CD
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
Foundations
Weeks 1 to 2Week 1
Foundations
- A full-stack app from scratch with an agent
- Data model, auth, API
- Deploying on day three
You build: A working app with auth and a database
Week 2
Project 1: the app
- Production deploys
- Environment and secrets
You build: The app in production
Project 1, the gate at week 2
The app
A working web application with sign-up, sign-in, a database and one core action, in production by the end of week 2.
You hand in
- Deployed app
- Data model
- Auth
- API
The gate
Sign up, sign in and the core action work in production.
- 2
Core craft
Weeks 3 to 4Week 3
Core craft
- Tests as the contract
- Reviewing agent code
- Debugging what you did not write
You build: Tests and a CI pipeline
Week 4
Project 2: under test
- Coverage on core paths
- Green pipelines
You build: The app under test, deployed on every merge
Project 2, the gate at week 4
Under test
Put the app under test and deploy it on every merge.
You hand in
- Test suite
- CI pipeline
- Coverage report
The gate
Coverage on the core paths and a green pipeline.
- 3
Squad build
Weeks 5 to 6Week 5
Squad build
- Four people, one repo
- Pull-request-only workflow
- Code review that catches things
You build: Squad feature planning; squads form
Week 6
Project 3: the squad feature
- Rotating roles
- Reviewing each other
You build: A squad feature shipped through review
Project 3, the gate at week 6
The squad feature
Four people, one repository, one feature, shipped through pull requests and review.
You hand in
- The feature
- Review history
- Role rotation log
The gate
Every squad member reviewed and was reviewed.
- 4
Security and reliability
Weeks 7 to 8Week 7
Security and reliability
- OWASP with an agent's help
- Observability
- Fixing a defect and proving it
You build: A hardening pass
Week 8
Project 4: three defects
- Failing test first
- Verification
You build: Three defects found, fixed and proved
Project 4, the gate at week 8
Three defects
Find three real defects in the app, including one from the OWASP top ten, and prove each fix with a test.
You hand in
- Findings
- Failing tests
- Fixes
The gate
Each fix has a failing test that now passes.
- 5
Capstone
Weeks 9 to 10Week 9
Capstone
- Your own product
- Performance and cost
- Documentation
You build: Capstone in production
Week 10
Project 5 and the viva
- Monitoring
- Defending the code
You build: Your product in production with monitoring; the viva
Project 5, the gate at week 10
Capstone
Your own product, in production, monitored.
You hand in
- Deployed product
- Monitoring
- Performance notes
- Documentation
The gate
The viva: defend the code you and the agent wrote.
- 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 deployed applications and features, a working knowledge of agentic software engineering, and the habit that matters most: proving the code is right before you say it is.
- 1
Build a full-stack web application with auth and a database from a blank repository with an agent, and deploy it on day three.
- 2
Put an application under test with a CI pipeline and review agent-written code with judgement.
- 3
Work in a squad on one repository through pull requests and code review.
- 4
Find, fix and prove defects, including the OWASP top ten, with tests.
- 5
Ship your own product to production with monitoring, performance and documentation.
- 6
Defend the code you and the agent wrote, on camera.
Roles this prepares you for
- Full-stack engineer
- Software engineer
- Junior to mid engineer (AI-assisted)
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, Software Engineering with AI Bootcamp
Example
- Week 2Graded, gate signed
The app
Sign up, sign in and the core action work in production
- Week 4Graded, gate signed
Under test
Coverage on the core paths and a green pipeline
- Week 6Graded, gate signed
The squad feature
Every squad member reviewed and was reviewed
- Week 8Graded, gate signed
Three defects
Each fix has a failing test that now passes
- Week 10Graded, gate signed
Capstone
A viva: defend the code you and the agent wrote
- 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.