Tech hiring Product, design & quality

Hire product managers who can say no.

A product manager decides what gets built, for whom and in what order, then works with design and engineering until it ships and the result is measured. We shortlist product managers assessed on how they reason about users, evidence and trade-offs, not on how many frameworks they can name.

01 The role

What a product manager does, and what they ship.

A product manager owns the question of what to build next. They talk to customers, study usage data and the market, pick the problem most worth solving, and write it down clearly enough for designers and engineers to act on. Then they stay with the work through delivery, launch and the numbers afterwards.

The job is hard because every input conflicts. Sales wants the feature that closes one deal, engineering wants to pay down debt, the founder has a new idea each week, and the data is incomplete. A product manager has no authority over any of them. They have to choose, explain the choice and keep people working towards it.

This is not project management. A project manager makes sure agreed work lands on time and on budget; a product manager is accountable for whether it was the right work. Current practice favours continuous discovery, roadmaps built around outcomes instead of feature lists, and enough fluency in SQL and analytics tools to check a claim without waiting for an analyst.

What they ship

  1. Product strategy and an outcome-based roadmap
  2. Problem statements and product requirement documents
  3. A prioritised backlog with the reasoning written down
  4. Customer interview notes and discovery findings
  5. Success metrics and a launch plan for each release
  6. Experiment designs and post-launch reviews
  7. Pricing, packaging and go-to-market input

02 Skills and stack

What product managers work with, and what is optional.

The tools here are interchangeable and quickly learned. What separates product managers is the first column, and the kind of product they have done it on: B2B or consumer, early or mature, regulated or not.

Core

The role cannot be done without these.

  • Customer discovery and user interviews
  • Prioritisation and trade-off decisions
  • Product strategy and roadmapping
  • Clear writing: specs, PRDs, decision records
  • Metrics and product analytics
  • Influence without authority
  • Working fluency with engineering and design

Tooling

Varies from team to team.

  • Jira or Linear
  • Productboard or Aha!
  • Notion or Confluence
  • Mixpanel, Amplitude or PostHog
  • Google Analytics 4
  • SQL with Looker or Metabase
  • Figma and FigJam, or Miro
  • Hotjar or Microsoft Clarity
  • LaunchDarkly or Statsig for feature flags

Adjacent

Useful, not required.

  • A/B testing and experiment design
  • Pricing and unit economics
  • Go-to-market and product marketing
  • API and system design literacy
  • Regulatory awareness: payments, health, data privacy
  • Scrum and Kanban delivery
  • Evaluating AI features

03 When to hire one

Signs you need a product manager, and signs you need someone else.

The wrong hire for the problem is an expensive way to learn what the problem was. Check your situation against both columns.

Hire a product manager when

  • The founder is still the product manager

    It worked with five engineers. Now decisions queue behind one calendar, and the team builds whatever was said most recently.

  • Engineers ship on time and usage does not move

    Delivery is healthy; outcomes are not. Somebody needs to own why features are chosen and whether they worked.

  • The roadmap is a list of customer requests

    Every large account gets its feature and the product grows sideways. A product manager finds the common problem underneath the requests.

  • You are adding a second product or market

    One person can no longer hold the whole picture. Each product line needs someone accountable for its users and its numbers.

  • Design and engineering disagree and nobody decides

    Debates about scope run for weeks. A product manager makes the call, writes down why and moves on.

Look elsewhere when

  • The scope is fixed and you need it delivered by a date

    That is delivery, not discovery. A project manager plans it, tracks it and manages the risks; a product manager would keep reopening the scope.

    Hire project managers
  • You have only three or four engineers

    At that size the founder should stay close to users. Another engineer usually adds more than a layer between the founder and the team.

    Hire software developers
  • You mostly need usage numbers and dashboards

    If decisions are being made well and only the evidence is missing, hire the person who produces the evidence.

    Hire data analysts
  • The problem is that the interface confuses people

    A product manager will diagnose it and then ask for a designer. Hire the designer.

    Hire designers
  • You have an idea and no team to build it

    A product manager with nobody to build produces a strategy document. A dedicated team gives you product, design and engineering together.

    See dedicated teams

04 How we assess

How we assess product managers, before you meet one.

A CV says what someone claims. We test what they can do, then send you the evidence with the shortlist.

  1. Stage 1

    Profile review

    We look for products the candidate actually shaped: what they owned, what was decided on their recommendation and what the result was. We discount titles, certificates and CVs that list ceremonies run instead of outcomes reached.

  2. Stage 2

    Practical exercise

    For product roles the practical exercises matter most: a product problem to break down, in which the candidate identifies the user, chooses what to prioritise, defines how success would be measured and says what they would leave out.

  3. Stage 3

    Conversation with our team

    Our team asks the candidate to talk through one product decision that went right and one that went wrong. We probe how they gathered evidence, who disagreed and how that was handled, and how well they understood what engineers said was hard.

  4. Stage 4

    Review and levelling

    Reviewers score accuracy, speed, problem-solving, communication and teamwork, then assign a level using our product framework. For product managers the notes record the scope the person has owned: a feature, a product area or a whole product line.

  5. Then

    Your shortlist

    Assessed candidates, with notes and scores.

The engine

Evalia

Assessments run on Evalia, the assessment platform we built ourselves. Across the ProDevs network, more than 100,000 assessments have been completed.

The levels we assign are public. Read the product framework, or see how a hire runs from brief to offer.

05 Seniority

How much can you hand over? It depends on the level.

The title on a CV tells you little. What matters is how much a product manager can be handed without someone checking each step.

Associate

Owns a feature

  • Writes clear specs and tickets for work someone else has prioritised
  • Runs customer interviews and reports what was said, not what was hoped
  • Follows a release through to launch and checks the metric afterwards
  • Needs guidance on prioritisation and on handling senior stakeholders

Product manager

Owns a product area

  • Runs discovery and decides what the squad builds next, with reasons
  • Sets success metrics before launch and reports honestly against them
  • Says no to stakeholders and keeps the relationship
  • Works out with engineers what to cut when the estimate is too large

Senior

Owns a product line and its strategy

  • Sets strategy for a product and ties it to commercial targets
  • Balances several teams’ roadmaps and resolves conflicts between them
  • Recommends pricing, packaging and market entry to leadership
  • Coaches other product managers and raises the standard of their specs

06 Interview questions

Seven questions, worth asking a product manager.

For your own interviews, after ours. Each question comes with what a strong answer tends to show.

  1. Tell me about a feature you decided not to build. How did you make the case?

    A good answer shows: A real request from a real stakeholder, the evidence they used, and how the conversation went. A candidate who cannot recall saying no has been taking orders, whatever the title says.

  2. Describe something you shipped that failed. How did you know, and what happened next?

    A good answer shows: A metric defined in advance, a result that missed it and a decision to change or remove the feature. Weak answers redefine success afterwards or blame execution.

  3. You have capacity for one of three projects this quarter. Talk me through choosing.

    A good answer shows: They ask about goals, evidence and cost before reaching for a scoring method. RICE or similar is fine as an aid; reciting it as the answer is not. Listen for how they treat uncertainty.

  4. How do you find out what customers need, as opposed to what they ask for?

    A good answer shows: Interviews about past behaviour instead of hypothetical wishes, watching people use the product, and checking the story against usage data. “We send a survey” on its own is thin.

  5. An engineer says the feature will take three times longer than planned. What now?

    A good answer shows: Curiosity about why, then a search for a smaller version that still delivers the outcome, and early honesty with stakeholders about the date. Pushing the team to work harder is the answer to worry about.

  6. Which metric would you judge this product by, and what could make it misleading?

    A good answer shows: A metric tied to user value instead of activity, plus awareness of how it can be gamed or distorted by customer mix and seasonality. The second half of the question is where experienced candidates separate themselves.

  7. How technical do you need to be to do this job well?

    A good answer shows: Enough to follow an architecture discussion, read an API document and query data, without telling engineers how to build. Either extreme, “I leave all that to them” or designing the database, is a warning.

07 Ways to engage

Four ways to bring a product manager in.

A permanent hire is the usual route, not the only one. Choose by how long the work lasts and who should employ the person.

Placement fee, of first-year salary. One-time.
10–15%
Replacement guarantee on direct hires.
2 weeks
To a first shortlist, for most roles.
48h
  • Direct hire

    A permanent employee on your contract and your payroll. One-time placement fee of 10–15% of first-year salary.

    Tech hiring
  • Dedicated team

    A product manager inside a team we assemble and run for you: product, design and engineering on your roadmap, for a monthly retainer.

    Dedicated teams
  • Outsourcing & payroll

    A full-time person in a country where you have no legal entity. ProDevs employs and pays them: 20% of salary if we find the person for you, or 5% of salary, capped at $500 a month, for payroll and compliance on someone you have already chosen.

    Outsourcing
  • Freelance project

    A defined piece of work with a clear end. You pay the agreed price per milestone through escrow, plus a 5% client fee. Free to post.

    Freelancers

08 Around the role

A product manager is one seat. These are the others.

A product manager sits at the centre of a squad with a designer and a group of engineers, and reports to a head of product or the founder. They have no line authority over the people whose work they direct, so the role runs on trust and clear reasoning.

Product designer
Runs discovery together and agrees which problem a design is solving before it is drawn.
Engineering lead
Trades scope against time and hears early what is technically risky.
Data analyst
Defines success metrics before launch and reads the results after.
Project manager
Hands over agreed scope for delivery planning on larger programmes.
Sales and customer success
Collects requests, and explains what is and is not coming, and why.

09 Client testimonials

Hear it first-hand, from companies that hired.

Founders, operators and executives describe working with ProDevs, in their own words.

10 Questions

Hiring product managers, answered.

Something else? Book a call (opens in a new tab) and ask us directly.

  • What is the difference between a product manager and a project manager?

    A product manager decides what should be built and why, and is judged on whether users and the business benefit. A project manager makes sure an agreed piece of work is delivered on time, within budget and to scope. Small teams often ask one person to do both; the skills overlap less than the titles suggest.

  • When does a startup need its first product manager?

    Usually when the founder can no longer talk to customers, set priorities and answer the team’s questions in the same week. That tends to arrive with a second engineering squad or a second product. Before that point, a founder who stays close to users is normally the better product manager.

  • Does a product manager need a technical background?

    Not a coding background, but technical fluency. They should follow how the system fits together, understand why an estimate is large, read API documentation and pull basic data themselves. For developer tools, infrastructure or AI products, ask for deeper technical experience in the brief so it is assessed.

  • Should a product manager have experience in my industry?

    It helps most in regulated fields such as payments, lending and health, where rules shape what can be built. Elsewhere, the ability to learn a domain quickly from customers matters more than years spent in it. Tell us which you need and we shortlist accordingly.

  • How do you assess product managers?

    In four stages: a review of the products the candidate has shaped, a test with practical exercises on a product problem, an in-depth conversation with our team, and a joint review in which a level is assigned against our public product framework. Assessments run on Evalia, the platform we built ourselves.

  • How long does hiring a product manager take, and what does it cost?

    For most roles you see a first shortlist within 48 hours of agreeing the brief, and most companies find their hire within two to three weeks. A direct hire carries a one-time placement fee of 10–15% of first-year salary and a two-week replacement guarantee.

Talk to ProDevs

Tell us about the role.

Tell us the level and the stack. We will tell you how quickly we can put assessed product managers in front of you.

Project work

Need it for a project instead?

Not every job needs a full-time hire. Describe the work, get proposals from vetted freelance product managers, and pay per milestone through escrow. Free to post.