5 Comments
Feb 4Liked by Hemant Pandey

Yah it's nice. I got a lot of out of it

Expand full comment

Great piece!

I have to say that being product minded is not enough; you need to be in organization that value this otherwise you might look intrusive/nosy

Expand full comment

Be a problem solver, not just someone who solves technology problems.

Some of the problems in the product or organization are not technical, yet your contribution can be valuable.

Nice article, Hemant!

Expand full comment

Great article Hemant! I love hearing about engineers like you, who are thinking about being Product Minded and striving to up your game, and build better product. Awesome! Your points about engineer's having passion and curiosity are spot-on. I like to say that engineers can "see around corners" and discover complexity before it happens. Edge cases! That's why we need durable teams, and tech needs a spot at the table along with the customer/product team! – FYI, my own post on the topic: https://blog.bosslogic.com/p/moving-away-from-the-monolith-faster-better-with-a-product-mindset-f8f0dc58653c?r=2xiufs (I've been planning another one about how to structure a product oriented team... finding your's makes me think I need to write it as my next post).

Expand full comment

antastic insights, Hemant! Your breakdown of what it takes to be a Product Minded Engineer is spot-on. The emphasis on passion, curiosity, and customer-centric thinking truly sets the stage for impactful engineering. Your article serves as an insightful guide for engineers looking to go beyond technical problem-solving and make a real impact on product success. Kudos!

Expand full comment