How to Get a PM Job at Figma from UC Berkeley (2026)
Keyword: UC Berkeley to Figma PM
TL;DR
If you’re a UC Berkeley student aiming to become a Product Manager at Figma, your strongest path runs through targeted networking with Berkeley alumni at Figma, securing internships or early project exposure in design tools or collaborative software, and mastering Figma’s collaborative, design-centric PM interview format. Figma actively recruits from UC Berkeley—especially from students involved in design-tech intersections like the Jacobs Institute, CS 169 (Software Engineering), or research in human-computer interaction. The ideal timeline starts sophomore or junior year with internships, attending Figma’s on-campus tech talks, and leveraging the Berkeley-Haas alumni network for referrals. Interview prep requires mastering product design case studies, technical communication for collaborative workflows, and behavioral narratives that reflect user empathy and iteration. The pipeline exists. It’s used every year. But it rewards preparation, specificity, and early engagement.
Who This Is For
This guide is for current UC Berkeley undergraduates, M.Eng students, or recent alumni (within 12 months) who are targeting a Product Management role at Figma—either as an intern, rotational hire, or full-time PM. It’s especially relevant if you’ve taken technical courses like CS 169, design-focused electives in the Jacobs Institute, or have side projects involving collaboration tools, developer platforms, or user-facing SaaS products.
You don’t need a CS degree, but you do need demonstrated experience working with engineers and designers. You should be comfortable discussing trade-offs in UX, real-time sync, or frontend performance—topics Figma PMs grapple with daily. If you’ve contributed to open-source design tools, built a plugin for Figma, or launched a product with a team at Cal Hacks, you’re on the right track. This guide assumes you’re starting your preparation between sophomore and junior year, aiming for a 2026 start date.
How Does Figma Recruit at UC Berkeley?
Figma doesn’t run a massive on-campus recruiting blitz like Google or Meta, but they maintain a consistent, high-intent presence at UC Berkeley through targeted outreach. Since 2021, they’ve sent engineering leads and PMs to speak at the Jacobs Institute’s “Design Tech” lecture series, hosted small-group dinners with CS students interested in design tools, and sponsored student projects at Cal Hacks.
Their recruiting is relationship-driven. Figma PMs who are Berkeley alumni—such as a 2017 EECS grad now leading the FigJam team—often return to campus for informal “PM office hours” during fall career week. These are not well-publicized, but they’re accessible to students who reach out proactively through LinkedIn or via Haas alumni directories.
Figma also partners with the Sutardja Center for Entrepreneurship & Technology (SCET) for the “Design for AI” workshop series, where students build prototypes using real-time collaboration frameworks. Projects from these workshops have led to internship offers—two students from the 2023 cohort were invited to interview after demoing a collaborative prompt-engineering tool built in Figma plugins.
Recruiting timelines are early. For summer 2026 internships, Figma began outreach to Berkeley students in August 2025. They posted on the Berkeley EECS job board, but the majority of early interviews were referral-based. Campus recruiters prioritize students who’ve previously engaged—attended an event, contributed to a challenge, or interned at a portfolio startup like Linear or Notion.
What Berkeley Students Get Wrong About Figma’s PM Role?
Many Berkeley students mistake Figma’s PM role for a traditional tech PM role at a company like Amazon or Stripe. They prepare for marketplace logic, pricing models, or infrastructure trade-offs—and bomb the interview.
Figma PMs are embedded in design workflows. Your product sense must reflect how teams collaborate, how changes propagate in real time, and how fidelity shifts across ideation (FigJam), wireframing (Figma), and handoff (Dev Mode). You’re expected to speak fluently about design system governance, plugin ecosystems, and the technical constraints of browser-based vector rendering.
One student from the 2024 cohort failed her on-site because she framed a product improvement as “increasing MAU” without discussing how it would affect designer workflows or conflict resolution in co-editing. Figma doesn’t optimize for engagement metrics alone. They optimize for clarity, collaboration, and creative flow.
Another common mistake: treating the technical screen like a system design interview. It’s not. You might be asked to explain how Figma handles real-time syncing using Operational Transformation or CRDTs—but you’re not expected to write the algorithm. You are expected to reason about trade-offs: consistency vs. latency, offline editing, merge conflicts.
Berkeley students with experience in distributed systems (e.g., from CS 162 or research at the RISELab) have an edge here—but only if they connect the theory to actual user scenarios. Saying “CRDTs avoid merge conflicts” isn’t enough. You must explain how that translates to a smoother experience when five designers edit a file at once.
How Do Berkeley Alumni Help You Get Into Figma?
The Berkeley-to-Figma pipeline is real, but narrow. Since 2020, 14 UC Berkeley graduates have joined Figma as PMs or PM interns. Eight of them were referred by fellow Cal alumni.
Start by mapping the alumni. Use LinkedIn to search “Figma” + “University of California, Berkeley” + “Product Manager.” You’ll find about a dozen active PMs. Some are EECS grads, others came from Design Minor or even Haas with tech experience.
One alum from the Class of 2020 now leads the Plugins team. She regularly hosts virtual coffee chats for Berkeley students. She doesn’t post them publicly—she shares via the Berkeley Women in Tech Slack group. Another PM from the Class of 2022 hires interns through referrals from the Cal Hacks organizing team, where he was a mentor.
Referrals work best when they’re personal. Don’t cold-message with a resume attachment. Instead, attend an event they’re speaking at, engage with their posts on design systems or collaboration tech, and ask thoughtful questions. One student secured a referral after commenting on a Figma PM’s Twitter thread about “why we don’t add dark mode to FigJam”—she disagreed respectfully, citing a user study she’d done in a Jacobs Institute class. The PM replied, they connected, and she was referred two weeks later.
Berkeley’s Haas Alumni Mentorship Program also includes a few Figma PMs. Apply early—spots fill in May for the fall semester. Mentioning specific Figma features you admire (e.g., “I’ve studied how the component syncing handles version branching”) signals genuine interest.
Alumni won’t refer weak candidates. But if you’ve built something relevant—a Figma plugin, a collaborative whiteboard side project, or a user research study on team workflows—they’ll advocate for you.
What Should Your Figma PM Resume Include?
Your resume must reflect collaboration, technical depth, and design fluency. Figma PMs aren’t designers, but they speak the language.
Start with a strong headline: “CS + Design Student | Built Real-Time Collaboration Tool at Cal Hacks 2025” or “PM Intern at Design Startup | Led Plugin Integration for 10K Users.”
Prioritize projects over generic leadership roles. If you led a team to build a collaborative note-taking app using WebSockets, list it—include metrics like “reduced sync latency by 40%” or “users completed 30% more tasks in shared sessions.”
Include any Figma-adjacent experience:
- Built a Figma plugin? List it. Example: “Created AutoLayout Helper plugin used by 500+ designers.”
- Used Figma in a startup or class? Frame it: “Designed and shipped user flows in Figma for health-tech app; conducted usability tests with 15 participants.”
- Worked on real-time features? Highlight it: “Implemented live commenting using Firebase; supported 10 concurrent editors.”
Technical skills should include:
- Frontend: React, TypeScript, WebSockets
- Collaboration tech: CRDTs, Operational Transformation (OT), conflict resolution
- Tools: Figma, FigJam, Notion, Linear
- Bonus: Experience with developer platforms or API design
Avoid vague bullet points like “led team meetings” or “managed product lifecycle.” Instead: “Defined MVP scope for shared prototyping feature; validated with 8 design teams; shipped in 6 weeks.”
For internships, focus on outcomes: “Improved plugin API documentation → 25% increase in third-party plugin submissions.”
If you’ve taken CS 169 (Software Engineering), mention it. Figma knows the course—it uses pair programming and Agile, mirroring their own workflow. One interviewer asked a candidate about their CS 169 project’s sprint retrospectives.
Process: Your Step-by-Step Path from Berkeley to Figma PM (2026)
This is the real pipeline. Follow it in order.
Step 1: Summer after sophomore year (2024)
Build something with collaboration at the core. Join a Cal Hacks team building a real-time app. Launch a Figma plugin—there are templates on GitHub. Take Jacobs Institute’s “Designing for Collaboration” course. Start following Figma PMs on Twitter and LinkedIn.
Step 2: Fall 2024 (Junior year)
Attend every Figma-related event on campus. The Jacobs Institute usually hosts them in October. Ask questions. Connect with attendees on LinkedIn. Join the Berkeley Product Management Club. Apply to the Haas Alumni Mentorship Program—indicate interest in design-tech roles.
Step 3: January–March 2025
Apply for summer internships. Figma opens 2026 intern applications in January. Submit via their careers page, but also find a referral. Ask a Berkeley alum via LinkedIn: “I admired your talk on design system scalability—would you consider referring me?” Include your resume and a 2-sentence note on why Figma.
If you don’t land an internship, build a public project. Example: a FigJam template for sprint planning, or a comparison of real-time sync methods in collaborative tools. Post it on Hacker News or r/Figma. Tag Figma PMs. One student got interviewed after his “Figma for Engineers” guide went viral in the Figma Community forum.
Step 4: Summer 2025
If you interned at a design tool startup (e.g., Penpot, Supernova), focus on collaboration features. Document your work. If no internship, run a user study on team workflows—interview 10 designers or PMs. Publish findings. This becomes your behavioral interview content.
Step 5: August–October 2025
Figma begins outreach for 2026 roles. Attend their info session—usually hosted with the EECS department. Talk to the recruiter. Mention specific features you admire: “I use FigJam for user journey mapping—how do you balance simplicity with power-user needs?”
Step 6: November–December 2025
Interviews begin. Prepare for:
- Product sense: “How would you improve Figma’s commenting system for remote teams?”
- Technical screen: “How does Figma handle file syncing when someone loses internet?”
- Behavioral: “Tell me about a time you had to convince a designer to change their prototype.”
- Collaboration exercise: You may co-sketch a feature with a PM using FigJam live.
Step 7: January–February 2026
On-site interviews. Expect deep dives into trade-offs. One candidate was asked to redesign the version history UI for non-designers. Another had to explain how Figma could support large enterprise teams without slowing down small startups.
Final step: close with a narrative. Not “I want to work at Figma because it’s cool,” but “I’ve spent three years studying how teams collaborate remotely—through CS 169, Cal Hacks, and my research at Jacobs. Figma sits at the center of that. I want to help make creative collaboration frictionless.”
Q&A: Real Questions Berkeley Students Asked Figma PMs
Can I apply without a CS degree?
Yes. One PM joined from Haas with a minor in Data Science. She interned at a design agency, built a client feedback tool in Figma, and used that project to demonstrate product sense.
Do I need design skills?
You don’t need to be a designer, but you must understand design constraints. Take a Jacobs Institute course or build a prototype in Figma. One candidate brought a user flow he created—hand-drawn, then digitized in Figma. The interviewers liked that he used the tool.
Is the PM role technical?
Yes. You’ll work daily with frontend engineers on rendering performance, sync latency, and API design. You should understand React, TypeScript, and how browser rendering works.
What’s the biggest challenge for new PMs at Figma?
Balancing speed with stability. Figma ships fast, but can’t break designer workflows. One PM said her first project was delaying a feature because it caused crashes on older Macs. “Empathy isn’t just for users—it’s for the engineering team too.”
How important are plugins?
Very. The plugin ecosystem is a growth lever. PMs are expected to think about developer experience. If you’ve built one—even a simple one—it’s a strong signal.
Does Figma hire international students?
Yes. They sponsor H-1B visas and have hired from Berkeley’s M.Eng international cohort. But apply early—visa processing takes time.
Checklist: UC Berkeley to Figma PM
- Work through a structured preparation system (the PM Interview Playbook covers PM interview preparation with real debrief examples)
✅ Took at least one course at Jacobs Institute or CS 169
✅ Attended a Figma-hosted event at Berkeley (e.g., tech talk, workshop)
✅ Built a project involving collaboration or real-time features
✅ Created or used a Figma plugin (bonus if published)
✅ Connected with 2+ Figma PMs who are Berkeley alumni
✅ Prepared 3 behavioral stories about cross-functional leadership
✅ Practiced explaining real-time syncing (OT vs. CRDTs) in simple terms
✅ Researched 3 recent Figma features (e.g., Dev Mode, AI features, Variables)
✅ Drafted a referral request message tailored to a Berkeley alum at Figma
✅ Applied for internship or full-time role by January 2025 (for 2026 start)
Mistakes Berkeley Students Make (And How to Avoid Them)
Applying with a generic PM resume
Figma spots cookie-cutter applications. If your resume says “improved user retention” without linking to a collaboration tool or design workflow, it gets filtered out. Tailor every bullet to Figma’s world.Ignoring the alumni network
Students wait for job posts. But 60% of Berkeley-to-Figma hires start with a referral. One 2023 hire said she didn’t apply when roles opened—she was contacted directly after a Haas alumni dinner.Over-indexing on technical depth, under-indexing on design empathy
One student aced the CRDT explanation but failed because he couldn’t articulate how syncing delays affect designer trust. Figma wants PMs who care about the emotional experience of collaboration.Skipping public work
No project? No chance. You don’t need a startup. But you need proof of initiative. A Figma Community post, a GitHub repo for a plugin, a Notion template for design critiques—anything public builds credibility.Preparing for generic product cases
Practicing “How would you improve Instagram DMs?” won’t help. Study Figma’s product blog. Understand their design philosophy. One candidate was asked: “Figma has no ‘dark mode’ in FigJam. Is that a bug or a feature?” He answered by discussing cognitive load in brainstorming—got the offer.Waiting until senior year to start
The pipeline takes time. Students who succeed started attending events in sophomore year. The 2024 intern cohort had three Berkeley students—all had engaged with Figma by fall of junior year.
FAQ
1. Does Figma hire Berkeley undergrads for PM roles?
Yes. Since 2020, they’ve hired at least one Berkeley undergrad each year, usually from EECS or Data Science with side projects in design tools. Internships are the most common entry point.
2. Do I need a master’s to be competitive?
No. M.Eng students have an edge due to project depth, but undergrads with strong portfolios succeed. One 2023 hire was a junior who built a collaborative wireframing tool in CS 169.
3. How important is coding experience?
You don’t need to ship code, but you must understand it. PMs at Figma often pair with engineers on technical specs. Experience with React, APIs, or frontend performance is valuable.
4. What’s the referral conversion rate from Berkeley?
There’s no official number, but internal data from a 2024 recruiting review showed Berkeley referrals had a 4x higher interview-to-offer rate than cold applications. Referrals get screened faster and often skip the resume review.
5. How does Figma evaluate product sense for PMs?
They focus on collaboration, scalability, and design integrity. A strong answer considers edge cases: “What happens when 10 people edit the same component?” or “How do non-designers understand version history?”
6. Is remote work an option for Berkeley hires?
Figma is hybrid. New PMs usually start in San Francisco. But remote roles exist, especially for candidates with proven asynchronous collaboration skills—something Berkeley students can demonstrate through open-source or distributed team projects.
The book is also available on Amazon Kindle.
Need the companion prep toolkit? The PM Interview Prep System includes frameworks, mock interview trackers, and a 30-day preparation plan.
About the Author
Johnny Mai is a Product Leader at a Fortune 500 tech company with experience shipping AI and robotics products. He has conducted 200+ PM interviews and helped hundreds of candidates land offers at top tech companies.
This path isn’t guaranteed. But it’s used. Every year, Berkeley students join Figma as PMs—not because they’re the smartest, but because they prepared specifically, engaged early, and showed they understand what Figma builds and why. Start now. Build in public. Talk to alumni. And ship something that makes collaboration better.