Product Manager: market

Vacancy

an open job that cleared the quality gate and lists at least two technologies

Observed candidate

a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter

Matchable candidate

not counted yet

Window

jobs open at the moment the snapshot was built

Junior / Associate PM leads a small part of the product or individual features under mentorship. Jump to Middle — independent ownership of a direction: discovery, prioritisation, metrics, launches. Senior is responsible for a large product or important direction, influences strategy. Group / Lead PM manages several products or a team of PMs. Career flow: (often from analytics, development, BA, marketing, support) → Associate / Junior PM → Middle → Senior → Group / Lead PM → Head of Product → CPO. Pure Junior openings are few — entry to the profession is competitive (see separate question).

Top tools: agile, product owner, scrum, jira, backlog. Tools: Jira + Confluence (backlog, documentation), Figma (design and prototypes), analytics (Amplitude, Mixpanel, Yandex Metrika, GA4), SQL (growing requirement — get data yourself), Miro, roadmapping tools, AI tools for research and feedback analysis. Key skills: product thinking — see the user problem and value behind features; discovery — custdev, interviews, hypothesis testing, market and competitor analysis; working with metrics — define, compute and move the right product metrics, unit economics, metric tree; prioritisation — decide what to do and what not, and argue it; strategy and roadmap — product vision and the path to it; A/B tests — verify changes with experiments; working with the team — set tasks, explain "why", lead the team without formal authority; stakeholder management — align interests of business, users, team; communication and influence — the PM's main tool; UX sense — understand the user and good design; technical horizon — speak with development in the same language. English — for the international market. Main thing: PM is valued not for tool knowledge but for the ability to find what to build and bring it to measurable result.

Terms are constantly confused, and there is no single answer — much depends on the company. Basic difference: Product Owner (PO) — a role from the Scrum methodology: a person who manages the backlog of one team, formulates and prioritises tasks, accepts the result, works closely with the team in sprints. PO is focused on "what the team does in the next sprints" — on execution. Product Manager (PM) — a broader role: responsible for the product as a whole — strategy, market, users, metrics, business result; decides not only "what's in the sprint" but "what product and direction at all". In practice: in some companies PM and PO are one person (especially in small ones); in others PM sets strategy while PO leads the backlog and team next to them; in yet others "Product Owner" is just an accepted name for a product manager. In Russia "Product Owner" is often used as a synonym for PM or as a title for a PM level closer to the team. Bottom line: when reading a job posting, look at responsibilities, not the title — if it's about strategy, market, metrics and result, it's PM work; if it's only about backlog and sprints, it's PO in the narrow sense. Career flow: PO in the narrow sense — a common step to a full PM.

Three roles with similar abbreviations and different essence. Product Manager is responsible for what to build and why — for the product, its value to users, and the business result; the key question — "are we making the right thing". Project Manager is responsible for how to deliver — that the defined scope of work is done on time, on budget, and with the right quality; the key question — "are we making the thing right and on time" (see /research/pm/project-manager). Roughly: product manager decides what to do; project manager makes sure it's delivered. Business Analyst is responsible for requirements — elicits and formalises what exactly needs to be done within a given direction, describes processes and requirements for the team (see /research/analyst/business-analyst). Roughly: PM chooses the direction and is accountable for the result; BA works out requirements in detail within it; Project Manager organises delivery. In small teams these roles are often combined in one person; in large ones — separated. Career flow: people often come into Product Manager from Business Analyst, Project Manager, analytics, development, or marketing.

PM work is a continuous cycle of "understand → decide → build → measure". 1) Discovery (product research) — understand which user problem is worth solving: interviews and custdev, behaviour analysis in the product, market and competitor study, gathering and analysing feedback, formulating and testing hypotheses. Goal — don't build what nobody needs. 2) Strategy and vision — where the product is heading, on what market, for what users, what its differentiation is; on the horizon of quarters and years. 3) Roadmap — product plan: which big tasks and in what logic, tied to goals (not just a list of features with dates). 4) Prioritisation — the most important and the hardest: decide what to do now and what — not, and why; resources are always limited, and a good PM is recognised by what they refused to do. 5) Task setting for the team — convey the problem and goal (not dictate the solution), work with design and development, explain "why". 6) Launch and iterations — roll out the change, verify with an experiment, look at metrics, draw conclusions and repeat. 7) Stakeholder work — align interests of business, users, team, and leadership. Key: PM achieves results through influence, data, and arguments, not through power — formally they almost don't manage anyone.

A product manager does not need to code, and a technical education is not mandatory — but it all depends on the product. What is definitely needed: technical horizon — understand at a high level how the product is built, what API, databases, frontend and backend are, what is technically cheap and what is expensive; this is needed to speak with development in the same language, adequately assess timelines and realism, not be "deceived" and not demand the impossible. When tech background matters: for technical products — platforms, APIs, infrastructure, dev tools — a Technical PM with real technical depth is needed (see /research/pm/tech-pm); people often come there from development. When not critical: for most consumer and business products, understanding of users, market, metrics, and business matters more than code. What's actually more important than a technical degree: product thinking, ability to work with users and data, communication, business sense. SQL — separately: this is a growing requirement for almost all PMs (ability to get data yourself), and it's worth mastering regardless of background. Bottom line: PM is a role open to people without technical education, but requiring constant growth of technical horizon; for technical products the technical bar is higher.

Why entry is hard: pure Junior PM openings are few (per Zorky CRM sample 252 jobs are open, and almost all are Middle+), the profession is popular and competition high, and employers want to see proven product results which a newcomer by definition doesn't have — classic "no work without experience, no experience without work" trap. So people more often move into PM from adjacent roles rather than coming "off the street after courses". Working entry paths: 1) Transition from an adjacent role inside or near the product — analyst (especially product), Business Analyst, developer, designer, QA, marketer, support, Project Manager; you're already in the product team and gradually take on product tasks. 2) Domain expertise — deep knowledge of an industry (finance, logistics, medicine) + product skills = PM for a product in that industry. 3) Associate / Junior PM programmes at large companies — rare, competitive, but real. 4) Your own pet product / launch of something of your own — a proven result, even small. Skills roadmap: product thinking and frameworks (JTBD, discovery), working with metrics and unit economics, SQL, UX basics, custdev and interviews, prioritisation, Agile. Resources: books ("Inspired" Marty Cagan — classic, etc.), product management courses (ProductStar, Yandex, GoPractice — known for its simulator, Simulator from GoPractice), product communities. Main advice: not "learn to PM from scratch", but get into a product team in any role and grow into PM from inside, accumulating proven results.

252 active open Product Manager positions in the Zorky CRM sample. Important about this number: the vast majority are Middle and Senior; pure Junior positions are few (entry to the profession goes mainly by transition from adjacent roles). The real market is wider than exact-term search — the role is named "product manager", "product owner", "PM", "product owner". Geography: Russia / remote / Belarus. Sources: hh.ru, Habr Career, getmatch, LinkedIn, Telegram (product communities and job channels). Product Manager — in-demand and popular profession with sustained demand for experienced specialists and high competition for entry positions. NB: in the Zorky taxonomy there's also a separate "product" direction — some product roles may be counted there.

A Senior Product Manager is responsible for a large product or important direction and for its result. Strategic thinking: see the product on the horizon of quarters and years, understand market, competitors, trends, formulate strategy and vision, not just manage a backlog. Discovery mastery: deeply understand users, test hypotheses fast and cheap, distinguish real problem from noisy "wishes", don't let unnecessary things get built. Working with metrics: define the right product metrics (not easily-moved ones), compute unit economics, build a metric tree, work correctly with A/B tests, make decisions on data. Prioritisation and focus: tough about deciding what NOT to do; protect team focus from request flow; find the highest-impact levers. Influence without power: lead team, design, development and stakeholders via arguments, data, and trust; align conflicting interests of business and users; sell ideas to leadership. Business thinking: understand product and company economics, link product decisions to money. Technical horizon: assess feasibility and cost, speak with engineers as equals. UX sense: understand the user and design quality. Leadership: set culture and bar of the team, for Lead — develop Junior PMs. Communication: oral and written — primary tool. English — for the international market. The main value of a Senior — not "manage the product" but find what will bring the greatest result and bring it to measurable impact, owning the outcome.