[PM] Is it time to embrace the role of Product Engineer?

October 13, 2024

Why am I addressing this topic?

Reason number 1.

Recently, I started using a new code editor - Cursor. Its capabilities are excellently showcased on https://www.cursor.com/, so I won't go into detail about this tool. In short, it greatly reduces the time spent writing code by utilizing large language models.

After a few days of use, I noticed that I feel more like a Product Designer/Manager than a Software Engineer. Working with Cursor, I focus more on connecting components/modules rather than building code from scratch. Of course, you need to verify and test what the tool provides, but there are moments when the conversation takes on more of a form of proposals and suggestions for the editor to change something ("Let's change the UI and make it more modern.").

Combining these two roles, we get a Product Engineer, and it turns out there's a demand for such individuals. Below is a graph from Google Trends for the phrase "Product Engineer" over the last 5 years.

tech1-1.jpg Google Trends - Product Engineer

Reason number 2.

And here we can again mention Cursor. The potential it holds is enormous. And this makes me unsure whether the role of Software Engineer in its current form will exist in 2-3 years. Moreover, I've noticed a certain trend (at least when it comes to Salesforce projects) where developers are getting more responsibilities not directly related to code. Of course, contact with business has always been there, but I feel it's taking on a slightly different role (greater responsibility in this area).

As a result, as a Software Engineer, I need to develop a wider range of skills to navigate conversations with marketing or sales departments well (once I'm allowed access to them, which unfortunately varies).

Who is a Product Engineer?

When I started looking for answers to this question, it turned out that several interesting articles have already been written on the subject. I even dug up a Product Engineers' manifesto - https://productengineer.org/.

tech1-2.jpg Product Engineer Manifesto - https://productengineer.org/

I totally agree with these points, and interestingly, I'd like to work this way. To be involved at an earlier stage of product development, not often just at the stage of assigning a Jira ticket at a planning meeting. As I mentioned earlier, in daily work, we often don't know where specific requirements come from, and the entire development process suffers as a result.

Another great source is https://posthog.com/blog/product-engineer-vs-software-engineer. I particularly liked the following statement.

tech1-3.jpg https://posthog.com/blog/product-engineer-vs-software-engineer

You could say that a Product Engineer is somewhat like a founder, but not working in their own startup. The necessity for a broader perspective and ensuring that what we do actually impacts the final product are crucial in all of this.

Job Offer Example

I regularly use the Brilliant app (learn by doing). In one of the emails I received, there was a brief mention that they're looking for people to join their team. Out of curiosity, I clicked and saw an offer for the role of Product Engineer: https://jobs.lever.co/brilliant/24f348c1-34db-4fec-b360-adb98bb2d7a9.

The scope of work section is particularly interesting.

tech1-4.jpg https://jobs.lever.co/brilliant/24f348c1-34db-4fec-b360-adb98bb2d7a9

Sounds good, doesn't it? And they don't require specific technologies, adding that you can always catch up: "Lack of prior experience with a specific technology is never disqualifying, but extensive experience with Elm, Django, or GraphQL would help you fill important skill gaps on our current team."

This aligns with what Bartek Pucek recently said in a conversation with Mateusz Chrobok (IT Manager gotowy na jutro. Jak wdrożyć Agentów AI i osiągnąć sukces – AI_devs LIVE). Bartek is recruiting for his startup proofs and points out that "it's hardest to find people with an imperative to act." I think this is a great summary of the Product Engineer role.

Key Points

  • A Product Engineer is focused on building a fantastic product as a whole, not just its software-related components.
  • The development of code editors and copilots is forcing programmers to expand their responsibilities and improve their soft skills.
  • In the final analysis, the most important thing is the "imperative to act."
  • Is it time to embrace the role of Product Engineer? Definitely yes. Even if we don't get such a job title, it's a good idea to demonstrate its desirable characteristics.

SOURCES