Staff / Principal Product Designer, Design Systems

📍 Job Overview

Job Title: Staff / Principal Product Designer, Design Systems

Company: Rho

Location: New York City, New York, United States

Job Type: FULL_TIME

Category: Product Design / Design Systems

Date Posted: 2026-08-25

Experience Level: Staff / Principal (10+ years implied)

Remote Status: On-site

🚀 Role Summary

• Spearhead the ownership and evolution of Rho's design system, establishing it as the governed frontend layer for the entire product suite.

• Define and enforce architectural standards, design tokens, component specifications, and motion language to ensure cohesive and high-quality user experiences.

• Collaborate closely with engineering guilds and product teams as a peer to drive the implementation and adoption of design system principles and components.

• Elevate the overall craft and consistency of the product by setting and maintaining a high bar for design quality across typography, branding, and microinteractions.

📝 Enhancement Note: This role is specifically for a senior individual contributor focused on design systems, emphasizing ownership, technical depth (design in code), and a strong understanding of financial product complexity. The "Staff / Principal" title suggests significant autonomy and strategic influence.

📈 Primary Responsibilities

• Own the architecture, design tokens, primitives, and motion language of Rho's design system, ensuring it scales effectively with product growth.

• Develop and maintain a robust governance model and contribution process for the design system, enabling 80+ engineers and PMs to ship consistently.

• Partner with frontend engineers to translate design system specifications into production-ready code components, enforcing standards through linting and CI.

• Define and implement design standards that elevate the craft across the organization, focusing on typography, branding, motion, and microinteractions.

• Act as a thought leader and advocate for the design system, driving adoption and providing guidance to product teams on its effective utilization.

• Conduct deep dives into financial workflows to ensure the design system effectively supports complex, multi-role, and permission-scoped user experiences.

• Continuously iterate on the design system based on feedback, usage data, and emerging design and engineering best practices, fostering a culture of "ship, then sharpen."

📝 Enhancement Note: The responsibilities clearly indicate a hands-on role with significant strategic scope. The emphasis on "governed frontend layer," "components in code," and "lint and CI" highlights a deep integration with the engineering process.

🎓 Skills & Qualifications

Education: While no specific degree is listed, a strong portfolio and demonstrable experience in building and governing design systems at scale are paramount. A background in HCI, Design, Computer Science, or a related field would be beneficial.

Experience: A minimum of 7 years of dedicated product design experience is required, with a substantial portion focused on owning, building, and governing design systems at a significant scale.

Required Skills:

• Design Systems Ownership: Proven experience leading and owning a design system from inception to maturity, including architecture, governance, and contribution models.

• Design in Code: Strong aptitude or direct experience designing within code environments or collaborating intensely with engineers on code implementation.

• Technical Design Skills: Proficiency in translating complex design requirements into scalable design tokens, primitives, and component specifications.

• Craftsmanship: Exceptional taste and attention to detail in typography, branding, motion design, and microinteractions.

• System Thinking: Ability to think in primitives, states, edge cases, and two-way doors to build resilient and adaptable systems.

• Collaboration: Proven ability to partner effectively with engineering guilds, product managers, and other designers as an equal.

• Problem Solving: Capacity to thrive in ambiguity and proactively solve complex design challenges within financial workflows.

• Figma Proficiency: Advanced skills in Figma for component design, prototyping, and system documentation.

Preferred Skills:

• Experience with financial technology (FinTech) or complex enterprise software.

• Familiarity with frontend architecture principles and technologies (e.g., React, Vue, CSS-in-JS).

• Experience establishing and managing design system contribution models.

• Understanding of AI applications in design or documentation.

• Experience with design tooling for code generation or linting.

📝 Enhancement Note: The "at least 7 years" and "owned one" requirements are critical. The emphasis on "design in code" and "real medium" points towards a "design engineer" or highly technically adept designer profile. The specific mention of "AI agent can query" suggests a forward-thinking approach to design system documentation.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Design System Deep Dive: A comprehensive case study showcasing a design system you have owned and governed at scale. This should detail the architecture, token strategy, component development, governance model, and contribution process.

• Pixel-Level Craftsmanship: A piece of work demonstrating exceptional attention to detail at the pixel level, showcasing mastery of typography, motion, and microinteractions.

• Systems-Level Project: A deeply complex, systems-level project that illustrates your ability to think in primitives, states, edge cases, and complex workflows.

Process Documentation:

• Evidence of your process for developing and evolving design systems, including how you handle feedback, iterate on components, and manage contributions.

• Examples of how you've documented design system specifications, component behavior, and design principles in a way that is accessible and actionable for engineers.

• Demonstration of how you ensure consistency and quality across a large product surface area through system design.

📝 Enhancement Note: The application requires a portfolio that explicitly demonstrates ownership and governance of a design system, not just contribution. The distinction between a "polished case study frames" and a "real, working file" is crucial, indicating a need for tangible, production-ready design work.

💵 Compensation & Benefits

Salary Range: Given the Staff/Principal level, 7+ years of experience, and a high-cost-of-living location like New York City, a competitive salary range for this role is estimated to be between $180,000 - $250,000 annually. This range accounts for the senior individual contributor nature, specialized skills in design systems, and the demanding FinTech environment.

Benefits:

• Comprehensive health, dental, and vision insurance plans.

• Generous paid time off (PTO) and holiday schedule.

• Opportunities for professional development, including conferences and training focused on design systems and FinTech.

• Stock options or equity in a growing startup.

• 401(k) plan with potential company match.

• Support for in-office collaboration with a focus on dedicated workspace.

Working Hours: The role is specified as FULL_TIME, with an expectation of approximately 40 hours per week. However, the emphasis on "move fast" and "ship, then sharpen" suggests a dynamic environment where dedication to meeting deadlines and shipping high-quality product is paramount.

📝 Enhancement Note: Salary estimates are based on industry benchmarks for senior/principal product designers in major tech hubs like NYC, considering the specialized nature of design systems leadership and the FinTech industry. Benefits are inferred from typical startup offerings for attracting senior talent.

🎯 Team & Company Context

🏢 Company Culture

Industry: FinTech (Modern banking platform for startups). Rho operates in a highly regulated and competitive financial services sector, requiring a strong emphasis on security, reliability, and user trust.

Company Size: Rho is a growing startup, implied by the "80 plus engineers and PMs" and the need for a foundational design system. This means a dynamic, fast-paced environment with opportunities for significant impact.

Founded: Rho was founded in 2019, indicating it's a relatively established startup that has moved beyond its initial ideation phase and is now scaling its product and operations.

Team Structure:

• The role involves partnering with "our frontend guild," "our engineers," and "the design team." This suggests a collaborative, cross-functional structure.

• The design team is "heads down on building the governed frontend layer this quarter," indicating a focused, project-driven approach.

• The "Staff / Principal" title implies a senior individual contributor role, likely reporting to a Design Lead or Head of Design, with significant autonomy. Methodology:

• Artifact First: Emphasis on tangible outputs and deliverables.

• AI Native: Expectation to leverage AI tools in daily workflows.

• End-to-End Ownership: Designers are responsible for research, QA, and shipping their work.

• In-Office Collaboration: The company values in-person collaboration for complex system work.

Company Website: https://www.rho.co/

📝 Enhancement Note: The company culture is described as fast-paced, demanding, and highly collaborative, with a strong focus on craft and technical execution. The "startup" environment implies agility, ownership, and the potential for significant influence.

📈 Career & Growth Analysis

Operations Career Level: This is a Staff/Principal level individual contributor role. It signifies a senior position within the design discipline, focused on deep expertise in design systems and their application to product development. The role is about setting technical and craft standards for the entire organization's frontend experience.

Reporting Structure: While not explicitly stated, a Staff/Principal Designer typically reports to a Design Manager, Director of Design, or Head of Product. They are expected to work autonomously and influence product direction.

Operations Impact: The design system owned by this role forms the "governed frontend layer" of Rho's banking platform. Its successful implementation directly impacts the consistency, quality, scalability, and speed of product development, thereby affecting customer trust, user experience, and ultimately, revenue.

Growth Opportunities:

• Technical Specialization: Deepen expertise in design systems, frontend architecture, and design engineering.

• Leadership Influence: Shape the technical and aesthetic direction of Rho's entire product offering.

• Mentorship: Guide and mentor other designers and engineers on design system best practices.

• Strategic Impact: Contribute to the core technical foundation of a rapidly growing FinTech company.

• Potential for Team Leadership: As the design system matures, there may be opportunities to build and lead a dedicated design systems team.

📝 Enhancement Note: This role offers significant growth for a designer who wants to own a critical technical and craft foundation. The "Staff/Principal" designation implies a path towards technical leadership and strategic influence rather than people management initially.

🌐 Work Environment

Office Type: The role explicitly states "New York (in person)" and "We're in the office in New York because the best systems work happens shoulder to shoulder, obsessing over a real screen." This indicates a strong preference for an in-office, collaborative environment.

Office Location(s): New York City, New York, United States.

Workspace Context:

• Collaborative Hub: The office environment is designed for "shoulder to shoulder" collaboration, ideal for complex system design discussions.

• Technology Focus: Expect access to high-quality tools and technology necessary for detailed design work, including powerful workstations and displays.

• Cross-Functional Interaction: Frequent interaction with engineers, product managers, and fellow designers will be part of the daily routine.

Work Schedule: Full-time, with an emphasis on high pace and rapid iteration. While a standard 40-hour work week is implied, the culture encourages speed and dedication to shipping quality products, suggesting flexibility might be needed to meet project demands.

📝 Enhancement Note: The emphasis on in-office work for "systems work" is a key differentiator, suggesting a culture that values direct, face-to-face collaboration for complex technical and design challenges.

📄 Application & Portfolio Review Process

Interview Process:

• Initial Screening: Review of resume and portfolio against the specific requirements of design systems ownership and craft.

• Portfolio Walkthrough: Candidates will be asked to "walk us through a real, working file (not just the polished case study frames)" and present "a design system you actually built and governed." This will likely involve a deep dive into technical decisions and governance.

• Technical & Craft Discussion: Expect discussions on your approach to design tokens, component architecture, motion language, and pixel-level craft. This may involve whiteboard sessions or design exercises.

• Systems-Level Project Review: Presentation of a "deeply complex, systems level project" to assess your strategic thinking and ability to handle intricate problems.

• Cultural Fit & Collaboration: Interviews with design, engineering, and product leads to assess collaboration style, ego, and alignment with Rho's values.

• Final Round: Likely involves senior leadership to discuss overall vision and strategic alignment.

Portfolio Review Tips:

• Lead with Ownership: Clearly articulate your role and ownership in building and governing the design systems presented. Use "I" statements for your direct contributions.

• Show, Don't Just Tell: Provide access to "real, working files" (e.g., Figma files, code repositories if applicable) that demonstrate your process and the tangible output.

• Demonstrate Governance: Explain your process for documentation, contribution, and enforcement of standards. How did you prevent the system from being "abused"?

• Highlight Craft: Showcase specific examples of pixel-perfect execution, thoughtful motion, and microinteractions. Be prepared to defend your design decisions with reasoning.

• Address Financial Domain: If possible, showcase experience or a strong understanding of complex financial workflows and their design implications.

• Be Concise and Focused: While detailed, ensure your presentation is focused on the most impactful aspects of your work relevant to this role.

Challenge Preparation:

• Design System Architecture: Be ready to discuss how you would architect a design system for a financial platform, including token structure, primitive components, and scalability.

• Governance Model: Prepare to outline a practical governance model for a growing engineering and product team.

• Craft Standards: Think about how you would define and maintain high craft standards for typography, spacing, motion, and visual consistency across a complex application.

• Ambiguity Navigation: Prepare examples of how you handle ambiguous requirements and drive clarity in complex problem spaces.

📝 Enhancement Note: The application process is heavily focused on demonstrating tangible, hands-on experience with design systems. The requirement for "real, working files" and "systems you actually built and governed" is a significant filter.

🛠 Tools & Technology Stack

Primary Tools:

• Figma: The core design tool for UI design, prototyping, and likely for component specification and documentation.

• Design System Management Tools: While not explicitly named, tools for documentation, version control, and potentially code generation (e.g., Storybook, Zeroheight, specific internal tools) are implied.

• AI Tools: Explicitly mentioned as being used "natively," so expect AI-powered design assistants, research tools, or documentation aids.

Analytics & Reporting:

• Expect to use product analytics tools to understand how users interact with components and the overall product, informing design system iterations.

• Tools for tracking design system adoption and usage across teams might be utilized. CRM & Automation:

• Not directly applicable to the core design system role, but understanding how the design system integrates with the broader product development lifecycle, which involves CRMs and automation, is beneficial.

📝 Enhancement Note: The emphasis is on Figma as the primary design tool, but the role requires an understanding of how design systems are translated into code. The mention of "lint and CI" suggests familiarity with development workflows and potential integration points with engineering tools.

👥 Team Culture & Values

Operations Values:

• Restraint over Decoration: Prioritizing functional clarity and user-centric design over gratuitous aesthetics.

• Confidence over Noise: Creating interfaces that are clear, direct, and avoid overwhelming the user.

• Craftsmanship: A deep commitment to detail, quality, and elegance in all aspects of design, from pixels to motion.

• Ownership: Taking full responsibility for one's work, from initial concept through to shipping and iteration.

• Collaboration: Working as genuine equals with engineering and product to achieve shared goals.

• Speed and Quality: Balancing a fast-paced development environment with a high bar for design execution.

Collaboration Style:

• Peer-to-Peer: Collaborating with engineers and PMs as "genuine equals."

• Cross-Functional: Working closely with frontend engineers on implementing the design system.

• Artifact-First Communication: Relying on tangible design artifacts and working files for clear communication.

• In-Office Synergy: Valuing face-to-face interaction for complex problem-solving and system design.

📝 Enhancement Note: The company values a blend of high standards and high pace, emphasizing functional clarity and a deep commitment to craft. Collaboration is seen as a partnership between design, engineering, and product.

⚡ Challenges & Growth Opportunities

Challenges:

• Scalability of Design Systems: Ensuring the design system can effectively support rapid product expansion and a growing engineering team.

• Balancing Craft and Speed: Maintaining a high bar for design quality while operating in a fast-paced startup environment.

• Technical Depth Integration: Bridging the gap between design intent and actual code implementation, especially in a complex financial domain.

• Governance Adoption: Implementing and enforcing a governance model that is embraced by a large team, not resisted.

• Financial Domain Complexity: Designing for intricate financial workflows, multi-role permissions, and high-stakes transactions.

Learning & Development Opportunities:

• Deep Dive into FinTech: Gaining extensive experience in the nuances of financial product design and regulation.

• Design Engineering Mastery: Further developing skills in designing directly within or alongside code environments.

• System Architecture Leadership: Shaping the technical foundation of a critical product layer.

• Mentorship: Providing guidance to a growing design and engineering team on best practices.

• Industry Influence: Contributing to the evolution of design systems within the FinTech space.

📝 Enhancement Note: The primary challenge lies in building and governing a sophisticated design system that enables both speed and high craft in a complex domain. Growth opportunities are centered on deep technical specialization and strategic influence.

💡 Interview Preparation

Strategy Questions:

• "How would you architect a design system for a financial operating system like Rho, considering scalability, governance, and integration with code?"

• "Describe a time you had to enforce strict design standards on a team that was moving quickly. What was your approach, and what was the outcome?"

• "Walk us through a complex financial workflow and how you would design for it using a system-first approach. What are the key primitives and states?" Company & Culture Questions:

• "What does 'Restraint over decoration' mean to you in the context of financial product design?"

• "How do you balance low ego with high standards in a collaborative environment?"

• "How do you see AI tools enhancing the design system process and your role?" Portfolio Presentation Strategy:

• Structure: Begin with your most impactful design system ownership example, followed by your pixel-level craft piece, and then your systems-level project.

• Narrative: For each piece, clearly articulate the problem, your role and decisions, the process you followed, the challenges you overcame, and the quantifiable impact or outcome.

• Technical Details: Be prepared to discuss token architecture, component states, interaction patterns, and your governance strategy in detail.

• "Real, Working File": Have a Figma file ready that you can navigate live, showcasing your organization, component structure, and design logic. Be ready to discuss specific design decisions and their rationale.

• "Built and Governed": For the design system example, explicitly detail your contribution to its creation, implementation, and ongoing governance.

📝 Enhancement Note: Interview preparation should focus on demonstrating a deep understanding of design systems, a strong technical aptitude, exceptional craft, and the ability to thrive in a fast-paced, collaborative startup environment. Being able to articulate "why" behind design decisions is crucial.

📌 Application Steps

To apply for this Staff / Principal Product Designer, Design Systems position:

• Submit your application through the provided link on Ashby.

• Portfolio Customization: Tailor your portfolio to prominently feature your experience in owning and governing design systems at scale. Ensure it includes specific examples of your architectural decisions, token strategies, and governance models.

• Resume Optimization: Highlight your 7+ years of experience, focusing on roles where you had significant responsibility for design systems. Use keywords like "design systems," "governance," "product design," "frontend architecture," "Figma," and "design tokens."

• Prepare Your Walkthrough: Practice presenting your "real, working file" and design system case studies. Be ready to discuss specific design decisions, your rationale, and the impact of your work in detail.

• Company Research: Understand Rho's mission, its modern banking platform, and its target audience (startups). Consider how your design system approach aligns with their business goals and user needs in the FinTech space.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.

---