I saw this many more times than I wanted (and I bet you did too):
An OR Engineer starts in a new company. In a couple of months, they have an algorithm to solve an optimization problem. Itās not perfect, but it works, so they look for refinement. After some iterations, solutions seem ideal. But when going to real users, no one wanted the tool.
I didnāt just see this pattern in others. I felt it in my skin. Itās frustrating.
Though this is not a time to regret, I now firmly believe thatās not the way to succeed in Operations Research.
Today, Iāll share why becoming a Product OR Engineer is the key objective for Operations Research professionals aiming to create solutions that deliver genuine business value and user delight.
Todayās agenda in Feasible will cover:
š§ What does being a Product OR Engineer mean?
š„ Why are Product OR Engineers on the rise?
š„ How User-Driven Development becomes your advantage
Iāll give you examples of that last part, including a story from my team a year ago.
Ready? Letās dive in⦠šŖ
š§ What does being a Product OR Engineer mean?
Traditionally, OR professionals like us have excelled at solving complex mathematical problems.
Itās normal; weāve been trained for that.
Yet, these mathematically and algorithmically elegant solutions often donāt resonate with users, donāt get stakeholder buy-in, and fail to integrate into business processes. Itās unfortunate because you want to deliver value but canāt find a way.
We understand the connection between our optimization engine and software development, but not with a product. Without a product, weāll struggle to deliver our solution.
We need to develop solutions for business problems within a product.
You can own the entire solution lifecycle, from problem identification with stakeholders to deployment and continuous improvement.
(And now you realized -as I just did while writing- that Iām repeating a word: product, product, product.)
A Product OR Engineer merges technical OR expertise with a strong product mindset. In that role, you will:





