درباره این اپیزود
What happens when software engineers stop thinking like coders and start thinking like orchestrators?
In this episode, Amir sits down with Scott Gale, CTO and Founder of Fluency, to unpack one of the biggest shifts happening in engineering right now: the move from writing code by hand to directing AI agents with context, judgment, and intent. Scott shares how his team is already using coding agents in production, what that means for hiring and team design, and why the engineers who adapt fastest will be the ones who gain leverage, not lose relevance.
This conversation gets into the real change beneath the AI hype. Not just better tools, but a different shape of engineering work. Less manual syntax, more planning, auditing, collaboration, and system level thinking.
Key Takeaways
• The value of an engineer is shifting away from typing code and toward directing intent clearly
• Teams that give AI better context can get dramatically better output from coding agents
• Engineers do not need to become people managers, but they do need to learn how to manage agent driven work
• Hiring is starting to favor people who can collaborate, learn the product, and work effectively with AI
• Faster software delivery does not mean less to build, it often means companies can finally tackle more of the backlog
Timestamped Highlights
00:01 Scott Gale, CTO and Founder of Fluency, joins Amir to break down the shift from builder to orchestrator in modern engineering
02:36 How Fluency introduced coding agents with a three part approach: safe experimentation, mindset shift, and stronger context
04:35 Is this just the next step in software engineering, or does AI fundamentally change the role?
08:16 Why some engineers resist AI tools, and what helps people move from skepticism to real adoption
11:26 How technical interviews are changing as AI becomes part of everyday engineering work
16:59 Scott on whether companies will actually need fewer engineers, and why the demand for meaningful work is not going away
21:09 The practical lesson teams miss: better structured systems and better context make coding agents far more effective
One line worth remembering
“It’s not about losing your craft. It’s about managing a workforce of junior agents.”
Practical edge
Scott shares a useful operating principle for teams already experimenting with AI in engineering: if you want better output, do not start with prompts alone. Start with structure. The more clearly a system is organized, and the more context an agent can access, the more useful and reliable the result becomes.
That applies to hiring too. Technical skill still matters, but the engineers who stand out now are the ones who can collaborate across product and engineering, understand the business context, and make good decisions with AI in the loop.
Call to Action
If you are thinking through what AI means for engineering careers, team design, or product velocity, follow the show and share this episode with someone building in this new environment. For more conversations with founders and operators shaping where tech is headed, connect with Amir on LinkedIn.
