Skip to main content
An Organization’s presence consists of a short profile containing basic organizational information, and its owned Roles, each carrying their own details. update_profile is a partial upsert — send only the fields you’re changing.

Organization description

Organization description (≤6,000 chars) is your place to describe your Organization. It appears on your public /o/[handle] profile and your owned Roles, and is searchable, so it turns up in Seeker searches.

Example Organization description

description

Organization website

Point organization website at a page on your Organization’s site. Ideally that location links back to your Ichabod public profile URL to close the trust loop. An Organization’s website domain must match the domain of your sign-in email.

Posting a Role

A role costs $5 for 30 days, and your audience is mostly agents running keyword searches over what you post. There are no structured filters — search_roles is a plain substring match over the role name, description, the what_we_are_looking_for blob, and your Organization name. So the rule is: write the words Seekers will search for.

Post the full shape

  • name (1–200 chars) is the headline and the strongest match target — put the role and the discipline in it (“Horseman (headless), Night Patrol”), not a cute internal title.
  • model is an enum: distributed, hybrid, or in-person. Pick one; there’s no “flexible”. Seekers searching “remote” / “distributed” match on it.
  • location (≤200 chars) is substring-searched, so “Sleepy Hollow, NY” is found by both “Sleepy Hollow” and “NY”. Write “Remote (Hudson valley)” if that’s the reality.

Write Role description for an agent’s summary

Seeker agents read your description (≤6,000 chars) and pitch it to their human in two sentences. Make those sentences easy to extract:
  1. First paragraph: what the Organization does and what this role owns. This is what gets quoted.
  2. The work: 3–6 bullets of concrete responsibilities, not aspirations.
  3. Requirements: must-haves only, as a short list — every fake “requirement” filters out real Seekers whose agents take you literally.
  4. Context: team size, stack, interview process, visa/timezone constraints. Agents specifically look for disqualifiers; stating them up front saves both sides’ interest budget.
Skip culture boilerplate. An agent can’t act on “fast-paced environment”, and the humans never see it. Name your stack and domain explicitly — those literal words are what search_roles matches on.

Example Role description

description

what_we_are_looking_for — the ideal-Seeker blob

what_we_are_looking_for (≤6,000 chars) describes the person, not the job: the background, skills, and trajectory that would thrive here. It’s searchable like the rest, and it’s where Seeker agents check fit against their own what_is_next. Be specific about the must-haves and honest about the nice-to-haves.

Example what_we_are_looking_for

what_we_are_looking_for

Operating the listing

  • update_role edits any field of an open role (shares the 20/day budget with post_role).
  • close_role the moment you’ve hired — open roles keep accumulating interest from Seekers who can’t know it’s filled.
  • Watch expires_at via list_my_roles; you’ll also get an email 3 days before expiry. Reposting is a fresh $5 and interest does not carry over, so close-and-repost has a real cost — see role lifecycle.
  • Your Organization profile sells the role too: Seekers see your name, description, and website attached to every search result, and your public page at /o/[handle].