The right use case
Notion resumes are great as the portfolio link you drop in LinkedIn, a cover letter, or a recruiter DM. They are terrible as the PDF you upload to an ATS. Use both: Notion for the story, PDF for the application form. This guide builds the Notion half.
A Notion resume is a public page on Notion.so (or a custom domain) that combines a traditional resume layout with portfolio-style project write-ups, embedded demos, and long-form case studies. At its best, it reads like a tiny personal website without the cost or build time. At its worst, it is a disorganised Notion page with 40 emoji and no structure.
The pattern that works: keep the top of the page short and resume-like (3-column contact, summary toggle, clean experience list) so a skim reader registers the basics in 10 seconds. Put portfolio depth below the fold as an inline database of projects, each one clickable to a full case-study sub-page. Visitors who want to go deep can; visitors who do not, stay on the top.
8 blocks every Notion resume needs
Cover block (callout)
A full-width callout at the top with your name, target role, and one-line positioning statement. Use a single emoji (avoid more, one is tasteful, three is spam).
Contact row (3-column)
Email, phone, city on one row. Use Notion columns (type /columns) to align cleanly. Add icon prefixes from the Notion icon set or keep plain text.
Summary toggle
A toggle block labelled "Summary" with 2 to 3 sentences inside. Toggles save space on the live page and keep the overview tidy; recruiters click to expand.
Experience database
Create an inline database (not a page, a database). Properties: Role (title), Company (text), Start (date), End (date), Tags (multi-select for stack). View: gallery or timeline.
Project gallery
Second inline database with cover images. Each project page holds the write-up, screenshots, and a live demo link. Gallery view with large cards reads best on desktop.
Skills matrix
Use a simple 3-column table: language / framework / level. Keep it to 8 to 10 rows, not a laundry list. Frames competence without bloat.
Education and certifications
A plain list or a small table. Keep to the last 2 entries; do not expand on high school unless you are a fresher.
Footer (testimonials)
If you have 2 or 3 short quotes from past managers or clients, a clean quote block at the bottom lifts the whole page. Skip if you do not have them; fake testimonials read immediately.
5 things Notion does better than a PDF
Shareable single URL
One link covers the resume, portfolio, and long-form case studies. Recruiters clicking through LinkedIn see everything without a download.
Rich media (video, GIF, embeds)
Embed Figma files, Loom walkthroughs, Codesandbox demos inline. Especially strong for designers, PMs, and devs with shippable UI work.
Always up to date
One edit propagates everywhere the link lives. No PDF version drift, no "resume_final_v3_reallyfinal.pdf" problem.
Sub-page hierarchy for deep dives
Each project card opens a full write-up page. Hirers who want depth get it; hirers who only skim stay on the top page. Self-selecting read depth.
Custom domain via Super or Fruition
Point yourname.com at your Notion page using Super.so or the open-source Fruition proxy. Looks like a static site, content stays in Notion.
5 things Notion does worse than a PDF
ATS will not parse it
Notion pages are dynamic HTML. Applicant tracking systems expect a PDF or DOCX. You will still need a PDF export for every formal application.
No print control
Notion's PDF export is lossy: margins shift, columns break, fonts substitute. Do not rely on it as your application PDF. Use a proper builder for that.
Cannot password-protect on free tier
Anyone with the URL can read. If you include sensitive work (client names, salary figures), keep them in a sub-page and share that privately.
Search engines index public pages
By default, a public Notion page is crawlable. Future employers may find your resume from 2 jobs ago. Toggle search indexing off in Share settings if you want to limit this.
Design ceiling
Notion is flexible but not infinitely so. If you need tight pixel-level control (design leads, art directors), you will hit the ceiling fast. Treat Notion as a portfolio surface, not a replacement for Figma or Webflow.
7-step setup (start to publish)
1. Duplicate a base template
Start from a clean duplicate of a community template (search "resume" in Notion's template gallery) or start blank. Starting blank wastes 45 minutes reinventing layout.
2. Set page width to wide and full width off
Wide reads best on desktop. Full width stretches too far on 27-inch monitors. Toggle in the top-right menu.
3. Add cover image and icon
Upload a personal cover (1500x600 px) and a 48x48 icon. Avoid stock photography; an abstract gradient or your own photo works better.
4. Build the experience database
Type /database inline and add properties. Switch to gallery view, card size small, and hide properties that are not primary (like internal tags).
5. Build the project database with cover images
Each project gets a cover image, a 1-line description, and an "Open" link to the full sub-page. Card size medium or large for readability.
6. Share public with link, disable search indexing
Share, publish to web, turn off search indexing and allow edits. Copy the URL and bit.ly-shorten it for your LinkedIn and business card.
7. Export a PDF for formal applications
Do not submit the Notion page to job boards. Use ResumeBuildz or a similar tool for the PDF, and link your Notion URL in the summary line as "portfolio at yourname.notion.site".
Designer vs developer layouts
Designers lean visual: larger cover images, gallery view for projects with card size large, Figma embeds on every project sub-page, one or two case-study walkthroughs at the top. Keep text minimal on the landing page; let the work do the talking.
Developers lean structural: code-block syntax highlighting on project sub-pages, GitHub embeds, clear stack tags on each project, a skills matrix that names specific frameworks over generic skills. A developer Notion page reads more like a READMEthan a portfolio site, and that is the point.
Pair Notion with a real PDF resume
The workflow that wins: build both. Use a dedicated resume builder (ResumeBuildz, Teal, Rezi) to produce a 1-page ATS-clean PDF for every formal application. Use Notion for the public portfolio that you link from the top of the PDF and from LinkedIn.
A recruiter who wants a 10-second skim gets the PDF. A hiring manager who wants to understand your depth clicks through to Notion. The PDF passes the ATS. The Notion page converts the interest into a call. Each surface does what it is good at.
External references
Frequently asked questions
Can I submit a Notion resume to an ATS?+
Is a Notion resume free?+
Does Notion work for non-tech roles?+
Can I password-protect my Notion resume?+
How do I customise fonts on a Notion page?+
Will recruiters click a Notion link?+
How long should my Notion resume be?+
Build the ATS-clean PDF your Notion page links to
ResumeBuildz produces the 1-page PDF that passes ATS, while your Notion page handles the portfolio story. Each tool where it shines.