A measurable curriculum across six tiers of agentic posture and four threads of engineering practice. Every engineer is placed at kickoff, mentored weekly, and retaken at midpoint and wrap-up. Movement is named per engineer.

Engineering teams adopting AI seriously, not occasionally. CTOs and VP Engineering who want measurable team fluency. Companies running CDD or similar methodologies that need everyone fluent. Teams stuck between “we have Claude licenses” and “we ship faster with them.”

Do engineers train on sample code?

Gnar Immerse is a mentor-led program that runs entirely against the client’s own codebases. Every technique is proven on work the team is already shipping, which is what makes it stick.

What does a cohort look like week to week?

For GSC, a single senior Gnar mentor, Alex, ran the cohort over four weeks: two 45-minute 1:1s per engineer per week, each pairing on that engineer’s live project; a weekly cohort check-in; live-coding sessions and open office hours; and a dedicated Slack channel between sessions. It fit inside a normal workweek, roughly five to six hours per engineer, so delivery commitments held.

Where do we start if we’re not ready for a full engagement?

Take the free AI Readiness Assessment , or join a free Claude workshop. Both give you a real sense of where AI fits before any sales conversation.

AI training for engineering teams

AI training

A cohort program that takes your team from ad-hoc AI use to production-grade agentic development. Taught by the engineers who built our own AI-native methodology.

Talk to us about a cohort See how it works

Start with a four-week Immerse cohort on your own codebase.

Our cohort program, called Immerse. Immerse isn’t a course we wrote for clients. We built it to train our own engineering team into Context-Driven Development.

Placed at kickoff

Exercises start with each engineer’s current practice.

Mentored weekly

A senior Gnar mentor pairs on your own project.

Retaken at midpoint and wrap-up

Two retakes show how far each engineer moved.

What changes

Have the tools? We’ll build the practice.

By the end of the cohort

Every engineer has moved at least one tier on every thread. Most move two or more across multiple threads.

Learned on your own code

Every technique is proven on work the team is already shipping, which is what makes it stick.

Mentors who ship

Your team learns from the engineers who use this every day to ship.

Playbooks that stay

Each engineer leaves with a merged change in your codebase, a maintained context file, at least one reusable skill and a workflow they can describe.

Two ways in

On its own, or alongside a build.

Teams that want to go further pair Immerse with our AI Transformation work, from strategy through live automation, so the fluency the cohort builds turns into systems the company runs on.

Cohort

Four weeks, one mentor, your code

Built for a small team that already has the tools but not the practice.

With a build

Fluency built while the first build ships

Most AI Strategy engagements end with a roadmap that requires team fluency. Immerse is how that fluency gets built. Cohorts can run alongside the first build, so engineers ship with the skills the roadmap calls for.

How it works

How we’d work with you

Every engineer is placed at kickoff, mentored weekly, and retaken at midpoint and wrap-up. Movement is named per engineer.

Step 1 · Four weeks

Place every engineer

Each engineer is assessed at kickoff on how they specify work, delegate it, check the output and handle safety and cost. The results set each engineer’s exercises.