Kenect AI certified 129 employees on Claude Code in a single cohort.
Kenect AI (Kenect, LLC), an AI platform for automotive dealerships, put 129 engineers through the Practitioner level of Sthuthi's Claude Code track in one cohort. At that size, the aim was consistent engineering behaviour across teams rather than each team adopting Claude Code its own way.
129
employees certified
1
consolidated cohort
4 weeks
9 February – 6 March 2026
"The value for us was not simply showing engineers that Claude Code could write code. They already knew that. The harder question was how you use it responsibly across a larger engineering organisation where people are working in existing systems, reviewing one another’s changes and shipping software customers depend on. Sthuthi Tech built the training around that reality. There was a strong emphasis on understanding the codebase first, planning before changing things, testing the output and keeping the engineer in control. That made the programme practical for us rather than theoretical."
David Burggraaf · Chief Technology Officer, Kenect
Who took part
- Software engineers and senior engineers
- QA automation engineers
- Platform and integration engineers
- Technical leads
Across engineering, QA, platform and integration teams, at the Claude Code Certified Practitioner — Sthuthi Technologies' independent credential.
Focus
- Working in established repositories
- Feature work, debugging and refactoring
- Automated testing and code review
- Integration work and context management
- Engineer-led validation of every change
When
- Cohort 1 · 129 people
- 9 February – 6 March 2026
Each cohort followed the track's standard format: instructor-led sessions on real code, then a proctored, task-based assessment reviewed by a human assessor before a credential was issued.
What the programme focused on
With 129 people in one cohort, the programme concentrated on consistent engineering behaviour, so Claude Code adoption didn't develop differently from team to team.
Participants practised establishing context before asking for implementation work, separating planning from execution, inspecting generated changes, validating tests, and treating Claude Code as part of the development workflow rather than an unchecked code-generation layer.
Why one cohort
Kenect AI's 129 selected employees were handled as one consolidated cohort, so the programme didn't need a second batch.
Commercial terms, contract value and pricing are confidential and not shown.
Planning a cohort of your own?
Tell us how many engineers and which teams. We'll scope a pilot and quote it on one call.