An HTTPS JSON feed supplied by the employer with stable IDs, current records, an operational contact, and an explicit rights attestation.
Employer and recruiter onboarding
Job feed and submission contract
Submit authorized vacancies to PrepKloud with clear provenance, canonical application links, expiry dates, and privacy controls.
Supported source paths
Support means the source can be reviewed under this contract; it does not mean automatic approval or a provider partnership.
Employer-authorized Greenhouse, Lever, Ashby, or Workable identifiers using canonical hosted and apply URLs.
Permitted sources such as USAJOBS, or employer-provided JobPosting JSON-LD with express ingestion permission.
A manually reviewed vacancy linked to the employer or authorized ATS. Agency recruiters must confirm authority to advertise it.
Required job fields
Every approved record must be factual, current, attributable, removable, and safe to redirect to its original application destination.
- Identity: stable publisher ID, title, employer, location, workplace type, and employment type.
- Provenance: source type, source name, source system, employer website, and private operational contact.
- Dates: ISO 8601 posting, ingestion, and expiry timestamps. Expired jobs are excluded.
- Links: HTTPS canonical job, source, and application URLs controlled or authorized by the publisher.
- Discovery: concise skills and optional PrepKloud certification/path identifiers used only for relevance.
- Verification: employer-submitted, domain-verified, and public-contact-consent flags.
Rights, privacy, and public contact
The publisher must be the employer or have authority to distribute the vacancy and grant PrepKloud the limited right to review and display it.
Business email is used for operational review and is not displayed unless separate, explicit public-display consent is recorded.
Do not submit resumes, applicant data, passwords, access tokens, private keys, protected-class targeting, or unnecessary personal data.
A recruiter can withdraw public-email consent or request correction/removal at any time through jobs@prepkloud.com.
Deduplication, expiry, and takedowns
PrepKloud normalizes canonical URLs, removes common tracking parameters, merges duplicates conservatively, and prefers employer-controlled destinations.
- Closed or expired records must be removed from a full feed or explicitly marked for removal in a delta feed.
- PrepKloud may pause or remove a record whenever authority, validity, accuracy, or candidate safety is uncertain.
- Rights holders can request correction or takedown by emailing jobs@prepkloud.com with the canonical URL and proof of authority.
No restricted-board scraping
This contract never authorizes extraction from unrelated employers or restricted job boards.
PrepKloud does not scrape or ingest LinkedIn, Indeed, Glassdoor, Naukri, or Dice listings. Those providers appear only as clearly labeled, user-initiated outbound search destinations and do not imply partnership or endorsement.
Planned secure ingestion
The current static MVP creates a structured email draft for manual review and does not write recruiter submissions to Firestore.
A future backend can use Azure Functions for authenticated intake, moderation, rate limiting, audit events, scheduled feed processing, deduplication, and expiry. Connector credentials will remain in Azure Key Vault and be accessed through managed identity—not embedded in browser JavaScript.