RemoteCurrent / about ← Back to the board

About

A remote job index you can actually trust.

RemoteCurrent reads job listings straight from employers’ own hiring systems, every hour, and shows you exactly where each one came from. The story of why it exists is a separate read.

What it is

Most job sites are aggregators. They copy listings from other aggregators, keep stale posts alive to look busy, and route your application through their own funnel. RemoteCurrent does none of that. It polls the public feeds that employers’ career pages already use — Greenhouse, Lever, Ashby, Workday and others — normalizes what it finds, classifies how remote each role really is, and links you to the employer’s own application page. Nothing in between.

Every listing shows its source, the employer’s posted date, and that it was still live in the most recent sweep. The feed status page shows how every source is doing in real time.

How it works, precisely

The live RemoteCurrent pipeline is ordinary deterministic software. It requests published employer hiring feeds, applies public classification rules, writes a versioned dataset, and rebuilds this static site. No generative-AI model selects jobs, invents listing details, or decides how a role is classified. LLM-assisted development tools have helped write and maintain the software; the production inputs, rules, and outputs remain inspectable in the public repository.

RemoteCurrent verifies that a listing appeared in the employer’s public feed during the displayed sweep. It cannot verify that the employer is actively interviewing, and its interpretation of remote scope can be wrong. The employer’s application page is always the final authority.

The pledge

Who runs it

RemoteCurrent is built and maintained by Orpheus Rook (rook.works) as an independent project. It has no company behind it, no investors, and no advertising. The code, the source registry, and every classification rule are open at github.com/JJHerrmann/remote-current — audit any of it.

What it costs

Today, almost nothing. The crawler runs on GitHub Actions’ free tier and the site is served from GitHub Pages; the only real expense is the domain name. That is why there is no funding thermometer here yet — there is barely anything to fund.

If RemoteCurrent grows enough to outgrow the free tiers — a real database, a search API, email digests — that move to paid infrastructure will be shown here in full: what it is, what it costs per month, and how close reader support comes to covering it. Paid services get switched on only when donations can carry them, never on credit and never by adding ads.

Support RemoteCurrent

If RemoteCurrent has saved you time, you can chip in on Ko-fi. Support helps maintain the service, improve its coverage, and keep it free for everyone. Access, ranking, and application links never depend on contributing.

☕ Support on Ko-fi one-time or monthly · ko-fi.com/mindpalacegarden

Corrections and feedback

Every listing has a flag link that opens a correction report with the listing ID, source, and current classification already included. For a broader bug or suggestion, open a project issue or contact @remotecurrent.bsky.social. Please do not send résumés or application materials; RemoteCurrent is not an employer or recruiter.

What it does not collect

RemoteCurrent has no user accounts, stores no résumés, and does not handle job applications. It currently runs no first-party visitor analytics and sets no first-party tracking cookies. The static site is hosted by GitHub Pages, the support button opens Ko-fi, and the typefaces are delivered by Google Fonts; those providers may receive ordinary request metadata under their own policies.

Read directly from the source. Linked straight to the employer. Free, and staying that way.
— Orpheus Rook