We consider ourselves Builders first, software engineers second.
Our craft combines Product Thinking with technical execution.
We concern ourselves with matters of design and quality in the technical, aesthetic, and business domains, taking an active part in each to shape the product and empower others to do the same.
We take great professional pride in our products as a whole and refuse to limit ourselves to technical-only roles in our teams.
Our shared goal is simply to build great products, and recognize that achieving this requires builders who deeply understand the customer's needs.
In our work as Product Engineers, we have come to value:
- Continuous delivery of working software over promises and estimations
- Asking why to deeply understand the customer problem before diving into code
- Customer collaboration and feedback over tickets and second-hand knowledge
- Teamwork and communication over picking up tasks and working in isolation
- Using the product ourselves over relying on others to test our software
- Strategic thinking and understanding the market and context you're operating in
How to think like a Product Engineer (PDF)
Posts written by various people about the Product Engineer role:
- What is a Product Engineer? by Viljami Kuosmanen (@anttiviljami)
- The Product-Minded Software Engineer by Gergely Orosz (Pragmatic Engineer)
- How to Become a Product Engineer 🎨 by Luca Rossi and Rasmus Makwarth
- Product engineers by Sherif Mansour (Atlassian)
- From Code Monkey to Product Engineer by Saranga Buwaneka
- Are Product Engineers Replacing Software Engineers? by Peter White (@peterwhite)
- The Product Engineer Era by Nahuel Alberti (@NAlberti7)
- What is a product engineer (and why they're awesome) by PostHog
- Product engineer vs product manager: What's the difference? by PostHog
- Product Engineers by Lee Robinson
Star this repository to show your support for the Product Engineer Manifesto above!
