How it works
Nobody moves until both sides have seen enough to decide.
One mechanism, described once. What a company does, what a candidate does, and what the product refuses to do in between.
The mechanism
The four steps
01 A role is postedSalary range is mandatory. Five hard requirements at most, kept apart from the nice-to-haves. A named person owns the replies and sets the reply window. Posting is free.
02 The pool is queriedCategory, seniority, skills, location, salary band. The database returns no names. Every claim on a profile carries the register it came from and the date it was confirmed.
03 A request is sent, and answeredFrom a named person, with the pay attached, to somebody who never applied. They read the role and accept or decline. Nothing has been billed at any point up to here.
04 The meeting is agreed, and billedOne charge each time a candidate accepts a meeting, priced by how scarce the role is: €800, €1,500 or €2,500. Nothing else is billed, at any point, in either direction.
Symmetry
What each side is looking at.
The same event, seen from two chairs. Neither side is asked to act on less than the other.
The company sees while it searches
The full profile, once they acceptRole family, seniority, skills, location, salary band while you search. Name, employer and photograph become visible only once the candidate accepts your request.
Claims with provenanceEach one carries its source and its date. Nothing is self-asserted and left unmarked.
Its own rules, appliedThe requirements you published, checked against verified facts. You can read the result line by line.
Every outcomeWho accepted, who declined, and why. Including the ones you would rather not know.
The candidate sees before deciding
The whole role, before applyingSalary, the hard requirements, who they would report to, and how long the company takes to reply.
A named personNot an account, not a sequence. Somebody at the company, with the pay already attached.
Their own fitWhich requirements they meet and which they do not, before spending an evening on it.
An answer, alwaysWith the reason attached. It is a rule in the product, not a promise on a page.
Guarantees
The promises the product enforces.
These are not policies somebody could quietly stop honouring. Each one is a constraint in the software.
A reply window, capped at ten daysThe company chooses it and publishes it. Seven days is the suggested default. The product counts down in public and the company cannot silently let it lapse.
An answer for everybodyA decline names the requirement that was missed. Silence is not an available outcome.
No approach without consentNobody inside the network is written to unless they accepted the request first.
Salary on every listingA role cannot be published without a range. There is no exception, for any customer, in any market.
Five hard requirements, no moreIf everything is essential, nothing is. The cap is what makes roles comparable to each other.
One pipeline, no exportYour whole hiring process runs here. There is no applicant tracking system to buy, plug in, or deliver to.
Nobody applies without seeing the pay. Nobody is approached without agreeing to it. Nobody pays until both sides have said yes.
That is the whole design, and it is the only reason a two-sided network holds together.