Compass: start from a role

Compass runs the opposite way round from the bench. Instead of asking what suits this consultant, it starts from a role and asks who fits it — which is how a desk thinks when a client asks whether you cover something.

The families are learned, not listed

The role families down the side come from the corpus itself rather than a list somebody typed. When enough postings use a title, it becomes a role — so a role the market has just invented appears here without anybody adding it.

Level is kept separate

Java Developer, Java Lead and Java Architect are one family at three levels. Keeping seniority separate from the family lets you see the whole area at once and then narrow, rather than treating three levels as three unrelated markets.

Fit, on the row

Press a posting to see who fits that specific requirement, with the reasons and the gaps beside each name — and submit from there. You do not have to go and find the consultant first.

Notice how much is not stated. The rate range here rests on ten postings out of two thousand, and the arrangement is unstated on most of them. MetaOpus shows the size of the evidence beside the number rather than averaging silence into a figure that looks certain.

Rebuild taxonomy reclassifies the corpus and promotes recurring new titles into roles. It runs automatically after ingestion; the button is for when you want it now.