Filters vs Criteria

Getting Started

Search & Prompt

Agents

Shortlist

Sequences

Contacts

Exports & Integrations

Beta Access

Organization

Support

Filters vs Criteria

Learn the difference between filters and criteria, and when to use each.

Introduction

The initial set up of a search in Juicebox is crucial in order to achieve the best results. The more information we provide upfront, the better our search results will be as those requirements will be used to auto-populate the filters and criteria to refine our search pool, and rank candidates accurately.

If you’re not sure whether to use a filter or criteria in Juicebox, use the guide below!

	Filters	Criteria
Purpose	To narrow your search results	To rank your search results
Nature	Hard requirements that are more traditional or keyword based	Natural language that describe requirements a bit more nuanced or inferred
Best for	Yes / No Criteria: • Location • Job Title • Years of Experience • Company Nested Criteria: • Bachelor’s degree from Top 20 University • Software Engineer at Google • Founding AE at a Series A, B, or C startup	Inferences or soft skills: •Time-based experience: 3+ years at a SaaS company and 2+ years in a closing role • Ownership & impact: Built or led first-of-function initiatives (e.g., first PM, first sourcer, first RevOps hire); experience pushing Python-based models to production • Soft skills: Clear, high-signal async communicator; strong collaboration with product teams • Proven results: Consistent record of hiring senior technical talent, 100%+ quota attainment, ~$50k average deal size; experience as a player-coach (formal management a plus) • Nice to have: Open to remote, with preference for candidates based in San Francisco

To learn more about the filters provided by Juicebox, please visit our AI Filters article here.

To learn more about criteria, please visit our Criteria article here.

← Previous

AI Filters

Filters vs Criteria
Introduction