From Engineer to AI Product Manager: The Art of Unlearning

One of my mentors gave me an important piece of advice when I was moving from an engineering role to product management:

“You have to unlearn some of the things you did as an engineer and learn new things that PMs do.”

At the time, I didn’t fully understand it.
But after stepping into the PM role, I realized how true it was.

How I Thought as an Engineer

As an engineer, I was trained to:

• Jump straight into solutions

• Optimize for performance and correctness

• Measure success by what I built

The mindset was simple:
There is a problem → let’s fix it.

And honestly, that mindset works really well in engineering.

What Changed When I Became a PM

When I moved into product management, I had to unlearn a lot of this.

The game was different.

As a PM, I had to learn to:

• Sit with the problem longer than feels comfortable

• Say no to good technical ideas that don’t move the business

• Optimize for outcomes, not output

• Measure success by what actually changed for users and customers

Earlier, my instinct was:

“Let’s fix it.”

Now, my instinct is:

“Is this the right problem to fix at all?”

That pause, before jumping to a solution, was the hardest thing to learn.

It’s Not About Being Less Technical

This shift was not about becoming less technical.

It was about using technical knowledge differently:

• Asking better and deeper questions

• Challenging assumptions early

• Translating complexity into clarity for stakeholders

My engineering background didn’t disappear.
It just started working in a new way.

The Biggest Lesson

Engineering taught me how to build.

Product management taught me what’s worth building, and why.

If you’re an engineer moving into product management:

• You’re not starting over

• But you are rewiring how you think

And yes, some unlearning is required 🤓