The live transparency layer for open job data.
Inspect scraper outputs, download reviewed datasets, and track contributor activity across the Job Pool ecosystem.
Download reviewed data, inspect staged submissions, or expand coverage.
Built for contributors, analysts, researchers, and power users who want to inspect, download, or improve the live job data pool.
Top Pool Seeders
Rankings are derived from staged submissions and matched against promoted records.
| Rank | Contributor | Staged Records | Promoted Records | Submissions | Corrections | Last Submission |
|---|---|---|---|---|---|---|
| Loading... | ||||||
The live transparency layer for Job Pool.
This domain exists for visibility: bulk outputs, scraper documentation, contributor metrics, and inspectable
operational signals. For canonical API, schema, dataset, and RFC documentation, see
jobdatapool.com.
Built for contributors, analysts, researchers, and power users
This surface is optimized for users who want inspectable data behavior, not just a search box.
Downloads, scraper docs, and contributor visibility
jobpool.live is where transparency workflows are exposed without overloading the
consumer-facing product.
Coordinated access over uncontrolled scraping
Access patterns here are designed to reduce redundant scraping pressure while preserving source provenance and operational restraint.
Topology and handoffs across the four domains.
The workflow is intentionally layered so each surface can stay clear: operations on
datapool.work, canonical contracts on jobdatapool.com, transparency on
jobpool.live, and consumer UX on mewannajob.com.
Preprod: unreviewed candidate records.
Prod: reviewed public dataset records.
Review: the promotion gate between staged and public data.
From ingestion to end-user discovery
datapool.work powers ingestion operations
Scraper orchestration, source submission, and contributor workflows run on the operations layer.
jobdatapool.com anchors canonical data contracts
APIs, schema definitions, versioned datasets, and RFCs live on the canonical data domain.
jobpool.live exposes transparency + tooling
Bulk downloads, scraper docs, and contributor leaderboards make the system behavior inspectable.
mewannajob.com serves the consumer journey
Job seekers get a focused search experience without infrastructure-first complexity.
Progressive disclosure without confusion
mewannajob.com to jobpool.live
Link language: “View live data” for users who want visibility beyond standard search UX.
jobpool.live to jobdatapool.com
Link language: “Access API / datasets” for stable developer-facing contracts.
jobpool.live to datapool.work
Link language: “Contribute / submit a source” for ingestion and moderation workflows.
jobdatapool.com back to mewannajob.com
Link language: “Explore jobs” to route non-technical users back to the consumer surface.
Architecture commitments for a shared job data layer.
These principles mirror the RFC series: separate surfaces by responsibility, preserve provenance, and make access coordinated enough to reduce redundant scraping pressure.
Consumer UX, transparency tooling, canonical data contracts, and contributor operations are intentionally split across domains.
Listings should carry source and observation metadata so both humans and AI systems can reason with less guesswork.
Open access does not imply uncontrolled redistribution; source policies, rate limits, and operational restraint still apply.
Common questions about the model.
A few concise answers for how this pool is intended to work today, and where its current boundaries are.
Each surface has a distinct role: mewannajob.com for consumer search,
jobpool.live for transparency, jobdatapool.com for canonical data contracts,
and datapool.work for contributor ops.
No. This project is open by default in documentation and access patterns, but source-specific terms, usage policies, and redistribution constraints still need to be respected.
Listings include source and observation metadata in the ingestion path, and transparency endpoints expose freshness signals so downstream tooling can rank and filter responsibly.
Start from this transparency layer, then move into datapool.work for source submission, review, and
contributor operations.