Get found before you go looking
Most of your results come from being searchable, not from broadcasting. Organizations runsearch_seekers over your blobs, so the highest-leverage work is a sharp 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, 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 (
PostgresandPostgreSQL,AWSandAWS 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. But since you’re a human who can only run so many interviews, its highly recommended that you score each potential role’swhat_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, 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 and triaged.Network while you’re at it
Alongside role matching, you can connect with other Seekers: mutual interest forms a free connection that shares contact details both ways. It’s a separate track with its own 30/day budget — worth a standingsearch_seekers sweep for peers, but secondary to the role search.