Marketplace Liquidity at Dice

The Problem

When I joined Dice, I was surprised by how comfortable the organization was with long release cycles. Launching something valuable once a quarter was considered good. Some initiatives took over a year to see results.

Coming from Array's nimble environment, I kept asking: "What can we do in two weeks?"

The marketplace had a classic two-sided tension: Recruiters complained they couldn't find actionable candidates quickly enough. Candidates were frustrated by irrelevant outreach that felt like spam. Both sides wanted the same outcome—finding the right match—but their experiences were misaligned.

Recruiters weren't engaging enough quality candidates, and candidates weren't responding because the outreach felt generic. This was directly impacting our business: low recruiter adoption meant low ROI, which threatened renewals. Low candidate engagement made the marketplace less valuable for everyone.

Discovery: Understanding Both Sides

I ran interviews with recruiters and candidates separately to understand the friction points.

From recruiters:
Email was their preferred hook to get back into the platform. They wanted to know when relevant candidates appeared, not manually search daily. But they needed quality candidates for their active roles, not just volume.

From candidates:
They were tired of mass outreach. They couldn't tell if a recruiter's message was genuine interest or a spray-and-pray email blast. They wanted signals that someone had actually looked at their profile and thought they'd be a good fit.

The insight: We needed to help recruiters show genuine interest at scale—and give candidates a reason to believe it.

Building the Solution: Rapid Launch Strategy

Two features emerged: Automated Talent Alerts (notify recruiters when matching candidates appear) and Invite-to-Apply (let recruiters signal specific interest in a candidate for a role).

The challenge? Building this properly would touch multiple systems—our jobs product, search engine, email infrastructure, candidate profiles. It could easily become a 6-12 month project.

I worked with the engineering team to define an early version we could ship in weeks, not months. We focused on:

• •Basic search-to-email pipeline for alerts
• •Simple invite mechanism with clear role context
• •Minimal but functional UI for both sides

We architected it so we could move quickly now and harden later—modular components that could be improved without rebuilding the foundation.

Building the Early Access Program

Here's where culture shift happened. Dice didn't have a concept of "early access" with customers. Everything launched fully baked or not at all.

I partnered with our Account Management and Customer Success teams to create a framework: Select customers get early features in exchange for feedback. It was mutual value—we get real-world validation and can iterate; customers feel included in the product process and get a competitive edge.

This wasn't just about risk mitigation—it was about shortening feedback cycles from months to weeks. We could learn with real customers using a beta that wasn't perfect yet.

Launch & Iteration

We launched to our early access group within weeks. The feedback was immediate and actionable:

Search quality: Some alerts were too broad, others too narrow
Email timing: Daily was too much; weekly digests worked better
UX clarity: Candidates wanted to see why they were invited (which skills matched)

We incorporated these learnings and moved to general availability shortly after.

Results

Marketplace Impact

• •15% increase in candidate profile views—and these were quality, relevant views tied to active roles
• •8% higher response rate to Invite-to-Apply emails compared to standard recruiter outreach
• •20% YoY revenue growth from improved engagement on both sides of the marketplace

Organizational Impact

• •First structured early access program at Dice, shortening future feedback cycles across product org
• •Cultural shift: Demonstrated that "done right" doesn't always mean "done slowly"
• •Repeatable pattern: Other PMs adopted early access for their initiatives

Process Innovation

• •Feedback cycles shortened from months to weeks
• •Lower risk launches with controlled customer cohorts
• •Customer co-creation deepened relationships and improved retention

Key Learnings

1. Investing in culture is essential.
The biggest barrier wasn't technical—it was the assumption that "done right means done slowly." Showing a faster path with controlled risk changed how the team thought about launches.

2. Early access isn't just risk mitigation—it's a discovery tool.
The insights we got from real usage (search quality, email cadence, UX clarity) were things we never would have surfaced in internal testing. Customers revealed what actually mattered vs. what we thought mattered.

3. Two-sided marketplaces require empathy for both.
We couldn't just optimize for recruiter efficiency or candidate experience—we had to improve the relationship between them. Invite-to-Apply worked because it helped recruiters show genuine interest at scale.

4. Architecture for iteration, not perfection.
By building modular components, we could improve search algorithms, email logic, and UI independently over time. The foundation we laid in weeks supported improvements for years.

5. Process changes are product work.
Creating the early access program was as valuable as the features themselves. It became infrastructure for how Dice shipped products—demonstrating that product management includes changing how teams work, not just what they build.

6. Small wins create momentum.
Shipping Talent Alerts and Invite-to-Apply quickly, then iterating based on feedback, gave the team confidence. This success made it easier to propose other experiments and faster cycles.