Overview

I joined Polygon as the early and first design intern and second member ( after design head ) of the design team, at a pivotal moment when the company was still known by its early name, Matic, and was rapidly scaling toward becoming a Web3 giant.

Polygon is a blockchain scalability giant, valued at over $20 billion and backed by some of the biggest names in venture capital, including Sequoia Capital India, SoftBank, and Tiger Global. Their mission: to enhance Ethereum with faster, more affordable transactions through a powerful multi-chain system.

Being at the heart of this transition exposed me to high-stakes problem-solving, deeply technical product environments, and the raw speed of a Web3-native startup. The result? A phase of accelerated growth that shaped my design philosophy forever.

My Role

• Earliest design team member: I was the first design intern and second person on the design team, actively contributing during Polygon’s foundational growth period.

  
  

• Embedded with leadership: I collaborated directly with the CTO, CMO, founders, and Head of Design, building deep product intuition and decision-making context.

  
  

• 0→1 thinking: I worked on a wide range of core initiatives, staking flows, NFT marketplaces, internal concept apps, and more.

  
  

• Marketing + design systems: I partnered with the marketing team to deliver visual campaigns, landing pages, pitch decks, and a scalable design system for consistent execution.

  
  

• Evangelized design across teams: I led training sessions and built internal templates, helping cross-functional teams confidently use design tools and systems.

The Challenge

Designing at a high-growth Web3 protocol wasn’t about polishing pixels, it was about solving ambiguity. Here were the core challenges we faced:

1. Making blockchain interactions human: Designing experiences for users unfamiliar with crypto’s underlying mechanics.

   
   

2. Translating technical systems into usable flows: Smart contracts don’t come with UI, turning those into intuitive interfaces was a constant puzzle.

   
   

3. Designing at startup speed: Projects moved fast, and the design team was lean. Precision, alignment, and execution had to happen without friction. In this environment, design wasn’t decorative, it was foundational.

Design Approach

To make a meaningful impact, I had to go beyond aesthetics and dive deep into functionality, psychology, and performance.

Here’s how I approached the work:

• Tight dev collaboration: Worked closely with engineers to understand technical constraints and smart contract logic.

  
  

• Redesigned the staking dashboard: Built an experience that clarified actions, reduced friction, and encouraged confident decision-making.

  
  

• NFT marketplace overhaul: Conceptualized a cleaner, more usable interface with improved navigation, filters, and visual clarity.

  
  

• Behavioural UX strategy: Partnered with a behavioural researcher to bake user psychology into design decisions, especially around wallets and staking mechanics.

  
  

• Internal concept design: Helped launch several early internal concept apps in collaboration with the CPO and under the guidance of the design head, going from idea to interactive prototypes.

  
  

• Marketing and visual identity: Took ownership of product marketing visuals, event collateral, and landing page designs to support awareness and engagement.

  
  

• Template design + enablement: Built template systems for marketers and ran onboarding sessions to help teams use them independently and efficiently.

Moments That Shaped Me

Working at Polygon wasn’t just about design, it was about learning, breaking and designing under real pressure. The expectations were high, the pace relentless, and the impact visible. These are some of the moments that shaped my learning, resilience, and leadership instincts:

• Late-Night Shipping with Engineers
  
  

  One night, around 10 PM, I jumped into a build session with one of the frontend engineer. We were working on a building staking calculator from scratch, a feature that needed to go out that night. By 1 AM, we had not only designed and implemented the flow, but we pushed it live. No handovers. Just trust, tight loops, and aligned execution.
  
  

• 1:1 Whiteboarding with the CTO
  
  I carved out time every day to whiteboard with the CTO ( Anurag ) for an hour, where we unpacked the technical underpinnings of blockchain protocols and how they influence design. These sessions didn’t just help me understand blockchain - they helped me internalize it. The mental models I built there still shape how I approach Web3 UX today.
  
  

• Designing with Developers, Not for Them
  
  I joined ongoing frontend-UX brainstorms, not just to hand off designs, but to build alignment, troubleshoot edge cases, and co-create better solutions. These sessions weren’t meetings; they were momentum. Everyone brought ideas, constraints, and insights to the table, and we designed smarter because of it.
  
  

• Decks on the Clock
  
  On multiple occasions, I worked directly with the founders to polish decks just hours before major events. I was often pulled in for last-minute iterations, finalizing visuals, refining storytelling, and aligning the narrative. The pressure was real, but the result was always worth it: decks that converted attention into action.
  
  

• Sketching UX Ideas on Whiteboards Daily
  
  I filled whiteboards with interaction models, UI states, and flow charts daily. Sometimes alone, often with a PM or engineer. Every sketch was a conversation starter. A test. A validation. In a space as complex as Web3, whiteboards became my second screen - where clarity started before pixels ever appeared.
  
  

• Designing Internals That Never Saw the Light
  
  I co-designed early prototypes of internal tools and product experiments - many of which were never launched. But that was the lesson: not everything ships, but everything teaches you something. I learned how to quickly validate (or kill) ideas.
  
  

• Fireside Debriefs at 2 AM
  
  Some of the best product feedback I received happened not in meetings, but in casual, late-night office chats with the CPO or design lead. We'd wrap up a sprint, grab coffee, and just talk product. No slides. No figma files. Just raw thoughts, friction points, and “what ifs.” Those conversations sharpened my instincts more than any formal review.

  
  

• Rapid-Fire Revisions Before a Major Program Launch
  
  Just before a major ecosystem initiative was announced, I worked back-to-back with the marketing team to polish final decks and visuals. We pushed last-minute typography tweaks, layout refinements, and graphic updates until minutes before it went live across channels like Twitter, CoinDesk, and internal community hubs.
  That sprint taught me a lasting lesson: in Web3, design clarity is execution clarity - and when the spotlight’s on, trust is built through every pixel.

  
  

These moments weren’t glamorous. But they were real. And they made me a better designer, not just in terms of skill, but in judgment, urgency, and team dynamics.

Beyond Design: What This Journey Was Really About

My time at Polygon was never just about pushing pixels or shipping beautiful screens.

Yes, I worked across product design, user flows, and visual systems, but the real growth came from what happened beyond the canvas.

This experience taught me how to think like a founder, not just a designer. I wasn’t just designing for users, I was designing for outcomes, alignment, and scale. Here’s what that looked like:

• I learned to think in systems, not just screens, how every UX decision maps to broader user behavior, market expectations, and product growth.

  
  

• I spent hours learning blockchain UX fundamentals from the CTO and senior engineers, diving deep into what makes on-chain interactions usable, secure, and trustworthy.

  
  

• I built a sharper product-thinking mindset, learning to prioritize clarity, trust, and decision-making over aesthetic polish.

  
  

• I worked directly with founders and C-level leaders, which helped me develop a strategy-oriented design lens, understanding how design supports positioning, GTM, investor narratives, and long-term roadmaps.

  
  

• I observed how high-performing teams operate, and witnessed real-time team building, leadership decision loops, and creative problem solving from the inside.

  
  

• I practiced true collaboration, not just cross-functional, but vision-aligned collaboration, where every function contributes to a shared mission under tight timelines.

  
  

• Most importantly, I began to see design not just as a craft, but as a compound force for momentum, alignment, and value creation inside ambitious Web3 products.

  
  

This journey was never just about the tools and just design. It was about the mindset. The ownership. The ability to see the bigger picture and still execute with precision.

Key Takeaways

Reflecting on my time at Polygon, a few core lessons stand out:

This wasn’t a passive internship. It was a crash course in blockchain UX, startup chaos, and the high-stakes design needed to help a protocol scale globally. I walked in as an intern. I left as a product thinker, creative partner, and early contributor to one of the most exciting platforms in Web3.

• Designing for Web3 is designing for clarity and trust: Complexity is a given in blockchain, good UX turns confusion into confidence.

  
  

• Impact > titles: Even as an intern, I contributed meaningfully to product decisions and design direction. Leadership is earned through ownership.

  
  

• Cross-functional agility is everything: Engineers, researchers, marketers, we moved as one unit, and collaboration was the glue.

  
  

• Every pixel is strategic: From dashboards to decks, every design element had to align with the bigger mission of helping Polygon scale.

  
  

• Web3 UX isn’t a nice-to-have; it's survival-critical: If users can’t understand or trust what they’re doing, the product fails. Design is where that trust is built.

Confidentiality Notice: Due to NDA restrictions, this case study does not include source files, original design assets, internal strategy documents, or detailed technical specifications. What you see here represents the work at a high level while respecting company confidentiality.

Thanks for reading and taking the time!

If you’d like to know more about me or dive deeper into my work, feel free to reach out. Let’s connect, share ideas, and explore ways we can work together. Contact me anytime, I’d love to hear from you ♥

Let’s connect, email me, or DM me on twitter.