How we train and assess our engineers.
Our engineers train at GTMUNI, our sister academy. We start with people who can already write code and work with data, and teach them the revenue side: how GTM systems are meant to work, where they break and how to fix them.
Checked before they start.
Communication and technical readiness are judged separately, and both have to pass.
Technical base
Write a small Python or JavaScript program, read JSON, call an authenticated API, write a SQL join and use Git. Previous GTM jobs are not required.
English
A 45-minute written and spoken assessment. We assess clarity, listening, accuracy and asking good questions, not accent or nationality.
Technical exercise
60 minutes on a JSON transform, API pagination, a SQL join and secret handling, followed by 15 minutes explaining a trade-off to someone non-technical.
Eight weeks of building.
The programme runs on a simulated B2B company, with imperfect data and the failures engineers meet in production. It is designed so that 120 of its 160 hours are practical work.
Week 1
Customer lifecycle, ICP and buying groups, requirements and data ownership. Ends with a brief, a state map and a schema.
Week 2
CRM objects and permissions, SQL reconciliation, API authentication, pagination, webhooks and retries. Ends with a working CRM and reliable ingestion.
Week 3
Qualification and routing, owner capacity and fallbacks, signals and the cost of enrichment. Ends with a complete inbound system.
Week 4
Inbound, outbound, partner and product-led motions, opportunity stages and measurement. Ends with a reconciled lifecycle report.
Week 5
Structured AI extraction, evaluation, confident errors, privacy and deletion. Ends with an evaluated AI assistant and verified security fixes.
Week 6
Incident diagnosis, monitoring, rollback, cost and stakeholder updates. Ends with a repair defended live.
Weeks 7 and 8
The capstone: design, build, faults introduced by the assessors, measured costs, handover and a live defence.
More on the programme at gtmuni.com.
Checked before they finish.
Each engineer builds one system end to end: a signal comes in, the account is identified and enriched, qualified, routed to an available owner and written to the CRM after review, with the result, cost and recovery measured.
The assessors break it on purpose. The engineer has to recover it and explain their choices, and the grading is independent.
What you can look at before you meet them.
The engineer's own capstone: source code and configuration, tests, run logs, the cost ledger, the architecture, the runbook, deployment and rollback steps, and their written explanation.
Figures in the programme's simulated company, such as conversion rates, are fictional. The capstone shows an engineer can build and run the system, not that it lifted anyone's revenue.