Product-Minded Engineering in the AI Era
Drew Hoskins, former senior staff engineer at Meta and Stripe, outlines the strategic shift toward product-minded engineering. This analysis covers the 'Great Reindexing,' the Double Diamond framework, and actionable strategies for engineers to leverage AI tools while deepening user empathy and business impact.
The Strategic Shift to Product-Minded Engineering
The role of the software engineer is undergoing a fundamental transformation. As AI tools automate code generation, the leverage of pure technical execution diminishes, elevating the value of product thinking, user empathy, and strategic decision-making. Drew Hoskins, former senior staff engineer at Meta and Stripe, argues that the most valuable engineers are those who care as much about the 'what' and 'why' as the 'how.' This shift defines the 'product-minded engineer,' a professional who bridges the gap between technical architecture and user value.
The Great Reindexing
A core challenge in software development is the cognitive disconnect between engineers and product managers. Engineers typically index their thinking around system diagrams and technical constraints, while product managers index around user stories and business timelines. Hoskins calls the process of bridging this gap the 'Great Reindexing.' Engineers must learn to start with the user journey and then map it to the system, rather than starting with the system and hoping it serves the user. This reindexing is not just a soft skill but a critical technical competency that ensures the right problem is being solved.
Frameworks for Execution
To operationalize this mindset, engineers should adopt the Double Diamond framework: Discover, Define, Develop, and Deliver. A common failure mode is skipping the Discover and Define phases to jump straight to Develop. This leads to building the wrong thing efficiently. By engaging in the early phases, engineers can narrow down viable solutions based on technical constraints and user needs. Additionally, writing scenario tests—tests that simulate full user journeys rather than isolated functions—helps engineers internalize product context and identify usability issues before they reach production.
AI as a Force Multiplier
AI is not replacing engineers but changing their primary value proposition. While AI can generate code, it cannot inherently understand user intent or business strategy. Engineers can leverage AI to accelerate the 'Discover' phase by analyzing large volumes of customer feedback and support tickets. This allows engineers to make data-driven product decisions without waiting for product managers to synthesize insights. However, relying solely on AI for code generation without developing product skills leads to a 'multiple choice' career path, where engineers become passive consumers of AI output rather than active creators of value.
Conclusion
The future belongs to 'M-shaped' professionals who possess deep technical spikes and broad product skills. Engineers who invest in ownership, collaboration, and user empathy will remain highly leveraged. The strategic imperative is clear: do not just write more code; write better products. By mastering the reindexing from system to user, engineers can secure their relevance and drive greater business impact in the AI era.
Key insights
-
The 'product-minded engineer' is defined by a balanced focus on the 'what' and 'why' alongside the 'how.' This mindset is not exclusive to product companies but applies to any role where code serves a user, including infrastructure and internal tools.
Impact: Redefines engineering career trajectories, moving away from pure technical depth toward hybrid roles that command higher strategic influence and compensation.
-
The 'Great Reindexing' is the cognitive process of shifting from a system-centric view to a user-journey-centric view. Engineers must learn to start with user problems and map them to technical solutions, rather than the reverse.
Impact: Reduces misalignment between engineering and product teams, leading to faster development cycles and higher user satisfaction by ensuring the right problem is solved.
-
AI tools are reducing the leverage of pure coding skills, making product skills, collaboration, and ownership the new differentiators. Engineers who rely solely on AI for code generation without developing product intuition risk stagnation.
Impact: Shifts hiring criteria and performance metrics from code volume to business impact, requiring engineers to demonstrate strategic thinking and user empathy.
-
The Double Diamond framework (Discover, Define, Develop, Deliver) is critical for avoiding the trap of premature development. Most engineering failures stem from skipping the Discover and Define phases to jump straight to building.
Impact: Improves resource allocation by ensuring technical effort is spent on validated user needs, reducing waste and increasing the probability of product success.
-
Discoverability is a high-leverage product skill often overlooked by engineers. A feature that is not easily found by users provides no value, regardless of its technical sophistication. Simple discoverability hacks can yield significant ROI.
Impact: Increases feature adoption rates and user engagement, directly impacting key business metrics such as retention and conversion without requiring complex backend changes.
Action items
-
Implement scenario testing in your development workflow. Write tests that simulate full user journeys, including edge cases and real-world contexts, to identify usability issues and product gaps before deployment.
Impact: Enhances product quality and user experience by catching context-dependent bugs early, reducing post-launch support costs and improving user trust.
-
Use AI tools to analyze customer support tickets, sales calls, and user feedback. Extract patterns and pain points to inform your 'Discover' phase, allowing you to make data-driven product decisions independently.
Impact: Accelerates the discovery process and empowers engineers to identify high-impact opportunities, reducing dependency on product managers for user insights.
-
Adopt the Double Diamond framework for all major projects. Explicitly define the Discover and Define phases before starting development, ensuring alignment on user needs and technical constraints.
Impact: Prevents scope creep and misaligned development efforts, ensuring that engineering resources are focused on solving validated user problems.
-
Invest in discoverability features for your products. Add contextual cues, error messages, and UI elements that guide users to new features, ensuring that built functionality is actually used.
Impact: Increases feature adoption and user engagement, maximizing the return on investment for development efforts and improving overall product value.
-
Develop metacognitive skills by regularly assessing your strengths and weaknesses. Allocate time for learning product, collaboration, and ownership skills, rather than just technical upskilling.
Impact: Positions engineers for senior leadership roles by demonstrating strategic thinking and self-awareness, key traits for high-impact hybrid professionals.
Quotes
“my definition would be an engineer who cares at least a month as much about the what and the why as the how”
“I call it the great reindexing, because when you're developing a product, you start with uh the user journey and then you go to the system”
“you probably are going to need all three of those don't just do more code, but develop some of these higher level skills such as product skills, collaboration skills, ownership skills”