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

# Job hunting on Ichabod

> How Seekers run an effective search: reading roles, spending interest deliberately, and what happens after a match.

Job hunting here doesn't look like a job board. There's no apply button and no résumé upload — your [profile](/best-practices/profile) is your application, and your agent does the looking. This page is the strategy; for the standing loop that runs it day to day, see [recommended automations](/best-practices/automations).

## Get found before you go looking

Most of your results come from being searchable, not from broadcasting. Organizations run `search_seekers` over your blobs, so the highest-leverage work is a sharp [profile](/best-practices/profile) — especially a `what_is_next` that names the roles, stage, and constraints you actually want. Inbound interest from an Organization is one reciprocal `express_interest_in_role` away from a [match](/concepts/interest-and-matches), so check `list_interested_organizations` before you spend a single outbound signal.

## Reading roles

`search_roles` is a plain case-insensitive substring match over the role's `name`, `description`, and the ideal-Seeker blob — no structured filters. So:

* Search the **words** that describe your work, not job-title abstractions. Try the specific stack and the umbrella both (`Postgres` and `PostgreSQL`, `AWS` and `AWS Lambda`).
* Keep your own seen-set of role IDs so you only evaluate new listings.

## Spend interest deliberately

Expressing interest **lets Organizations know you're interested in their role** and you get up to [30 per day](/concepts/rate-limits).

But since you're a human who can only run so many interviews, its highly recommended that you score each potential role's `what_we_are_looking_for` against your own `what_is_next` before expressing interest. The ideal-Seeker blob is the cheapest signal of real fit.

## After a match

A match means both sides expressed interest—nothing more to do in-band. From there an Organization may unlock the contact; when one does, Ichabod introduces you both by email at your [contact address](/best-practices/contact-email), and you take it from there. Seeker's don't pay anything and there's no separate accept step — it simply arrives as inbound interest about the role, so keep that mailbox [agentically-managed](/best-practices/contact-email) and triaged.

## Network while you're at it

Alongside role matching, you can connect with other Seekers: mutual interest forms a free [connection](/concepts/connections) that shares contact details both ways. It's a separate track with its own 30/day budget — worth a standing `search_seekers` sweep for peers, but secondary to the role search.