Week 30, 2026
My manager should probably skip reading this week’s newsletter.
Not because I’m unhappy. Not because I’m disengaged. Not because I’m preparing a dramatic LinkedIn announcement featuring a black-and-white profile picture and a paragraph about “exciting new opportunities.” The reason is much simpler, and probably more uncomfortable: I regularly apply for Product Management jobs.
Not once every few years. Not when a reorganization happens. Not when I’m frustrated. Regularly. And before anyone jumps to conclusions, let me clarify the important part: It’s NOT because I want a new job. I like what I do. I enjoy the people I work with. I believe in the products I help build. Yet every few months, I update my resume, scan open roles, and apply for positions that genuinely interest me. Why?
Because somewhere along the way, I realized that most Product Managers spend a lot of time studying Product Management but very little time studying the market for Product Managers. We consume blogs. We listen to podcasts. We subscribe to newsletters. We attend conferences. We collect frameworks like souvenirs from professional tourism. Yet the most revealing source of information I’ve found isn’t AI or a conference keynote or a viral LinkedIn post. It’s an interview. Interviews are my version of market research. Or maybe a better analogy is this: It’s speed dating for Product Managers. Two strangers meet, exchange expectations, talk about priorities, discuss problems, and quickly decide whether they see the world in a similar way. Every conversation provides a glimpse into how another organization thinks about product. Every role description exposes assumptions. Every hiring manager reveals priorities. And every interview teaches me something.
What began as curiosity gradually became a habit. Then the habit became a learning system. Today, I genuinely believe one of the most effective ways to understand where Product Management is heading is to occasionally sit on the other side of the hiring table and see what questions organizations are actually asking.
What surprised me most is how often those conversations challenge assumptions I didn’t realize I was carrying. Most Product Managers think they understand the profession because they practice it every day. That sounds reasonable until you remember that many of us have spent years inside a single environment. We learn one company’s terminology. One company’s roadmap process. One company’s stakeholder culture. One company’s approach to customer discovery. One company’s definition of success. Then, without realizing it, we start treating those practices as universal truths. Long tenure creates expertise. It can also create blind spots.
Interviews expose those blind spots quickly. I’ve sat in conversations where an interviewer described a process that sounded revolutionary before realizing it was just their version of something we already do under a completely different name. I’ve also experienced the opposite. Processes I assumed were industry standard turned out to be highly specific to one organization. There is a special kind of Product Manager humility that comes from discovering your company’s sacred product ritual would sound completely foreign somewhere else. Sometimes an interviewer asks a question you haven’t considered in years. Sometimes they describe organizational structures that force you to rethink how decisions get made. Sometimes they reveal expectations that barely existed three years ago. Suddenly you realize that while you were becoming increasingly effective inside your environment, the broader profession was evolving in parallel. The profession evolves whether we pay attention or not. And the best way to stay aware of those shifts is to step outside your own ecosystem once in a while and listen carefully.
One pattern appears almost every time. Regardless of company size, industry, geography, or maturity, hiring managers consistently gravitate toward remarkably similar themes. They want Product Managers who can demonstrate measurable impact. They care about business outcomes. They care about customer value. They care about product strategy, roadmap ownership, execution capability, user empathy, cross-functional influence, and leadership without direct authority. Different companies use different words. Different interviewers prioritize different examples. But the signal is surprisingly consistent. The market increasingly rewards Product Managers who can connect actions to outcomes.
That’s one reason I find interviews so valuable. They cut through the noise. Thought leaders may debate frameworks. Social media may “celebrate” achievements. Conferences may promote trends. But hiring managers reveal what organizations are actually willing to pay for. And what they repeatedly evaluate is impact. Not “I attended meetings.” But “I drove outcomes.” Not “I managed a roadmap.” But “I delivered measurable business value.” Not “I coordinated stakeholders.” But “I influenced decisions that improved customer or business results.” Every interview reinforces the same lesson: The market rewards impact, not activity.
When I review job descriptions, I often notice the same pattern reflected in resume guidance and hiring criteria. Organizations want evidence that a Product Manager can identify opportunities, align teams, execute effectively, and create results that matter. The further you progress in your career, the less interested people become in what you managed and the more interested they become in what changed because you managed it.
This is where the real value appears. Many people think interviewing only makes sense when they need a job. I think that’s like saying customer interviews only make sense when you’re ready to launch a product. Product Managers would never accept that logic in their own work. We believe in continuous discovery. We believe in staying close to customers. We believe in gathering feedback early and often. Yet many of us treat our own careers as if feedback should only occur during moments of crisis or transition. What if interviews were viewed differently? What if they were treated as professional discovery?
The hiring manager becomes the customer. The role description becomes the problem space. The interview becomes research. Suddenly the entire experience looks less like job hunting and more like learning. Most Product Managers collect frameworks. Interviews collect reality. Sometimes one interview surfaces more practical insight than weeks of reading content online. Sometimes one interview teaches more than a conference. You hear emerging expectations before they become mainstream. You notice changing language before it becomes standard. You discover new organizational models before they appear in case studies. Most importantly, you learn whether the capabilities you are developing remain relevant beyond the walls of your current employer.
Weak Product Managers assume their company’s processes are universal. They stop benchmarking themselves. They confuse tenure with market relevance. They become insulated from industry evolution. Strong Product Managers stay curious. They seek external feedback. They challenge their assumptions. They continuously benchmark themselves against a changing market. The best way to benchmark Product Management is to see how other companies define it.
So no, this isn’t a confession about leaving. It’s a confession about learning. The goal isn’t to leave. The goal is to learn. Career growth is not only about promotions, bigger teams, larger budgets, or more ambitious roadmaps. Career growth is also about understanding how the profession itself is changing.
If you’re happy in your role, great. Stay. Build. Grow. Contribute. But don’t become isolated. Interview occasionally even when you are happy. Benchmark yourself against the external market. Stay curious. Listen carefully to what hiring managers ask. Track changing expectations. Learn how different organizations practice Product Management. Treat interviews as research. Study the market you operate in, including the market for Product Managers themselves. Because the deeper lesson I’ve learned from this habit is simple: the best Product Managers are students of systems, incentives, behavior, and change.
Why would we exclude our own profession from that curiosity? The biggest lesson wasn’t finding a new job. It was discovering how quickly the definition of Product Management evolves. The organizations that interview us reveal what the market values today. And the Product Managers who keep learning from those conversations stay relevant tomorrow.
This newsletter reflects my personal views and experiences as a product manager. It does not represent the views, strategies, or opinions of my employer or any organization I am affiliated with.
