For the past few years, I've been on a journey that has shaped my career and technical expertise—working as a Product Engineer.
The Evolution of a Product Engineer
Unlike software engineering, where the focus is often on implementing features based on requirements, product engineering demands a holistic approach. It involves not only understanding the requirements but also the user needs, business goals, and technical feasibility—and then finding the optimal way to bring them together. This shift in perspective has significantly influenced the way I think about building software.
From Code to Product Thinking
One of the biggest shifts in my mindset was moving from simply shipping features to ensuring they align with the product's vision. Early in my career, I'd often take a ticket, implement the logic, and move on to the next task. But as I took on more responsibility, I began asking deeper questions:
- Why does this feature matter?
- How does this feature help the user?
- How does it impact the user experience?
- Is there a simpler way to achieve the same result?
- What are the tradeoffs of each possible solution?
This shift led me to challenge assumptions, suggest alternative solutions, and advocate for user-first design in engineering discussions.
Building a product isn't just about writing clean code; it's about balancing tradeoffs.
Key Lessons Learnt
1. Technical Excellence Is a Means, Not the Goal
As much as I love writing well-structured and performant code, I've realised that technical brilliance doesn't always translate to product success. Some of the best solutions I've implemented weren't the most elegant, but they were the most effective given the constraints.
2. Understanding Business Context Changes Everything
Working on product teams, I've had to consider business realities—timelines, costs, and market needs. Features that seem necessary from an engineering perspective may not always make sense from a business standpoint. This awareness has helped me prioritize better and focus on delivering value rather than just functionality.
3. Collaboration is a Superpower
Product engineering sits at the intersection of development, design, and business strategy. I've had to improve my communication skills, align with designers on UX decisions, and justify tradeoffs to stakeholders. This has made me a better engineer—not just in coding, but in driving meaningful discussions that lead to better products.
4. User Empathy is a Competitive Advantage
Writing software is easy; building something that truly resonates with users is the challenge. Learning to put myself in the user's shoes—understanding their frustrations, workflows, and mental models—has helped me build better products. This is why I pay attention to usability, accessibility, and even micro-interactions that improve the overall experience.
5. Automation and Developer Experience Matter
As a product engineer working on multiple projects, I've seen how much time is lost to repetitive tasks, poor tooling, or inefficient workflows. Investing in automation—whether through better CI/CD, internal tools, or AI-assisted workflows—has been a game-changer. A great developer experience doesn't just make engineering more enjoyable; it speeds up product iteration and innovation.