Skip to main content
Hired is four areas that only make sense as a chain. Material flows one way: what you did becomes evidence, evidence becomes a document, the document goes out to a company, and what happens next comes back as a record. The loop at the end is the part people miss. An interview that went well is not just a stage change — it is new material about you, and it belongs back in the brain so the next resume is better than this one.

The four areas

Brain

Everything you know about your own career, stored raw. Roles hold an unlimited free-form brain dump plus polished reusable bullets called highlights. There are also notes, projects, education, skills and certifications.

Resumes

Documents assembled from that material. One JSON contract shared by the editor, the renderer and the tools, so a half-written document still renders.

Pipeline

Applications through ten stages, with an activity timeline, tasks, and follow-up dates that set themselves when a stage changes.

CRM

Companies and the people at them, as records in their own right — with their own research notes and their own timelines.

The vocabulary

These words mean something specific here. Using them gets you what you meant.

Two rules that explain most surprises

Some tools replace, some append

This is the single most important mechanical fact about the product, because getting it wrong deletes work silently. The rule an assistant is given: read first, modify, write back whole. When somebody tells it something new about a job already on file, that is append_role_brain_dump — not update_role.

Isolation is not a setting

Every workspace is private, and that is a property of the code rather than a permission you can misconfigure. Every function that touches content takes the owning account as its first required argument, and every query filters on it, so a call site that forgot is a call site that does not compile. Admins manage accounts — invitations, suspensions, password resets, instance configuration. There is no path, through the app or through an assistant, from an admin to another person’s brain, resumes or applications. The full security model →

Where the work actually happens

Both surfaces run on exactly one implementation of every rule, so anything an assistant writes shows up in the app immediately, and anything you edit in the app is what the assistant reads next.

In conversation

Everything. Every capability in the product is reachable as a tool — that is the project’s own rule, and a feature is not considered finished until it is.

In the browser

The direct-manipulation half: dragging a card between stages, typing into the resume editor, looking at the paper, printing the page.