What Is a Reverse Job Board? How the Model Works, Who Tried It, and What Operators Should Learn

Every job board you've used works the same way: employers post jobs, candidates apply, and the board charges employers for the privilege. A reverse job board runs the model backwards. On a reverse job board, candidates create profiles instead of applying to postings, and employers browse those profiles and pay to contact the people they want to hire. The candidates are the listings. Employer access is the product.

The idea has produced some of the most-loved products in hiring, and some of its most instructive failures. The two best-known reverse job boards, RailsDevs and Hired, are both gone. If you run a job board or you're thinking about building one, that history is worth more than any feature list, because it tells you precisely when this model works and when it quietly runs out of inventory.

This guide covers how reverse job boards work, how they differ from the concepts they're constantly confused with, how they make money, what happened to the boards that tried it, and the version of the model that survives contact with reality.

What is a reverse job board?

A reverse job board is a hiring marketplace where job seekers list themselves and employers do the searching. Instead of a feed of job postings, the core surface is a directory of candidate profiles: skills, experience, availability, sometimes rate or salary expectations. And instead of candidates applying, employers reach out.

The concept has a longer history than most people assume. In 2012, a developer named Andrew Horner built the "reverse job application," a single page listing himself and inviting companies to apply to him. The idea resurfaced as a real business category in 2021 when Joe Masilotti launched RailsDevs, a directory of Ruby on Rails developers that companies paid to contact. RailsDevs inspired a wave of imitators across other niches, most of them literal forks of its open-source codebase.

Here's the model side by side with a traditional job board:

That last row is the one that decides whether the model works, and we'll come back to it.

Reverse job board vs. reverse recruiting vs. talent marketplace

"Reverse job board" gets tangled up with three adjacent concepts: reverse recruiting, reverse job search, and talent marketplaces. The distinctions matter if you're evaluating any of them as a business, so here's the reverse job board alongside each:

Reverse job board: a self-serve directory. Candidates list profiles; employers search and pay to make contact. The operator runs a marketplace, not a service. RailsDevs was the canonical example.

Reverse recruiting: a paid service for job seekers. A reverse recruiter represents the candidate, finding roles, tailoring applications, and pitching them to companies. Firms like Find My Profession sell this as a done-for-you job search. The candidate pays, which is the opposite of a reverse job board's economics.

Reverse job search: a tactic, not a platform. It's the job seeker's practice of targeting companies directly instead of applying to postings. No operator, no marketplace.

Talent marketplace: a managed matching platform like Hired, Toptal, or A.Team. Superficially similar in that employers browse talent, but the platform inserts itself into matching, vetting, and often payment, taking a percentage. A reverse job board is thinner: it sells access, not matchmaking.

There's also the scale question. LinkedIn Recruiter and resume databases like Indeed Resume are the reverse model operating at massive scale: candidates maintain profiles, employers pay for search and outreach. A niche reverse job board is a bet that in one specific talent pool, a curated directory beats the giant generic database. That's the same bet every niche job board makes against Indeed, applied to the candidate side.

How reverse job boards make money

Reverse job boards monetize the employer side almost exclusively. Charging candidates to be listed kills supply, and supply is the whole product. The recurring patterns:

Pay-per-contact credits. Employers buy credits and spend one to open a conversation with a candidate. RailsDevs used a version of this: browsing was free, but messaging a developer required a paid company subscription. Contact-gating protects candidates from spam, which is itself part of the pitch, since outreach on a paid channel is scarcer and more serious than a LinkedIn inbox.

Profile unlocks. Profiles are partially redacted, with name, contact details, and sometimes employer history hidden until the employer spends an unlock. This makes profile access itself the paid product, and works when the profiles carry rare, high-value information.

Employer subscriptions. A flat monthly or annual fee for directory access, sometimes bundled with a number of contacts per month. Simpler to sell, but it needs enough new candidate supply each month that the subscription keeps earning its renewal.

Success fees. A percentage-of-salary fee on completed hires. This drifts the business toward a recruiting agency or talent marketplace, with the enforcement problems you'd expect, since employers and candidates can simply take the conversation off-platform. It's also, quietly, where the money actually was: per RailsDevs' public numbers, hiring fees made up roughly 90% of its revenue, with subscriptions the remainder. The best-known "reverse job board" was economically a lightweight recruiting agency with a profile directory attached, a fact that should shape how you price one.

Most operators combine a couple of these, and the same pricing psychology that applies to job posts applies here: employers pay for scarcity and relevance, not volume. For where this fits in the broader landscape of job board revenue, see our guides to job board business models and monetization.

Real reverse job boards, and what happened to them

The category's track record is short and unusually well documented, because its flagship was run in public.

RailsDevs is the case study worth reading in full. Joe Masilotti launched it in November 2021, open-sourced the code, and ran it in public: about 100 developer profiles in the first week (largely from his existing Twitter audience), 600+ developers and 30+ hires by the end of year one, and roughly $146K in first-year revenue per Starter Story's case study, averaging around $10,000 a month at its best. It was profitable, respected, and genuinely useful. He archived the project in July 2025 after almost four years, without pointing to any operational cause. His farewell note says only that it was time to make space for what's next. Many of the reverse boards you'll find in older roundups were forks of RailsDevs, and most died faster than it did.

Hired proves the ceiling problem from the other direction. It raised $133 million and was once valued at around $500 million as the "apply to you" tech talent marketplace. It came close to winding down in 2020, was acquired by Vettery (Adecco) that November, and the marketplace was finally folded into LHH, Adecco's talent arm, in June 2024. Even with venture scale, candidate-side inventory economics were brutal.

The category also churns fast: many of the boards recommended in older roundups are offline, so verify any "active reverse job boards" list before relying on it.

Why the poster children shut down

Nobody involved published a formal post-mortem, but the structural pressures are visible in the model itself.

Candidate profiles are perishable inventory. A job posting is useful for its entire 30–60 day life, and the employer who posted it will post again next quarter. A candidate profile is useful until the candidate gets hired, and the best profiles, the ones employers pay to reach, exit the pool fastest. Success consumes your inventory. A reverse board that works well is a reverse board that must constantly re-acquire its own supply.

The cold start is double-sided and steeper. A traditional board can bootstrap the job side with aggregation and give candidates a reason to show up on day one. There is no equivalent backfill for people. You can't aggregate willing-to-be-contacted candidates, so supply has to be earned one trust-building interaction at a time, before any employer demand exists to reward it.

Demand is cyclical in a way supply isn't. Employers pay to browse candidates only when hiring is competitive and talent is scarce. When the 2022–2024 tech downturn flipped the market, with more developers looking and fewer companies hungry, the willingness to pay for proactive developer outreach evaporated. A model whose only revenue is "employers pay to reach scarce talent" has no floor in a soft hiring market, whereas job posting demand slows but doesn't vanish.

Niche trust doesn't scale. RailsDevs worked because Rails developers trusted Joe. That trust was the moat and also the constraint. It doesn't franchise into adjacent niches, which is why the forks mostly failed: they copied the code, which was never the hard part.

When the reverse model actually works

None of this means the model is dead. It means the model is conditional, and the conditions are strict enough to write down as a checklist:

• Talent-scarce niche. Employers must struggle to find these people. If candidates outnumber roles, nobody pays to browse.
• High-value, high-skill roles. The cost of a bad or slow hire must justify paying for outreach. Senior engineers, specialized clinicians, and niche legal talent qualify. Commodity roles don't.
• A trust asset on the candidate side. Candidates list themselves where they feel represented and protected. An existing community, newsletter, or reputation in the niche is close to a prerequisite. The same niche validation discipline that applies to a normal board applies double here, because supply is so much harder to bootstrap.
• Employers who already source proactively. If hiring in your niche happens through recruiters and outbound anyway, you're replacing spend that exists. If employers post-and-pray, you're educating a market, which is expensive.
• A plan for inventory churn. Some flow of new candidates has to be structural (community, content, the job board itself) rather than a launch spike.

Score your niche honestly against those five. Most niches fail at least two, which is the real explanation for the category's graveyard. It's also why the survivors mostly aren't pure reverse boards at all.

The hybrid model: a job board with a paid talent directory

The version of this model that keeps showing up in profitable niche boards isn't the pure reverse board. It's the hybrid. Run a traditional job board as the foundation: job postings give you evergreen inventory, SEO surface area, and a reason for candidates to visit every week. Then add an opt-in candidate directory on top, and sell employers access to it as a second product.

The hybrid fixes the pure model's structural problems one by one. Candidate supply regenerates because job seekers keep arriving for the listings and some convert into profiles. Revenue has a floor because job-post income doesn't vanish in a soft market. And the directory inherits the board's niche trust instead of having to build it from zero.

This is the model Cavuno supports natively. Candidates build profiles with AI resume parsing, an AI-searchable talent directory sits alongside your job listings (public or employers-only, with candidates controlling their own visibility), and a talent access paywall lets you sell profile unlocks and contact credits through Stripe, as subscriptions or one-time packs, next to your job post plans. You can run it as a pure reverse board if your niche clears the checklist above, or as the hybrid if you want the safer economics.

Whichever shape fits your niche, go in with the model's history in view. The reverse job board is a genuinely good idea whose pure form has punishing inventory economics, and the operators who make it work sell candidate access as a product, not the product. For the step-by-step version covering supply acquisition, pricing, and when to start charging, see our guide to starting a reverse job board. If you're still weighing models, start with the job board business models guide.