* Product management is a high velocity communication game. You are constantly working with customers, customer success managers, sales engineers, CXOs, marketing team, sales people etc. * You can easily have a 1000 open tickets. You need to stay on top of which are in progress and what are the priorities. * The customer may communicate with multiple people in your organization but ultimately it is your responsibility to ensure that their priorities are taken into consideration and addressed. * Slack, Outlook in Office 365, Jira, and Zendesk are the goto tools
Here is the interview https://prodjeeves.com/transitioning-into-product-owner-role-interview/
I want to hear what the community says. What would you like to hear?
What would you like to ask other product managers? If you have some questions, let me know.
Otoh, I am also trying to understand the space. If you can spend sometime for an interview, please let me know. I would be glad to.
I'd ask them what PMs do in their organization, what POs do, and what the difference is in their mind. Ask what level of detail they operate at, what they delegate to others, and what types of things are expected to be passed up to their boss.
You also might get interesting perspectives if you explore outside the software industry. Product managers exist in all kinds of companies, with the same overall goal to understand the market and produce the correct product under the correct business model. But the day-to-day of a software PM is vastly different than the day-to-day of a PM that produces retail goods, for example.
How do you balance priorities that you're hearing from customers with priorities that you're hearing from sales? PMs often find themselves in between sales, customers and engineering, and balancing those conflicting priorities is tough.
How do you convince engineers to take on hard tasks? A lot of times PMs come up with great ideas but engineers will balk at actually implementing them because "it's too hard."
At some companies, Product Manager is a high responsibility, high accountability position that drives the roadmap. They are responsible for deciding what gets built and ensuring that it's both feasible and will generate the highest ROI. They are accountable for moving the product forward and coordinating across departments to make sure the right work is getting done.
On the other end of the spectrum, some companies treat the Product Manager like a communication switchboard or a Jira ticket manager. These positions don't have much power, don't make major decisions, and mostly follow orders from someone else. They spend their days sifting through Slack channels, Jira tickets, and nagging developers for updated estimates.
The trick is to get the person to elaborate on their experience before you tell them what type of Product Manager you're looking for. The challenge is that if you describe the position too much up front, most candidates will simply adjust or embellish their experience to match what they think you want to hear. If you instead ask them detailed questions about what they did at previous companies, you'll get a more unbiased view of their prior experience.
> Here is the interview https://prodjeeves.com/transitioning-into-product-owner-role...
Be careful about using Product Manager and Product Owner interchangeably. They mean different things at different companies.
Answering this well requires a) ability to communicate convincingly, b) evidence, typically through user data, research, competitor analysis, etc., c) authority in your space, d) ability to translate business requirements into technical speak, and vice versa, and e) respect from the team you're working with.
Add long-form writing in there. One of the most important things is alignment so everyone knows what they're doing and why they're doing it. This helps people become independent, make their own decisions, and take actions.
Upstream emails that align everyone across several functions, skillsets, and abstraction levels prevent many small interactions and ambiguities downstream, effectively leveraging your time.
Explaining the objectives at a high level in terms everyone understands, then going incrementally deeper to tie these objectives to specific actions of the relevant people.
Tying revenue to scalability to spinning up Kubernetes nodes to an open issue to a line in a particular file that should be changed is a journey across abstraction levels.
This is our current state, this is our desired state, this is the gap between the two, and we haven't crossed that gap because X, Y, and Z. This is what we'll do to solve that, cross that gap, and go from our current state to our desired state.
Writing down these things exposes thought processes and rationale. It allows people to chime in at the abstraction level they prefer to augment, correct, poke holes, shed light on blind spots, and question assumptions in these thought processes. It also enables everyone to be on the same wavelength.
The above "tying" thread allows an advisor to comment, a CEO to comment, a designer to comment, a developer to comment, and a domain expert to comment. Each one of them has a place they can "hook" into.
How many conversations/requests/Slack direct messages/phone calls does this prevent?
I replied yesterday to someone asking about what they can do to understand and monitor product usage and drive development[0]. I wrote a bit about this in an "index" reply[1], and wrote about dealing with clients to develop custom machine learning products (mid six-figure projects) in a twitter thread[2].
- [0]: https://news.ycombinator.com/item?id=25270028
- [1]: https://news.ycombinator.com/item?id=25244246
- [2]: https://twitter.com/jugurthahadjar/status/131066829330549965...
Andvanced version: "Create and describe some case, puzzle, exam that you whould give your future product manager on the interview"
This will give you a good perspective of how he sees himself as a product and rich soil for open discussions.
Reality is by the 2-3rd interview, a PM candidate necessarily knows as much about your product or company as a prospective customer and the least technical sales person, and presumably they would buy what you are selling. Get them to sell your product back to you.If you are an enterprise interviewer, you're basically looking for polish and acumen, and if you are a startup I'd recommend looking for self awareness. A mismatch is basically a time bomb, so understand your own business.
The best PMs I have ever met were amazing because part of being that smart is they were strategic about the products they took on. This upstream eye for growth and the ability to be a part of it, which they had consciously developed with experience (and some, mainly elite, education), positioned them for success because growth beats literally everything. Ask what they think the factors in the growth trajectory of your product are.
> Product Manager is a bullshit job that is wildly overpaid due to managerialism and the tech bubble excess.
Some have called Product Management the “Visionary’s Whipping Post” as role sits internally between the company’s development, accounting, production, and accounting teams who all need someone to blame for their woes. Others have describes the role in terms of shuttle diplomacy between external customer needs and internal corporate objectives. How would you describe or frame the role of Product Manager?
For your own organization, where do you strike the balance between Microsoft's "Promise everything even if you don't have it" and Apple's "Say Nothing until it's available in the store," promotional strategies and how does your position relate to your unique line of products, industry and customers?
Are you currently in a product expansion phase or option/feature expansion phase?
Are you positioning yourself for a new market segment or extending your reach into the existing customer base?
What products or industries do you admire or see as well managed?
How would you tackle a situation where a customer wants something completely diffrrent, which you are made aware of during UAT.
What is a customer journey?
What do yoh thing of working agile?
Hiw do you start off after being hired onto a project and broader system ecosystem you have never been part of before.
Have they ever worked on a product before it had achieved a sense of product-market-fit, and if so, how did they help it get there?
When they did not feel content in their role, what was lacking? And when they did feel content in their role, what were the great elements that set it a cut above the rest?
If a product manager has any muscle they not only have to project product goals but they must also defend the product from internal incompetence, which is far more challenging than it should be.