Using HiringOrchestrator

Hosted job board

Publish a job and it appears on a public board at /o/your-workspace. The board collects applications automatically, and each posting is structured so search engines and aggregators can read it.

Publishing

publish_job_posting puts a role on the board; unpublish_job_posting removes it. Applications land directly against the job’s pipeline, deduped per candidate, ready to triage. Publishing is an act command with an undo handle.

Google for Jobs

Each posting emits complete JobPosting structured data (schema.org JSON-LD): title, description, hiring organization, location, posting and expiry dates, and, when present in your data, employment type and salary. Remote roles are marked as such with the location requirement search engines need. We publish what is in your job, and never fabricate salary or employment type.

Structured data makes a posting eligible for the Google for Jobs experience; eligibility is not a guarantee of placement, which Google decides. The same markup is what most aggregators parse.

The aggregator feed

A single XML feed of all live postings is served at /o/your-workspace/distribution/jobs.xml. It follows the widely-supported job-feed lineage, so a job network or board you register it with can ingest every open role from one URL. Apply links carry a source tag so you can see where applications came from.

Agent-driven distribution

  • distribute_posting turns on the channels for a live posting and returns an undo handle; withdraw_distribution reverses it; get_distribution reads the current state.
  • generate_social_post drafts share-ready copy for a published role, with a source-tagged link appended, so you can post it where your audience is.