Skip to content
All job descriptions

Product

Product manager job description

Product manager job description. This page describes the role for a small team.

What a product manager decides on a small team, how to write the post so it is not a project-coordinator ad, and a salary example for Germany.

Published November 20, 2026 · 4 min read

Product manager job description

A product manager on a small team decides what gets built next and writes it clearly enough that an engineer can start without a second meeting. They do not run the engineers. They do not own the sales quota. On a team that is still small, they are often the person who stops the company from building five half-finished features at once.

Write the post for that decision. If the seat is really a project coordinator who updates a board, call it that. Candidates who have done the job can tell the difference from the first paragraph, and they will not apply to the wrong one.

The decisions this seat owns

The product manager talks to people who already pay, not only to people who might. They come back with a problem written in the customer's words, a guess at how often it happens, and a proposal for the smallest change that would tell you if the guess is right. They keep a single ordered list. When sales brings a new request, the product manager either puts it on that list and takes something off, or they say no and record why.

They do not own the technical design. That sits with the backend engineer. The post should say so. A product manager who is hired to "be technical" and also to design the schema will collide with the person who has to maintain it.

They also do not own hiring policy. They will help interview for their own team. The stages, the notes, and the rejection still belong on the candidate record, in the same system the company uses for every role.

What a useful post includes

Name the product and the customer. "You will work on the dispatch screen used by warehouse leads at mid-size carriers" is a job. "You will drive alignment across stakeholders" is not. Name the founder or the head of engineering they will sit with. Name the meeting that already exists, and say whether you expect them to cancel it.

Publish the salary. The band on this page, €65,000 to €92,000 with a midpoint around €78,000, is an example for a mid-level product manager on a 30-person B2B team employed in Germany in 2026. It is not a market report. A French contract, a first product hire, or a company in Berlin with equity as a large part of the offer needs its own numbers. Put yours in the post before you share it.

Skip the tool parade. A team of thirty does not need a product manager who has rolled out three roadmapping products. It needs someone who can write a one-page problem and keep the list short.

Example: the first product hire

A 25-person software company in Cologne had a founder who still wrote every ticket. Engineers waited two days for a decision that could have been a sentence. The founder published a post asking for a product manager with "ten years in enterprise SaaS" and a record of managing managers.

The rewrite was shorter. The hire would spend the first month on five customer calls and the tickets those calls produced. They would not hire a team. They would not own a budget beyond the next quarter's build. The published band matched the number finance had approved. Three of the four finalists had been product managers at companies under fifty people. The fourth had the enterprise résumé and wanted a team of six. The post had already told him that team did not exist.

After the post goes live

Use the same text when you score applicants. If the post says the first month is customer calls and tickets, the interview should ask about a call the candidate ran and a ticket they wrote. A case study about a platform you do not sell tells you something else. When the work shifts, update the post the same week. An old description keeps collecting applications for a job you are no longer hiring.

Frequently asked questions

Does a 20-person company need a product manager?

Not on day one. You need one when the founder is still the only person who can explain why a feature is next, and that explanation is blocking the engineers. Hire for that gap. Do not hire to have the title on the website.

What should the first 90 days cover?

Sit with five customers who pay you, write down the jobs they hire the product for, and turn the next month of work into tickets an engineer can start without a meeting. A roadmap slide is optional. A clear no to the other requests is not.

Qonir is ATS software for small teams. The job, the candidate, and the stage stay on one record.

Tags

  • product
  • job description
  • small teams