Post the role, list your skills, and see the overlap before anyone signs anything. If a term still won't budge, an onchain court settles it - not another email thread.
Give it a title, describe the work in plain terms, and list the skills that actually matter. That skill list is what the matching in Clause III reads.
Loading...
List your skills the same plain way, link your résumé, and say what you'd expect to be paid. Nothing here is scored or ranked — it's just what gets compared against open roles.
Loading...
The match score is a plain skill overlap: shared skills divided by the total distinct skills across both lists, computed on the server. No hidden weighting — you can read the same list the algorithm reads.
Loading...
Choose any posted role and candidate to test the dispute flow, even when their pay figures currently match.
Skills can line up while a number still doesn't — salary, start date, scope. When that happens, either side can raise a dispute on that specific term. It's filed with GenLayer's Internet Court: a random panel of AI validators reviews the two positions and returns a ruling, usually within minutes, without either side needing to agree first.