During a summer internship on Figma's design systems team, Jenning Chen shipped improvements to the editor's style picker — search, a list view for color styles, and text style metrics — from inception through launch. Her account of the internship covers remote onboarding and the work itself.
Remote onboarding
Chen first encountered Figma at a 2017 fall college career fair, where a booth demo drew her into a conversation about design tools. The role did not work out that year, but she joined the internship program this summer. Onboarding remotely, she found teammates scheduling virtual coffee chats and flooding Slack with greetings, and her team sent a welcome card as a Figma file filled with greetings and doodles.
Working remotely
Chen expected miscommunication over Slack and email, difficulty forming close relationships, and fewer chances to absorb context from people nearby. She worried about asking for help over Slack and about getting lost in the shuffle. The team was deliberate about offsetting that: weekly company-wide events included a biweekly show-and-tell where Figmates share recent learnings or in-progress work, Thursday tech talks where colleagues presented passions and creative projects, and one-on-ones covering Figma's product and growth. Team activities such as cooking classes, online escape rooms, and scavenger hunts provided more personal contact. Before starting project work, she built product fluency — understanding Figma's features and design terminology — by asking her mentor, teammates, and Slack channels, and found colleagues willing to hop on a call to work through obstacles.
The style picker project
The style picker lets users browse and apply paint, text, effect, or layout grid styles to objects in the Figma editor. Meetings with designers and product managers made clear the improvements were in high demand: the original picker became unmanageable as the number of styles grew, obscuring important information and forcing users to scroll through long lists. Chen was initially hesitant to take responsibility for a popular, user-facing feature as an intern, but came to see it as a learning experience. Working with Shana Hu, the team's product designer, she implemented three changes:
- Search: users usually have a particular style in mind, and can now find it within a few keystrokes.
- Color styles list view: the style name — a style's most identifying attribute — was obscured in the grid layout; the new list view shows it clearly alongside the thumbnail.
- Text style metrics: displaying font size and line height directly in the text style picker saves users time when choosing a style.
Because the design systems team is structured vertically, the project spanned the stack: TypeScript and C++ in the editor and Ruby in the backend. Chen presented the feature internally at show-and-tell and faced several hurdles before launch. Populating the metadata of existing text styles with the new metrics required migrating millions of styles, and the migration alone took an entire day. Incorporating critique feedback and making last-minute bug fixes added further pressure, though Chen says these obstacles deepened her understanding of the codebase. Ahead of launch she worked with the data science team on tracking the right metrics and with marketing on launch-day details, then watched reactions arrive as the feature went live.
What the internship changed
Based on peers interning elsewhere, Chen had expected to work on a specific part of a feature; instead she saw what shipping a product end to end takes — conception, critiques, implementation, metrics, promotion, and launch. Alongside technical lessons such as the rules of React Hooks and the dangers of props spreading, cross-functional interactions improved her ability to communicate technical information, and design critiques, bug bashes, and collaboration with designers sharpened her product and UX intuition. Carrying engineering responsibility for a feature boosted her confidence. She credits mentor Josh Shi for his guidance and feedback.




