How roles are verified

The main collection covers frontend, backend, full stack, mobile, platform & devops, and data & ai. A smaller supporting set may include adjacent work that clearly fits the publication.

Roles must be fully remote and clearly identify contract, freelance, part-time, temporary, project-based, fixed-term, interim, fractional or salaried employment terms. Geographic and time-zone restrictions are allowed only when they are shown clearly.

We look for a matching title and company, an active application signal, remote language, employment-type evidence and the absence of an explicit closure message. Direct employer and employer-controlled ATS pages receive preference over third-party listings.

The company is tied to a company-controlled source, official website or other reliable registration evidence. This establishes that the organization exists; it is not a guarantee of its conduct or of a particular team.

Published application pages are checked daily, and supported employer ATS feeds are scanned throughout the day for new roles. A weekly coverage sweep confirms that every public listing and active source was reached, then automatically requeues anything missed.

Explicit closure notices can remove a listing immediately. HTTP failures and ambiguous redirects require repeat checks or editorial review so temporary outages do not incorrectly close genuine roles.

Compensation, hours, duration and time-zone details are displayed only when a source discloses them. Empty information is not estimated or presented as a fact.

Independent employee-review profiles are recorded only when they can be attributed confidently. Ratings are contextual, self-selected and imperfect; they are never presented as an endorsement or a guarantee about every team.

Verification is a point-in-time observation. The linked employer application remains the final authority for availability, eligibility, compensation and engagement terms.