The recruiter calls Tuesday morning. They're checking in about the role you applied for two weeks ago. You can't remember which company it was, what level they listed, or which version of your resume you sent. You stall, ask if you can call back, and spend the next ten minutes scrolling through your sent folder trying to reconstruct the application.
Job searches and career transitions are the same shape: too many small inputs over too many weeks. Listings, applications, recruiter calls, prep notes, interview rounds, follow-ups, the recurring question of what do I actually want. By the third or fourth round, the picture is fragmented across email, LinkedIn, a spreadsheet you started Sunday, and the part of your brain that's stretched thin from also doing your current job.
A vault that holds one page per company, with the application material, the conversation log, and your honest take on each step, makes the search feel like one project instead of thirty. (For the underlying decision-making shape applied to any major life choice, Capture and Compare Options for Any Major Decision is the matching guide.)
One page per company, plus a parent page for the search
In a markdown vault like Docapybara, each company you're considering gets its own page. Pages nest with no depth limit, so under each company you can keep child pages for the Job description, Recruiter notes, Application materials, Interview prep, Interview notes, and Decision. Above all of them sits a Job search parent page that holds the broader strategy and the comparison view.
The structure stays light early — when you're just sniffing around, a company page might be three sentences. As things get serious, the page grows. The vault doesn't force you to fill out a template before you've even decided whether you're interested.
A "what I actually want" page that comes first
Before any application, the most useful page is one called What I actually want. Two or three paragraphs on what you'd take, what you'd refuse, what you'd negotiate hard for, and what you're afraid of repeating from your current role.
This page exists to keep the search honest. Every job search drifts — you start clear-eyed about wanting smaller teams and end up considering a 10,000-person company because the recruiter is friendly and the salary is higher. The drift isn't necessarily wrong, but you should notice it. The What I actually want page lets you compare every offer back to the version of yourself who started.
Update it as the search progresses. The first version, written in week one, is often more honest than week six. Both versions are useful. "My November draft of what I wanted vs my January draft — what changed?" The agent reads both and tells you. Sometimes the change is real growth in your thinking; sometimes it's signs you're rationalizing.
For career transitions specifically — moving from one industry to another, leaving consulting to start something, going from IC to management — this page is what keeps you from accepting a job that's structurally the same as the one you're trying to leave.
A pipeline that doesn't pretend to be a CRM
You don't need a real CRM for this. An inline :::database::: directive on the Job search parent page works as a simple pipeline — columns for company, role, source (recruiter / referral / cold apply), status, last contact date, and a note on what's next.
Six column types are available — text, numbers, dates, checkboxes, single-select, multi-select — so you can mix prose with categorical fields like interest level and stage without forcing every entry into the same shape.
The agent maintains it. "Add Acme Corp — senior PM role, came in via Sarah's referral, status applied, last contact today. Next: follow up if I don't hear back by Friday." Row appears.
When the pipeline gets crowded, ask for a focused view: "Show me everything in 'phone screen' or later, sorted by last contact date — anything that needs a follow-up?" Or: "List the companies I rated 8 or higher on interest, regardless of status."
For longer searches that span months, the same pipeline is also a useful retrospective. "Of the companies I applied to, which sources generated the most phone screens — referrals, cold applications, or recruiters?"
Application materials that don't get lost
Most applications need a slightly different resume and a tailored cover letter. Most people end up with seven versions of each in a folder, none of them clearly labeled, and they lose track of what they sent where.
A Materials child page under each company holds the version you sent. Drop the resume PDF and the cover letter as plain markdown on the page. PDFs are auto-converted to markdown so the agent can read them as searchable text — useful when you're prepping for an interview and want to remember exactly what you said.
For drafting the materials, the agent helps. "Read the job description for Acme and the version of my resume I sent to Globex last month. Draft a tailored cover letter that emphasizes the relevant experience." You get a starting draft grounded in your actual past materials, not a generic template.
When the agent drafts something, your Materials page captures the version you actually used — including whatever edits you made. So a year later, when you're applying somewhere similar, you can reuse the version that already worked.
Recruiter and conversation notes that survive the next call
Every recruiter call produces a small amount of useful information that tends to evaporate. The salary band they hinted at. The role they said you should also look at. The thing they mentioned about the team's reorg that you weren't supposed to know.
Voice is the right capture tool right after the call. "Just got off with Maya at Acme. Salary band she hinted at is 180-220 plus equity. She said the role might also flex into a staff PM seat depending on level. Mentioned the team is restructuring under a new VP — worth asking about in the next round." Forty seconds, transcribed onto the company's Recruiter notes page with a timestamp.
For longer calls — a forty-minute initial conversation with a recruiter — record it (with permission). The transcription comes back with speaker labels, so you can see what they said versus what you said. Useful when you're trying to remember whether you committed to anything specific.
The agent can pull the conversation history when you need it. "Summarize my conversation history with Acme — every call, every email, what's been said about salary, level, and the team." You walk into the next round with the full picture instead of the impression you've been carrying.
Interview prep that compounds across companies
Interview prep is one of the most leveraged uses of a vault, because most of what you prepare for one interview is reusable.
A Interview prep page (under the Job search parent, not under any specific company) can hold your stories — the times you led through ambiguity, the times you disagreed with a manager, the times something failed and what you learned. Write each one out once; reuse across companies.
The agent can adapt them: "Read the Acme job description, look at my prepared stories, and tell me which three stories best match what they're looking for in this role." Or: "For the Globex interview, draft answers to the five most common behavioural questions, drawing on my prepared stories where they fit."
For technical or domain-specific interviews — case studies, take-homes, system design — drop the practice problems you've worked through on a Practice child page. The agent can find a similar one when needed.
For the company-specific prep — what's their recent product news, who's the hiring manager, what's the team's reputation — the agent's web_search tool can pull current information into the page. "Find what's been written about Acme's product launches in the last six months." Comes back with sources. (Hiring managers running the other side of this loop hit a similar shape — see How to Use AI Notes for Hiring.)
Interview notes that capture what was actually said
Right after each interview round, capture before the impressions decay. Voice for ten minutes works — talk through who was in the room, what they asked, what you said, what you wish you'd said, what you noticed about the team's vibe.
The transcription lands on a Interview notes page under the company. The agent can pull patterns across rounds: "Summarize all my interview notes for Acme. What's consistent across the panel — what do they seem to care about, what concerns came up more than once, where did I struggle?"
For follow-up emails, the agent drafts: "Read the interview notes from this morning's round. Draft a short follow-up email to the hiring manager that references the part of the conversation about the team's roadmap." The email comes back specific, not generic — because it's grounded in your actual notes.
For the final-round decision, the same notes are gold. You can read across every round and see whether the picture got clearer or murkier. Murkier is a signal; clearer is a signal too.
Offer comparison and the honest decision page
When the offers come in, the comparison gets real. Each offer letter is a PDF; drop it on the company page and the agent reads it. "Compare the offer from Acme and the offer from Globex side by side — base, equity vesting, bonus structure, severance, total comp at year three."
A Comparison page under Job search holds the side-by-side. An inline database with columns for total comp, role, level, team, manager you'd report to, your honest interest level, and what worries you about each.
The honest decision page — the same shape as the Capture and compare options for any major decision shape — holds your real take on each offer. What I actually think about Acme. What I actually think about Globex. What I'm afraid I'd regret. Not the spreadsheet version. The honest version.
When you're ready to decide, ask the agent: "Read the 'what I actually think' paragraphs and the comparison. Summarize the leanings." You get a reflection of your own thinking that's harder to dismiss than gut feel.
A starter shape that works on day one
If you're starting a job search today, here's where to begin:
- Job search — one parent page.
- What I actually want — one page, written before any applications.
- Pipeline — one page with the inline database, fed as you apply.
- Interview prep — one page with your reusable stories.
- For each company you're seriously considering — one child page, with sub-pages as needed.
That's enough structure. The vault grows with the search; you don't have to set up everything upfront.
For career transitions specifically — leaving a field, starting something new, taking time off — the same shape works with one extra page: Transition reasoning, where you write down honestly why you're considering this and what success would look like a year out. That page is your anchor when the search gets long and the doubts arrive. (For learning the new field itself, AI Notes for Learning a New Skill is the next step.)
The point isn't to professionalize your job search. It's that when the next recruiter calls Tuesday morning, you have the full picture in one searchable place — and when an offer is finally in front of you, you're choosing with a clear head instead of a tired one.
Try Docapybara free. Start with the what I actually want page tonight, and see how much clearer the next conversation feels.