a young discipline we’ve spent a lot of time working out « how » to build software. But once you have the foundations, you need devs who engage with the « why » actively. Engineers who have a thirst for using technologies to leapfrog human/user problems. Those with empathy to reach for magical experiences. That is what de fi ned a product engineer in my books... Great product engineers know, that minimum lovable products need the right depth to be considered during the build phase.
early feedback ⚖ Drives Proactive discussions Inquisitive TIPS: Ask “why” this, are there simpler alternative options? Drive alignment, common understanding Focus on the problem, and priority
communicator 🤝 End to end ownership Take ownership TIPS: Build a strong relationship with design & product management Reach out for feedback on how valuable they see your product suggestions Own or drive decisions Measure and sharte results
engineer? Super Power Median Liability P0 P0 P0 P1 ( optional ) P1 P2 ( optional ) In next month In next quarter P0 liablity P1 liability P0 Median Categorize behaviours Create action items
leadership The Pragmatic Engineer newsletter by Gergely Orosz Taro Access the collective wisdom of Tech industry experts Lenny’s newsletter about product, driving growth, and accelerating your career.