Courses / Live bootcamps
AI Automation Engineer Bootcamp
Replace six manual business processes with agents and automation that keep running.
- 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.
Operations people, analysts and generalist builders who want to replace manual business processes with automations and agents that keep running after they walk away.
Before you start
Comfortable with spreadsheets and one scripting language, or willing to learn Python in block one.
Skills
- n8n
- Make
- Python
- APIs
- LLM steps
- monitoring
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
Process to automation
Weeks 1 to 2Week 1
Process to automation
- Mapping a process worth automating
- n8n, Make and code: when each
- Triggers, queues, idempotency
- Python for people who did not think they needed it
You build: A process map and the first automation
Week 2
Project 1: one process
- Reruns
- Bad input
You build: One manual process automated end to end, on a schedule
Project 1, the gate at week 2
One process
Automate one manual process end to end, running on a schedule.
You hand in
- Process map
- The automation
- Rerun and bad-input tests
The gate
The automation survives a rerun and a bad input.
- 2
Agents in the loop
Weeks 3 to 4Week 3
Agents in the loop
- LLM steps with structured output
- Human approval steps
- Auditing what the agent did
You build: An approval-gated agent step
Week 4
Project 2: approval
- Evidence per decision
- Audit logs
You build: An approval-gated agent automation, deployed
Project 2, the gate at week 4
Approval
Add an LLM step that decides, a person who approves, and a log that shows why.
You hand in
- Agent step with structured output
- Approval queue
- Audit log
The gate
Every agent decision is logged with its evidence.
- 3
Integrations
Weeks 5 to 6Week 5
Integrations
- CRMs, spreadsheets, email, chat
- APIs without documentation
- Secrets and permissions
You build: A three-tool automation; squads form
Week 6
Project 3: three tools
- Failure isolation
- Retries
You build: A cross-system automation touching three tools
Project 3, the gate at week 6
Three tools
One automation across a CRM, a spreadsheet and a chat tool.
You hand in
- Integrations
- Secrets handling
- Failure isolation
The gate
Failures in one tool do not corrupt the others.
- 4
Reliability
Weeks 7 to 8Week 7
Reliability
- Monitoring automations
- Retries, dead letters, alerts
- Testing automations
You build: Monitoring and a test harness
Week 8
Project 4: monitored
- Seeded failures
- Paging
You build: A monitored automation with alerts and tests
Project 4, the gate at week 8
Monitored
Make an automation you would trust overnight.
You hand in
- Monitoring
- Retries and dead letters
- Alerts
- Test harness
The gate
A seeded failure pages someone and is recoverable.
- 5
Scale
Weeks 9 to 10Week 9
Scale
- Many automations, one platform
- Cost and ownership
- Documentation for operators
You build: Platform design
Week 10
Project 5 and the viva
- Six processes on one platform
- Defending the worst failure
You build: A small automation platform running six processes; the viva
Project 5, the gate at week 10
The platform
Six processes on one platform someone else can operate.
You hand in
- The platform
- Cost model
- Operator documentation
- Ownership plan
The gate
The viva: defend the platform and its worst failure.
- 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 operations 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 operations 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 automations that are monitored, not hoped for, and the judgement to choose no-code, code or an agent for each step of a real process.
- 1
Map a process worth automating and choose between no-code tools, code and an agent for each step.
- 2
Build automations with triggers, queues and idempotency that survive reruns and bad input.
- 3
Add LLM steps with structured output, human approval and an audit trail.
- 4
Integrate CRMs, spreadsheets, email and chat, and APIs without documentation, with secrets handled properly.
- 5
Monitor automations with retries, dead letters, alerts and a test harness.
- 6
Run a small automation platform and defend its worst failure.
Roles this prepares you for
- AI automation engineer
- Operations engineer
- Business systems analyst
- RevOps or BizOps engineer
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, AI Automation Engineer Bootcamp
Example
- Week 2Graded, gate signed
One process
The automation survives a rerun and a bad input
- Week 4Graded, gate signed
Approval
Every agent decision is logged with its evidence
- Week 6Graded, gate signed
Three tools
Failures in one tool do not corrupt the others
- Week 8Graded, gate signed
Monitored
A seeded failure pages someone and is recoverable
- Week 10Graded, gate signed
The platform
A viva: defend the platform and its worst failure
- 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.