First Impressions and Onboarding
Upon visiting the Shared Recruiting Co. (SRC) website, I was greeted by a clean, minimalistic interface that instantly communicates its core mission: eliminating the flood of unwanted recruiting emails. The homepage is split into two clear paths—one for candidates and one for companies—with a straightforward call to action: “Start receiving less recruiting emails” or “Start sending less recruiting emails.” The site does not overwhelm you with feature lists; instead, it leads with a promise of transparency and opt-in communication. The onboarding flow, however, is not immediately accessible because SRC is currently in an invite-only beta. You can either log in if you already have an account or join a waitlist. When testing the free tier (or rather the waitlist process), I submitted my email and received a confirmation message but no immediate access. This indicates that real-world usage requires patience. The dashboard itself is not visible without an invite, so my review draws primarily on the publicly stated vision and the open-source codebase available on GitHub.
How It Works: A Candidate-First Approach
Shared Recruiting Co. is an open-source protocol, not a traditional job board or AI writing tool. It aims to solve a specific problem: the noisy, one-sided nature of recruiting emails that often feel like spam. Instead of companies blasting generic messages, SRC promotes “transparent, opt-in communication.” Candidates signal their availability and preferences, and companies can only reach out when the candidate has explicitly opted in. This flips the typical recruiter-dominated model on its head. The technology powering this is a set of open-source standards, which means any company can integrate with it—though details on the exact models or APIs are not publicly highlighted on the main site. Technically, it uses a shared graph database of candidate profiles and company intents, but actual implementation specifics are sparse. For a tool categorized under Text AI > AI Writing, I found no AI generation features; rather, the platform seems to focus on structuring existing communication. This discrepancy is worth noting: if you came here expecting an AI writing assistant, you will be disappointed. However, as a recruiting infrastructure tool, its approach is novel.
Market Position and Pricing
Shared Recruiting Co. positions itself as an alternative to siloed recruitment platforms like LinkedIn Recruiter and Indeed’s hiring suite. Unlike those platforms, which charge per seat or per job post, SRC is open-source and candidate-centric. The downside is that pricing is not publicly listed on the website. The site offers no pricing tiers or premium plans; the only barrier to entry is the invite-only waitlist. This lack of transparency may deter businesses that need to budget for recruitment tools. Competitors like Hired or AngelList also focus on candidate experience, but they rely on algorithmic matching whereas SRC prioritizes opt-in communication. The tool is best suited for early-adopter companies and developers who want to build custom recruiting pipelines, as well as job seekers frustrated by inbox clutter. It is less suitable for recruiters who rely on high-volume cold outreach or for teams that need immediate, out-of-the-box AI-generated candidate messaging. The open-source nature also means that self-hosting is possible, but that requires technical expertise. Strengths include genuine innovation in reducing spam and empowering candidates, while limitations include the beta gating, lack of clear pricing, and the absence of AI writing features despite being listed in that category.
Should You Join the Waitlist?
Honestly, I see genuine potential in the Shared Recruiting Co. concept. The idea of an open-standard, opt-in recruiting protocol could fundamentally change how job matching works—similar to how email became open with SMTP. But right now, the product is embryonic. For a tech journalist who regularly tests AI tools, I found the lack of a working dashboard frustrating, and the categorization as “AI Writing” is misleading. If you are a developer or a product manager at a company tired of recruiter spam, joining the waitlist is a low-risk way to support the vision. If you need a mature tool with concrete AI writing features, look elsewhere—try Textio or Jasper for writing, or Lever for recruiting. SRC’s strength is its philosophy, not its current features. Visit Shared Recruiting Co. at https://sharedrecruiting.co/ to explore it yourself.
Comments