juicebox-reference-architecture
A blueprint for building scalable, production-grade systems that integrate Juicebox AI for talent intelligence workflows.
Install
mkdir -p .claude/skills/juicebox-reference-architecture && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8979" && unzip -o skill.zip -d .claude/skills/juicebox-reference-architecture && rm skill.zipInstalls to .claude/skills/juicebox-reference-architecture
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Implement Juicebox reference architecture.Key capabilities
- →Design candidate search services with caching
- →Implement queue management for analysis tasks
- →Structure ingestion and export pipelines
- →Deduplicate candidates across sources
- →Batch ATS export requests
How it works
The architecture utilizes a service layer for searching, a Redis cache for result persistence, and a Bull queue to manage asynchronous analysis and ATS export tasks.
Inputs & outputs
When to use juicebox-reference-architecture
- →Designing candidate search services
- →Implementing caching with Redis
- →Building ATS export pipelines
- →Structuring ingestion workflows
About this skill
Juicebox Reference Architecture
Overview
Production architecture for AI-powered candidate analysis integrations with Juicebox. Designed for recruiting teams needing automated dataset ingestion from job descriptions, intelligent candidate scoring and ranking, result caching for repeated searches, and seamless export to ATS platforms like Greenhouse and Lever. Key design drivers: search result freshness, candidate deduplication across sources, outreach sequencing, and analysis pipeline throughput for high-volume hiring.
Architecture Diagram
Recruiter Dashboard ──→ Search Service ──→ Cache (Redis) ──→ Juicebox API
↓ /search
Queue (Bull) ──→ Analysis Worker /profiles
↓ /outreach
ATS Export Service ──→ Greenhouse/Lever
↓
Webhook Handler ←── Juicebox Events
Service Layer
class CandidateSearchService {
constructor(private juicebox: JuiceboxClient, private cache: CacheLayer) {}
async findAndRank(criteria: SearchCriteria): Promise<RankedCandidate[]> {
const cacheKey = `search:${this.hashCriteria(criteria)}`;
const cached = await this.cache.get(cacheKey);
if (cached) return cached;
const results = await this.juicebox.search(criteria);
const ranked = results.profiles.map(p => ({ ...p, score: this.scoreCandidate(p, criteria) }))
.sort((a, b) => b.score - a.score);
await this.cache.set(cacheKey, ranked, CACHE_CONFIG.searchResults.ttl);
return ranked;
}
async exportToATS(candidates: string[], jobId: string, ats: 'greenhouse' | 'lever'): Promise<ExportResult> {
const deduped = await this.deduplicateAgainstATS(candidates, jobId, ats);
return this.juicebox.export({ profiles: deduped, destination: ats, job_id: jobId });
}
}
Caching Strategy
const CACHE_CONFIG = {
searchResults: { ttl: 1800, prefix: 'search' }, // 30 min — candidate pools shift slowly
profiles: { ttl: 3600, prefix: 'profile' }, // 1 hr — profile data stable short-term
analysisRuns: { ttl: 7200, prefix: 'analysis' }, // 2 hr — analysis results are expensive to recompute
atsState: { ttl: 300, prefix: 'ats' }, // 5 min — ATS pipeline freshness for dedup
outreach: { ttl: 60, prefix: 'outreach' }, // 1 min — sequence status changes frequently
};
// New search invalidates matching cached results; ATS export clears ats cache for that job
Event Pipeline
class RecruitingPipeline {
private queue = new Bull('juicebox-events', { redis: process.env.REDIS_URL });
async onSearchComplete(searchId: string, results: RankedCandidate[]): Promise<void> {
await this.queue.add('analyze', { searchId, candidateIds: results.map(r => r.id) },
{ attempts: 3, backoff: { type: 'exponential', delay: 2000 } });
}
async processOutreachEvent(event: OutreachEvent): Promise<void> {
if (event.type === 'reply_received') await this.flagForRecruiterReview(event);
if (event.type === 'bounced') await this.markInvalid(event.candidateId);
await this.syncStatusToATS(event);
}
}
Data Model
interface SearchCriteria { role: string; skills: string[]; location?: string; experienceYears?: number; companySize?: string; }
interface RankedCandidate { id: string; name: string; title: string; company: string; score: number; skills: string[]; profileUrl: string; }
interface OutreachSequence { id: string; candidateId: string; jobId: string; steps: OutreachStep[]; status: 'active' | 'replied' | 'bounced' | 'opted-out'; }
interface ExportResult { exported: number; duplicatesSkipped: number; atsJobId: string; }
Scaling Considerations
- Parallelize search requests across role categories — Juicebox API supports concurrent queries
- Cache analysis results aggressively — AI scoring is the most expensive operation per candidate
- Batch ATS exports by job requisition to minimize Greenhouse/Lever API round-trips
- Deduplicate candidates across searches before outreach to avoid double-contacting
- Rate-limit outreach sequencing to maintain sender reputation and deliverability
Error Handling
| Component | Failure Mode | Recovery |
|---|---|---|
| Candidate search | Juicebox API timeout | Retry with reduced result count, serve cached results if available |
| Analysis pipeline | Scoring model latency spike | Queue with timeout, return unscored results with flag |
| ATS export | Greenhouse rate limit | Batch retry with exponential backoff, notify recruiter on persistent failure |
| Outreach sequence | Email bounce | Mark candidate invalid, remove from active sequences, update ATS |
| Webhook handler | Duplicate event delivery | Idempotency key on event ID + candidate ID |
Resources
Next Steps
See juicebox-deploy-integration.
When not to use it
- →When real-time data freshness is not required
Prerequisites
Limitations
- →Requires infrastructure components like Redis
- →Complexity increases with the number of integrated ATS platforms
How it compares
This architecture provides a structured, scalable approach to candidate processing compared to ad-hoc script execution.
Compared to similar skills
juicebox-reference-architecture side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| juicebox-reference-architecture (this skill) | 0 | 27d | Review | Advanced |
| mcp-builder | 136 | 3mo | Review | Advanced |
| nodejs-backend-patterns | 12 | 2mo | No flags | Intermediate |
| perplexity-reference-architecture | 1 | 27d | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
nodejs-backend-patterns
wshobson
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.
perplexity-reference-architecture
jeremylongshore
Implement Perplexity reference architecture with best-practice project layout. Use when designing new Perplexity integrations, reviewing project structure, or establishing architecture standards for Perplexity applications. Trigger with phrases like "perplexity architecture", "perplexity best practices", "perplexity project structure", "how to organize perplexity", "perplexity layout".
vendor-implementation
No-Trade-No-Life
基于Hyperliquid成功实现经验,为新交易所供应商提供Yuan框架集成指南。使用此技能当需要为新的交易所创建供应商实现,包括项目结构设计、API集成、核心服务实现和最佳实践。适用于交易所API集成、金融系统开发、微服务架构设计。
perplexity-architecture-variants
jeremylongshore
Choose and implement Perplexity validated architecture blueprints for different scales. Use when designing new Perplexity integrations, choosing between monolith/service/microservice architectures, or planning migration paths for Perplexity applications. Trigger with phrases like "perplexity architecture", "perplexity blueprint", "how to structure perplexity", "perplexity project layout", "perplexity microservice".
mcp-builder
Harmitx7
Model Context Protocol (MCP) server integration mastery. Building custom MCP servers, standardizing tool exposes, managing standardized communication between large language models and localized datasets, securing boundary contexts, and architecting resource schemas. Use when modifying, extending, or