> ## Documentation Index
> Fetch the complete documentation index at: https://www.landbase.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Search Contacts

> Find people by title, department, management level, location, and career trajectory.

<div id="breadcrumb-wrapper" />

<div
  style={{display: 'none'}}
  data-related-resources={JSON.stringify([
{ title: 'Build Audience', href: '/reference/tools/build-audience' },
{ title: 'Expand Titles', href: '/reference/tools/expand-titles' },
{ title: 'Tools overview', href: '/reference/tools' }
])}
  id="page-related-resources"
/>

# Search Contacts

<div className="blog-post-content">
  Find people by who they are professionally — their role, seniority, department, location, and career trajectory.

  ## What you can filter on

  * **Job title** — with automatic normalization ("CEO" and "Chief Executive Officer" are treated as equivalent)
  * **Department and management level** — validated taxonomy values (Engineering, Sales, Marketing / C-Level, VP, Director, Manager, IC)
  * **Location** — country, state, or raw address search
  * **Tenure** — how long they've been in their current role (in months)
  * **Career signals** — recently promoted internally, or hired externally into a new role
  * **Skills and experience** — keyword matching against job descriptions, skills lists, and profile descriptions

  The career signal filters are particularly useful for timing-based outreach — someone who just got promoted into a VP role is more likely to be evaluating new tools than someone who's been in the seat for 3 years.

  ## How it differs from Build Audience

  Search Contacts returns **person-level results only**. [Build Audience](/docs/reference/tools/build-audience) combines company and contact filters together in a single query. Use Search Contacts when you're looking for people independent of company criteria; use Build Audience when you need both.

  ## Result limits

  Search Contacts returns up to 10,000 matching contacts per query.
</div>