CAREER LIBRARY

Questions to ask
of a role.

Static editorial starting points for reading a role. This public page does not inspect live postings, outcomes or your Career Twin.

EXAMPLE REVIEW PROMPTS · PRODUCT MANAGER
Roadmap ownership

Check whether the posting asks for prioritisation decisions and what evidence could support them.

SQL

Check whether SQL is required, preferred or absent in the exact posting.

Experimentation

Check whether the role asks for designing, interpreting or acting on experiments.

Regulated domain

Check whether domain experience is a must-have, a preference or not mentioned.

Example review prompts, not measured requirement frequency. Load a real posting for its current requirements.

WHAT A GUIDE HOLDS

Four editorial starting points.

The guides are static. They are not fed by the vacancy catalogue, outcomes or a candidate profile.

THE SCORE

Operate the engine.

A fit score you cannot take apart is a number somebody is asking you to trust. This one comes apart.

Example
PLAYABLE29 · SCORE-COMPUTING

Take a fact away.

Five requirements on the left, one candidate’s facts on the right, links drawn between them. Remove any fact and its link retracts, the score recomputes, and the requirement it served goes unmatched with a label saying so.

FIT92every fact kept

No fact supports “SQL”. That link stays undrawn, and the score says so rather than rounding up.

Range on this example: 58 to 92, depending on what you remove. Click a fact to take the controls.

This control is an example of how linked evidence affects a score. It does not know who you are. Personal assessment requires one selected posting and candidate-confirmed facts.

In this example, no fact supports SQL. The link stays undrawn and the example score stays lower.

  • Example links are visible
  • An unsupported example stays unmatched
  • No personal score on this public page

Where the facts come from is on how it works.

SALARY

Salary evidence, when available.

SALARY LANDING · PRODUCT MANAGER

No salary distribution is connected to this public guide. The empty state avoids inventing one.

A selected posting may state a range. This public guide does not turn one range into a market distribution or a personal salary position.

Load a real posting to compare its stated pay with your own guardrails.

  • No salary dataset attached
  • No city or seniority distribution inferred
  • Missing measurements stay empty

THE TWO NUMBERS

Neither is measured here.

This static guide has no runtime catalogue or candidate population data.

DEMAND · WHAT THE POSTINGS ASK FOR
Postings naming SQLRequires a measured, defined source set.
Postings naming experimentationRequires the same measured source set.
Postings naming a regulated domainRequires the same measured source set.

NOT_MEASURED on this public route. No requirement-frequency series is connected.

SUPPLY · WHAT CANDIDATES HOLD

A candidate-supply percentage would require a defined, observed population. No such source is connected, so no comparison is drawn.

  • No second series
  • No purchased dataset standing in for one

NOT_MEASURED. This public guide has no observed candidate population.

DUPLICATE RECORDS

A source check, not a live count.

This guide does not inspect provider records or infer that a role is filled.

DUPLICATE RECORDS · PRODUCT MANAGER
Potential duplicate recordsRequires imported provider records.
Posting lifecycleRequires a measured observation window.

No provider-record series is connected to this public guide. Matching company, title and location is only a deduplication rule.

This public guide does not canonicalize or count records at runtime. The product can merge matching company, title and location records, but it does not yet identify already-filled roles or infer ghosts.

No lifecycle measurement is connected. The missing series stays empty.

  • Static deduplication rule explained
  • No filled-role or ghost inference
  • No rate quoted before there is a cycle to count

THE GUIDES

Six static editorial starting points.

These public guides have no candidate context. For a personal assessment, load a real posting and compare it with candidate-confirmed history.