Job Pool Web Topology
Domain architecture and system topology for the Job Pool open job-data ecosystem.
This document defines the web topology for Job Pool as a multi-surface platform: a consumer-facing job product, a live transparency and power-user layer, a canonical data infrastructure domain, and an ingestion/contributor operations domain.
Overview
The Job Pool ecosystem is a multi-layered platform designed to separate user experience, data infrastructure, and data generation pipelines into distinct, scalable domains.
This architecture enables high-conversion consumer experiences, transparent real-time data visibility, developer-grade open data access, and scalable ingestion and contributor workflows.
Rather than a single monolithic product, Job Pool operates as a connected system of specialized surfaces.
Terminology
The key words MUST, SHOULD, and MAY are used to indicate requirement strength within this document.
“Job Pool” refers to the full ecosystem. Individual domains represent bounded surfaces within that ecosystem.
Domain Inventory
| Domain | Layer | Primary Audience | Primary Function |
|---|---|---|---|
mewannajob.com |
Consumer Product | Job seekers | Job search, SEO pages, alerts, saved searches, and conversion flows |
jobpool.live |
Transparency & Power User | Analysts, contributors, power users | Bulk downloads, pooled scraper downloads, scraper docs, limited CRUD, contributor leaderboards |
jobdatapool.com |
Canonical Data Infrastructure | Developers and external data consumers | API, schemas, versioned datasets, and stable developer documentation |
datapool.work |
Ingestion & Contributor Operations | Contributors, maintainers, operators | Scraper orchestration, ingestion, review, moderation, and source submission workflows |
System Topology
The ecosystem is designed as a pipeline: work is created, structured, made transparent, and finally surfaced to job seekers.
Scrapers, pipelines, submissions, review tools, and contributor operations.
Canonical API, schemas, versioned datasets, and source-of-truth references.
Bulk downloads, pooled scraper outputs, scraper docs, limited CRUD, and leaderboards.
Job search, SEO entry points, saved searches, alerts, and conversion paths.
Domain Responsibilities
mewannajob.com — Consumer Product Layer
Primary Role: user acquisition and job search experience.
- Job search UI
- SEO landing pages
- Alerts and engagement flows
- Conversion funnel
Positioning: “Find jobs fast.”
Design principle: simple, fast, and focused on outcomes — not infrastructure.
jobpool.live — Transparency & Power User Layer
Primary Role: real-time visibility into the job data ecosystem.
- Bulk downloads
- Pooled scraper downloads
- Contributor leaderboards
- Limited CRUD operations
- Documentation on scrapers
Positioning: “See the live job data ecosystem.”
Design principle: expose the system without overwhelming the average user.
jobdatapool.com — Canonical Data Infrastructure
Primary Role: source of truth for structured job data.
- Public API via
api.jobdatapool.com - Bulk dataset distribution
- Schema definitions
- Versioned data access
- Developer documentation
Positioning: “The source of truth for job data.”
Design principle: stable, predictable, and developer-trusted.
datapool.work — Ingestion & Contributor Layer
Primary Role: data generation and system operations.
- Scraper orchestration
- Data ingestion pipelines
- Contributor submissions
- Review and moderation tools
Positioning: “Where job data gets built.”
Design principle: flexible, internal-first, and iteration-friendly.
User Journey Mapping
Consumer / Job Seeker
The normal user enters via mewannajob.com, searches and interacts with job listings,
and may optionally click “View live job feed” to visit jobpool.live.
Power User / Analyst
A power user enters via jobpool.live, accesses bulk data, scraper outputs,
and contributor leaderboards, then navigates to API or dataset resources on jobdatapool.com.
Developer
A developer enters via jobdatapool.com to consume APIs, datasets, schemas,
and technical documentation. They may navigate back to jobpool.live for live ecosystem context.
Contributor / Builder
A contributor engages through jobpool.live for visibility and credibility,
then contributes through datapool.work.
Cross-Domain Linking Strategy
Each domain reinforces the others through intentional navigation while preserving separate product psychology and user intent.
| Origin | Link Language | Destination | Purpose |
|---|---|---|---|
mewannajob.com |
View Live Data / See the Job Pool | jobpool.live |
Move curious users from job search into the transparency layer |
jobpool.live |
Access API / Datasets | jobdatapool.com |
Move technical users toward stable data infrastructure |
jobpool.live |
Contribute / Submit a Source | datapool.work |
Route contributors into ingestion and review workflows |
jobdatapool.com |
Explore Jobs | mewannajob.com |
Route non-technical users back to the consumer product |
Architectural Principles
Each domain serves a distinct purpose: UX, transparency, infrastructure, or operations.
.com signals stability, .live signals real-time visibility, and .work signals execution.
Users only see complexity when they opt into it; default paths remain simple.
Users, visibility, developers, contributors, and data pipelines reinforce one another.
Ecosystem Flywheel
Job Pool’s defensibility comes from the loop between consumer traffic, transparency, developer adoption, contributor activity, and increasing data quality.
Implementation Requirements
MUST: mewannajob.com remains the primary consumer-facing product surface.
MUST: jobpool.live remains the power-user and transparency layer for bulk downloads, pooled scraper downloads, scraper docs, limited CRUD, and contributor leaderboards.
MUST: jobdatapool.com remains the stable canonical data domain for APIs, schemas, datasets, and developer documentation.
SHOULD: datapool.work should be used for contributor and operational workflows that would clutter product-facing surfaces.
Avoid: Raw infrastructure details should not be primary navigation on mewannajob.com.
Avoid: jobdatapool.com should not be treated as a marketing-first landing page.
Strategic Outcome
This topology enables Job Pool to function as a consumer job platform, a real-time data transparency layer, a developer-facing data infrastructure platform, and a scalable data ingestion network.
Together, these form a defensible, multi-surface platform rather than a single product.