What does “product thinking” mean in a developer job posting?
When a job posting says “we’re looking for a developer with product thinking,” I want to ask: what exactly will I be able to decide?
I like to understand why we’re doing something. Before spending two weeks writing code, I’d rather understand who needs it and how they’re going to use it. It may turn out that their problem can be solved in two days.
Then you look at the responsibilities. Write the code, check that everything works, ship the update. If something breaks after release, roll back to a working version. While you’re at it, look at how competitors solve the same problem and think about where to go next.
And this is where it gets interesting. I’m expected to care about the product as if it were my own. If we got it wrong and spent three months on something nobody needed, that’s partly my responsibility too. But if we got it right and the product brought the company a solid profit? I still have the same salary and, if I hit my targets, a bonus. The profit stays with the owners. So I’m being asked to share the risk, while the conversation about sharing the profit never even starts.
Decision-making is interesting too. Can I suggest not doing a task at all if I can see it won’t deliver any value? Can I stop a release if I realize customers could be left without service?
AI is interesting too, by the way. The first thing people usually discuss is how to write and review code faster. Let’s say a developer can now do their part twice as fast. But if the task then sits in approval for a week, maybe we should also look at what’s happening during that week?
So when someone tells me to “treat the product like it’s your own,” I’d ask two questions. First: what will I be able to decide? And second: how will we share the outcome if it works?