Engineering Practice Lead

The role that directs agents on the hardest work, keeps code patterns healthy, and coaches the next layer of engineers.

Who this role is for: A staff-level engineer with strong judgment on code structure, deep familiarity with the codebase, and the patience to teach.
Not this role: An architect-at-a-distance. The Engineering Practice Lead is in the code every day, shaping patterns as they emerge.
Pairs with: The Delivery Model, The Delivery Squad, Context Manager.

What the Engineering Practice Lead owns

Where the Context Manager owns the shared context, the Engineering Practice Lead owns the code. Specifically: the quality of what agents produce, the patterns they follow, and the judgment about when an agent session is going somewhere useful vs. somewhere expensive.

This is a working role, not a supervisory one. The Engineering Practice Lead directs agents on the hardest work, reviews the hardest PRs, and makes the call when a piece of code needs a human to finish it.

The three parts of the job

Like the Context Manager’s job, none of these is a project with an end date; all three run continuously.

Part 1

Build

Hands-on with the hardest work each squad is shipping.

What this looks like

Pick up the one or two features where agent drafts are struggling; direct the agent sessions personally.
Know when to let the agent run another cycle and when to stop it.
Review PRs against the spec’s intent, not against a diff.
Pair with the Squad Lead when the judgment call is ambiguous.

Boundary

Do not become every squad’s reviewer. Squad Leads own PR review. The Engineering Practice Lead is pulled in for the hard 10%.

Part 2

Standards

The pattern library and the trajectory of the codebase.

What this looks like

Maintain a pattern library in the shared context: what works, with example PRs that show each pattern.
Retire patterns that stop working, with a migration note for affected code.
Update the coding standards every increment — never let them drift past reality.
Notice when multiple squads are solving the same problem three different ways, and converge them.

Boundary

The Engineering Practice Lead doesn’t own architecture — that’s the architect’s remit. The split is: architecture is system boundaries and integration; patterns are how code inside each boundary is shaped.

Part 3

Coach

Teaching the squad the skill of directing agents well.

What this looks like

Pair with Squad Leads on their hardest agent-direction calls.
Run short clinics: how to brief an agent, how to read agent output critically, when to stop.
Review what engineers are writing to agents, not just what agents are producing.
Spot the engineer who is about to become a strong Squad Lead, and invest in them.

Boundary

Coaching is not mentoring-in-the-abstract. It happens inside PRs, spec reviews, and agent sessions. If it feels like a classroom, it probably isn’t working.

Let it run, or stop it

The single most valuable Engineering Practice Lead skill — and the hardest to teach — is knowing when an agent session is going to produce something worth reviewing and when it is drifting. Below are the signals to read.

Let it run

The agent’s internal monologue cites the spec and the relevant context files correctly.
It is making incremental edits in the expected files, not jumping around.
Its test output is either passing or failing with the precise error you’d expect.
It asks clarifying questions when it hits ambiguity rather than guessing.
The shape of the code so far matches the pattern library.

Stop it

It’s editing files outside the scope of the task.
It’s citing a pattern that isn’t in the pattern library, or one that was retired.
It’s re-running the same failing test with small tweaks — a sign of flailing, not progress.
It’s adding new dependencies without the human in the loop.
Its explanation stops matching the code it’s producing.

How to intervene well

When a session needs to stop, the goal is not just to take over. It is to leave the agent, the engineer, and the shared context in a better state for next time.

Stop early.The longer a drifting session runs, the more expensive the recovery. Cutting a session at 15 minutes of drift costs less than 2 hours.
Diagnose in one sentence.“It’s citing the wrong pattern because the business-context documentation doesn’t distinguish X from Y.” The diagnosis sharpens the fix.
Fix the cause, not the symptom.If the cause is content, edit the context file. If it’s a brief, fix the brief before re-running. If it’s a skill, pair with the engineer on the next session rather than taking over.
Re-brief explicitly.Restart the session with a tighter scope and the corrected context. Don’t hope the agent will pick up the change implicitly.
Log the pattern.If this is the second or third time this class of drift has happened, it belongs in the pattern library or in the audit log so the Context Manager can propagate the fix.

Relationships with other roles

The Engineering Practice Lead is not the only senior technical role. Clean boundaries prevent the “everyone does everything” failure mode.

Architect

Owns system boundaries and integration patterns. The Engineering Practice Lead owns patterns inside each boundary.

Context Manager

Owns the shared context’s shape and health. The Engineering Practice Lead contributes the code-pattern content and coaches engineers on reading it.

Squad Lead

Owns squad delivery. The Engineering Practice Lead steps in on the hardest 10% and coaches the Squad Lead on the rest.

Quality Lead

Owns verification. The Engineering Practice Lead makes sure squads produce code that verification can actually catch problems in — observable, testable, instrumented.

Squad Engineers

Day-to-day agent operators. The Engineering Practice Lead teaches them when to stop a session and reviews their hardest drafts.

Product Manager

Owns intent. The Engineering Practice Lead pushes back when a spec is unimplementable or when acceptance criteria aren’t observable.

How to know the role is working

Agent output gets better across squads, not just the ones the Engineering Practice Lead touches. The pattern library and coaching propagate quality beyond direct involvement.

Drift is caught early. Long, expensive agent recovery work becomes rare because Squad Leads and Squad Engineers learn to stop sessions themselves.

The pattern library is used. Engineers cite it in PR descriptions. New code matches the patterns. Retired patterns are migrated cleanly.

Warning signs. Every hard PR comes to the Engineering Practice Lead personally. Squad Leads stop making calls because they’re waiting for a second opinion. The pattern library hasn’t been updated this increment. Coaching becomes slideware instead of paired work.

← Back to Resources