Zero ghost jobs.
By construction.
Stale listings, fake roles, and hidden pay aren't policed here — they're structurally impossible. Every number below is computed from the same database that runs the board, refreshed hourly. Nothing is copywritten.
The receipts
Computed live · refreshed hourlyCollecting — this median publishes once at least 5 listings have completed a full publish → take-down cycle. No estimates in the meantime.
How we know this: Median of the publish and take-down timestamps stamped on every listing's distribution record. When a role is filled or closed, removal from the board happens in the same action — this is how long that takes, recomputed hourly.
No live listings at this instant — this percentage is computed over live listings only, never carried over from history.
How we know this: Every live listing is joined to its employer's current verification status at query time. Publishing to this board requires organization verification, so the target is 100% — always.
No live listings at this instant — this percentage is computed over live listings only, never carried over from history.
How we know this: Counted from the salary-range fields on every live listing. A role cannot be published to this board without a pay range; listings that predate the gate can briefly hold this under 100% until they cycle out.
Early days — we publish raw counts once the board holds 25+ concurrent roles. Integrity comes first; volume follows. Never padded, never estimated.
How we know this: Counted with the exact query the public board renders from — published, open, not deleted. If a role is in this number, it is on the board this second.
Early days — we publish raw counts once the board holds 25+ concurrent roles. Integrity comes first; volume follows. Never padded, never estimated.
How we know this: Counted server-side from application records created through IQMela's own apply flows this calendar month (UTC) — ground-truth database rows, not client-side analytics.
Enforced by infrastructure, not policy
Most boards ask employers to keep listings honest. IQMela's publishing pipeline makes the dishonest states unrepresentable.
Verified employers only
An organization cannot publish to this board until it passes verification. There is no paid badge and no self-declared checkmark — the gate sits inside the publish action itself.
Filled means gone
Closing or filling a role triggers the take-down in the same action that changes its status, and both timestamps are recorded. The median above is measured from those records — it is the enforcement, audited.
Pay on every listing
The publish flow rejects any role without a salary range before it can reach the board. The show-pay percentage above is the live measurement of that gate.
What the verified mark means
When a job card or job page carries the verified mark, the employer behind it has passed IQMela's organization verification — a legal-entity check performed by the platform, not a label employers give themselves and not something that can be bought.
The mark is derived from the employer's currentverification status every time a page renders. It is never stored on the listing, so it cannot go stale — and if an organization's verification lapses, the mark disappears from every one of its listings automatically.
The proof of an honest board is the board.
Browse live roles →Every figure on this page is recomputed from the production database when the page regenerates (at most hourly). Where the data is too thin to support a claim, we say so instead of showing a number.