AI Came for the Developer's Job First — Then Rewrote It

This week on Project Flux we're joined by Emile Kfouri, who leads developer-facing AI work at Autodesk, for a conversation about who AI actually disrupts first — and why it isn't who you'd guess.

🎧 Short on time? Hit play — the full 46-minute conversation is right here.

When people picture AI coming for jobs, they picture the warehouse, the call centre, the factory floor. Emile's answer is more uncomfortable: the first job AI came for was the one building AI, the developer. Not to delete it, but to rewrite what it means to do it well.

The shift he keeps returning to is outcome-based design. For years, building software and building anything in construction, meant telling a machine precisely how to do something. AI flips that: you describe the outcome you want and let the system work out the how. That sounds like less work. In practice it moves the hard part somewhere else, into being clear about what "good" actually looks like.

Which is why Emile spends less time talking about writing code and more about scaffolding (not that kind!). The interesting engineering now is architecting multi-agent systems and encoding the human heuristics that tell a model when it's confidently wrong. The judgement that used to live quietly inside an experienced developer's head suddenly has to be made explicit and that turns out to be the skill that's getting scarcer, not more common.

The most counterintuitive stretch is where he draws the line the other way: the clearest signals for when you should not reach for AI at all. For a guy whose day job is helping people build with it, that restraint is the tell and it's the part worth stealing for your own team, whether you're in AEC or anywhere else that's rushing to bolt AI onto everything.

Why it matters: If your value was in producing the output, AI is coming for it. If your value is in knowing which output is worth producing, you just got more valuable.

👉 Listen to the full conversation with Emile Kfouri — on outcome-based design, multi-agent scaffolding, heuristics, and the future skills that actually hold their value.

Enjoying Project Flux? Get a step ahead on AI and tech — subscribe to the newsletter and we'll land the week's most important developments in your inbox every Monday.

Project Flux is independently owned, funded, and operated by its founder. Any external references or features are for community benefit only and do not imply endorsement, control, or ownership.