We assess the people who build the product
Six roles, one standard. We only cover work where the job is deciding under ambiguity and the brief always arrives wrong, so backend, data and infrastructure are out of scope.
- 15 min
Product Designer
A portfolio shows the final screens. It never shows what the brief said before they fixed it, what they argued for and lost, or what they cut when the deadline moved.
See the assessment - 15 min
Product Manager
A CV lists shipped features. It never shows which ones they argued against, what they killed, or whether the roadmap was theirs or handed to them.
See the assessment - 15 min
UX Researcher
A research portfolio shows tidy findings. It never shows the studies that were badly framed, or whether the recommendation survived contact with the business.
See the assessment - 15 min
Frontend Engineer
A coding test shows whether they can write the function. It never shows whether they should have.
See the assessment - 15 min
Design Engineer
A GitHub profile shows what they merged. It never shows what they talked the team out of.
See the assessment - 15 min
UX Writer
A writing sample shows the final sentence. It never shows what the screen looked like before, or what they refused to paper over.
See the assessment
Before you pick one
No, and it isn't on the roadmap either. Each role has its own bank of situations written for the decisions that job makes: a product manager is asked about a deal lost to a missing feature, a UX writer about an error message covering for a broken flow. Running someone through another role's situations would produce a number, and the number wouldn't mean anything.
Pick by what the person will decide. If they own what gets built and why, that's the product manager assessment, whatever you call the job. If they live between design and engineering deciding when a component should exist, that's design engineer. Titles vary by company; the decisions don't.
Only where the job is deciding under ambiguity with a brief that arrives wrong. That limit is permanent. Backend, data and infrastructure stay out because their hard part can be verified other ways. If a role you hire for belongs inside that limit and isn't here, tell us: the pages for roles we haven't built yet carry a direct line for exactly that.
You have a role open right now
Request access and your first candidate is on us. Setting up the role takes about ninety seconds.