JUN 18, 2020 · 6 MIN READ
The Product Manager Job Description has a few things in common across companies. Essentially, the Product Manager is the CEO and the janitor of the product.
A Product Manager is expected to be the liaison between the business teams and the development teams.
Learn how to break into product management.

An organization may choose to follow agile or waterfall, but the Product Manager is always expected to be a follower of the agile methodology.
The product team is the bridge between all the different stakeholders of a project.
The success of a product rests on the shoulders of a Product Manager.
Equally important, if not more important, is the fact that the failure of a product also rests on the shoulders of a Product Manager.
Nobody wants their product to end up on the list of the top 10 product fails of all time.

The following expectations are generally mentioned in any product management job description.
The ability to create a product roadmap with a vision for the future is a definite expectation.

The Product Manager not only needs to come up with the vision, but also drive the vision.
The ability to interview multiple stakeholders to try and figure out their underlying problems is an art.
Many times, people tell you what they think could be a good feature, but they are only describing their perceived solution to an underlying problem.
A Product Manager's job is to figure out that underlying problem.
Then, the product team needs to brainstorm various ideas to come up with a solution to that underlying problem.
The product team may very well choose a completely different solution. The customer's proposal can act as a benchmark, but doesn't have to be the main solution.
This soft skill is very rare. We can only find it in the best of Product Managers.
This skill is at the heart of driving the vision.
There will always be people who are comfortable with the way things are going and will not like any new ideas that the product team comes up with.
The key here is to remain calm and firm.
Change doesn't happen overnight.
The Product Manager needs to keep on driving the conversation, and trying to brainstorm as much as possible. The ultimate goal is to move forward, to disrupt the status quo.
Effective and efficient stakeholder management is the basic expectation from any and every Product Manager.
Stakeholders can be the external customers, the developers and even the leadership team.
The art of influencing without authority can be very useful here.

Everyone has their idea of doing things.
The Product Manager's job is to figure out the common ground and then move up from there.
Every Product Manager should know how to effectively manage the entire product life cycle.
The product may succeed or it may fail. Either way, the product team must be aware of all the metrics and indicators that point to a change in the stage of a product's life cycle.

The applicability of each of the above requirement can be different depending on the seniority of the role.
Let us cover the seniority aspect in the next section.
It is important for everyone in the fields of product management and project management to be clear about the following differences.
Many job descriptions use these 2 titles interchangeably.
However, every candidate should keep in mind that the Product Owner roles is generally junior to the Product Manager role.
During the interview stage, it is best to ask up front the exact roles and responsibilities expected of the candidate.
However, the underlying product skills are common.
One major difference is that everyone already expects a Product Manager to display product leadership qualities.
Before I move on, I want to state that there is no defined educational criteria to hire a Product Manager.
Product management courses do exist.
But it depends on an individual's specific environment whether or not a course would be beneficial.
The point of this article is to point out the generic minimum qualifications that most product management job descriptions have.
Here are some minimum qualifications -
Here is a sample of the job description that a candidate can expect.
Before any interview, every candidate should take out time to fully research the job description.
The job description may seem generic, but each line in it carries a specific intent.
Many people just skim through the roles and responsibilities without fully grasping the significance of each item.
If there is a requirement for coding skills, then don't ignore that requirement. Never assume that a product management job doesn't require coding skills.
The requirement has been mentioned there because the interviewer genuinely expects you to know how to code.
Subscribe to my newsletter for all the latest updates.