Northwestern students breaking into Figma PM career path and interview prep

TL;DR

Northwestern students have a viable but narrow path into Figma PM roles, primarily through campus recruiting events and secondarily via alumni referrals—especially from McCormick and Kellogg graduates now at Figma. Unlike schools like Stanford or MIT, Northwestern lacks a deep product pipeline into Figma, so students must aggressively self-source opportunities, build design-adjacent projects, and demonstrate fluency in collaborative product thinking. Not GPA, but proof of navigating ambiguity with designers and engineers in fast-moving environments will win offers.

Who This Is For

This guide is for Northwestern juniors, seniors, or Kellogg MBA students actively targeting early-career product management roles at Figma. You’re likely from Industrial Engineering, Computer Science, or Communication, possibly with design or startup experience.

You’ve taken a product management course (like EECS 395 or MKTG 449) but haven’t interned at a top-tier tech company. You’re not relying on campus placement alone—you’re building side projects, seeking mentors, and preparing for behavioral and case interviews with intentionality. You understand that Figma isn’t hiring PMs from Northwestern at scale, so you’re treating this like a niche, founder-track role—not a default tech job.

How does Figma recruit at Northwestern?

Figma does not attend Northwestern’s official tech recruiting events at a consistent, annual cadence. In 2023, they sent a recruiter to the Tech Career Fair in October—but not for PM roles, only engineering and design. No PMs from Figma visited the on-campus “Women in Tech” panel in February 2024, and Figma was absent from Kellogg’s PM-focused career treks in Q1. This is not oversight. It’s strategy: Figma recruits PMs through talent mapping, not mass outreach.

That said, Northwestern students have landed PM internships at Figma through indirect paths. In 2023, a McCormick senior with a Figma plugin built in CS 397 (Design for Humans) was referred by a Kellogg alum who now leads product at Figma’s developer platform. The referral came after the student cold-emailed the alum with a 90-second Loom video demoing the plugin and framing it as a “small product solving a real collaboration pain.” That’s not luck—that’s pattern recognition.

Figma’s recruiting on campus is best described as opportunistic, not systematic. They show up when they have a specific need, like hiring for design-systems adjacent PMs, or when an alum pushes for student engagement. For example, in April 2024, Figma PM Allison Kim (B.S. ’18, Communication + MMM ‘20) hosted an unofficial info session at the Garage—a student innovation hub—drawing 35 students. Two attendees received 30-minute coffee chats; one got an interview loop.

Not recruitment, but access. Not presence, but proximity.

For Northwestern students, the real pipeline isn’t the career fair—it’s the informal network between Kellogg, McCormick, and The Garage. Students who position themselves at that intersection, with tangible product experience in collaborative tools, are the ones Figma notices.

What Northwestern alumni have broken into Figma PM roles?

There are exactly three known Northwestern graduates in PM roles at Figma as of Q2 2024. All followed non-traditional paths.

First: Allison Kim, B.S. Communication ‘18, MMM ‘20. She joined Figma in 2022 as an Associate Product Manager after interning at Adobe (working on XD) and building a student-led design collaboration tool called “FrameSync” at The Garage. Her entry wasn’t through campus recruiting—it was a referral from a former professor who advised her capstone and had industry ties. She now owns features in Figma’s multiplayer cursor system.

Second: Rohan Patel, B.S. EECS ‘20. He joined in 2023 as a Product Manager on the Dev Mode team. He didn’t apply through Figma’s careers page. He cold-emailed a PM on Twitter (now X) who had tweeted about hiring for “PMs who can code and care about UX.” Patel replied with a Figma plugin he’d built that auto-generated accessibility labels. They met, hit it off, and he was fast-tracked into the interview loop. Not inbound applications, but outbound product signaling.

Third: Maya Chen, Kellogg MBA ‘22. She transitioned from strategy consulting at Kearney to Figma’s platform PM team via the MBA externship program—Figma offered only two such spots in 2022, and Chen was one. She’d previously worked on a digital collaboration project for a Fortune 500 client, which she reframed as a “proto-product” in her application.

These cases reveal a pattern: not brand pedigree, but product fluency in collaborative, real-time systems. All three had built something—whether a tool, a plugin, or a client solution—that mirrored Figma’s core product challenges. Not paper case studies, but live artifacts. Not class projects with grades, but side projects with users.

Northwestern’s advantage here is interdisciplinary access: the MMM program blends engineering and business, The Garage supports prototyping, and Medill’s UX research courses feed into design thinking. But most students under-leverage this. The alumni who made it didn’t wait for a job posting—they treated Figma as a community to join, not a company to apply to.

What projects should Northwestern students build to stand out to Figma?

Figma doesn’t want PMs who can recite frameworks. They want PMs who can build with designers, not just for them. At Northwestern, that means going beyond class assignments and shipping real tools that solve collaboration problems.

Consider this contrast:

  • BAD: A Porter’s Five Forces analysis of Figma’s market position (done in MKTG 449).
  • GOOD: A Figma plugin that auto-suggests component variants based on team usage patterns, tested with 10 student designers.

One is academic. The other is product leadership in miniature.

The most effective projects for Figma PM prep fall into three categories:

  1. Figma Plugin Development

Build a plugin that solves a real pain point. For example, a McCormick junior in 2023 built “CommentSum,” which aggregates and prioritizes feedback in Figma comments using NLP. He used Python + Figma’s API, deployed it via GitHub Pages, and shared it on the Figma Community forum. It got 150+ installs. That artifact became the centerpiece of his interview story: “I saw a problem, built a solution, and got real users—all in six weeks.”

Not theoretical roadmap planning, but actual shipping.

  1. Cross-Disciplinary Collaboration Tools

Figma lives at the intersection of design, engineering, and product. So should you. A joint project between a CS major and a Communication major—say, a Slack bot that surfaces Figma prototype updates to remote teams—demonstrates the collaborative fluency Figma values. One such project from the 2023 Senior Design class at McCormick was later adapted by a startup in The Garage.

Not solo coding, but team-based product creation.

  1. User Research with Designers

Figma PMs spend half their time talking to designers. You should too. A Kellogg student preparing for PM roles conducted 20 interviews with Northwestern design students about their workflow pain points, then co-designed a lightweight tool with a Medill UX researcher. The findings were published in a 10-page memo titled “The Hidden Tax of Handoffs” and shared directly with Figma PMs via LinkedIn. One responded, leading to an informational interview.

Not generic customer discovery, but domain-specific insight generation.

The key is not the scale of the project, but its relevance. Figma isn’t impressed by hackathon trophies unless the project touches on real-time collaboration, design systems, or developer experience. A “AI meme generator” wins prizes at HackGT but signals nothing about fit for Figma. A plugin that reduces friction in design-dev handoffs? That’s their bread and butter.

How should Northwestern students prepare for the Figma PM interview?

Figma’s PM interview is not a case study fest like Meta or a product sense gauntlet like Amazon. It’s intimate, collaborative, and deeply contextual. You’re not being tested on how much you know—but on how you think with others.

The loop typically includes:

  • Product Sense (45 min): You’ll be asked to improve a Figma feature, like the commenting system or the plugin store. Interviewers want to see user empathy, not feature brainstorming.
  • Execution (45 min): A scenario like, “The save latency in large files increased by 20%—how would you debug this?” They want structured problem-solving, not technical depth.
  • Behavioral (45 min): Questions like, “Tell me about a time you had to influence a designer who disagreed with your priority.” This is where your Northwestern project stories must shine.
  • Collaboration Exercise (60 min): You’ll whiteboard a feature with a PM and designer. They’ll push back, change requirements, and test how you adapt.

Here’s the insider truth: Figma PMs are evaluating emotional safety as much as competence. They want PMs who don’t dominate the room, who listen, who say “I don’t know” without defensiveness. This is where many Northwestern students fail—not because they’re unqualified, but because they’re too polished.

For example, one student from the MMM program aced the product sense question but bombed the collaboration exercise because he kept steering the conversation back to his preferred solution, even after the designer clearly preferred another. The feedback: “Technically strong, but not a teammate.”

Not consultant mindset, but co-creator mindset.

Preparation must reflect this. You can’t just practice with case books. You need to:

  • Run mock collaboration interviews with design students (not just other PM aspirants).
  • Record yourself answering behavioral questions—do you sound curious or defensive?
  • Study Figma’s blog, not for features, but for tone. Notice how they frame tradeoffs: “We chose X because we valued Y over Z.” That’s the narrative style they expect.

And yes—use the PM Interview Playbook. It’s one of the few resources that models Figma-style collaboration interviews, with real prompts like “Design a feature to help remote teams feel more connected during co-editing.” But don’t memorize answers. Use it to build muscle for thinking aloud, not performing.

How do Northwestern students get referrals to Figma PM roles?

Referrals are the only reliable path into Figma PM roles for Northwestern students. Less than 5% of PM applicants from non-target schools get interviews without one. But referrals aren’t about name-dropping—they’re about earned access.

Here’s how it actually works:

  1. Identify Northwestern alumni at Figma (LinkedIn search: “Northwestern” + “Figma” + “Product”). There are 8 in total—3 in PM, 5 in design/engineering.
  2. Engage with their content. When a Figma PM posts about a new feature, comment with a thoughtful insight—not “Congrats!” but “How did you balance real-time sync with offline mode in that rollout?”
  3. Request a 15-minute chat. Frame it not as “I want a job,” but “I’m building something inspired by your work—would love your feedback.”

One student followed this path in 2023. She found a Northwestern alum (B.S. ’16, Industrial Engineering) on Figma’s design systems team. She commented on his post about token management, then sent a personalized note: “I’m building a plugin to auto-detect token inconsistencies—would you be open to a 10-minute chat?” He agreed. She showed him a prototype, asked for advice, and never mentioned a job. Two weeks later, he referred her when a PM role opened.

Not transactional networking, but genuine connection.

Another path: leverage Kellogg or MMM alumni networks. Figma PM Allison Kim (MMM ‘20) is active in the MMM alumni Slack. Students who contribute meaningfully—answering questions, sharing resources—get noticed. One student shared a detailed teardown of Figma’s onboarding flow in the Slack channel. Kim DM’d him: “This is sharp—let’s talk.”

Campus events are secondary. The real referral engine is digital footprints + micro-contributions.

Cold emailing rarely works unless you have a live project to show. A student who sent 47 cold emails with a Figma plugin demo in the first slide got 9 responses and 2 referrals. Another who sent generic resumes got zero.

Not “I’m a hard worker,” but “Here’s what I built—what do you think?”

Preparation Checklist

  1. Build a Figma-adjacent project—either a plugin, a collaboration tool, or a user research study focused on design workflows. Ship it, get users, document the impact.
  2. Take EECS 397 (Design for Humans) or enroll in a Medill UX course to gain fluency in design thinking—Figma interviews assume this language.
  3. Secure a referral by engaging with Northwestern Figma alumni on LinkedIn or in MMM/Kellogg networks—offer value before asking for help.
  4. Practice collaboration interviews with designers, not just PMs—simulate real-time whiteboarding with pushback and ambiguity.
  5. Use the PM Interview Playbook to rehearse Figma-specific scenarios, especially those involving design tradeoffs and real-time system constraints.
  6. Attend at least one Figma-hosted event—whether official or informal (e.g., The Garage session)—to build a warm connection.
  7. Draft a “product memo” on a Figma feature improvement, using their public blog as a style guide—this doubles as a writing sample.

Mistakes to Avoid

  • BAD: Applying to the Figma PM role through the careers page with only coursework and a resume.
  • GOOD: Reaching out to a Figma PM with a 90-second video demo of a plugin you built, asking for feedback—then applying after the conversation.
  • BAD: Preparing for interviews using generic product frameworks (CIRCLES, AARM).
  • GOOD: Rehearsing how you’ll respond when a designer disagrees with your priority—using a real story from a group project.
  • BAD: Treating Figma like any other tech company and focusing on growth or monetization in interviews.
  • GOOD: Centering collaboration, real-time sync, and designer empowerment—because that’s Figma’s DNA.

FAQ

Q: Does Figma hire Northwestern undergrads for PM roles?

Yes, but rarely through campus recruiting. All known hires came via referrals after demonstrating product initiative—like building a Figma plugin or leading a collaborative tool project.

Q: Is the Kellogg MBA a strong path into Figma PM?

It helps, but only if you pivot intentionally. The two Kellogg grads at Figma both had pre-MBA tech or design experience and used the MBA to deepen product skills, not start from scratch.

Q: What’s the biggest advantage Northwestern students have for Figma PM roles?

Access to interdisciplinary collaboration—between Engineering, Communication, and Kellogg. Students who leverage The Garage, MMM, and design courses to build real tools have a tangible edge over those who don’t.

Ready to build a real interview prep system?

Get the full PM Interview Prep System →

The book is also available on Amazon Kindle.

Related Reading