There is a phrase that came up repeatedly in our conversations with engineering leaders over the past year.
“We need more people who can solve problems.”
At first glance, that sounds obvious. After all, solving problems has always been the purpose of engineering. But when leaders talk about problem solving today, they are describing something different from what they were looking for even a few years ago.
The distinction is subtle but important. Historically, many engineering organisations were built around a relatively linear process. Product teams defined requirements, engineering managers broke work into tasks, and developers executed against those specifications. Success was often measured by how efficiently and accurately someone could deliver what had been requested.
AI is beginning to challenge that model. As code generation becomes faster and more accessible, the value of simply implementing a solution is changing. The ability to write code remains essential, but it is no longer enough on its own. Increasingly, engineering leaders are looking for people who can move beyond execution and contribute to the entire process of solving a business problem.
The engineer who thrives in this environment is not necessarily the person who writes the most code. It is the person who can understand a customer need, challenge assumptions, navigate ambiguity, and determine the most effective path from idea to outcome.
The shift changing how teams work
One engineering leader we spoke to described a growing preference for assigning ownership of an initiative to a single engineer rather than dividing it among multiple specialists. Rather than working exclusively within a frontend or backend lane, that engineer is expected to understand the broader context, collaborate with product and design stakeholders, and take responsibility for delivering a complete solution. Specialists still exist, but they increasingly serve as advisors rather than hand-off points.
The result is a role that requires far more judgement than before. This is one reason communication has become such a critical skill. For years, communication was often treated as a secondary competency for engineers. Something useful, but not necessarily central to the craft itself. AI is changing that dynamic. Whether an engineer is collaborating with stakeholders, writing requirements, reviewing AI-generated output, or prompting an AI agent, the ability to express ideas clearly has become a core part of the job.
Several leaders noted that engineers are now spending more time closer to the business problem and less time focused solely on implementation. As a result, written and verbal communication increasingly influence technical outcomes.
The same trend is changing what career progression looks like. For much of the industry’s history, advancement was often associated with increasing technical specialisation. Engineers became experts in a framework, platform, language, or architecture pattern. While deep expertise remains valuable, many leaders now describe a growing need for breadth alongside depth.
Want to talk product engineers?
30-minute intro call. No commitment or cost.
The engineers attracting the most attention are often those who combine strong technical foundations with curiosity about customers, products, and business goals. They are comfortable asking why before jumping into how. They can move between technical and non-technical conversations. They understand that building the right thing is ultimately more valuable than building the thing right.
This does not mean every engineer needs to become a product manager. Rather, it reflects a growing recognition that technology decisions and business decisions are becoming increasingly interconnected. When software can be produced more quickly, the bottleneck often shifts elsewhere. Clarifying requirements, prioritising opportunities, managing trade-offs, and aligning stakeholders become the constraints that determine success.
The engineers who can operate effectively in those spaces become disproportionately valuable. Perhaps the most significant change is psychological rather than technical.
Many engineers built their professional identity around their ability to write code. There is pride in craftsmanship, precision, and technical execution. Those qualities remain important, but AI is forcing organisations to place greater emphasis on judgement than output. In some cases, engineers may spend more time reviewing, refining, rejecting, and guiding work than producing every line themselves.
For some, that transition feels uncomfortable. For others, it creates an opportunity to expand their influence beyond implementation and into strategy, product thinking, and decision making.
The leaders we interviewed were not describing the end of software engineering. Far from it. Most remain convinced that experienced engineers will become even more valuable as AI adoption accelerates. What they are questioning is whether the traditional definition of engineering work still captures where value is created.
The career path emerging from these conversations looks different from the one many engineers entered. It rewards ownership over execution. Judgement over output. Curiosity over compliance. Communication over isolation.
Most importantly, it rewards people who can take an ambiguous problem and move it closer to a solution. The engineers who embrace that shift are unlikely to find themselves replaced by AI. They are far more likely to become the people guiding how AI is used in the first place.
Want to chat product engineers?
We’ve seen first hand how the world of software is changing and we’ve fully embraced it. If you want to learn more about what we’re doing in this space, give us a call.
