Courses / Live bootcamps
LLMOps Bootcamp
Serve, observe and pay for LLMs in production without surprises.
- 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.
Backend and DevOps engineers who are being asked to run LLM systems and want to do it without surprises.
Before you start
Backend or DevOps experience; Docker and one cloud.
Skills
- Python
- Kubernetes
- vLLM
- gateways
- tracing
- CI/CD
- SLOs
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
Serving
Weeks 1 to 2Week 1
Serving
- Hosted APIs versus self-hosting
- vLLM
- Batching, streaming, quantisation
- GPUs and cost
You build: A model endpoint
Week 2
Project 1: serving
- Load testing
- p95 reporting
You build: Self-hosted endpoint with load tests
Project 1, the gate at week 2
Serving
Serve an open-weight model at a stated throughput and latency.
You hand in
- vLLM deployment
- Load tests
- p95 report
The gate
Throughput and p95 latency under load reported.
- 2
Gateways
Weeks 3 to 4Week 3
Gateways
- Routing, retries, fallbacks
- Rate limits and budgets
- Caching
- Multi-provider
You build: A gateway
Week 4
Project 2: the gateway
- Outage simulation
- Budget enforcement
You build: Gateway with fallback surviving an outage
Project 2, the gate at week 4
Gateway
One endpoint in front of three providers that never shows a user an outage.
You hand in
- Gateway
- Routing rules
- Fallback tests
- Budgets
The gate
A provider outage survived without user-visible errors.
- 3
Observability
Weeks 5 to 6Week 5
Observability
- Tracing prompts and tools
- Token and cost accounting
- Online quality signals
You build: Tracing and cost dashboard; squads form
Week 6
Project 3: attribution
- Per-feature cost
- Dashboards
You build: Every request attributed to a feature and a cost
Project 3, the gate at week 6
Observability
Know what every request cost and which feature spent it.
You hand in
- Tracing
- Cost dashboard
- Quality signals
The gate
Every request attributable to a feature and a cost.
- 4
Release engineering
Weeks 7 to 8Week 7
Release engineering
- Prompt and model versioning
- Canaries and rollbacks
- Evals in the release path
You build: Release pipeline
Week 8
Project 4: safe releases
- Automatic rollback
- Release evals
You build: A bad release rolled back automatically
Project 4, the gate at week 8
Release pipeline
Change prompts and models without fear.
You hand in
- Versioning
- Canary
- Rollback automation
- Evals in the path
The gate
A bad release rolled back automatically.
- 5
Reliability at scale
Weeks 9 to 10Week 9
Reliability at scale
- Capacity planning
- Incident response for AI
- Secrets and security
- Runbooks
You build: Platform design
Week 10
Project 5 and the viva
- The platform with SLOs
- Defending the incident history
You build: The platform with SLOs, runbooks and a cost model; the viva
Project 5, the gate at week 10
The platform
Run it for a company with SLOs.
You hand in
- Capacity plan
- Runbooks
- SLO dashboard
- Cost model
- Incident log
The gate
The viva: defend the platform and its incident history.
- 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 platform 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 platform 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.
The platform layer every company running LLMs needs: serving, a gateway, observability, safe releases and runbooks, built once and carried to any team.
- 1
Serve open-weight models with vLLM, batching, streaming and quantisation, and load-test them.
- 2
Build an LLM gateway with routing, retries, fallbacks, rate limits, budgets and caching.
- 3
Trace prompts and tool calls, account for tokens and cost, and surface quality signals online.
- 4
Version prompts and models, run canary releases and roll back automatically.
- 5
Plan capacity, respond to incidents and manage secrets for AI systems.
- 6
Defend a platform's design, cost and incident history.
Roles this prepares you for
- LLMOps engineer
- ML platform engineer
- AI infrastructure engineer
- SRE (AI)
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, LLMOps Bootcamp
Example
- Week 2Graded, gate signed
Serving
Throughput and p95 latency reported under load
- Week 4Graded, gate signed
Gateway
A provider outage is survived without user-visible errors
- Week 6Graded, gate signed
Observability
Every request is attributable to a feature and a cost
- Week 8Graded, gate signed
Release pipeline
A bad release is rolled back automatically
- Week 10Graded, gate signed
The platform
A viva: defend the platform and its incident history
- 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.