Courses / Live bootcamps
GTM Engineer Bootcamp
Build the outbound machine: data, enrichment, automation, CRM, attribution.
- 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.
Sales and marketing people, and engineers who want revenue work, who want to build the outbound machine: data, enrichment, automation, CRM and attribution. No code required to start.
Before you start
Sales or marketing experience, or an engineer who wants revenue work; no code required to start.
Skills
- Clay
- enrichment APIs
- n8n
- CRM automation
- SQL
- LLM personalisation
- attribution
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
The data layer
Weeks 1 to 2Week 1
The data layer
- Ideal customer profiles as data
- Enrichment tools and their limits
- Building a clean account list
You build: An enriched account list
Week 2
Project 1: the list
- Weekly refresh
- Deduplication
You build: A scored, enriched account list rebuilt automatically
Project 1, the gate at week 2
The list
Build the account list a sales team would actually use, and keep it clean without you.
You hand in
- ICP definition
- Enriched list
- Scoring
- Weekly refresh
The gate
The list refreshes without duplicates or stale rows.
- 2
Signals
Weeks 3 to 4Week 3
Signals
- Intent and trigger signals
- Scraping and APIs, legally
- Scoring
You build: A signal pipeline
Week 4
Project 2: signals
- Explainable scores
- Daily ranking
You build: A signal pipeline ranking accounts daily
Project 2, the gate at week 4
Signals
Rank accounts every day by what they are doing right now.
You hand in
- Signal sources
- Pipeline
- Scores with explanations
The gate
Scores are explainable per account.
- 3
Outbound
Weeks 5 to 6Week 5
Outbound
- Sequences and personalisation with AI
- Deliverability
- Compliance
You build: An outbound system; squads form
Week 6
Project 3: outbound
- Human approval
- Reply capture
You build: Outbound with AI-written, human-approved messages, running
Project 3, the gate at week 6
Outbound
Run outbound where AI drafts and a human approves every message.
You hand in
- Sequences
- Approval flow
- Deliverability setup
- Reply capture
The gate
Every message is approved and every reply is captured.
- 4
CRM and routing
Weeks 7 to 8Week 7
CRM and routing
- CRM as the system of record
- Routing and handoff
- Reporting
You build: CRM automation
Week 8
Project 4: routing
- Owner assignment
- Pipeline dashboards
You build: CRM automation with routing and a dashboard
Project 4, the gate at week 8
Routing
A lead lands with the right owner in a minute.
You hand in
- CRM automation
- Routing rules
- Handoff
- Pipeline dashboard
The gate
A lead lands with the right owner within a minute.
- 5
Attribution and scale
Weeks 9 to 10Week 9
Attribution and scale
- Attribution that survives scrutiny
- Experimentation
- Cost per meeting
You build: Attribution model
Week 10
Project 5 and the viva
- The engine end to end
- Defending the numbers
You build: The GTM engine with attribution and an experiment log; the viva
Project 5, the gate at week 10
The engine
Put it together and prove what it produced.
You hand in
- Attribution model
- Experiment log
- Cost per meeting
The gate
The viva: defend the numbers to a sceptical CRO.
- 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 GTM 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 GTM 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 go-to-market systems and the attribution to prove what they did, which is the whole of the GTM engineer role as companies now hire for it.
- 1
Turn an ideal customer profile into a clean, scored, automatically refreshed account list.
- 2
Build signal pipelines from intent and trigger data that rank accounts daily, legally.
- 3
Run outbound with AI-written, human-approved messages, deliverability and compliance.
- 4
Automate the CRM with routing, handoff and a pipeline dashboard.
- 5
Build attribution that survives scrutiny and an experiment log.
- 6
Defend the numbers to a sceptical revenue leader.
Roles this prepares you for
- GTM engineer
- Revenue operations engineer
- Growth engineer
- Sales operations lead
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, GTM Engineer Bootcamp
Example
- Week 2Graded, gate signed
The list
The list refreshes without duplicates or stale rows
- Week 4Graded, gate signed
Signals
Scores are explainable per account
- Week 6Graded, gate signed
Outbound
Every message is approved and every reply is captured
- Week 8Graded, gate signed
Routing
A lead lands with the right owner within a minute
- Week 10Graded, gate signed
The engine
A viva: defend the numbers to a sceptical CRO
- 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.