# Hired

> Hired is a career operating system you host yourself: a brain of everything you have done, a resume builder that assembles documents from it, and a pipeline for the search — all of it reachable from the assistant you already talk to.

- [Hired](https://docs.hired.tools/index.md): An applicant tracking system, for applicants. A career brain, a resume builder and a job-search CRM you host yourself, wired into the assistant you already talk to.
- [Your first ten minutes](https://docs.hired.tools/quickstart.md): Connect an assistant, teach it the rules, fill the brain, build the first resume. In that order — the order is the whole trick.
- [Connect an assistant](https://docs.hired.tools/connect.md): One URL, pasted once per client. Exact steps for Claude, Claude Code, ChatGPT, Cursor, VS Code, Windsurf, and anything else that speaks MCP.
- [Install the skills](https://docs.hired.tools/skills.md): Three files that teach an assistant the rules of this place before you have to. Where each client wants them, and what each one carries.
- [How it all fits together](https://docs.hired.tools/concepts/how-it-fits.md): Four areas, and which direction the arrows point between them. Read this once and the rest of the manual stops needing explanation.
- [The brain](https://docs.hired.tools/concepts/brain.md): Everything you know about your own career, stored raw and searched rather than read. Roles, brain dumps, highlights, notes, standing rules and the four supporting collections.
- [Resumes](https://docs.hired.tools/concepts/resumes.md): One flat JSON document, five templates, the Harvard OCS format by default. What the contract looks like, how the editor behaves, and why every field has a default.
- [The pipeline](https://docs.hired.tools/concepts/pipeline.md): Ten stages including four different endings, an activity timeline, tasks, follow-up dates that set themselves, saved views, and a read-only link for whoever is helping you.
- [Companies and contacts](https://docs.hired.tools/concepts/crm.md): The people and organisations behind the applications, as records in their own right — with research notes that survive the search and timelines of their own.
- [Filling the brain](https://docs.hired.tools/guides/fill-the-brain.md): How to get twenty years of work into a system in an afternoon, what actually belongs in a brain dump, and how to keep it current without it becoming a chore.
- [Tailoring a resume](https://docs.hired.tools/guides/tailor-a-resume.md): Reading a posting for what it actually rewards, mining the brain for real evidence, and writing bullets that survive the follow-up question.
- [Publishing and exporting](https://docs.hired.tools/guides/publish-and-export.md): A real PDF for the forms that want a file, an unlisted link for the ones that want a URL, and exactly what each one exposes.
- [Running the search](https://docs.hired.tools/guides/run-the-search.md): Capturing a posting, logging what happened, and chasing what is due — done by talking about your week rather than by maintaining a spreadsheet.
- [Research and interview prep](https://docs.hired.tools/guides/research-and-prep.md): Building a company record that is worth reading the night before, and turning it into a prep sheet the morning of.
- [The weekly review](https://docs.hired.tools/guides/weekly-review.md): Ten minutes that tell you which part of your search is broken, rather than how many applications you sent.
- [What to say](https://docs.hired.tools/guides/what-to-say.md): A phrasebook. The sentences that get you what you meant, grouped by what you are trying to do.
- [The eight workflows](https://docs.hired.tools/workflows.md): Multi-step jobs that come with every connection. Every one arrives as an ordinary tool, and as a slash command too in the clients that render MCP prompts.
- [The web app](https://docs.hired.tools/app.md): A tour of every screen: what it shows, what you can do there directly, and which parts are deliberately browser-only.
- [Security and privacy](https://docs.hired.tools/reference/security.md): What one person can and cannot see of another, what a connection token grants, what an unlisted link exposes, and what is deliberately not built.
- [Troubleshooting](https://docs.hired.tools/reference/troubleshooting.md): The failures people actually hit, and the first thing to check for each.
- [Questions](https://docs.hired.tools/reference/faq.md): The things people ask before deciding whether to use this.
- [How tools work](https://docs.hired.tools/tools/overview.md): What a connected assistant can see, how the counts break down, what the annotations mean, and the conventions every tool in Hired follows.
- [Brain tools](https://docs.hired.tools/tools/brain.md): Twenty-two tools over roles, brain dumps, highlights, notes, standing rules and the four supporting collections.
- [Resume tools](https://docs.hired.tools/tools/resumes.md): Eleven tools for writing documents, checking their length before saving, publishing them to a link and exporting real PDFs.
- [Pipeline tools](https://docs.hired.tools/tools/pipeline.md): Twenty-seven tools over applications, stages, the activity timeline, tasks, follow-ups, saved views, sharing and diagnosis.
- [CRM tools](https://docs.hired.tools/tools/crm.md): Twelve tools over the companies you are talking to and the people at them, including their own timelines and ping dates.
- [Account and connection tools](https://docs.hired.tools/tools/connections.md): Six tools for finding out who a connection belongs to, and for managing the wiring itself without opening a browser.
- [Admin tools](https://docs.hired.tools/tools/admin.md): Twenty-nine tools for running an instance: accounts, invitations, the waitlist, sign-in, email, billing, health and every stored setting.
- [Deploy it](https://docs.hired.tools/self-hosting/overview.md): One required environment variable, migrations applied on boot, and an owner account the app creates for itself. Docker, Railway or a laptop.
- [Self-host with Docker](https://docs.hired.tools/self-hosting/docker.md): One command. It pulls the published image, starts a Postgres alongside it, applies migrations and prints your password.
- [Self-host on Railway](https://docs.hired.tools/self-hosting/railway.md): Five minutes, one variable, no terminal. The app provisions itself on first boot.
- [Running it locally](https://docs.hired.tools/self-hosting/local.md): Node 20 or newer, a Postgres, and four commands.
- [Configuration](https://docs.hired.tools/self-hosting/configuration.md): Everything an instance can be configured with lives in the database, not in environment variables. One screen, one tool, and it takes effect on the next request.
- [Setting up email](https://docs.hired.tools/self-hosting/email.md): Resend, four steps, and a test send that tells you the exact reason when it fails. Optional — nothing is blocked on it.
- [Google sign-in](https://docs.hired.tools/self-hosting/google.md): A Continue with Google button on the sign-in page, who it lets in, and the one setting that decides whether strangers can create accounts.
- [PDF export](https://docs.hired.tools/self-hosting/pdf.md): What the renderer needs, which hosts already have it, and the fallback that produces the same document where they do not.
- [Charging for it](https://docs.hired.tools/self-hosting/billing.md): Optional. If you host an instance for other people and want them to pay for it, this is the Stripe wiring — and the deliberate gap in it.
- [Upgrading and backups](https://docs.hired.tools/self-hosting/upgrading.md): Migrations run themselves on boot, so upgrading is pulling a new image. Backing up is one pg_dump.
- [People and invitations](https://docs.hired.tools/administration/people.md): Three roles, invitations that work before email does, and the hard line between managing accounts and reading content.
- [The waitlist](https://docs.hired.tools/administration/waitlist.md): An open endpoint a static landing page can post to, a queue you review, and one click that turns a request into an invitation.
- [Health and errors](https://docs.hired.tools/administration/health.md): One tool that tells you whether the instance is working, and one that tells you what failed. Neither can see anyone's content.