From Code to Impact: The New Role of Engineers in an AI-Driven World – DevOps.com

This post was originally published on this site.

The rapid rise of AI is reshaping industries, including software development. It’s no longer a question of if AI will change engineers’ roles — it already has. The real question is, how can engineers amplify their impact in this new reality? 

With over five years of experience as a tech lead, engineering manager and platform engineering lead at one of the world’s largest job platforms, I have seen how much engineers value creative work and hate repetitive tasks. Now, thanks to AI, we can finally delegate those tasks to the personal junior engineer we’ve always dreamed of. 

So, what’s next for software engineers? 

To answer that, let’s turn to first principles thinking — a method for breaking down complex challenges into their fundamental truths. One helpful tool here is the 5 Whys technique, which helps us dig deeper into the why behind what we do — and see how AI can empower us, not replace us. 

Let’s break it down:  

  • Why do engineers write code? To build new features. 
  • Why do engineers need to build new features? To solve problems or meet user needs. 
  • Why do we need to solve problems or meet user needs? To create value for the business and improve user experience. 
  • Why do we need to create value for the business? To ensure the company’s growth and sustainability. 
  • Why is the company’s growth and sustainability important? Because it provides jobs, drives innovation and contributes to the economy. 
  • Why does this matter at all?  

As Steve Jobs said, “Innovation distinguishes between a leader and a follower.” True innovation isn’t about utility or profit — it is about leaving a mark. 

.ai-rotate {position: relative;}
.ai-rotate-hidden {visibility: hidden;}
.ai-rotate-hidden-2 {position: absolute; top: 0; left: 0; width: 100%; height: 100%;}
.ai-list-data, .ai-ip-data, .ai-filter-check, .ai-fallback, .ai-list-block, .ai-list-block-ip, .ai-list-block-filter {visibility: hidden; position: absolute; width: 50%; height: 1px; top: -1000px; z-index: -9999; margin: 0px!important;}
.ai-list-data, .ai-ip-data, .ai-filter-check, .ai-fallback {min-width: 1px;}

At its core, software engineering is about creating value and driving innovation. AI can assist with the how, but only humans bring the what and why. That’s where our creativity and insight remain irreplaceable. 

The Shift from Software Engineers to Product Engineers 

Traditionally, engineers are focused on writing clean, scalable code. With AI handling more execution, the focus is shifting to strategy and problem-solving. Engineers who embrace product thinking will become essential to their teams. 

Product engineers are more than just code experts. They bridge the gap between development and business impact by: 

  • Understanding product strategy and objectives and key results (OKRs) 
  • Understanding user needs and designing solutions that enhance user experience (UX) 
  • Identifying opportunities to contribute to product strategy  
  • Developing product mindset  

Why AI Makes Product Thinking Essential for Engineers 

AI is reshaping how products are built, tested and deployed, pushing engineers to shift from ‘How should I build’? to ‘What should I build and why? ’ 

To stay valuable, engineers must embrace product thinking: 

  • Become thinkers: AI generates code, but engineers understand user pain points and business goals, connecting technology with value.
  • Lead innovation: AI frees engineers from execution, allowing them to drive cross-functional, strategic initiatives.
  • Design for AI: Great engineers don’t just use AI — they design with it in mind, considering impacts on user workflows, privacy and ethics. 

Key Product Skills Every Engineer Should Develop 

For engineers looking to stay ahead in an AI-driven landscape, developing product skills is no longer optional—it’s essential. Here are the key areas to focus on: 

Understanding Product Strategy and OKRs 

Regardless of your role, you are hired to deliver value, and that value is ultimately tied to revenue. If users love the product, they’ll pay for it. That’s the return on your salary. 

To deliver real impact, engineers need to understand product strategy. It is not just about what to build, but also what not to waste time on. 

Start by engaging with the product team. Get familiar with OKRs and long-term company goals. For instance, if the goal is to boost e-commerce sales by 15% and the strategy is to improve the checkout flow, you now have a clear target. You can propose technical solutions that directly support that goal, making your work more aligned and more valuable. 

User-Centric Thinking 

Let’s revisit the second ‘why’: Why do engineers build features? To solve user problems. But we can’t solve what we don’t understand. 

Therefore, understanding user needs is crucial. Frameworks such as Jobs To Be Done and Customer Journey Mapping can help uncover what truly matters to users. 

Now, let’s return to our example of the checkout process. We know the abandonment rate is high, but why? To answer this, I suggest approaching the problem from two angles: 

  • Qualitative data: Ask questions such as, ‘Do we have user insights about the current pain points in the checkout flow’? 
  • Quantitative data: Analyze metrics to understand, ‘Where are users experiencing friction in the checkout flow’? 

Imagine users report that the payment screen is loading too slowly. By comparing this feedback with quantitative data (e.g., drop-off rates), you can validate their concerns and identify actionable solutions. 

Developing Product Solutions 

As you explore product thinking, you will identify potential solutions such as improving page load times to reduce checkout abandonment. 

However, treat this as a hypothesis, not a solution. Approach it strategically by: 

  • Framing it as a testable hypothesis
  • Using frameworks such as data, insight, belief, bet (DIBB)
  • Planning experiments or A/B testing to validate it 

By presenting your ideas in a structured way, you demonstrate both technical expertise and strategic thinking that aligns with business goals. 

Product Mindset 

Developing a product mindset starts with curiosity and critical thinking. I constantly ask ‘Is what I’m building truly valuable? Would I invest in it myself?’ 

I challenge assumptions, dig into customer data and let insights guide my work. It’s about falling in love with the problem, like simplifying complex payment systems for merchants. 

I stay proactive, treat the company like it’s my own and align my ideas with business goals. I don’t wait for tasks — I create opportunities. 

The Future of Engineering 

Engineers are in a unique position to lead. My advice? Take initiative. Get buy-in. Drive the product forward. Think differently. That’s how you make a real difference.