How to Use Notion for a Job Search

Build one Jobs database

Create a single database called Jobs, with one row per role. Add only the properties that answer practical questions:

• Company
• Role
• Status
• Application date
• Next action
• Next action date
• Recruiter
• Salary range
• Job posting link

Use a Select property for Status with stages such as Saved, Applied, Interviewing, Offer, and Closed.

Use a table for the whole search, a board grouped by Status to see movement, and a calendar for interviews and follow-up dates. The database should reveal which applications need action, which interviews are next, and which roles still deserve attention.

If updating a role takes several clicks, remove properties until the routine feels easy.

Give each company one working page

Open every database row as a page. Keep:

• The job description
• Recruiter and interviewer names
• Questions to ask
• Interview notes
• Salary information
• Short company research
• The next action

Paste the job description into the page because the original listing may disappear, but retain its link. Do not build a scrapbook; save only material that could change how you prepare, answer, or decide.

This matters because job postings become difficult to compare when you remember an unusual take-home assignment or remote arrangement rather than the official title.

Capture research while it still has context

Company research may arrive through Glassdoor, LinkedIn, Reddit, interview reports, recruiter messages, and email. Add anything important to the company page with one sentence explaining why:

• Former PM says the technical screen includes a workflow exercise.
• Several reviews mention slow decisions between product and engineering.
• Recruiter says the hiring manager values marketplace experience.

A plain-language sentence is more useful than a generic “Research” tag. Add context beside screenshots too; an unexplained image becomes difficult to identify on a crowded page. This prevents company pages becoming another bookmark graveyard.

Separate the pipeline from the research archive

Notion is strongest when information has clear fields and states. Application status, dates, and recruiter names fit that model.

Scattered screenshots, browser bookmarks, and social posts are harder. Search works when you remember the words in the note, but on interview morning you may remember only the idea. You might search “deploy cadence” while the review said “shipping rhythm.” That is why search by meaning matters.

Either copy important material into Notion and summarize it, or keep a searchable archive for raw research while Notion remains the tracker. dEssence can save articles, videos, PDFs, screenshots, and product pages through the Chrome extension, Telegram bot, or web app at dessence.ai, then retrieve them from questions in your own words.

The layers have separate jobs: Notion tells you what is happening with the application; the archive recovers what you learned about the company.

Make an interview-preparation view

Create a linked view of Jobs filtered to Status is Interviewing. Show Company, Role, Next action date, Interview stage, and Recruiter. Sort by the next action date and open the company page from this view.

Before each interview, reduce the page to five scannable blocks rather than writing a polished company essay:

1. What the company does
2. Why the role fits you
3. Evidence from your experience
4. Questions for the interviewer
5. Details recovered from research

Track people without building another CRM

For a small search, keep recruiters and contacts as text fields in Jobs. Create a Contacts database only when the same people connect you to several roles or companies. Store name, company, relationship, last-contact date, and next action, then relate contacts to relevant jobs.

Write personal context immediately after each conversation. Details stay useful only when attached to the person; the same principle helps recruiters who need to remember candidates and conversations.

Run a short weekly reset

Once a week:

• Update stale statuses.
• Add follow-up dates.
• Close inactive roles.
• Check that each upcoming interview has a preparation page.
• Move loose company notes into the correct row.

Do not spend the review reorganizing old material. Saving more does not create better recall—the hard-drive fallacy applies here too.

Your setup works when it shows the next action and brings the right company context into view before an interview. If maintaining it becomes a separate project, simplify the database before adding another template.