AI-Native Engineering Management
Two hats in one session: managers get hands-on with the tools their teams use, then redesign how the team works so AI use turns into output.
- Audience
- Development managers and group leads, including those who still code. Hands-on is mandatory.
- Duration
- 3 to 3.5 hours, hands-on throughout
- Group size
- 15 to 20 participants, on their own laptops with the tools they already use
- Hands-on
- On the team's real tasks, or on prepared exercises I bring
- Includes
- A tailoring call with the group lead beforehand and a follow-up session about 30 days later
- Where
- On-site in Israel, on-site abroad (I fly in for a few days and can run several sessions or teams back to back), or remote
What we cover
- What agents do reliably today, and why adoption alone doesn't move output.
- Where the bottleneck moves: review load, PR size, spec-first work, what to delegate.
- Measuring real impact (not "% of code written by AI"), token budgets and guardrails.
- Leading the change: coaching the team and growing champions.
What participants do
- 1 Debug a real crash or core dump with an agent, from reproduction to a verified fix.
- 2 Redesign one real team workflow: what to automate, what stays agent-assisted, what stays human, what needs approval.
What they take home
- One redesigned team workflow, with verification and owners per step.
- A 30-day plan for their team.
- A repo with the workshop's exercises and materials.
Frequently Asked Questions
Can you tailor it to our team?
Yes. Before the session I have a tailoring call with the group lead. The hands-on part then runs on the team's real tasks, or on prepared exercises I bring.
Does it matter what language or stack we use?
No. The agent reads and writes the code, whatever the language. Participants work on their own laptops with the tools they already use. Exercises run on the team's real tasks, or on prepared exercises I bring.
Can you run it on-site abroad?
Yes. I fly in for a few days and can run several sessions or teams back to back. It also runs on-site in Israel or remote.
What happens after the workshop?
About 30 days later I run a follow-up session with the group. Participants also keep a repo with the workshop's exercises and materials.
Related workshops
Role-Specific Harness Engineering and Token Optimization
Same model, different harness, very different results. Participants build a harness tuned to their role and measure what it saves on a real task.
See the Harness Engineering workshopAgent Orchestration and Automation with Codex
Several agents in parallel can save real time, or just burn tokens. Participants learn to tell the difference, then take a multi-agent workflow off the laptop and run it automatically.
See the Agent Orchestration workshopGet in touch
Tell me about your team and what you want them to walk away with.