The first serious version of Mokchi is heavily biased toward Product Design.
That’s intentional.
It’s the area where I can look at a question and know whether it feels plausible. I can tell when a seniority probe is useful versus performative. I can tell when feedback about ownership, product judgment, or impact is actually meaningful.
That makes Product Design a good place to establish quality.
But the underlying system shouldn’t be a designer-only tool.
Someone interviewing for an administrative role shouldn’t be evaluated on product strategy.
Someone preparing for sales should be tested on a completely different set of signals.
Someone interviewing for a management role should face questions around leadership, judgment, and people decisions.
So the product architecture is moving toward a simpler idea:
Understand the role first. Build the interview second.
Product Design becomes our first deeply curated specialty.
Not the boundary of the product.