The craft
Your expertise does not disappear. It changes scale.
Software Factory Engineer is the role of engineers who run a governed engineering factory on their company's production applications: they set the rules, arbitrate changes and sign off what goes to production.
Every developer is asking the same question today.
What happens to my job when machines can write code? Our answer is simple: it moves up a level. The repetitive upkeep work, the kind that used to go to external contractors, moves to the factory. What remains, and gains value, is judgment: understanding a production application, deciding what is acceptable, and being accountable for it. That is exactly what a Software Factory Engineer does.
In practice, what does an SFE's day look like?
The role: run production instead of enduring it
An SFE no longer spends the day handling one ticket after another. They define the rules the factory applies, choose the autonomy tier for each perimeter, review and arbitrate proposed changes, and answer for the evidence bundle that comes with every delivery. They know the AI agents working for them the way a workshop lead knows their machines: strengths, limits, the settings that matter.
It is a full engineering role that demands more expertise, not less: architecture, security, software quality and a fine understanding of their sector's regulatory constraints.
Which requires a precise set of skills.
From scoping to evidence: what an SFE can do
Let's follow one change from end to end. It all starts before the first line of code: the SFE scopes and governs, translating company and sector requirements into executable rules, who approves what, on which environment, with which checks. Without that scoping, the factory would have nothing to comply with.
With the rules in place, they run the factory: orchestrating agents, choosing authorized models, setting the autonomy tier and recognizing the moment to take back control. When the factory proposes a change, they arbitrate it with the eye of an architect and a security lead, then decide with full knowledge.
And because that change will go to production in a regulated sector, the SFE answers for it all the way: reading, completing and defending the evidence bundle in front of an auditor, under the AI Act, DORA, NIS2 or an ISO 42001 program. Scope, run, arbitrate, answer: it is a single professional gesture, and it is what gives the role its value.
Skills that can be passed on, and validated.
A career path built with schools and user companies
The SFE role is not invented alone in an office. The career path is built with schools and user companies, sharing the same skills framework and the same validation pathway. That pathway assesses what an engineer can do on real production applications, not what they memorized from a course.
The path grows with the people who practice it: each user company helps refine the framework based on what its teams experience in the field.
Which leaves the question that matters to leadership: what happens to your teams?
Team trajectory: absorb the backlog, not shrink the ranks
Argy is not a team-reduction project. It is a project to absorb the backlog and debt that have been piling up for years for lack of hands. Your internal engineers become the ones who run the factory, and regain control of work that used to be outsourced.
Upskilling is gradual and supported: a guided training path, built into the tool, lets everyone practice on their own perimeter before taking responsibility for it. Your teams do not have to choose between delivering and learning.
And if you are a developer, here is what it changes for you.
For developers: a career path, not a productivity gadget
We do not promise to make you faster on today's ticket. We offer you a role with a future: the one who decides what the machine is allowed to do in production, and answers for it. It is a broader, more visible responsibility, closer to the decisions that matter in your company.
Your engineers already have what matters most. Let's give them the framework.
Prepare your teams for the role ahead
We build your engineers' trajectory with you: pilot perimeter, training path, roles and responsibilities within the factory. Let's talk about your teams and what you want them to become.