Data and citation guide
Public resources for researchers, readers and agents using Remote Design Roles. Start with the report for context, then use its linked data to check the figures.
Choose a source
| Resource | What it contains |
|---|---|
| Monthly reports | Dated hiring findings, sampling limits and CSV/JSON downloads. |
| Skills in job listings | Current descriptions of the work employers seek, including AI skills, with sample sizes, example roles and dated aggregate CSV/JSON captures. |
| Report catalog (JSON) | Schema version 1. Published editions, citation URLs, dates, reporting definitions, download links and checksums. |
| Current jobs (JSON) | Schema version 2. Currently visible listings, public job URLs, source pay evidence and separate publication and verification dates. |
| Jobs RSS feed | Current job summaries for feed readers. Publication dates use the board’s publication time when known, otherwise the source’s time. |
These resources are public and require no account or API key. Each board provides its own data at these paths. Follow the canonical job or report URL when checking or citing a result.
Cite a dated report
Use the publication, report title, month, edition and canonical report URL. For example:
Remote Design Roles. “August 2026 hiring report.” Edition 1. https://remotedesignroles.com/reports/2026-08
For a changing live report or job listing, include the date you accessed it. A later live snapshot can differ from a dated edition. A closure does not establish a hire, and the monitored sample does not represent every remote employer.
The JSON download preserves the edition’s original payload. Its dataSha256 is the SHA-256 digest of the UTF-8 serialization JSON.stringify(payload), without a trailing newline. It is not a hash of the complete JSON file or the CSV. Keep the reporting definition with any extracted figures.
Use a skills observation
The skills page explains what matching employers describe and links to example roles. Its dated downloads preserve aggregate counts, the number of roles with substantive text, employer counts and the skill-definition version. Cite the board, capture date, definition version and skills page URL. A skill mention can be a responsibility, requirement or preference; the counts cannot establish what every employer expects or whether AI caused a role to change.
Interpret job dates and pay
In jobs.json, sourcePublishedAt is the date supplied by the source; boardPublishedAt is when the board published the listing; verifiedAt is when we checked it. Missing dates are null. The compatibility field listedAt uses sourcePublishedAt, then boardPublishedAt; listedAtBasis identifies which one. updatedAt can include a verification update. Verification never creates a new RSS publication date.
The pay object preserves disclosed wording and supported ranges. Each range retains its currency, period and basis: salary, on-target earnings (OTE), total, net or unknown. A missing endpoint is null. We do not infer USD from a dollar sign, annualize pay, convert currencies or combine geographic tiers. Source wording may disclose pay without supplying a comparable numeric range.
Schema version 2 adds pay evidence and date provenance. The compensation field now uses retained source pay wording, including pay found in the employer description. compensationCurrency and compensationUnit are null unless one supported range establishes them. comparableRange only describes the individual listing; publishing a pooled pay statistic requires the separate sample rules in our methodology.
Check the method and current source
Report downloads contain aggregate observations, without subscriber details or visitor identifiers. Do not add daily inventory counts to estimate unique monthly jobs, or combine incompatible reporting definitions into a single trend. For availability and application terms, follow the employer source linked from the job page.