What this guide helps with
Pay is useful only when the source provides enough detail. puntWork separates source pay values from missing or unsafe ranges, and labels sampled market evidence when a page does not cover every active listing.
Decision guides
How to read source pay values, salary ranges, missing pay, and sampled salary coverage without over-trusting a single listing.
Pay is useful only when the source provides enough detail. puntWork separates source pay values from missing or unsafe ranges, and labels sampled market evidence when a page does not cover every active listing.
Look for the pay chip, the partner source, the contract type, and whether the final application page repeats the same amount. If pay is missing, puntWork should say that instead of inventing a number.
Compare several active listings in the same city or category, then treat the range as a decision signal rather than a guarantee. Final pay can depend on shift pattern, seniority, benefits, and employer rules.
These labels are the bridge between job listings and the decision guides. They tell you how strong the underlying evidence is before you act on it.
What partner feeds, sampled listings, aggregate counts, and job-source facts mean on puntWork pages.
How to use inventory deltas between nearby cities and regions when the current page is too narrow.
A practical checklist for checking known, missing, and stale job facts before leaving puntWork for a partner application page.
How puntWork uses feed refreshes, dateModified, datePosted, and validThrough signals to keep Belgian job pages current.
How to interpret Dutch, French, English, and bilingual signals in Belgian job listings without over-reading sampled text.
How to compare interim, temporary, fixed-term, permanent, and recruitment-agency listings on puntWork.
How puntWork reads remote, hybrid, and telework wording in Belgian job listings.
What happens when a candidate clicks Apply, why puntWork uses a redirect, and what to verify on the partner page.