Skip to main content
Everything in Hired is reachable from a conversation. The web app is where you go to look at the result, adjust it by hand, and do the two jobs a conversation is bad at: direct manipulation and rendering. The left rail holds Dashboard, Me, Resumes, CRM and Pipeline — the content. Docs, this manual, Settings and — for admins — Admin are account actions, so they live in the profile menu at the top right instead. ⌘K / Ctrl+K opens a search palette: somewhere to go, something to create, and every role, resume and application by name. Your work autosaves. The brain, the resume editor, the pipeline and the CRM have no save button anywhere; a small indicator tells you when a change has landed. The settings and admin forms are the exception — those have a Save, and typing a new name into Settings → Account and navigating away loses it. Both themes are supported. The toggle is on the Appearance tab in Settings, not in the top bar.

​
Dashboard

/ What is due and what has gone quiet, ahead of everything else. Stats across the top — what is in flight, response rate, what you sent this week, how much is in the brain — then follow-ups due, recent activity and open tasks. It is the screen to open on a Monday, and it answers the same question list_follow_ups does, laid out rather than listed.

​
Me

/brain and /brain/<roleId> Every role with its date range and highlight count. Opening one gives you the brain dump in a full-width editor beside its highlights, plus the role’s own fields — company, title, employment type, location, dates, scope summary and tags. The four supporting collections — education, projects, skills, certifications — and your free-floating notes live here too.
You can type into a brain dump directly, and sometimes that is the right thing. But the fastest way to fill one is still to talk: twenty minutes of rambling beats twenty minutes of typing into a textarea, and it produces better material.

​
Resumes

/resumes and /resumes/<id> The list is every document with its target role and company, how many applications it is attached to, and whether it is published. Favourites pin to the top. The editor is one of the two deliberately browser-first parts of the product. On the left, the document — sections you can reorder with ⌃/⌄, hide rather than delete, and rename freely. On the right, the paper: the real renderer, not an approximation, so what you see is what the PDF and the published page produce.

Design

The palette icon. Template, font family, base size, line height, accent colour, margins, and whether the photo shows — per resume.

Share

Create an unlisted public link, or withdraw one. What that exposes.

PDF

Downloads the file. Where the host has no headless browser, ⋯ → Open print view is the fallback.

​
Pipeline

/applications and /applications/<id> One toolbar across the top picks the view, the cut and the search.
Drag-and-drop across the six live stages. The four endings get their own view rather than a column each.
Sortable, and it edits in place — stage, follow-up, salary and location are the cells themselves. A Waiting column counts days since anything last moved, which is the column to sort on when you want to know what has gone quiet. Select rows to close a batch out in one action.
A month of everything that has a date on it — follow-ups, task deadlines, logged activity.
Filters combine — all of them, with each other. Stage chips are the fast lane; the Filter button holds the source, the company, which resume went out, how long something has sat still and how much you want it. A cut worth keeping saves under a name. Opening an application slides it in from the right, so you keep your place on the board. The people you are talking to come first, then the resume you sent — drawn as the page it is, not named in a dropdown — then the timeline. The posting itself is folded away, because you pasted it once and it is the thing on that screen you look at least. The employer is a chip: click it for their research, their people and the other roles you have there.

​
CRM

/crm/companies, /crm/contacts, and a page per record Two filterable lists. Companies shows when you last applied and what is still live; contacts shows who is attached to what. Both filter — to the companies where you know someone, to the people whose ping is due. A company page carries its details, its research notes, every application you have there and every contact who works there. A contact page carries their details and their own timeline. Contacts attach to applications straight from here rather than being retyped, and removing one from an application never deletes the person.

​
Settings

/settings Three tabs, opening on Connections — because a new user’s first ten minutes are spent pasting a URL into an assistant, not changing a password.

Connections

Every assistant wired to your workspace, when each last called in and from what. Set up, test, rename, rotate, disconnect — and the three skills, each as a raw SKILL.md and as a zip.

Account

Name, email, password, and the profile photo that every document shares.

Appearance

Theme.
Admins get a link through to Settings → Admin from here. What lives there →
The app used to carry its own /docs page listing every tool. It is gone: these pages say the same things, and the tool tables here are generated from the same array the server sends, so there is no second copy to keep right. /docs on your instance redirects here. The skill files stayed behind on Settings → Connections, because they are served by your instance — byte for byte the copies in the repository it is running — and a static site cannot build you a zip out of them.

​
The pages without a login

Three, and they are the entire public surface of an instance. Exactly what each one exposes →