Amro Agentic AI certified 32 experienced engineers on Claude Code.
Amro Agentic AI, which builds practical agentic AI products, put 32 engineers through the Practitioner level of Sthuthi's Claude Code track. The team was already technically experienced, so the programme went beyond basic AI-assisted coding into production workflows and review discipline.
32
employees certified
1
consolidated cohort
3 weeks
19 January – 6 February 2026
"Our team did not need another general introduction to AI. We needed a stronger engineering method for using Claude Code on real development work. Sthuthi Tech understood that from the beginning. The programme went into context management, planning changes before implementation, working across larger codebases, debugging and, importantly, reviewing what Claude produces instead of assuming the first answer is correct. I liked that the certification treated the engineer as accountable for the outcome. That is exactly how these tools need to be adopted in serious technical environments."
Hemant Joshi · Founder & Chief Cloud and AI Architect, Agentic AI AMRO
Who took part
- AI engineers and software engineers
- Cloud engineers
- Solution architects
- Application developers
Across AI, software, cloud and architecture roles, at the Claude Code Certified Practitioner — Sthuthi Technologies' independent credential.
Focus
- Production-oriented Claude Code workflows
- Repository context and implementation planning
- Debugging, refactoring and testing
- Architectural reasoning and engineering review
When
- Cohort 1 · 32 people
- 19 January – 6 February 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
Because the cohort was experienced, the certification concentrated on using Claude Code well when an engineer already has architectural constraints, existing repositories and production requirements to work within.
The central outcome was consistent review discipline: generated code still had to be understood, challenged, tested and owned by the engineer responsible for the change.
Why one cohort
The 32 people were the technical group identified for the initial engagement, so Amro completed the programme in a single cohort.
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.