Open index · free forever · the story
RemoteCurrent / story ← Back to the board

The story

I got mad at job-board paywalls, so I built RemoteCurrent

RemoteCurrent is a free, open index of remote jobs, read straight from employer hiring feeds every hour — no account, no paywall, no stored résumés. Here is why it exists.

Why I built it

A little about me and what I’ve been doing for the last several weeks.

I’ve been struggling with a conventional nine-to-five. Migraines, back problems, and other things keep interrupting my workflow and making my current role increasingly hard to sustain.

I thought: I already do a lot of data-analytics work. Maybe I can find a remote job that lets me do that from home — somewhere I can recline when my back hurts, or work asynchronously so that on a migraine day I can take an extended break, let it blow over, and continue afterward.

Then I kept running into paywalls.

I hate paywalls.

One site showed me nineteen jobs but told me there were more than a thousand others available if I paid $99 a year.

That bothered me. A lot.

These aren’t secret jobs. They aren’t a product someone manufactured. It’s a curated aggregation of listings from employers’ own sites — including roles that never make it all the way to LinkedIn. It bothers me because it means someone in a financially secure position is leveraging people who are looking for work — whatever condition they may be in — and charging them for the chance to better their lives.

Seems gross.

So I decided I wanted an alternative: a site that pulls the listings and shows you the damn things without holding them hostage behind a subscription.

How it works

Every hour, RemoteCurrent checks public hiring feeds directly from employers — the ones their own career pages use, from Greenhouse, Lever, Ashby, Workday and others. It identifies the remote roles, normalizes them into a consistent format, and publishes them with links to apply directly through the employer. As I write this, it is tracking more than 3,500 remote listings from over 70 companies.

No accounts. No sponsors. No ads. No stored résumés. No “we found more matches — now pay up.”

It is, admittedly, a very well-dressed pre-alpha. Remote work is described inconsistently across employers, hiring systems are messy, and automated classification should be scrutinized at the best of times. That is why the sourcing is visible and the project is open: you can see every source and how it is doing, the code and every classification rule, and a note on each listing showing where it came from and when it was last confirmed live. If you would rather it come to you, you can subscribe to a filtered slice by RSS.

What about stale listings and ghost jobs?

A “ghost job” usually means a published role an employer may not genuinely intend to fill. RemoteCurrent cannot see inside a company’s hiring decisions, so it cannot label a listing real or ghost — and honestly, neither can anyone else.

What it can do is read the employer’s own public feed every hour. When a listing disappears from that feed, it disappears from RemoteCurrent — it is not kept around as a scraped copy the way most aggregators do. That removes one common kind of dead posting, the long-expired repost. It is not proof that an employer is actively interviewing or intends to hire.

So it is worth being exact about what the site knows:

What it costs, and what I promise

Right now, almost nothing. The crawler runs on free CI and the site is served as static files; the only real expense is a domain. If RemoteCurrent grows enough to need paid infrastructure, that move will be shown 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.

I’m committed to RemoteCurrent never being sold, never requiring a subscription, and never charging anyone a dime to look for work. Frankly, the listings aren’t mine to sell. They belong to the employers publishing them and the people trying to find them.

Anyone can build another AI job board, and plenty of people have. What I’m trying to build is something transparent, useful, and accountable instead of another layer of algorithmic slop between people and work.

A note on how I built it

I know this doesn’t sit well with everyone, and that’s fine. I did not type every line of this. I typed very few of them. I used Claude Code to implement what I wanted — the connections to employers’ public hiring feeds, the layout, the hourly refresh.

That’s what made it feasible for one person, dealing with a fair amount at the moment, to pull this together in a few weeks while keeping human judgment in the loop until it was something I was comfortable putting online under my name.

I’d love your feedback — on the site as it exists and on what to build next.

If it helps

If you like the concept, enjoy the workflow, or find something that helps you: browse the board, share it around, and leave me a coffee if you can.

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

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