CronJobs publishing standards

Editorial and research policy

This policy explains who publishes CronJobs guides and reports, how claims are checked, where automation can assist, why the content exists, and how substantive updates and corrections are handled.

Effective and last reviewed September 1, 2026

Who creates and reviews the content?

Guides, product explanations, and original-data reports are published by the CronJobs engineering team. CronJobs is operated by a small team of working software engineers who build and maintain the job-ingestion pipeline, Discord product, and public site. The organization is the author when work reflects shared product implementation, data operations, and editorial review rather than one person’s independent opinion.

Article pages identify the CronJobs engineering team in the visible byline and link to the About page. CronJobs is separately identified as the publisher in structured data.

How are guides and product claims produced?

  • Product claims: commands, prices, access rules, schedules, storage behavior, and feature boundaries are checked against current source code, configuration, public product behavior, or an explicit production contract.
  • External facts: comparisons and career guides prefer official documentation, maintained community pages, government sources, and other primary sources. The page states an observation or review date when a source can change.
  • Original data: CronJobs jobs reports use aggregate, read-only queries over the eligible production inventory. Each published snapshot records its exact observation time, methodology version, definitions, thresholds, limitations, and immutable downloads.
  • Recommendations: advice is labeled as guidance rather than universal outcome evidence. A recommendation does not become a numeric claim unless a dated source supports it.
  • Release checks: the static site runs automated checks for canonicals, titles, descriptions, structured data, sitemap membership, important evidence links, and selected product boundaries before deployment.

How can automation and AI assist?

Automation and AI can assist with research organization, drafting, consistency checks, code changes, data formatting, and test generation. They do not replace source verification. Before publication, factual product claims are compared with current implementation or production evidence, numerical claims require a date and source, and generated site output must pass the same build and regression checks as hand-written changes.

CronJobs does not publish invented quotations, fabricated experience, synthetic user testimonials, or unsupported market statistics. When the available evidence cannot support a conclusion, the page should state the limitation instead of filling the gap with a confident estimate.

Why does CronJobs publish this content?

The purpose is to help U.S. software engineers evaluate job-search options, understand the CronJobs product, and use dated evidence without mistaking one inventory for the entire labor market. Search visibility and AI citations are useful distribution outcomes, but they do not justify creating unrelated pages, multiplying near-duplicate answers, or changing a conclusion beyond what the evidence supports.

How are freshness and dates handled?

A visible “last updated” or “reviewed” date advances only after a substantive check or change. Substantive work includes rechecking sources, correcting a factual boundary, revising the method, adding new evidence, or materially improving the answer. Formatting-only edits, metadata-only edits, and routine deployments do not make old evidence new.

Dated data snapshots remain immutable. A later observation receives a new dated report; the mutable manifest and latest pointer identify the newest completed snapshot without rewriting the earlier record.

How are corrections handled?

Material errors are corrected where they appear. If a change affects a published dataset’s definitions or queries, CronJobs advances the methodology version or publishes a documented replacement rather than silently rewriting the historical observation. Pages keep qualified language when an issue is uncertain, and source removals or closures are recorded when they change a recommendation.

To report a factual error, use the CronJobs Discord and contact an admin with the page URL, disputed statement, and supporting source. Privacy or deletion requests follow the process in the Privacy Policy.

What commercial relationships are disclosed?

CronJobs offers optional candidate Premium and employer posting tiers. Product pages identify prices and access boundaries, while comparison pages disclose that CronJobs is reviewing its own service. Sponsored job placement is a product feature and is separate from the evidence used in editorial comparisons or original aggregate reports.

Related evidence policies