What is factory engineering?
What we’ll cover
How coding agents flipped the balance of planning, implementation, and review, the difference between product engineering and factory engineering, and the kinds of problems a factory engineer solves.
What is engineering?
If you've done any amount of software development in the past year, you've probably been using an interactive coding agent to get work done: Claude Code, Codex, Warp's Agent, or whatever else.
These tools completely changed software development; we used to start with the code and let autocomplete guide us, and now we start with the prompt and review the code on the other side.
The power of using agents to drive software development has raised an almost existential question: what even is software engineering now?
The fall of prompt engineering
Let’s break down software engineering into three steps: planning / discussion, implementation, and code review. Before agents, implementation was the bulk of deep work, and engineers used the time left over for architecture discussions and code review.
- Plan
- Implement
- Review
But now that we have agents doing the bulk of the implementation, the balance has flipped.
- Plan
- Implement
- Review
In fact, if you’ve been increasing your velocity to fill that gap, it can feel more like this:
- Plan
- Implement
- Review
- Review
- Review
- Review
If you stop there… it feels like engineering was replaced with 20% meetings and 80% drudgery.
But if we pause for a moment, there are some valuable engineering challenges worth solving from cost, quality, and security standpoints:
- Plan: When should the agent involve humans to draft a plan vs. proceeding with implementation? What questions should it ask? What goes into a good product or technical spec?
- Implement: Now that agents are writing code, how do we optimize the cost and quality of that code? What access permissions do agents have across secrets, MCPs, and skills?
- Review: How do we give agents the tools to verify their own work end-to-end before tagging us for review? How can agents assess the risk of a PR, and include that assessment in the pull request to save humans time?
These are all the types of systems engineering questions that engineers used to answer with syntax and abstractions, now at a higher level.
What is factory engineering?
These stages of development can be defined as new engineering roles:
- Product engineering: building the product itself. This is the collaboration loop with an agent across planning and PR review.
- Factory engineering: building the system of agents that builds the product: the software factory, hence factory engineering. This optimizes the cost and quality of agents pieces through automation. That doesn’t mean full automation, though; it means automating low-risk work and only requiring human attention when absolutely necessary.
Here are some sample questions you'll answer as a factory engineer:
- “Our agent keeps adding test cases and code comments that it really shouldn’t. Could someone make the agent write better code?”
- “I keep copy/pasting these error monitor reports into an agent when I’m on-call. Could we automate this?”
- “Our API bill skyrocketed after the latest model release. Could we be moving some workflows to cheaper models without sacrificing code quality?”
The larger your team becomes and the more agents you deploy to build it, the more valuable factory engineering becomes.
Throughout this course, you'll learn the best practices to become a factory engineer yourself.