Cross-Meta Design System
Product Design Intern
06/2025 - 09/2025
In Experiment
Stephen Barros
Bethany Fong
2 product managers
3 product designers
3 software engineers
1 data scientist
2 art/visual designers
1 content designer
5+ partner teams
Figma,
Origami Studio,
LottieFiles
System thinking
Visual design
Interaction design
Product strategy
Micro-interaction
Eng handoff
Monthly actively users
Meta-owned apps
design proposals
product flows
Here are my major contributions throughout my internship:
Unfortunately, I am unable to share this work publicaly.
Please send me an email if you're interested to learn more about my internship at Meta and see the full case study!
I got to work with the most talented team and here's what they said about me!
There is so much that we can learn from you as much as I hope you have learned while being here! Thanks for being a prototyping and design system superhero. It was so inspiring to witness.
Senior Product Designer
You've contributed such high-quality design work in such a brief time! It's inspiring how quickly you camped up on design systems and passion you had for systems thinking!
Product Manager
Jen, your thoughtfulness and intention with every presentation has been so impressive. I've learned so much fro you - from design perspective, and how to present and communicate a message so effectively.
Program Manager
Your thorough preparation and dedication helped us move forward smoothly, passing both the data and design reviews with ease. I'm confidence you'll achieve great things!
Data Scientist
Balancing expression and functionality by understanding product goals.
Cross-Meta Design System serves not just one product, but many as a unifying layering to represent Meta as a company. It requires a constant balance of flexibility and expression, with a touch of neutrality. I've learnt that it's essential to cultivate a deep understanding of the products, company business goals, and the intricate network of internal teams.
Design and think in scale - molecular and atomic.
I've learned that components are more molecular and atomic in nature and design system requires designers to constantly shift in scales. Parter team utilize smaller pieces to build their products. The lowest level of adoption that we should aim for, which allows the most flexibility, is a combination of utilizing our tokens in conjunction with the smaller components.
Expand the horizon and leverage system thinking to scale impacts.
Components work in unity and in harmony with each other to create a cohesive system experience. I've learnt to constantly ask questions that leverage a higher level of system thinking beyond the components themselves: How does this change impact the entire system? How to scale this feature in other experiences? Will this work in harmony or in conflict with our existing system?