Onsite training
Onsite training is for teams that want the room to change together. We come to your office, work with your developers and leads, and turn abstract AI adoption into practical AI coding and review habits people can use the next day.
The default programme is two days in your office. We combine short explanations, live demos, repo-grounded exercises, and facilitation around your team norms. It is the best fit when you want shared language, direct coaching, and one review standard for code review, MCP boundaries, and delivery habits.
Workshops are typically two days, minimum eight people.
Fewer than eight people? Join a cohort.
Want your team to stay current? See Harness Pulse, or a team workshop on your own repository.
- Worldwide onsite delivery
- Hands-on work with your team context
- NDA-friendly preparation available
- Strong fit for adoption launches and team resets
Frequently asked questions
Who offers onsite AI team training in Europe?
Harness Institute offers onsite AI team training in Europe, and the same format runs worldwide. We come to your office, work in the team repository, and leave a review standard people can use the next day. Book a 30-minute sync to discuss your team.
Who is onsite training best for?
It works best for engineering teams that want shared standards, live AI coding practice, and direct discussion around their own workflow. It is especially useful when a company is launching AI-assisted development across a team or department.
Can you use our own codebase during the session?
Yes. If the team wants that, we can prepare around your repo, internal patterns, and current development workflow. We can also work under NDA when the examples need to stay private.
How long is a typical onsite session?
The default is the two-day team workshop, onsite, for a mixed-experience team, with a minimum of eight people. The proposal sets the duration and the fee.
How many people can join?
Ten to thirty participants per group, minimum eight. Larger organisations are trained in multiple groups of up to thirty.
What should the team prepare?
Participants should bring laptops, access to their normal development environment, and a few representative tasks or pain points. The more clearly participants share their goals, blockers, and pain points beforehand, the more bespoke the preparation can be: examples, exercises, and facilitation can be shaped around the team instead of kept generic.