What changes for engineering managers when agents join the team
When AI agents pick up tickets, the engineering manager's job shifts from allocating work to designing the system that work flows through. A practical view.
Cenk Gultekin··1 min readDraft
For years, a large part of an engineering manager's week has been allocation: who picks up what, who is blocked, who needs help. When agents start taking well-scoped tickets, that part of the job shrinks. Something else grows in its place.
The new parts of the job
- Writing work so it can be executed: clear tickets, explicit acceptance criteria and examples become leverage, not overhead.
- Encoding how the team works: coding standards, release steps and review rules become reusable skills and instructions that agents follow every time.
- Reviewing differently: less line-by-line reading, more checking intent, tests and risk.
- Coaching people on judgement: the work that remains for engineers is the work that needs taste, context and ownership.
What does not change
Accountability stays with the team. Agents do not own outcomes, people do. The best managers I see are treating agents like a new kind of team member: onboarded properly, given narrow permissions at first, and trusted with more as they earn it.
In the AI Hub
- Leadership
- Engineering management