Berkeley students breaking into Notion PM career path and interview prep

Notion hires PMs from Berkeley, but not because of brand name—it’s because specific students master the unspoken product thinking culture at Notion: collaborative, user-obsessed, and deeply iterative.

Title: Berkeley students breaking into Notion PM career path and interview prep

TL;DR

The real pipeline isn’t career fairs; it’s Haas founder circles, intern referrals from past PMs at Notion, and stealth prep using Cal Hacks and BCPI to build portfolio-grade projects that mirror Notion’s product ethos. Most Berkeley applicants fail not from lack of smarts, but from treating Notion like a FAANG—this is not a company that rewards polished, rehearsed answers, but raw, user-centered reasoning with a hacker’s instinct for workflow design.

Who This Is For

You're a UC Berkeley student—undergrad or master’s—in EECS, Data Science, or MBA—actively building products, not just listing “product interest” on your resume. You’ve shipped a side project using Notion APIs or built a workflow tool for a student org, and you’re targeting early-career PM roles (Associate PM, Rotational PM, or New Grad PM) at product-led SaaS companies. You know Notion isn’t Google or Meta, and you’re drawn to their small PM team, deep design collaboration, and founder-like autonomy.

You’re not just looking for a PM job—you want this PM job. If your plan is “apply online and hope,” stop. This guide is for the 10% who treat the Berkeley-to-Notion path like a product launch: intentional, iterative, and referral-powered.

How does Berkeley feed into Notion PM hiring?

Notion doesn’t run on-campus recruiting at Berkeley for PM roles. They don’t sponsor H-1B visas for new grads, and they’re not chasing top 5% GPAs. That doesn’t mean Berkeley students don’t get in—it means the path is curated, not conventional.

The true pipeline begins in three places:

Cal Hacks and BCPI (Berkeley Center for Product Innovation) – Notion PMs regularly judge these events. In 2023, a student who built a collaborative syllabus tool at Cal Hacks 10 was recruited directly by a Notion PM who saw the demo. The tool used Notion’s API to auto-generate course templates—mirroring Notion’s own “building blocks” philosophy.
Berkeley-Haas founder network – Notion’s early DNA was shaped by YC and founder-led product development. Berkeley students who interned at YC startups (especially workflow tools like Coda, Linear, or Airtable) and later joined Notion via lateral PM moves. One current Notion PM interned at Notion’s competitor Slab via a Haas alum referral, shipped a feature mimicking Notion’s toggle lists, then was headhunted.
Internal referrals from Berkeley engineers at Notion – There are currently 17 Berkeley grads in engineering at Notion (LinkedIn, Oct 2023). When they recommend a PM candidate, especially one with shared project history (e.g., Hackathon teammates, CS 169 group projects), the resume bypasses recruiter screens.

Notion’s PM hiring is not GPA-obsessed, but impact-obsessed. They care whether you changed behavior, not whether you got an A in CS 61B. A student who automated club onboarding for Cal Blueprint using Notion forms and Zapier got more attention than a candidate with Meta internship but no personal projects.

Bottom line: Notion isn’t recruiting Berkeley. They’re recruiting builders who happen to be at Berkeley. The school is a feeder not by brand, but by culture—Berkeley’s hacker ethos aligns with Notion’s “tinker, ship, repeat” mindset.

What do Notion PMs actually do—and how does Berkeley prepare students for it?

Notion PMs don’t just define roadmaps—they co-create products with design and eng from day one. They sit in on user interviews, prototype in Figma, and write SQL to analyze feature adoption. The role is not about stakeholder management or PowerPoint decks—it’s about being the customer’s proxy while moving fast in a small team.

Berkeley prepares students for this—if they pick the right classes and projects.

Take CS 169 (Software Engineering): Most students treat it as a coding class. But the students who win PM roles don’t just build the MVP—they define user stories with real pain points, run usability tests, and iterate based on feedback. One student team built a shared lab notebook app for science majors; they interviewed 30 users, used Notion as a proto-MVP, then rebuilt in React. Two team members are now at Notion—one as a PM, one as an engineer.

Or IEOR 130 (Manufacturing Systems): Sounds unrelated? Not for PMs who think about workflow efficiency. One PM candidate used IEOR 130’s cycle time analysis to optimize onboarding for a student-run tutoring app—then applied that same logic in the interview to improve Notion’s template gallery discovery.

Berkeley also offers Design 177 (Design for AI) and Info 254 (HCI in Practice)—classes where students don’t just learn design thinking, but apply it in high-fidelity prototypes. These are gold for Notion interviews, where you’ll be asked to redesign a feature in real time using Figma or paper.

But not all Berkeley prep is academic. The best candidates have built in public. One student ran a Substack called Notion for Students, reverse-engineering Notion’s UX decisions and proposing alternatives. Another open-sourced a Notion API wrapper for campus clubs. Notion PMs follow these—quietly. They’re not looking for sycophants, but for people who think like them.

Berkeley doesn’t teach “PM skills” in a vacuum. It teaches systems thinking, rapid iteration, and user empathy—if you take the right path. The students who succeed aren’t those who joined PM clubs and networked. They’re those who treated every class project as a startup.

How do Berkeley students land interviews at Notion?

You won’t get a Notion PM interview from LinkedIn or Handshake. The inbound funnel is nearly closed. Interviews come from: referrals, competitions, and strategic cold outreach.

Referrals are king. But not the “Hey can you refer me?” type. The effective referrals come from shared context. A Cal Hacks teammate now at Notion will refer you not because you asked, but because you shipped something together. One student got referred after building a hackathon project that used Notion as a backend—his teammate later joined Notion’s API team.

Hackathons are the backdoor. Notion PMs and engineers judge Cal Hacks, Greylock Hack, and BCPI challenges. Winning isn’t required—just shipping something Notion-esque. In 2022, a team built “StudyFlow,” a Notion-based study planner with embedded Pomodoro timers and progress tracking. They didn’t win, but a Notion PM DM’d them post-event. Two were hired within 6 months—one in eng, one in PM.

Cold outreach that works is specific, not generic. A student who analyzed Notion’s mobile onboarding funnel using Hotjar-style heatmaps (on a dummy account) sent a 3-slide deck to a PM on LinkedIn: “Here’s where users drop off, and here’s a prototype fix.” The PM replied, “This is what we’re working on. Let’s chat.” That turned into an internship.

What doesn’t work:

Applying online with a generic PM resume
Attending “Tech at Notion” info sessions and asking surface questions
Saying “I love Notion” without dissecting why their UX works

Notion’s hiring bar is high, but not because they want ex-FAANG talent. They want people who already think like Notion PMs—and Berkeley students who build in public, compete in the right events, and create leverage through shared projects are the ones who get pulled in.

What’s the real Notion PM interview process—and how should Berkeley students prep?

Forget behavioral-heavy Meta loops or system design marathons. Notion’s PM interview is product sense, user empathy, and execution clarity—all tested in realistic scenarios.

The process:

Recruiter screen (30 min) – Filter for motivation and fit. They’ll ask, “Why Notion?” If you say “I use it every day,” you’re out. If you say, “I analyzed how template defaults shape user behavior, and I think the blank slate problem is under-addressed,” you’re in.
Product exercise (take-home, 2–3 hours) – Example: “Design a feature to help remote teams manage async standups in Notion.” They’re not grading Figma skills. They’re grading: Did you define the user? Did you consider edge cases? Did you tie it to business goals?
Onsite (4 rounds):

Product sense (45 min) – “How would you improve Notion’s mobile search?” Expect to sketch flows, debate tradeoffs, and justify decisions with user logic—not metrics.
Execution (45 min) – “You launched a new AI summarization feature. Adoption is low. Diagnose.” They want root cause analysis, not just “we need better marketing.”
Leadership & collaboration (45 min) – “How would you handle a designer who disagrees with your prioritization?” Notion values humility and co-ownership.
Value alignment (30 min) – “Tell me about a time you shipped something fast with incomplete data.” This is where your hackathon or BCPI project shines.

Berkeley students prep wrong when they:

Over-prepare frameworks (like CIRCLES or AARM) — Notion doesn’t want cookie-cutter answers
Focus on metrics over user stories — this is a UX-driven company
Practice with generic PM books — the context is missing

The right prep:

Use real Notion features as case studies. Pick one—like template recommendations—and write a 1-pager: user problem, solution, tradeoffs.
Practice aloud with a timer. Record yourself answering “How would you improve Notion for students?” Listen for fluff. Cut it.
Do mock interviews with PMs who’ve been through it. Notion’s process is unique. Use Exponent or PM Interview Playbook for realistic mocks tailored to Notion’s style—not generic FAANG prep.

One Berkeley student prepped by rebuilding Notion’s sidebar navigation in Figma and writing a 500-word rationale. He used it in the interview. He got the offer.

How can Berkeley students use alumni and campus resources to break into Notion?

Notion doesn’t have a “Berkeley alumni group.” But Berkeley students do have access to the right people—if they’re strategic.

Key levers:

Haas alumni in YC startups – Notion is YC alumni (W14). Berkeley MBA and undergrad founders in YC batches (like Deel, Ironclad) often know Notion PMs. One student cold-emailed a Haas alum at Coda (also YC) and asked for an intro to a Notion PM. Got it. Landed coffee chat.
BCPI mentor network – BCPI has ex-PMs from Atlassian, Slack, Notion. They’re not always listed publicly. Ask the program director for “PM mentors who work in collaborative tools.” One student got paired with a Notion PM who’d gone through BCPI’s predecessor program.
CS 169 and Info 159 TAs – Many are ex-Notion or ex-Coda engineers. They don’t advertise it. But if you stay late after lab and ask, “What’s it like building workflow tools at scale?” you might get an ear. One TA referred a student after seeing their final project on task dependency graphs.
Cal Hacks Slack and Notion – Yes, Cal Hacks uses Notion. Join the 2023–2024 organizer team. You’ll meet sponsors—including Notion engineers. One organizer was invited to a “builder dinner” in SF, met a PM, and got fast-tracked.

The mistake? Thinking alumni = LinkedIn outreach. The win? Shared work product. One student didn’t just ask for advice—she shared her Notion template for hackathon ideation, tagged a Notion PM in a post, and said, “Built this inspired by your team’s blog on modular thinking.” He replied, “This is cool. Want to chat?”

Berkeley’s advantage isn’t its name. It’s its density of builders. Tap into that. Contribute first. Ask later.

Preparation Checklist

Ship a project using Notion’s API or ecosystem – Build a tool for students, clubs, or personal use. Open-source it or write about it.
Compete in Cal Hacks or a BCPI challenge – Focus on workflow, collaboration, or productivity tools. Even if you don’t win, ship.
Take Info 254 or Design 177 – These hands-on design classes give you real artifacts for portfolio discussions.
Reverse-engineer a Notion feature – Write a public analysis: “Why Notion’s toggle lists work,” or “How template defaults drive onboarding.”
Use PM Interview Playbook for Notion-specific mock interviews – Practice live with realistic scenarios, not hypotheticals.
Get a referral through shared context – Don’t ask cold. Build something first, then connect.
Run a user test on your own project – Notion PMs love customer empathy. Show that you test, not assume.

Mistakes to Avoid

BAD: Applying online with a resume that says “Passionate about product” and lists a semester-long PM club project.
GOOD: Applying with a referral after shipping a Notion-based scheduler for 500+ students, with testimonials and usage data.

BAD: Prepping for the interview by memorizing PM frameworks and quoting Ken Norton’s old blog posts.
GOOD: Practicing aloud with timed prompts like “Improve Notion for remote engineering teams,” focusing on user pain points, not jargon.

BAD: Reaching out to alumni with “I admire Notion, can you refer me?”
GOOD: Sending a 3-paragraph email with a link to your project, one specific insight about their product, and a humble ask for feedback—not a job.

FAQ

Do I need a CS degree from Berkeley to get a PM role at Notion?

No. Notion hires PMs from diverse backgrounds, including MBA and Info majors. What matters is product intuition and shipping experience—not your major. A Haas MBA with a shipped Figma prototype has a better shot than an EECS student with no projects.

Is internship experience at big tech required?

Not at all. Notion values builder experience over brand-name internships. A summer spent building a campus tool with Notion APIs is more relevant than a passive internship at Amazon.

How important is the Berkeley brand for Notion hiring?

Low. Notion doesn’t recruit by school. They recruit by signal. Berkeley helps because of its culture of building, hacking, and launching—but only if you use it. A student from a small college who shipped more would beat a Berkeley student who didn’t.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.