COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY
COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY
COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY
COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY COMMUNITY

My Nokia Internship Experience

I still remember receiving the email, I had really wanted to work on a design systems team and was ecstatic to get the offer. What would it be like working with such a legendary company? How would I contribute to their design systems? Fast forward a year, and I can joyfully say it's been an adventure I'll never forget. I’m thankful for Glenda and Ian for giving me the opportunity to experience what it’s like working with designers whose work shows how much they care about the product and work tirelessly to make the process efficient for other designers.

What I worked on

Originally, I was taking on small tasks to understand how to use the design system and learn about all the libraries. After I got comfortable with the systems, I was ready to take on bigger projects. I took on two main ones:
1-Post-launch improvements, 2-Improving the Contribution & Reward Model Experience.

I took ownership for both projects, conducting research in various phases to identify the stakeholders involved, pain points they experienced, and how my solution can meet their needs and business goals. I wanted to think beyond the 1-2 month timeline, making sure I was accounting for impact 6-12 months on the roadmap.

My research identified a lot of growth opportunities for the design system. It led me to expand documentation for two existing libraries - Maps & Charts. It also led to the creation of a new Advanced Prototype Library. I was able to redo the Home page for the documentation, redesign illustrations, and start defining processes for the work our team did.

Impact

Things I worked on:

  • Component libraries (Core, Charts, Advanced Prototyping of Core Components)
  • Documentation research and improvements
  • Developer & designer get started guides
  • Illustration library
  • Design principles
  • Contribution + reward model documentation
  • Defining processes and content organization
  • Public launch strategy
  • Monthly newsletters
  • Monthly team workshops
Components inserted

Initiatives

In my first four months, I was a Student Ambassador representing the Canadian interns. I led monthly meetings, workshops, and created opportunities to network. I worked with 5 other ambassadors to organize guest speakers each month, featuring senior executives from different departments to share their career journeys with the students. At the end of the term, we hosted a celebration for all the work completed by interns. I led a sharing session where 5 interns shared the work they were proud of to inspire the next terms students.

Bringing Community to Nokia

Within my team, I wanted to bring my passion of culture and community to each interaction, spark some joy, and just find ways to work together where possible. After 4 months into my internship, I wanted to take it upon myself to do something for the team. So, each month I:

  • facilitated knowledge sharing sessions
  • hosted design challenges
  • ran growth strategy workshops
  • onboarded the next set of interns
Community page

Toronto Tech Week Panel

To bring Nokia’s work to the Toronto community, I hosted a Design Systems Panel as a part of Toronto Tech Week’s events. I got the approval from my manager, Glenda and in less than 2 weeks, organized the whole event. Did you know cold-emails and LinkedIn messages are pretty effective when organizing an event? I sent out messages to a couple Design Systems leaders in Toronto, inviting them to come share their work and journey. To my surprise, a lot of folks were interested! Space was limited so we had 3 panelists from Telus, Thomson Reuters, and Nokia. I hosted the panel, and learned a lot not only about design systems but how to connect with designers in the space. The event was 3 hours and an immense success!

Collage 1 Collage 2 Collage 3 Collage 4

Nokia Design Week

I took on organizing the first ever (and hopefully annual 🤞🏼) Nokia Design Week event. This involved everything from inception - creating the theme, finding the speakers, the branding, and anything else you can imagine. You can find some of my work below, including the website.

Browser

Public Launch

To support the public launch of ABC, I developed the social media strategy, crafting core messaging and shaping the launch narrative. I identified key channels, designed a phased rollout, and created community engagement messaging to drive interaction. Additionally, I produced visuals—including static images and GIFs—to enhance the campaign. Anticipating potential challenges, I also prepared response strategies for adverse reactions, ensuring a smooth and well-received launch. While we have not launched yet, working on all the content and working with the larger brand team was an exciting experience.

Browser

What I Learned

Design systems feel like the atoms of a product—tiny building blocks that come together to create something much bigger. That way of thinking really clicks with me as a logical thinker. I love how structured components can scale and shape an entire experience, making everything more cohesive and intentional.

But beyond just the technical side, I realized I have the agency to shape my time at any company however I envision it. I don’t have to just go with the flow—I can actively create the kind of environment I want to be part of. Bringing a sense of community to Nokia made me feel more connected, like I was part of something bigger than just my role. It’s a reminder that work isn’t just about what I build—it’s also about the people I build it with.

What my colleagues have to say

Kind words from colleagues who’ve seen my work first hand.

Colleague words 1 Colleague words 1 Colleague words 1

What’s next

I’m excited to keep pushing the boundaries of how we interact with technology—whether through design systems, innovative interfaces, or building tools that bring people closer together. As I look ahead, I’m focused on deepening my understanding of interaction design, exploring new ways to shape meaningful experiences, foster community, and create products that feel both intuitive and impactful.