Skip to content

For hiring teams

Interview product management candidates with one link

Send a product management candidate one link. An AI interviewer asks about their real work, and you decide from the quoted scores.

Free while Aethel is in early access: one interview link, up to 25 interviews a month, about 3 of them with a video interviewer, the rest by voice. No card needed.

Hiring for product management

What makes this hard to screen

Product managers are often fluent talkers, so a phone screen can go well without telling you much. Claimed wins are hard to separate from the work of the team around them. You want evidence of how they decide what to build and what to drop.

Roles this field covers: product manager, technical product manager, product owner, program manager, growth product manager, head of product.

Listen for these in a transcript

  • Uses data and customer research to make a call, and names what was cut to make room.
  • Sets a success measure before launch and reports the measured result, good or bad.
  • Describes disagreeing with an engineer or executive and how they settled it with evidence.

Warning signs

  • Builds whatever the loudest customer or executive asked for.
  • Has no success measure and cannot say why a launch fell short.
  • Takes every disagreement up the chain instead of working it out.

How it works

How to interview with a link

  1. Step 1: Create a link for the role

    Choose the field "Product management", the level, and a specialty such as product manager or technical product manager.

  2. Step 2: Send it to your candidates

    Share it wherever you already find product management candidates.

  3. Step 3: Candidates interview on their own time

    It takes about 15 minutes, and they know the interviewer is an AI.

  4. Step 4: Review and decide

    Mark each one Advance, Not a fit, or Undecided.

The interview

What the interviewer covers

It follows up on each answer and picks the product management topics that fit the role.

  • A product decision that was hard to make and how it turned out
  • Finding the customer problem worth solving before deciding what to build
  • Cutting scope to hit a date
  • A launch that underperformed and what they learned
  • Choosing the metrics that define success
  • Turning customer feedback into a roadmap
  • Saying no to a powerful stakeholder
  • Working with engineering on a technical trade-off

What the scoring looks for

Strong work: the candidate uses evidence (data and customer research) to decide, names the trade-off and what was cut, sets a success measure before launch, and reports the measured result honestly.

Warning signs: the candidate builds whatever the loudest customer or executive asks for, has no success measure, cannot explain why a launch failed, or takes every disagreement to someone more senior. The scoring AI is told to score an area below 60 when its answers show one of these.

Your questions

Sample must-ask questions

Up to three per link. The interviewer is told to ask each one as written, and every result shows whether it was asked word for word, asked in other words, or not asked. Examples:

  1. Tell me about a feature you decided not to build. How did you make that call, and who disagreed?
  2. Describe a launch that missed its goal. What did you learn, and what did you change?
  3. How do you choose the metric that tells you a feature worked?

Starter templates

Start from a common role

Start a link from one of these and edit anything.

  • Product manager

    Focus: Deciding what to build, writing clear requirements, working with engineering and design, measuring results

  • Product operations manager

    Focus: Planning and launch processes, product data and tools, routing customer feedback to the right teams

  • Technical product manager

    Focus: APIs and platform products, technical trade-offs, planning work with engineering teams

  • Technical program manager

    Focus: Running programs across several teams, dependencies and risks, schedules, status updates for leaders

Results

What you see for each candidate

  • The full transcript

    Every answer, in order.

  • “Not enough evidence”

    Shown instead of a guess, never as a low score.

  • Your decision and private notes

    Only your team sees them.

The four scored areas

Each out of 100, with quotes.

Product judgment (evidence, options, trade-offs)
Counts as evidence when the candidate describes a specific product problem or decision: the evidence they used, the options, the trade-off they made, or the measured result.
Prioritization and strategy (goals, metrics, roadmaps, scope)
Counts as evidence when the candidate describes how they decided what to build and in what order: goals, metrics, roadmaps, scope cuts, customer research or market reasoning.
Communication (specs, updates, getting alignment)
Counts as evidence when the candidate describes explaining product decisions to other people: specs, roadmaps, launch notes, presentations, or getting a group aligned on a decision. Answers that respond to the question asked, in a clear order, with a concrete example, also count, but only up to 80 on their own. Grammar, word choice and fluency are never judged.
Stakeholder collaboration (engineering, design, customers, saying no)
Counts as evidence when the candidate describes working with engineering, design, sales, customers or leadership, including resolving disagreement or saying no. Saying "we" is not, by itself, collaboration evidence.

Aethel never scores faces, voices or accents, and does not verify degrees, licenses or work history. How Aethel uses AI

FAQ

Questions hiring teams ask

Can it tell a growth PM from a platform PM?

Put the specialty and the product area on the link. A growth link draws on funnels and experiments; a technical PM link draws on APIs, platforms and engineering trade-offs.

Does it give a product case or a whiteboard exercise?

No. It asks about decisions the candidate already made in real jobs. If you run product cases, keep them for a later round.

Can we hear how they say no to a stakeholder?

Saying no to a powerful stakeholder is one of the topics it can choose. Make it a must-ask question if you want it in every interview for the role.

See also the questions companies ask and the pricing page.

Send your first product management interview link

Want to show candidates what to expect? What the interview covers for product managers