Courses / Live bootcamps
AI Sales Engineer Bootcamp
Run technical discovery, build the proof of concept, close the technical win.
- 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 who sell technical products, or engineers who want to, who need to run technical discovery, build the proof of concept and close the technical win.
Before you start
Either you sell technical products or you build them and want to.
Skills
- discovery
- demo engineering
- integration
- LLM APIs
- security questionnaires
- presenting
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
Discovery
Weeks 1 to 2Week 1
Discovery
- Technical discovery that finds the real problem
- Mapping a buyer's stack
- Scoping a proof of concept
You build: A discovery record
Week 2
Project 1: the scope
- Success criteria the buyer agreed to
- Risk
You build: A discovery record and PoC scope for a fictional buyer
Project 1, the gate at week 2
The scope
Run discovery with a fictional buyer and scope a proof of concept they would sign.
You hand in
- Discovery record
- Stack map
- PoC scope with success criteria
The gate
The scope names success criteria the buyer agreed to.
- 2
The demo
Weeks 3 to 4Week 3
The demo
- Demos that prove, not tour
- Demo environments as code
- Handling the hard question
You build: A demo environment
Week 4
Project 2: the demo
- Rebuilding from scratch
- Recording
You build: A reproducible demo environment with a recorded demo
Project 2, the gate at week 4
The demo
A demo environment you can rebuild in an hour, and a demo that proves the claim.
You hand in
- Environment as code
- Recorded demo
The gate
The demo is rebuilt from scratch in under an hour.
- 3
The proof of concept
Weeks 5 to 6Week 5
The proof of concept
- Building against the buyer's data
- Security questionnaires
- Integration
You build: PoC in progress; squads form
Week 6
Project 3: the PoC
- Meeting the criteria
- Questionnaire answers
You build: A PoC on the buyer's data with an integration
Project 3, the gate at week 6
The PoC
Prove it on the buyer's data with the integration they need.
You hand in
- PoC
- Integration
- Security questionnaire answers
The gate
The PoC meets the agreed criteria.
- 4
The technical win
Weeks 7 to 8Week 7
The technical win
- Architecture reviews
- Objections and competitors
- Pricing and packaging conversations
You build: An architecture proposal
Week 8
Project 4: the review
- Objection handling with evidence
- Recording the review
You build: A written proposal and a recorded technical review
Project 4, the gate at week 8
The review
Win the architecture review.
You hand in
- Architecture proposal
- Objection responses with evidence
- Recorded review
The gate
The review answers every objection with evidence.
- 5
Scale
Weeks 9 to 10Week 9
Scale
- Running many PoCs
- Tooling for sales engineers
- Feeding product
You build: Toolkit design
Week 10
Project 5 and the viva
- The toolkit and playbook
- Defending a technical win
You build: A sales-engineering toolkit and playbook; the viva
Project 5, the gate at week 10
The toolkit
Make the next twenty PoCs faster.
You hand in
- Toolkit
- Playbook
- Product feedback loop
The gate
The viva: defend a technical win end to end.
- 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 sales-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 sales-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 demos, proofs of concept and toolkits, and a recorded technical win, which is what a sales-engineering hiring manager asks to see.
- 1
Run technical discovery that finds the real problem and scope a proof of concept with agreed success criteria.
- 2
Build reproducible demo environments as code and give demos that prove rather than tour.
- 3
Build a proof of concept on the buyer's data with an integration, and answer security questionnaires.
- 4
Run architecture reviews, handle objections and competitors, and hold pricing conversations.
- 5
Build a sales-engineering toolkit and playbook and feed product.
- 6
Defend a technical win end to end, on camera.
Roles this prepares you for
- Sales engineer
- Solutions engineer
- Pre-sales engineer
- Solutions architect (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, AI Sales Engineer Bootcamp
Example
- Week 2Graded, gate signed
The scope
The scope names success criteria the buyer agreed to
- Week 4Graded, gate signed
The demo
The demo is rebuilt from scratch in under an hour
- Week 6Graded, gate signed
The PoC
The PoC meets the agreed criteria
- Week 8Graded, gate signed
The review
The review answers every objection with evidence
- Week 10Graded, gate signed
The toolkit
A viva: defend a technical win end to end
- 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.