Staff Designer - Design Systems

If you are sold on the vision of the company, you may want to consider the design team as a place to make this a reality. The design team at PhonePe is a bunch of creative trailblazers who are leading the effort to make a dent in the fintech universe. The design team consists of Product Designers, Visual Designers, Graphic & Motion Designers, and Illustrators who are all engaged in blending art and science into a promising value proposition for our users. About Design Systems at PhonePe PhonePe today is much more than a single product. Our teams design across the PhonePe Consumer App, PhonePe Business, PhonePe Invest, PhonePe Appstore, and a growing ecosystem of products and experiences. As these products grow independently, our Design System provides the shared foundation that keeps us coherent as an ecosystem while helping teams build faster and at a consistently high level of quality. This is an interesting systems problem. The goal isn't to make every PhonePe product look the same. It's to figure out what should remain common across PhonePe, what should be flexible, and where individual products genuinely need to extend the system. The Design Systems team owns the foundations, components, patterns, standards and tooling that make that possible across design and engineering. The role You'll lead Design Systems horizontally across PhonePe. You'll own the direction of the system: its architecture, quality, adoption, governance and evolution and work closely with designers and engineers across PhonePe to make it better. This is not a role for maintaining a Figma library from a distance. You'll need to understand how the system is actually being used, get into the details when necessary, make difficult calls around standardisation and flexibility, and build the operating model that allows multiple product teams to contribute without fragmenting the system. You'll lead the Design Systems team and partner closely with Design Systems Engineering and design leaders across PhonePe. What you'll do Set the direction. Define the vision, principles and roadmap for Design Systems across PhonePe. Decide where we invest, what we standardise, and how the system needs to evolve as our products grow. Build a system, not a component library. Own the architecture across foundations, tokens, components and reusable product patterns. Think about how these work together across Android, iOS and web, not one component at a time. Design for the PhonePe ecosystem. Find the right balance between a shared PhonePe foundation and the needs of individual products. Create consistency where it adds leverage without forcing every product into the same mould. Design for India at scale. Make sure our foundations work across languages, content lengths, devices, accessibility needs and different levels of digital familiarity. Drive adoption. Understand why teams use, extend, detach or rebuild system components. Treat those behaviours as signals and make the system useful enough that teams want to build with it. Build the contribution model. Give designers and engineers across PhonePe a clear way to propose, contribute and improve shared patterns. Build governance that protects quality without turning the Design Systems team into the design police. Partner deeply with engineering. Work closely with Design Systems Engineering to keep Figma and production aligned. Be comfortable getting into conversations about component APIs, tokens, variants, implementation constraints, releases and migrations. Raise the quality bar. Hold a high standard for interaction, visual craft, accessibility and system quality. Make sure what enters the system is robust enough to work across products and at PhonePe's scale. Make the system easier to use. Improve documentation, tooling and workflows so designers and engineers can discover the right solution and use it without depending on the Design Systems team. Build the team. Manage and grow the designers in the Design Systems team. Devel