The rapid evolution of artificial intelligence (AI) is transforming the landscape of multiple industries, including software development. The question isn’t whether AI will change the role of software engineers — it already has. The real question is: How can engineers amplify their impact and thrive in this new reality?
As a professional with over five years of experience in software engineering, including roles such as tech lead, engineering manager and platform engineering lead at one of the world’s largest job aggregators, I have seen firsthand how much engineers dislike repetitive and routine tasks. Today, AI allows engineers to delegate these tasks to a ‘personal junior engineer’ that everyone has always dreamed about. This raises one of the many important questions: What is next for software engineers?
This is, indeed, an interesting question. To address it effectively, I propose we apply first principles thinking — a method that involves deconstructing complex problems into their most basic elements. One practical exercise within this framework is the ‘Five Whys’ technique, which can help us understand how AI can enhance software engineers’ roles rather than replace them.
Let us 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’s needs?
To create value for the business and improve user experience (UX)
- 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?
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.” Innovation isn’t just about solving today’s problems; it is about imagining what doesn’t yet exist and having the courage to create it. The sixth ‘why’ reminds us that we innovate not just for utility or profit but to leave a mark — to contribute something meaningful to the world.
By drilling down to these fundamentals, we see that software engineering is about creating value and innovation, allowing engineers to impact not just the ‘how’ of software development, but also the ‘what’ and ‘why’. This strategic involvement requires human insight and creativity — areas where AI cannot replace us.
The Shift From Software Engineers to Product Engineers
Traditionally, software engineers have focused on delivering clean, efficient and scalable code. While technical expertise remains critical, the rise of AI is shifting the emphasis from execution to strategy and problem-solving. Developers who incorporate product thinking into their work will position themselves as indispensable assets to their organizations.
A product engineer is more than just a code expert. 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 UX
- Identifying opportunities to contribute to product strategy
- Developing a product mindset
Why AI Makes Product Thinking Essential for Engineers
AI is not just a tool for automating repetitive coding tasks — it is also reshaping how products are built, tested and deployed. As AI models generate code, optimize infrastructure and even predict software failures, engineers must redefine their role in the development process.
To remain valuable, developers must shift their focus from ‘How should I build?’ to ‘What should I build and why?’ By embracing product skills, engineers can:
- Become ‘Thinkers’, Not ‘Doers’: AI can generate code, but it cannot deeply understand user pain points, business objectives and long-term scalability. Product engineers connect the dots between technology and business value.
- Lead Cross-Functional Innovation: AI-powered automation frees up engineers to drive innovation rather than get stuck in execution mode. Product-focused engineers work at the intersection of technology, business and UX. They lead strategic initiatives rather than just implement them.
- Design With AI in Mind: The best engineers do not just use AI tools — they design for them. Understanding how AI impacts user workflows, data privacy and ethical considerations gives engineers a competitive advantage in building future-ready products.
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 is essential. Here are the key areas to focus on:
Understanding Product Strategy and OKRs
Regardless of the role you hold in a company, you are hired to deliver value. Your salary is an investment and the company expects a return. Each organization defines value differently, but ultimately, it is linked to revenue — a clear indicator that users love the product and are willing to pay for it. They exchange money for the value they receive.
How can engineers focus on delivering this value? The answer lies in understanding product strategy. Product strategy isn’t just about deciding what to do; it is also about knowing where not to waste time and energy.
To gain this understanding, engage with the product team and be curious about OKRs and product strategy. Understand the company’s goals for the next year or five years and learn how the company plans to achieve them.
For example, imagine your company sets an OKR to increase e-commerce sales by 15%. The product strategy involves enhancing the mobile app’s checkout process to reduce abandonment rates. By understanding these business objectives, you now have guidance on how to deliver value. You can generate ideas to achieve the OKR, aligning your technical skills with business goals and contributing directly to the company’s success.
User-Centric Thinking
Now that we are clear on the goal, let us revisit the second ‘why’ in our exercise: Why do engineers need to build new features? The answer is simple — to solve problems or meet user needs. How can we solve user problems if we do not truly understand who our users are and what their problems might be?
This brings us to the second important skill: Having a strong understanding of user needs. There are many frameworks available to help structure this understanding. Two that I find particularly useful are Jobs To Be Done and Customer Journey Mapping.
Now, let us 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?’
For instance, 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 dive deeper into product thinking, you will start to identify potential solutions to business challenges. For instance, you might hypothesize that optimizing page load times could significantly reduce checkout abandonment rates.
However, it is crucial to remember that this is just a hypothesis, not a proven solution. This is where your product management skills come into play. Instead of jumping straight to implementation, approach it strategically:
- Frame your idea as a testable hypothesis
- Use frameworks such as data, insight, belief, bet (DIBB) to structure your proposal
- Outline a plan to validate your hypothesis through experiments or A/B testing
By presenting your ideas in a structured way, you demonstrate both technical expertise and strategic thinking that align with business goals.
Product Mindset
I have learned that developing a product mindset starts with curiosity and a critical, nonjudgmental approach. I always ask myself: Is what I am building really valuable? How valuable is it? I try to think like an investor — would I put my own money into this? What would I get in return?
Stay curious, I say. Question everything. Just because we have always done something one way does not mean we should keep doing it. I love digging into data to see how customers actually use our product. Trust me, it can surprise you.
For me, it is about developing a real passion for the problem. I am fascinated by payments, always looking for ways to make things simpler for merchants. Payments are complex, but our job is to make them feel simple.
I have learned to be proactive. I treat the company like it is my own. I do not wait for features to work on — I know the company’s goals. I figure out how to hit those goals, come up with ideas and pitch them.
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 is how you make a real difference.
