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 Today, Me, CRM and Pipeline — the content. Analytics is a tab on Today and Resumes is a tab on Me, because both are a second look at something you already have open rather than a separate filing cabinet. 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. Beside the profile menu is a bell. It carries one number — everything with a date that has come round: follow-ups due, people you meant to ping, tasks past their date — and opens them grouped by which of the three they are. Nothing in it can be dismissed. A thing leaves that list by being dealt with, which is the only honest way for a count of what you owe to reach zero. Your work autosaves. Me, 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.

​
Today

/ Two tabs, and the first one is the front door: the list, not the numbers. Everything you owe, in two columns that stay apart on purpose. On the left the things you wrote down, grouped by overdue, today, the next seven days, later and no date — click a title to reword it, change its date in the row, or drop it. A task carries a detail as well as a title, and hangs off at most one thing: an application, a company, a person, a resume, a role in Me, a note, or nothing. Whatever you hang it on shows it, and deleting that thing takes the task with it. On the right the chase list: the follow-ups and pings whose dates have come round, where the verbs are “logged it” and “push it out three days”, plus the box that puts someone new on it. Ticking a task and logging a chase are not the same act, which is why they are not one list. Above both is a line for reporting what just happened, because that is usually why you opened the app. It answers the same question list_follow_ups does, laid out rather than listed. /tasks still works and lands here.

​
Analytics

/?tab=analytics How the search is going, which is the same subject at a different altitude — so it is the second tab rather than a screen of its own, one click from the list and never in the way of it. /analytics still works and lands here. At the top, the funnel drawn as a flow chart: every application enters on the left as “Applied”, the survivors carry across to the phone screen, the interview, the final round and the offer, and everything that leaves peels off sideways to where it went — rejected, no response, withdrew, offer accepted, still going. An application that was rejected after two interviews leaks out of the interview rung, not the applied one, because progress is measured by how far it actually got. A rung nobody was ever in is not drawn at all. Share chart, on the chart’s own card, copies it to the clipboard or downloads it as a PNG or an SVG. There is not a company, a role or a person’s name on it — only the shape — which is what makes it the one thing here that is safe to post. The PNG is rendered server-side by the same headless browser the PDF export uses; where an instance has no browser the SVG is offered instead and opens anywhere an image does. Over MCP it is export_funnel_image, and get_funnel gives an assistant the numbers behind it. Below that: what is in flight, response rate, what you sent this week and how much is on file; the diagnosis of which step is losing people; what is on the board right now; and recent activity.

​
Me

/me and /me/<roleId> Five tabs: Roles, Profile, Notes, Education & more, and Resumes. Each is an address — /me?tab=notes — so you can link straight to one, and the browser’s Back button walks them the way you would expect. Every role with its date range and highlight count. Opening one gives you the background 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 background 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

/me?tab=resumes and /resumes/<id> The list is a tab on Me. Every document with its target role and company, its estimated page count, how many applications it is attached to and where those got to, and whether it is published. A tailored copy says what it changed from the base it came from, and sits under it. Favourites pin to the top; a search box and a sort control narrow the grid, and both live in the address so a filtered view can be linked to. Opening one goes to /resumes/<id> — the editor keeps its own full-screen address, and an old /resumes bookmark redirects to the tab. 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, resizable, and it edits in place — stage, follow-up, salary and location are the cells themselves, with dates on a calendar rather than a browser’s own date box. Two columns count days and they answer different questions: Waiting is how long it has sat in the stage it is in, Quiet is how long since anything at all was logged. Quiet is the one to sort on for chasing, and it pairs with the “Nothing logged for” filter. Drag the divider between two headings to set their widths, which are saved to your profile. 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. The Filter button holds every dimension: the stage, the tags, the company, which resume went out, how long something has sat still and how much you want it. It opens on the dimensions and you step into one, so a list of stages is a click rather than a scroll past forty companies. Two chips stay above the board — Everything and Needs a nudge — because what is overdue is the one cut worth reaching from anywhere. 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.

​
Archive

/archive Everything you have deleted, and how long each thing has left. Deleting a company, a person or an application does not destroy it: it drops out of every list, board, picker, filter and count immediately, and waits out a retention window — thirty days unless an admin changed it — before it goes for good. Restore acts straight away. Delete for good asks first, and the question is built from what you ticked: “deleting Stripe also deletes the 3 applications archived with it, and their timelines” rather than “delete 4 items”. Neither of the two destructive acts can reach anything that is not already in here, so nothing in this app can be destroyed in one step. It is in the profile menu and the command palette rather than the sidebar, but the way you will actually get here is the Undo on the toast, or the quiet line under each list saying that kind has something in the bin.

​
CRM

/crm/companies, /crm/contacts, and a page per record Two filterable lists. Companies shows when you last applied and what is still live, with its industries and locations as labels; contacts shows who is attached to what, with each person’s tags and the mark of whichever platform they actually answer on. Both filter — to the companies where you know someone, to the people whose ping is due — and the search box matches tag names as well as everything else. Behind the Filter button is everything a chip row cannot hold: industry, size, location and tags on companies; tags, company and “nothing logged for” on people; and on both, the gaps worth fixing in one sitting — no website, no email, filed under nothing. It opens on those dimensions rather than on every value at once, so you pick Industry and then pick an industry; typing searches across all of them together. Dimensions AND with each other and OR inside themselves, and every count is counted against the rows the other filters left. Sorting is the column headings, or the Sort control beside the filter, which lists every key — including the ones whose column is hidden on a narrow screen, where the headings are not there to click. Dragging the divider between two headings sets their widths; those are saved to your profile rather than the URL, so the list looks the same wherever you open it. Tick rows and a bar appears: tag all of them, put all of them on the chase list, export just those, or delete them. Each list exports on its own too, and what comes out is what you were looking at — same filters, same search, same order. A company page carries its details, its research notes, every application you have there and every contact who works there. Industry, size, location and its own tags are pickers: tick to attach, type to create, recolour, delete. A contact page carries their details, their tags, their links 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

One row per thing wired to your workspace, each saying whether it is on and whether it needs you. Open one for its URL, setup steps, test, rename, rotate, disconnect — or, for a mail and calendar account — Google, Microsoft 365, or IMAP and CalDAV — to test, reconnect and disconnect. Connect opens a library of everything you can add, assistants on one tab and accounts on the other, with what you already have marked as connected. Plus 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 →